One possible solution is for the ttfautohint-generated bytecode to do a 'test division' (e.g. I'm corresponding with the people involved so that ttfautohint can be patched. Ttfautohint uses division extensively, much more often than other hinting tools, and it does this repeatedly, so the errors accumulate, resulting in point coordinates being 'blown up'. While the TT spec prescribes that division should truncate (so 5/3 should be equal 1 in the TrueType hinting language), some implementations perform rounding (so 5/3 = 2). The problem is in the implementation of the division operator in some rasterizers.

I'll do some experiments with turning off instructions above a certain limit.

I just received information from another user that the same problem happens with Canon MP550. Supporting different kinds of file naming schemes is among the more advanced functionalities.ĭavid, that's an excellent point. We've designed the TransType user interface to address this.Įveryone has somewhat different requirements for what a 'technical font production tool' should do, and our goal is to address the most common ones in a product such as TransType 4, and give more demanding customers a more advanced tool which offers them more flexibility. Sometimes, this is leading to problems on the users' end. and it still continues to be the case in 2013.ĭuring TransType testing, we've uncovered a remarkable number of naming errors in larger font families (in shipping fonts made by different renowned vendors), where the PostScript name, the weight information or the copyright string was 'off' in one of the fonts.

One thing I can say, though, is that the by far most common problem reported by many people has always been the difficulty to get the family naming right, including style linking etc. Many thanks for your feedback! All things that you mention are planned for an edition of the product that will be targeted more specifically at the font foundries.

Transtype 4 reviewsd