The Windows-native localization model differs from that of VisualAge C++ in two ways:
1. Windows and VisualAge C++ Locales
The Windows-native localization model (as supported by
the Win32 APIs) is not the same as the POSIX model supported by
VisualAge C++. For this reason, changing the country via the
Control Panel will not alter the cultural behavior of your
VisualAge C++ application. Similarly, changing the LC_ environment
variables will have no effect on
an application calling native-Windows APIs.
Further, confusion may arise because both the Windows operating system and VisualAge C++ files are known as locales but there is no similarity between the two.
2. Windows ANSI and Windows OEM Code
Pages
The Windows operating systems support two classes of code
page:
Because locales are bound to a specific code page, there must be a separate locale for each country-language-codepage combination. If you want the locale that is bound to the ANSI code page, you must specify the codeset-qualified name that identifies the code page. For example, the following specifies the English, Great Britain, code page 1252:
en_GB.IBM-1252
For locales bound to OEM code pages, you should specify only the language-country name. For example, the following identifies French Canada, using the currently active code page:
fr_CA
![]()
Internationalization
Localization and
Locales
![]()
Make Your
Program International
