RE: A way forward

> 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 ?


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