https://bugzilla.redhat.com/show_bug.cgi?id=857860
--- Comment #14 from Behdad Esfahbod <behdad(a)fedoraproject.org> ---
(In reply to comment #11)
Hmm. FreeType is completely unaware of `gasp'. Especially with
the
introduction of ClearType, handling of `gasp' has become non-trivial. I
would really like to not add this.
This is where we disagree :). If it's non-trivial, it's even more non-trivial
for FreeType-using pieces of the stack...
(In reply to comment #12)
To be more specific, handling of `gasp' belongs into the same
category as
handling OpenType tables, this is, one level higher.
I wouldn't think so. It directly affects rasterization, and as we have
established in other threads, rasterizing using bytecode hinting with disregard
to gasp table can be problematic. Sure, we can force all FreeType users to
implement gasp table handling, but I see it more fit in the library itself.
--
You are receiving this mail because:
You are on the CC list for the bug.