Thanks for both answeres, yes the problem is vague, and vague to describe...
We have as string and have the internal utf8 flag switched to on:
# my example may be any string from a database /user input etc.
my $example = "just a string that i nééd to be utf8 encoded, but can't
+ see it in the chars, so guess::encode won't work";
use open ':utf8';
use open ':std';
my $cgi = new CGI;
-type => 'text/html',
-expires => '-1d',
-cookie => [$cookie],
-charset => 'UTF-8',
Now the first time it's called using mod::perl regestry it prints:
just a string that i nééd to be utf8 encoded, but can't see it in the
+chars, so guess::encode won't work
but the second time:
just a string that i nÃ©Ã©d to be utf8 encoded, but can't see it in th
+e chars, so guess::encode won't work
This is weird, and i have no controll over how mod perl internally stores it's values.
"We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise." - Larry Wall.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.