GetTextExtentPoint32W May Fail with Unicode Characters > 0x

• Microsoft Windows NT Workstation version 4.0
• Microsoft Windows NT Server version 4.0

SYMPTOMS

In certain instances under Windows NT 4.0, application code that uses the GetExtentPoint32W API and the lpszText parameter to point to text containing certain Unicode characters may fail. Using GetLastError() to find the problem in the code will have no return code. The same application running under Windows NT 3.51 does not have this problem.

MORE INFORMATION

Using a debugging tool to single-step through a failing application may reveal that the function fails if the data at the lpszText pointer contains extended characters. These characters include umlauts, grave accents, and so on, or any Unicode characters greater than hex value 0x100. This problem is difficult to reproduce because the application code may work fine if cStrTest is on the stack.

RESOLUTION

To resolve this problem, obtain the hotfix below, or wait for the next service pack.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.