BUG: GetGlyphOutline returns corrupt glyphs with GGO_BITMAP (159427)
The information in this article applies to:
- Microsoft Platform Software Development Kit (SDK) 1.0, when used with:
This article was previously published under Q159427
4.00
WINDOWS NT
kbgraphic kbbuglist
SYMPTOMS
The function GetGlyphOutline() occasionally returns corrupted bitmaps of TrueType glyphs when called with the GGO_BITMAP format. This problem occurs only on Windows NT 4.0. The corrupted bitmaps usually resemble a "Venetian" blind where every other scan line appears to have been inserted from some other source.
There is no practical workaround for this bug involving the use of
GetGlyphOutline. The problem can be avoided by using TextOut on a memory DC
and using the BitBlt function to copy a bitmap similar to the one to be returned by GetGlyphOutline.
Additionally, the problem can be avoided by specifying a rotation matrix in
the call to GetGlyphOutline that would result in a rotation of 1 degree or more. This approach, however, suffers from the loss of hinting to the resulting bitmap glyph.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article.
MORE INFORMATIONSteps to reproduce the problem
The problem can be reproduced by asking for glyph bitmaps for a series of
characters over a range of Font heights. A specific case can be reproduced
with a font height of -104 device units for the Wingdings font and the
character code equivalent of the letter "i" in the ANSI character set.
| Modification Type: | Minor | Last Reviewed: | 7/11/2005 |
|---|
| Keywords: | kbbug kbpending KB159427 kbAudDeveloper |
|---|
|