[Bug 547532] freetype with the bytecode interpreter enabled falls back to no hinting instead of autohinting when no hinting bytecode is available

bugzilla at redhat.com bugzilla at redhat.com
Tue Dec 15 04:26:15 UTC 2009

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


--- Comment #7 from Matthew Miller <mattdm at mattdm.org>  2009-12-14 23:26:14 EDT ---
Upstreaming and getting the issue fixed is a great long-term approach. However,
I also think we should revert this change until that is in place, as it
significantly degrades the user experience. (Hence the original summary of this
issue and its focus on that, rather than on the underlying problem.)

I took a quick look at the source, and src/base/ftobjs.c has a section with a
big comment starting "Determine whether we need to auto-hint or not" -- it
seems like it's _probably_ no big deal to add the appropriate logic there.

There's also some code in src/truetype/ttobjs.c which decides if a crippled
(patent-safe) version of the bytecode interpreter needs to be used for a
specific font (apparently some need it to even load properly). This sets a flag
which the ftobjs.c code later uses....

Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the fonts-bugs mailing list