But doesn't that error occur for both Windows and "other" systems? On both WinXP and linux, the following code generates the same 2-byte file name (interpreted according to the local codepage). 

open(my $fh, '>', chr(0x2660)) or die $!

[download]

(Too lazy to find out how to encode ö.)

So it appears that Perl passes the string's internal buffer to the system call. I don't see how that can be used to demonstrate that Perl assumes an encoding for the file name. Quite the opposite, it seems to show that Perl assumes file names are binary strings. It's up to the user to encode them.

In reply to Re^5: MD5 non ascii file name by ikegami
in thread MD5 non ascii file name by benjwlee

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.