General MBCS Programming Advice
The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.
Use the following tips:
For flexibility, use run-time macros such as
_tcschrand_tcscpywhen possible. For more information, see Generic-Text Mappings in Tchar.h.Use the C run-time
_getmbcpfunction to get information about the current code page.Do not reuse string resources. Depending on the target language, a given string might have a different meaning when translated. For example, "File" on the application's main menu might translate differently from the string "File" in a dialog box. If you need to use more than one string with the same name, use different string IDs for each.
You might want to find out whether your application is running on an MBCS-enabled operating system. To do so, set a flag at program startup; do not rely on API calls.
When designing dialog boxes, allow approximately 30% extra space at the end of static text controls for MBCS translation.
Be careful when selecting fonts for your application, because some fonts are not available on all systems. For example, the Japanese version of Windows 2000 does not support the Helvetica font.
When selecting the font for dialog boxes, use MS Shell Dlg instead of MS Sans Serif or Helvetica. MS Shell Dlg is replaced with the correct font by the system before creating the dialog box. Using MS Shell Dlg ensures that any changes in the operating system to deal with this font will automatically be available. (MFC replaces MS Shell Dlg with the DEFAULT_GUI_FONT or the System font on Windows 95, Windows 98, and Windows NT 4 because those systems do not handle MS Shell Dlg correctly.)
When designing your application, decide which strings can be localized. If in doubt, assume that any given string will be localized. As such, do not mix strings that can be localized with those that cannot.
See Also
MBCS Programming Tips
Incrementing and Decrementing Pointers