Visual C++ Vers 2.0 README.WRI, Part 6 Internationalization

Last reviewed: March 19, 1998
Article ID: Q120922
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Edition, version 2.0 on the following platform: x86

SUMMARY

The following is based on the Visual C++ version 2.0 README.WRI file:

SDK Requirements for National Language Support

Visual C++ version 2.0 correctly handles all multibyte-character set (MBCS) issues, including use of Input Method Editors (IME). However, to enable MBCS behavior for the development environment and build tools, you must develop on the appropriate MBCS platform, namely, with Windows NT "Daytona" for Japan, Korea, Taiwan or the People's Republic of China. The Windows NT "Daytona" SDK and the Open Database Connectivity (ODBC) SDK included with Visual C++ version 2.0 do not include MBCS-enabled libraries or header files. To use the MBCS-enabled versions of these Windows APIs, you must use the Windows NT SDK and ODBC libraries and header files for the appropriate country/region.

Help Files With Japanese DBCS Characters

In order to build help files with Visual C++ version 2.0 that contain Japanese double-byte (DBCS) characters, you must replace the installed versions of the help file components with those found on the CD-ROM disk in the \MSVC20\BIN\HELP.JP directory. Replace the following files:

HC30.EXE HC31.EXE HC31.ERR HC.BAT

Note that these help compilers, while DBCS-enabled, do not work on .RTF files created with Microsoft Word version 6.0.


Additional reference words: 2.00
KBCategory: kbreadme
KBSubcategory: VCGenIss
Keywords : VCGenIss kbreadme
Version : winnt:2.0
Platform : winnt


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.