For one, you'd need to decode the UTF-8 encoded @ARGV input into Perl's internal unicode representation. Similarly, encode any unicode output back to UTF-8 for the terminal.

... use Encode; binmode STDOUT, ":utf8"; # for output for my $old_name (map decode('UTF-8', $_), @ARGV) { ...

Instead of explicitly decoding @ARGV input, you could also use -CA (see perlrun). The problem with this option is, though, that you can't put it in the shebang line (error: "Too late for "-CA" option at..."), but only on the command line like perl -CA yourscript.pl ...

Update: actually, #!/usr/bin/perl -CA  finally does seem to work, too, as of Perl 5.10.1.


In reply to Re: Trying to understand behavior of split and perl in general with UTF-8 by almut
in thread Trying to understand behavior of split and perl in general with UTF-8 by hdv.jadev

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.