[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] Patented bytecode interpretter and fallback to autohinter
From: |
Werner LEMBERG |
Subject: |
Re: [ft-devel] Patented bytecode interpretter and fallback to autohinter |
Date: |
Thu, 25 Feb 2010 23:21:55 +0100 (CET) |
>> why do you need a `partial' if there is no possibility to find out
>> which ranges are hinter or unhinted?
>
> What I want to use this info for is to be able to write
> configurations that say "if the font doesn't have bytecode hinting,
> then enable the autohinter". Now one should ask where should the
> line for "has / doesn't has" be drawn... I don't know. What I know
> is that:
>
> - A font having hints for all but a few glyphs should be
> considered yes.
>
> - A font having hints for just a few should be considered no.
>
> No idea about the in-between. That's what I called "maybe". But
> it's not a very flexible API. Another way would be to get the
> number of hinted glyphs. I'm not sure.
Sounds sensible. The arguments could be `start' and `end' of a range
(or (-1,-1) to indicate that we want the hinted glyphs of the whole
font, regardless of the CMap); the return value could the number of
hinted glyphs.
Werner