Re: Fix xcopy so output is either unicode (console) or oem (file)
"Kirill K. Smirnov" <lich(a)math.spbu.ru> wrote:
The written strings in 866 and 1251 code pages are only readable when output console code page matches the string encoding.
This is in wine. In windows only cp866 is readable regardless of ConsoleOutputCP.
As I said I tested under Windows (XP) only, and SetConsoleOutputCP does change the behaviour of WriteConsoleA for me. If it wouldn't I'd call it a bug. I tested under Windows 2003 and SetConsoleOutputCP does NOT change the behaviour of WriteConsoleA for me. Does Windows play us a trick?
"Kirill K. Smirnov" <lich(a)math.spbu.ru> wrote:
The written strings in 866 and 1251 code pages are only readable when output console code page matches the string encoding.
This is in wine. In windows only cp866 is readable regardless of ConsoleOutputCP.
As I said I tested under Windows (XP) only, and SetConsoleOutputCP does change the behaviour of WriteConsoleA for me. If it wouldn't I'd call it a bug.
I tested under Windows 2003 and SetConsoleOutputCP does NOT change the behaviour of WriteConsoleA for me. Does Windows play us a trick? I've re-tested with Windows XP - the result is not changed. Mystery?
-- Kirill
"Kirill K. Smirnov" <lich(a)math.spbu.ru> wrote:
The written strings in 866 and 1251 code pages are only readable when output console code page matches the string encoding.
This is in wine. In windows only cp866 is readable regardless of ConsoleOutputCP.
As I said I tested under Windows (XP) only, and SetConsoleOutputCP does change the behaviour of WriteConsoleA for me. If it wouldn't I'd call it a bug. I tested under Windows 2003 and SetConsoleOutputCP does NOT change the behaviour of WriteConsoleA for me. Does Windows play us a trick?
No the difference in observed behaviour was caused by the fact that I ran the test under FAR, once I run it under cmd.exe I see what you do. -- Dmitry.
participants (2)
-
Dmitry Timoshkov -
Kirill K. Smirnov