The information in this article applies to:
SYMPTOMSOn Windows 98, the OpenGL function wglUseFontOutlines does not work with DBCS or UNICODE strings. On Windows NT, UNICODE strings work; however, DBCS strings do not. CAUSEDBCS strings are not handled by the glCallLists function, which is used to draw the display list built by wglUseFontOutlines. The reason is that a DBCS string contains characters that are one byte or two bytes each depending on the high byte. Because DBCS strings are not a consistent length, glCallLists does not parse them. RESOLUTION
On Windows NT, however, UNICODE strings can be used with wglUseFontOutlines. You can convert the desired DBCS character set to a UNICODE character set using the MultiByteToWideChar function. You can pass a character string with the DBCS characters desired to MultiByteToWideChar. Then, pass the resulting UNICODE string to wglUseFontOutlines. The listbase you pass to wglUseFontOutlines is the index of the first display list in your character set. You need to determine the numeric value of the first UNICODE character in your character set to pass to wglUseFontOutlines. You must set the display list base to the same base
using glListBase prior to calling glCallLists. Finally, you need to convert the actual string you are going to use to UNICODE as well. MORE INFORMATION
On Windows 98, you cannot use DBCS or UNICODE strings with wglUseFontOutlines and glCallLists. UNICODE is supported on Windows NT. For Windows NT, the following steps can be followed to use a DBCS string:
Additional query words:
Keywords : kbGDI kbNTOS400 kbOpenGL kbSDKPlatform kbWinOS98 |
Last Reviewed: April 21, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |