[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] A few more problematic fonts
From: |
Hin-Tak Leung |
Subject: |
Re: [ft-devel] A few more problematic fonts |
Date: |
Sun, 24 Nov 2013 23:00:11 +0000 (GMT) |
------------------------------
On Sun, Nov 24, 2013 11:45 GMT Werner LEMBERG wrote:
>> 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?
It is obvious which is which when everything is working correctly... When it
isn't, then it takes a while to see which part(s) are broken.
>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.
It may not even be a desirable thing to do - at least it appears from some of
these issues that bitmaps are either used (without good outline data) or
ignored.
- 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,
Hin-Tak Leung <=