I couldn't fully trace this, nor understand all. If you are going to have some trial, 4 lines of dirty patch to ProjectDocs::Parse.pm seems to me work.

1. decode $self->{buffer} to character. Add 2 lines 

use Encode qw/decode/;
$self->{buffer}=decode('UTF-8', $self->{buffer});

[download]
just after the line 
  
$self->{buffer} = join "\n", qq[<div class="pod">], $self->{buffer}, "
+</div>";

[download]
,which is in the "end_pos" sub.

2. encode $self->{buffer} back. Add 2 lines 
use Encode(qw/encode/);
$self->{buffer}=encode('UTF-8', $self->{buffer});

[download]
just after 
$self->SUPER::parse_from_file(@_);

[download]
,which is in "parse_from_file" sub.

before SUPER::parse_from_file, it has no troble. after SUPER::parse_from_file, it is troubled. "end_pos" is callback from Pod::Parser.

In reply to Re: utf8 problems with Pod-ProjectDocs by remiah
in thread utf8 problems with Pod-ProjectDocs by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.