[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft-devel] New FreeType release within a week

From: Dave Arnold
Subject: Re: [ft-devel] New FreeType release within a week
Date: Tue, 2 Jan 2018 15:02:36 -0800
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

I think this may be a result of an implementation choice for combining T1 and CFF. There is no limit to the number of hints that can occur in a Type1 charstring. Each time there is a hint substitution, previously used hints are discarded. On the other hand, CFF requires that all hints be declared at the beginning of the charstring and imposes a limit so they can be easily stored in a common structure.

I looked at the example that Ewald gave, ztm-Reg.pfb gid 479 'shade'. While the [hv]stem operators are used 344 times in this charstring, the hints are not all unique. There are just 10 unique hstems and 10 unique vstems. When converted to CFF, this font would therefore declare just 20 hints, easily within the limit.

To answer Nikolaus' question, this font is legal Type1 and should render hinted in Adobe implementations.



On 1/2/2018 8:35 AM, Werner LEMBERG wrote:

I'm wondering, how about leaving the CFF limit as is and apply it
to Type1, too, and just turn off hinting for that glyph?  Not
entirely correct, but an easy way out when the hinting obviously
went wrong.
Actually, since the FreeType hinter handles it fine, how about
returning a specific error code when this happens and fall back to
the old engine, if it is available?  Otherwise, perhaps the
Maybe, yes, but I think unhinted is the easiest solution.  However,
this shouldn't prevent you with testing other solutions :-)


Freetype-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]