I guess the ideal thing to do is to see the number of hinted glyphs
for various fonts to get some idea about it.
It's very probable that a font designer would add hinting for glyphs
that only need them. So maybe just 10% of glyphs should be considered
a 'yes.' Not sure of course.
Mostafa
On
On 02/24/2010 06:19 PM, Werner LEMBERG wrote:
Not really. A yes/partial/no answer should be enough.
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
On 02/25/2010 05:21 PM, Werner LEMBERG wrote:
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
On 02/23/2010 08:26 PM, Werner LEMBERG wrote:
Basically, I think this is a FontConfig issue; all TrueType fonts
which need autohinting should be configured as such.
I understand your stance. However, having to configure fonts individually is
something we have tried to avoid before.
On the
On the other hand I see the problem you have. However, there is
currently no possibility (built into FreeType, I mean) to find out
whether a font has TrueType hints or not. It's straightforward to
add such a function, and FontConfig might use it during the
creation of the cache.
That
Hi,
In Fedora rawhide I enabled the patented bytecode interpretter a while ago
since the patents expired. I've received reports since that this has resulted
in degraded rendering of some fonts.
Apparently, from what I hear, with Medium hinting, the autohinter is not used
even if the font
In Fedora rawhide I enabled the patented bytecode interpretter a
while ago since the patents expired. I've received reports since
that this has resulted in degraded rendering of some fonts.
Apparently, from what I hear, with Medium hinting, the autohinter is
not used even if the font
