Comments on: Parkinson Type Design joins Typekit https://blog.typekit.com/2012/03/08/parkinson-type-design-joins-typekit/ News about Typekit Thu, 15 Mar 2012 19:15:33 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Tim Brown https://blog.typekit.com/2012/03/08/parkinson-type-design-joins-typekit/#comment-3205 Thu, 15 Mar 2012 19:15:33 +0000 http://blog.typekit.com/?p=6917#comment-3205 In reply to Eric Carl.

TrueType hinting has no place in high-resolution environments like the iPhone/iPad retina display, and in fact, it has no place in many low-resolution environments. We currently only serve TrueType files to Windows, and even then only for text faces. Display faces, like these from Jim Parkinson, are best served with PostScript-based outlines for smooth rendering at large sizes.

As high-resolution experiences become more common, anti-aliasing-related rendering issues will disappear. However, the clarity brought on by Apple’s retina displays will reveal (and is already revealing) the awkwardness of poorly drawn and spaced fonts. Plus, we’ll continue to have to deal with CSS-related rendering issues.

Good question, Eric.

]]> By: Eric Carl https://blog.typekit.com/2012/03/08/parkinson-type-design-joins-typekit/#comment-3204 Thu, 15 Mar 2012 18:35:27 +0000 http://blog.typekit.com/?p=6917#comment-3204 Completely off topic, but out of curiosity, what kind of role does font hinting play on a high-res display like the new iPad 3? My understanding is that hinting is required to keep fonts rendering clearly on the low resolution of traditional displays, but does something like the retina display, especially as those high resolutions become more wide spread in the future, negate the need for such a laborious and time consuming process?

]]> By: Alan Bennington https://blog.typekit.com/2012/03/08/parkinson-type-design-joins-typekit/#comment-3203 Wed, 14 Mar 2012 18:43:52 +0000 http://blog.typekit.com/?p=6917#comment-3203 All wonderful…especially like Apex!!

]]>