W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

RE: A way forward

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 27 Jul 2009 19:30:08 +0000
To: Dave Crossland <dave@lab6.com>, John Hudson <tiro@tiro.com>
CC: "www-font@w3.org" <www-font@w3.org>
Message-ID: <045A765940533D4CA4933A4A7E32597E0210BE11@TK5EX14MBXC120.redmond.corp.microsoft.com>
> Any foundry that signs up to TypeKit or similar demonstrates that,
> although they might prefer something else, raw TTFs are acceptable to
> them.

If and only if the file are served raw i.e. directly reusable in a different context. TypeKit uses a number of techniques to obfuscate the font through the use of data URIs and segmenting among others.[1]

So the font is effectively well obfuscated for the majority of users. If raw TTFs were acceptable to the foundries who work with TypeKit, why go through all this trouble ?


[1] http://blog.typekit.com/


Received on Monday, 27 July 2009 19:30:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:03 GMT