Re^4: dos path accents

Using short file names won't work on Windows NTFS file systems for which support for 8.3 file names is disabled. For performance reasons, the file servers where I work do not support 8.3 file names. See How to Disable the 8.3 Name Creation on NTFS Partitions.

There are also times when one needs in one's Perl script the true file name with all its halfwidth katakana and right-to-left Hebrew in it. This is often my situation.

I understand the reason why Perl's support of Unicode file names on Windows is the way it is — which is to say, lame. But I sure wish, in the interest of simple things being easy, it were not the way it is. Even in those cases, like mine, where portability isn't a factor, the often-suggested workarounds using Win32API* modules are less than ideal. And in an ever more plural world, it makes Perl seem not very Modern that it can't speak Chinese file names as easily as it can speak English ones.

Comment on Re^4: dos path accents

Replies are listed 'Best First'.
Re^5: dos path accents by Anonymous Monk on Oct 23, 2010 at 06:43 UTC
Like one of the links I posted says, use Win32::Unicode	[reply]
Re^6: dos path accents by Jim (Curate) on Oct 24, 2010 at 04:40 UTC
Like one of the links I posted says, use Win32::Unicode I addressed this already when I wrote: Even in those cases, like mine, where portability isn't a factor, the often-suggested workarounds using Win32API* modules are less than ideal. As its perldoc page says, Win32::Unicode is a "perl [sic] unicode-friendly [sic] wrapper for win32api [sic]" (i.e., a Perl Unicode-friendly wrapper for Win32API; specifically, Win32API::File). For me, one problem with Win32::Unicode is that I cannot easily install it on the systems at work where I need to use it. These systems are running ActivePerl 5.8.8 and there's no Win32-Unicode PPD file available for this older version of Perl in the default ActiveState repository. Is this an insurmountable impediment? Problem not, but it makes trying to use the module "less than ideal" for me. It's many more than a few mouse clicks away. Another problem with Win32::Unicode is its documentation: very scant and — let's be frank — in unreadable English. Ouch!	[reply]
Re^7: dos path accents by Anonymous Monk on Oct 24, 2010 at 08:10 UTC
...For me, one problem with Win32::Unicode is that I cannot easily install it on the systems at work where I need to use it. These systems are running ActivePerl 5.8.8 and there's no Win32-Unicode PPD file available for this older version of Perl in the default ActiveState repository.Is this an insurmountable impediment? Problem not, but it makes trying to use the module "less than ideal" for me. It's many more than a few mouse clicks away. I hear you, if only life was ideal, but its only a bunch of extra clicks once. If you want it, its there for the taking. If you're not satisfied with your vendor, work with your vendor, get another or become your own. Another problem with Win32::Unicode is its documentation: very scant and — let's be frank — in unreadable English. Ouch! Which parts need improvement? AnnoCPAN? ;D To me, the English looks like machine translation, but I can follow it.	[reply]