One problem, even with Win32, is that you can have multiple filesystems on a single system, even within a single tree. Not every filesystem handles filenames the same way. Any solution for Perl would be incomplete without the possibility to override the encoding decision per path.

I'm hoping for a solution that is sufficiently abstracted that all platforms can use it. Win32's implementation would probably be a bit easier than one for, say, Linux, but even if you have to set things explicitly per path, it's better than what we have now. The following is copied from a post to p5p a while ago.

I tend to agree, however pragmas tend to be global, program- or packagewise, and what suits best here is individual, perl-call flag.

Global is a problem in most cases, but I feel it would be perfect here, simply because the filesystem is equally global. In fact, it's even longer lived than your Perl program :)

Better yet, global variables can be localized to dynamic scope. This is good, because when you set the encoding for /foo, it should work for encoding-unaware modules too.

Maybe a hash would be nice: 

    ${^FS_ENCODING}{foo} = 'A';
    ${^FS_ENCODING}{foo}{bar} = 'B';
    ${^FS_ENCODING}{foo}{bar}{baz}{quux} = 'auto';


    open my $fh, ">", "/foo/bar/baz/quux/blah/hello.txt";

[download]
Which then actually does: 
    open my $fh, ">", join("/",
        ""
        encode(detect_encoding("/"), "foo"),
        encode("A", "bar"),
        encode("B", "baz"),
        encode("B", "quux"),
        encode(detect_encoding("/foo/bar/baz/quux"), "blah"),
        encode(detect_encoding("/foo/bar/baz/quux/blah"), "hello.txt")
+,
    );

[download]

Juerd # { site => 'juerd.nl', do_not_use => 'spamtrap', perl6_server => 'feather' }

In reply to Re^5: Writing UTF8 Filename (Win32) by Juerd
in thread Writing UTF8 Filename by amiribarksdale

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.