Re: GetGlyphOutline API
- From: "Mihai N." <nmihai_year_2000@xxxxxxxxx>
- Date: Wed, 10 Jan 2007 21:31:20 -0800
Having switched to UNICODE it started getting the wrong answer when....
nChar=131 (but not others which I have detected so far).
So why is this?
Is it a bug?
Because 131 is interpreted by GetGlyphOutlineA
as a character in the current system code page (ansi code page).
If ansi the system is English US, ansi cp is 1252, and 131 (decimal)
is "single low-9 quotation mark", which most likely exists in your font.
But 131 is interpreted by GetGlyphOutlineW
as a Unicode. Which is a (non-visible) control character, most likely non-
existent as a glyph in any normal font.
--
Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email
.
- Follow-Ups:
- Re: GetGlyphOutline API
- From: David Webber
- Re: GetGlyphOutline API
- References:
- GetGlyphOutline API
- From: David Webber
- GetGlyphOutline API
- Prev by Date: Re: Upgrade MFC
- Next by Date: how to split a unsigned char array in vc++;
- Previous by thread: GetGlyphOutline API
- Next by thread: Re: GetGlyphOutline API
- Index(es):
Relevant Pages
|