> Yesterday's opentype font meeting touched upon hinting and
> ttfautohint briefly.  I see the infinality patch is already gone
> (next release, 2.13.2 I guess - bits of it was removed in 2.13.1
> already).  Question is, does its removal impact the functionality of
> ttfautohint?

No.

> Are we getting into a situation where ttfautohint is hinting for the
> (limited) "good enough" light hinting model of recent freetype?

It's not clear what you are actually asking.  ttfautohint is an
incarnation of FreeType's auto-hinter, translated into TrueType
bytecode, more or less.  This is not related to interpreting bytecode.

> And dropping support, and/or compatibility/ awareness of intended
> usages of outcome in other *cough* microsoft *cough* hinting models?

Well, the Infinality stuff was basically unmaintained; it essentially
consisted of a large bunch of exceptions for some special fonts.
Alexei and I agree that we no longer need this.  There was not a
single voice objecting to its removal, by the way...


    Werner

Reply via email to