Perl operators that deal with paths suffer from The Unicode Bug. The path actually used is provided by the following sub:

sub path_actually_used {
   if (is_utf8($_[0]) {
      my $s = $_[0];
      utf8::encode($s);
      return $s;
   } else {
      return $_[0];
   }
}
[download]

That means that if you have encoded bytes in an upgraded string, Perl will get it wrong.

my $s = chr(9734);
mkdir($s);           # ok
utf8::encode($s);
mkdir($s);           # ok
utf8::upgrade($s);
mkdir($s);           # not ok
[download]

It's virtually impossible to get into that situation without a bug in your code because the encoding functions always return a downgraded string.

You've already identified the solution:

• If the path is a string of encoded text (i.e. UTF-8), passing it through utf8::downgrade($s) will ensure it's used correctly.
• If the path is a string of decoded text (i.e. Unicode Code Points), encoding it (e.g. using utf8::encode($s)) will ensure it's used correctly.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.