Subject: commit: Win font problem
From: Matti Picus (matti@picus.org)
Date: Sun Oct 14 2001 - 15:35:55 CDT
The problem is that we use EnumFontFamilies to step through the fonts. I
quote the MSDN info: "EnumFontFamilies randomly selects and enumerates one
font of each available type family." But then we filter the font families
by character set. If the function chooses to return a font pointer that is
non-ansi, we reject it.
A quick fix is to not filter the fonts at all. A better fix is to use
EnumFontFamiliesEx which allows specification of character sets up front.
Unfortunately, here are the system requirements:
Windows NT: Requires version 4.0 or later.
Windows: Requires Windows 95 or later.
Windows CE: Unsupported.
Is this acceptable to all?
Matti
At 05:21 PM 14/10/2001 +0100, you wrote:
>Hi Matti,
>
>there is an outstanding problem with the fonts listed in the AW
>controls (on Windows). For some reason not all fonts available on
>the system are listed. In my case I do not get the Hebrew "David"
>font. Would you have time to look into this? I have been nagging
>about this for a while, as it is a serious problem for Hebrew users
>(it seems to affect common Hebrew fonts), but without a Win
>compiler I cannot sort it out myself.
>
>(I suspect that AW sets some criteria for what fonts it wants from
>the system and these are too strict or something.)
>
>Tomas
This archive was generated by hypermail 2b25 : Sun Oct 14 2001 - 15:37:17 CDT