... if anyone thinks if it worth it (or if it isn't) please share your opinions.

Yes, I'd say it's definitely worth it. You could make a little girl a little happier... if that does mean something to you :) — Ok, seriously, if you have the time to look into this, please go ahead!

IMHO, some way to conveniently handle different filename encodings is the only missing component in Perl's otherwise excellent support for unicode and other encodings.

Personally, I would favor a generic, platform-independent solution, where you can simply use a pragma to specify what encoding the filenames are in (in a particular environment). Of course, one would somehow have to account for the idiosyncrasies of the individual platforms. For example, on Windows it would probably make sense to take advantage of the magic that the wide-char conversion functions do offer when fed with the right parameters. Apart from that, I think less magic is more, i.e. no auto-detection of encodings and stuff like that...

Actually, I've been meaning to come up with a patch myself, but I have to admit I haven't got around to it yet (and the temporary workaround based on USING_WIDE in fact works quite well for what I was primarily in need of...)

In reply to Re^2: unicode version of readdir by almut
in thread unicode version of readdir by dk

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.