[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] A few more problematic fonts
From: |
Werner LEMBERG |
Subject: |
Re: [ft-devel] A few more problematic fonts |
Date: |
Sun, 24 Nov 2013 12:45:07 +0100 (CET) |
> Perhaps that was a dumb question. Somehow I was expecting the
> antialiased effect to be applied to the everything uniformly
> i. e. to the bitmaps also... This probably really means toggling
> bitmaps probably should automatically toggle aa in the opposite
> direction also?
No. IMHO, a font which provides embedded bitmaps should ensure that
the `gasp' table has the correct settings, this is, using B/W
rendering for ppem values that have embedded B/W bitmaps. The two
Hong Kong fonts don't have a `gasp' table at all, which I consider a
bug.
> Is it difficult to make the bitmap toggle cycle through
> bitmap+outlinefallback, bitmaponly, outlineonly?
Not really, but I don't see the benefit. It's quite obvious which
glyphs are represented by a bitmap, isn't it?
FreeType currently doesn't honour `gasp' table values automatically,
delegating it to the application. It has been suggested from various
people to change that, but I haven't had found time yet to think about
possibilities how to implement that.
Werner
- Re: [ft-devel] A few more problematic fonts, (continued)
- Re: [ft-devel] A few more problematic fonts, Hin-Tak Leung, 2013/11/21
- Re: [ft-devel] A few more problematic fonts, Hin-Tak Leung, 2013/11/24
- Re: [ft-devel] A few more problematic fonts, Hin-Tak Leung, 2013/11/24
- Re: [ft-devel] A few more problematic fonts,
Werner LEMBERG <=
- Re: [ft-devel] A few more problematic fonts, Hin-Tak Leung, 2013/11/24