You've got another problem. Your browser incorrectly passed the ę character as %C4%88 that is, as a string which happens to be UTF-8 but should have passed it as %u0119. You've got to *guess* during your URL parsing if someone has started passing you a byte-string which happens to look like a UTF-8 string and if so, reinterpret it as UTF-8 instead. If you're being fully careful, you should also be using the Content-Type of the HTTP header your server sends, the client sends, and the HTML content encoding you sent when generating your page.

Here's what I use.

sub uri_unescape {
    my $to_decode = shift;

    return if ! defined $to_decode;
    $to_decode =~ s/\+/ /g;

    # A "good enough" check to see if the browser encoded high bit
    # characters as UTF-8 by looking for something that resembles a
    # URL-encoded utf8 octet series
    #
    # utf8 encoding starts with 11xxxxxx in the first byte and
    # 10xxxxxx in the subsequent bytes
    # http://en.wikipedia.org/wiki/UTF-8#Description
    my $is_byte_encoded_utf8 = $to_decode =~ /%[c-fC-F][[:xdigit:]]%[8
+9abAB][[:xdigit:]]/;

    $to_decode =~ s/%([[:xdigit:]]{2})/chr hex "0x$1"/eg;

    # Decode the "UTF-8" if it looked like it was such. If I enter
    # this block, the string may now be UTF-8 encoded as a perl
    # string.
    if ($is_byte_encoded_utf8) {
        $to_decode = Encode::decode( 'utf8', $to_decode );
    }

    # Promote %uXXXX escapes up to characters. This is after the
    # Encode call so I don't inadvertently cause a promotion to utf8
    # and then ask Encode to do another promotion.
    $to_decode =~ s/%u([[:xdigit:]]{4})/chr hex "0x$1"/eg;

    return $to_decode;
}

[download]

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

In reply to Re^3: "use encoding" behaviour change under Perl 5.10? by diotalevi
in thread "use encoding" behaviour change under Perl 5.10? by gnosek

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.