Re: [Mingw-users] MSYS code page

[Renato S. <br....@gm...>]

Erwin, the reason why I haven't switched to ANSI in cmd.exe is because
there are Windows programs themselves that work only with the OEM code
page, at least in Windows 32-bits. For example, ipconfig and even cmd.exe
itself will send CP850 bytes to Windows console even though active code
page is 1252. So I think one reason why they didn't migrate to ANSI was
because of programs shipped with Windows itself.

One problem of multiple encodings is mixing them together in your terminal.
It's annoying having to choose one encoding for the terminal when in
reality you need to deal with several from different programs. For example
I use MinTTY with ANSI/Latin1 but ipconfig outputs CP850. The solution I'm
using here is making each of these CP850 programs into symlinks to a bash
script that is going to use iconv to convert from that to Latin1. It's been
working quite well.