Thanks.
So, on a default US English system, the console uses CP 437 and windows apps
use CP 1252.
I've been looking in the MSDN library and can't find a table that lists the
code page number for each platform language. Any pointers?
I'm particularly interested in testing our legacy non-unicode MFC app for
support of multi byte code pages and I'm not sure where to start. I figured
that I need to get a good understnading of how code pages are "used" by
non-unicode apps.
The biggest issue, I think, is in dealing with file names, which are always
encoded in Unicode.
Richard
> "Richard Otter" <sorry@yahoo.com> wrote...
>
[quoted text clipped - 13 lines]
>
> Well, GetACP() and GetOEMCP() should be able to help you here.
"Richard Otter" <sorry@yahoo.com> wrote...
> So, on a default US English system, the console uses CP 437 and
> windows apps use CP 1252.
Yes. Much of Western Europe uses 1252 and 850 (rather than 437).
> I've been looking in the MSDN library and can't find a table that lists the
> code page number for each platform language. Any pointers?
Sites like http://www.microsoft.com/globaldev/nlsweb list them out....
> I'm particularly interested in testing our legacy non-unicode MFC app for
> support of multi byte code pages and I'm not sure where to start. I figured
[quoted text clipped - 3 lines]
> The biggest issue, I think, is in dealing with file names, which are always
> encoded in Unicode.
Yes, there are many cases where you cannot represent every item in one that
is in the other, but the roundtripping works okay because the display issue
of the "wrong glyph" is just a display issue.

Signature
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
Windows International Division
This posting is provided "AS IS" with
no warranties, and confers no rights.