[Bug 368561] ligature-related font rendering bug with 'ff' and 'fi'

[bugzilla at redhat.com]

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


https://bugzilla.redhat.com/show_bug.cgi?id=368561





--- Comment #13 from Ben Laenen <bl.bugs at gmail.com>  2008-08-27 11:49:33 EDT ---
(In reply to comment #12)
> Thanks Ben.  One thing that may help is to use two-component ligatures. That
> is, map the 'fi' to two glyphs that together form the 'fi' ligature.  Not
> sure though.

But then Freetype should know how to autohint those ligature components, and I
think that's even harder than the ligatures which in this case are at the
assigned code points. With components it needs to analyze the OpenType features
first. (OTOH, the ligatures don't have to use those code points, so it may need
the proper way of handling them anyway)

So I would expect Freetype to have a glyph list containing all Latin letters to
get its autohinter metrics from, and that list doesn't contain the fi
ligatures. If that's the case, it should be as easy as just adding them to that
list. But of course, I have no idea how Freetype's autohinter works :-)

-- 
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.