Re: Win32 encoding conversion mystery

The Windows API has two versions of each function that requires text strings: An "(A)NSI" version and a "(W)ide" version.

The ANSI version expects strings encoded using the Active Code Page. The ACP can be obtained from Win32::ACP(), and am encoding name suitable for Encode::encode and Encode::decode can be obtained from "cp".Win32::ACP(). For Western machines, these are 1252 and cp1252 respectively. (Not latin1 as you said.) This is what Perl's native functions use.

To manipulate any file, you need to use the Wide version. These are made accessible by Win32::Unicode and other modules from the same distro.

Comment on Re: Win32 encoding conversion mystery Select or Download Code

Replies are listed 'Best First'.
Re^2: Win32 encoding conversion mystery by mithaldu (Monk) on Aug 13, 2018 at 16:26 UTC
Based on your recommendation i wrote this: `use Win32::Unicode; my $wdir = Win32::Unicode::Dir->new; $wdir->open(@ARGV); my ( undef, undef, $file ) = $wdir->fetch; print join "\n", "length: " . length( $file ) . ", code points:", map +ord, split //, $file;` [download] Which gives the below result, which is identical with the weirdly "upconverted" unicode above, and without further processing useless, as it doesn't map to anything but mojibake on any codepage known to me. (And ACP gives me 1252, sorry for speaking inaccurately about that.) `d:\>perl filename_check.pl RJ209072 length: 17, code points: 226 123 226 78 233 9524 196 113 233 9568 196 191 233 8976 233 189 50` [download]	[reply] [d/l] [select]
Re^3: Win32 encoding conversion mystery by Anonymous Monk on Aug 13, 2018 at 17:23 UTC
What is it supposed to give you?	[reply]
Re^4: Win32 encoding conversion mystery by mithaldu (Monk) on Aug 13, 2018 at 17:36 UTC
I need the string as it is represented on the right side in the OP post, as those are the actual cp932 bytes, which i can convert to real UTF8. I could get these by using windows `dir`, so they are in the file system data, but dir's applications are limited. At the same time all the windows api calls seem to give me are the "mangled for visualizing" utf8 mojibake.	[reply]
Re^5: Win32 encoding conversion mystery by Anonymous Monk on Aug 14, 2018 at 00:12 UTC
Re^6: Win32 encoding conversion mystery by mithaldu (Monk) on Aug 14, 2018 at 08:38 UTC
Some notes below your chosen depth have not been shown here
Re^5: Win32 encoding conversion mystery by ikegami (Patriarch) on Aug 15, 2018 at 23:14 UTC
Re^6: Win32 encoding conversion mystery by mithaldu (Monk) on Aug 16, 2018 at 11:29 UTC


more useful options
	PerlMonks