FIX: Bad Characters in 32-bit App on Win32s on Russian Windows

Last reviewed: January 15, 1998
Article ID: Q126865

The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK) for Windows NT version 3.5
  • Microsoft Win32s versions 1.2, 1.25, 1.3

SYMPTOMS

When compiling, linking, and running a Russian application which was built using Microsoft Visual C++ version 2 under on Windows NT version 3.5 the application runs correctly. If this application is run on Russian Windows version 3.1 with the Win32s libraries version 1.2 or 1.25 installed, some parts of the user interface appear as meaningless set of characters.

CAUSE

The strings in the resources are stored in UNICODE format. Yet you must pass all strings to Windows 3.1 in ANSI format. The drawing of the resources is done by Windows 3.1. Win32s simply reads the 32-bit resources, converts them to the 16-bit format equivalent, and passes the resources to Windows 3.1. One stage of the conversion is to convert the UNICODE strings into ANSI strings. This conversion for the Russian language is broken.

STATUS

Microsoft has confirmed this to be a problem in the product(s) listed at the beginning of this article. This bug was fixed in Win32s version 1.3.


Additional query words: Cyrillic Russia 2.00 garbage corruption
Keywords : W32s KBIntlDev
Version : 3.5 | 1.2 1.25 1.3
Platform : NT WINDOWS
Solution Type : kbfix


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: January 15, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.