Unicode Functions Supported by Windows 95

 Last reviewed: January 15, 1998
Article ID: Q125671
4.00 WINDOWS kbprg

The information in this article applies to:

  • Microsoft Win32 Software Development Kit (SDK)

Unlike Windows NT, Windows 95 does not implement the Unicode (or wide character) version of most Win32 functions that take string parameters. With some exceptions, these functions are implemented as stubs that simply return success without modifying any arguments.

In general, Windows 95 implements the ANSI version of these functions. See the Win32 API documentation for information on particular functions and differences between the various Win32 platforms.

One major exception to this rule is OLE. All native 32-bit OLE APIs and interface methods use Unicode exclusively. For more information on this, please see the OLE documentation.

Excluding OLE, Windows 95 supports the wide character version of the following functions: 

   EnumResourceLanguages
   EnumResourceNames
   EnumResourceTypes
   ExtTextOut
   FindResource
   FindResourceEx
   GetCharWidth
   GetCommandLine
   GetTextExtentExPoint
   GetTextExtentPoint32
   GetTextExtentPoint
   lstrlen
   MessageBoxEx
   MessageBox
   TextOut
In addition, Windows 95 implements the following two functions for converting strings to or from Unicode: 

   MultiByteToWideChar
   WideCharToMultiByte

Additional reference words: 4.00
KBCategory: kbprg
KBSubcategory: KBIntlDev
Keywords : KBIntlDev kbprg
Version : 4.00
Platform : WINDOWS

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.