Re: How to convert non-ASCII output from qx

Try posting code. The console is traditionally legacy 1 char per byte code page. Type "chcp" at your console to see what it is. Programs normally print legacy CP data to console, not utf8. It would look like gibberish if it was utf8 printed to console. Also you can run into truncation/substitution problems, where your non-latin letters being real 1 char 1 byte "?"s. Technically a program can print binary to the console, often done by unix-ish tools. You could also try and mark the STDIN/STDOUT as utf8, i'm not sure how successful that is on Perl Windows (worst case, console spits out legacy cp, perl coverts all the invalid utf8 character sequences to a filler characters).

Comment on Re: How to convert non-ASCII output from qx

Replies are listed 'Best First'.
Re^2: How to convert non-ASCII output from qx by freonpsandoz (Beadle) on Jun 19, 2012 at 07:32 UTC
By "at your console" I assume you mean "in a cmd.exe window." Right after a reboot, chcp reports the active console code page as 437. Later on, some undetermined process changes it. After that, chcp reports the code page as 1252. My script does set STDOUT to UTF8 with binmode and the output, redirected to a file, is correct. I tried setting STDIN to UTF8, but this seems to have no effect on the behavior of qx.	[reply]

Replies are listed 'Best First'.

Re^2: How to convert non-ASCII output from qx
by freonpsandoz (Beadle) on Jun 19, 2012 at 07:32 UTC

By "at your console" I assume you mean "in a cmd.exe window." Right after a reboot, chcp reports the active console code page as 437. Later on, some undetermined process changes it. After that, chcp reports the code page as 1252. My script does set STDOUT to UTF8 with binmode and the output, redirected to a file, is correct. I tried setting STDIN to UTF8, but this seems to have no effect on the behavior of qx.

[reply]