Comments on: A closer look at TrueType hinting https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/ News about Typekit Sat, 08 Jan 2011 04:50:44 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Matthew Smith https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/#comment-2080 Sat, 08 Jan 2011 04:50:44 +0000 http://blog.typekit.com/?p=2434#comment-2080 Hi Tim,

Great write up, and helpful to the new, and according to the comments, the well versed alike. I’m curious to hear more about what TypeKit is doing to auto hint. Does that mean you all are attempting to apply an auto-hint to one font at a time and adjusting it per font? Or are you aiming at an algorithm that will cover more ground?

This is probably one of the main points that will draw people to use TypeKit over other services I would think.

]]>
By: Jason C https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/#comment-2079 Mon, 20 Dec 2010 14:16:45 +0000 http://blog.typekit.com/?p=2434#comment-2079 re: hours to hint a font.
Assuming we’re talking about “manually” hinting a font, using Visual TrueType, I think the 40 hours estimate is pretty accurate for a Latin 1 character set. A WGL character set could take twice that. The biggest factor in hinting time estimate is “what is the target rendering environment”? If you had to hint for a “black and white” rasterizer, it could take longer than 40 hours. Likewise, lighter weight fonts and italic fonts typically take longer than regular weight and roman fonts.

]]>
By: Tim Ahrens https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/#comment-2078 Mon, 20 Dec 2010 10:23:34 +0000 http://blog.typekit.com/?p=2434#comment-2078 Thanks, Jason!

Richard, very hard to give any numbers in my opinion. In hinting, like with many things in the world, initial improvements can be achieved quickly and without too much effort but as you get closer to perfection the effort that is necessary to achieve improvements increases. Good autohinting – we are currently improving our own system at Typekit – is already better than no hinting at all. Spending a few hours setting manual hints fixes most remaining problems but if you want relly perfect rendering you can spend much more time, virtually without any upper limit. Thinking of Verdana as an extreme example, where the hinting probably took weeks or months.

]]>
By: Richard Fink https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/#comment-2077 Sat, 18 Dec 2010 16:33:35 +0000 http://blog.typekit.com/?p=2434#comment-2077 Tough stuff to explain, Tim. Nice job of it.
Question: Peter Bilak of Typotheque has a posting on hinting in which he estimates that it takes about 40 hours to hint a font.
And I am assuming he means one font, one file – certainly not a four member family.
Does this time estimate agree with your experience?

]]>
By: Jason C https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/#comment-2076 Wed, 15 Dec 2010 13:32:03 +0000 http://blog.typekit.com/?p=2434#comment-2076 Great overview of hinting technology and the hinting process, Tim.

]]>
By: Tim Ahrens https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/#comment-2075 Wed, 15 Dec 2010 09:06:25 +0000 http://blog.typekit.com/?p=2434#comment-2075 In reply to Rich Carey.

Rich, all web fonts use Bézier curves. TrueType-based formats use 2nd order (quadratic) Bézier curves whereas PostScript-based formats use 3rd order (cubic) Bézier curves.

]]>
By: Rich Carey https://blog.typekit.com/2010/12/14/a-closer-look-at-truetype-hinting/#comment-2074 Wed, 15 Dec 2010 06:34:44 +0000 http://blog.typekit.com/?p=2434#comment-2074 webfonts dont use bezier curves, they use quadratic curves

]]>