Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread Jungshik Shin
On Mon, 22 Dec 2003, Jarkko Hietaniemi wrote: > (AFAIK) W2K and later _are able_ to use UTF-16LE encoded Unicode for > filenames, > but because of backward compatibility reasons using 8-bit codepages is > much > more likely. No. _Both_ NTFS (only supported by Win 2k/XP) and VFAT (supported by W

Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread Jungshik Shin
On Mon, 22 Dec 2003, Ed Batutis wrote: > "Jarkko Hietaniemi" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > You do know that ... > Yes. > > If wctomb or mbtowc are to be used, then Perl's Unicode must be converted > either to the locale's wide char or to its multibyte. This is

Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread SADAHIRO Tomoyuki
On Tue, 23 Dec 2003 09:47:32 +0900 SADAHIRO Tomoyuki <[EMAIL PROTECTED]> wrote: > I had talked on this "problem" (well, I don't know whether Perl > supports multibyte file/path names or not.) in a Japanese Perlers' > mail list. > > http://www.freeml.com/message/[EMAIL PROTECTED]/0004467 (in Japa

Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread Ed Batutis
"Jarkko Hietaniemi" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > You do know that ... Yes. If wctomb or mbtowc are to be used, then Perl's Unicode must be converted either to the locale's wide char or to its multibyte. This isn't trivial, but Mozilla solved this same problem. It

Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread SADAHIRO Tomoyuki
On Mon, 22 Dec 2003 14:31:15 -0500 "Ed Batutis" <[EMAIL PROTECTED]> wrote: > $newdir = "kanji_here_\x89\x5C"; > mkdir $newdir; > > The above works the way I'd expect, although > > print (-d $newdir ? 'yes' : 'no'); > > prints 'no' - oops a character handling bug! The second byte of the kanji i

Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread Jarkko Hietaniemi
*Which* multibyte? This is the key point. The answer on a Unix-like system is "the one you get when you do wctomb()". And that routine knows what to do by virtue of You do know that wctomb() has nothing to do with Perl's Unicode implementation? And that wctomb() is not defined to be Unicode? An

Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread Ed Batutis
"Jarkko Hietaniemi" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > *Which* multibyte? This is the key point. The answer on a Unix-like system is "the one you get when you do wctomb()". And that routine knows what to do by virtue of setlocale() (or the default if setlocale is never

Re: perlunicode comment - when Unicode does not happen

2003-12-22 Thread Jarkko Hietaniemi
In 'perlunicode' under 'when Unicode does not happen' there is the statement (regarding Unicode functionality and the file system-related functions and operators - BTW the author missed '-X' ): Oops. "One reason why Perl does not attempt to resolve the role of Unicode in this cases is that the

perlunicode comment - when Unicode does not happen

2003-12-22 Thread Ed Batutis
In 'perlunicode' under 'when Unicode does not happen' there is the statement (regarding Unicode functionality and the file system-related functions and operators - BTW the author missed '-X' ): "One reason why Perl does not attempt to resolve the role of Unicode in this cases is that the answers a