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] |
...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] |