Depending on your target operating systems and markets, you have several internationalization strategies:
Your application uses Unicode and therefore runs on WindowsВ 2000 and WindowsВ NT, but not on WindowsВ 95 or WindowsВ 98.
You use Unicode-specific functionality and all characters are 16 bits wide (although you can use ANSI characters in some parts of your program for special purposes). The C run-time library provides functions, macros, and data types for Unicode-only programming. MFC is fully Unicode-enabled.
Your application uses MBCS and can be run on any Win32 platform.
You use MBCS-specific functionality. Strings can contain single-byte characters, double-byte characters, or both. The C run-time library provides functions, macros, and data types for MBCS-only programming. MFC is fully MBCS-enabled.
The source code for your application is written for complete portability вЂ” by recompiling with the symbol _UNICODE or the symbol _MBCS defined, you can produce versions that use either. For more information, see Generic-Text Mappings in Tchar.h.
Your application uses a wrapper library for missing Unicode functions on WindowsВ 95, WindowsВ 98, and WindowsВ ME like the one described in . Wrapper libraries are also available commercially.
You use fully portable C run-time functions, macros, and data types. MFC's flexibility supports any of these strategies.
The remainder of these topics focus on writing completely portable code that you can build as Unicode or as MBCS.