locales, unicode and ansi with msvcrt (bug 8022)

[Dmitry Timoshkov]

"Jason Edmeades" <us at edmeades.me.uk> wrote:

>> Apparently you need to use appropriate console output APIs directly (that
>> take into account the console input/output code page) instead of using
>> MSVCRT APIs.
>> 
> 
> Unfortunately just using the wide console function will only help the 
> output to the screen, but as my test program shows there is the same 
> discrepency when the output is to a file handle...

What your test app is doing? It probably needs a test under Windows to
see in which encoding (ANSI/OEM) a not unicode app should receive input
via a pipe.

-- 
Dmitry.