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

Re: A way forward

From: karsten luecke <list@kltf.de>
Date: Sat, 25 Jul 2009 00:57:49 +0200 (MEST)
Message-Id: <200907242257.n6OMvnp1016158@post.webmailer.de>
To: www-font@w3.org
Dave Crossland wrote:
> 2009/7/24 John Daggett <jdaggett@mozilla.com>:
>> John Hudson wrote:
>>
>>>> But, if that is the case - if the existing cross site restriction is
>>>> good enough for foundries who support EOT, and their aim is to get
>>>> profiting from web fonts ASAP, why isn't supplying TTFs with corrupt
>>>> NAME tables and a changed file extension good enough?
>>> Because its a hack, because it exposes the font to unknown dependencies
>>> in which it might not function correctly, and because we've spent the
>>> past ten years getting good at producing fonts to spec rather than
>>> putting in hacks to solve short-term software issues. We want a nice
>>> clean web font spec, against which we can test our products. Further,
>>> some of us have customers whose procurement requirements would prevent
>>> us from delivering fonts with corrupt data.
>> Name tables can be obfuscated without being "corrupt", they can be
>> entirely copasetic but constructed in such a way that they would
>> effectively be unusable in desktop apps.
> 
> Typotheque's and one other influential foundry that I have seen
> licensing TTFs for "raw" usage but with referrer checking did corrupt
> the NAME table. That seems to be what they prefer, despite when you
> publicaly suggested this approach you (as you do here) suggested
> spec-compliant but 'copasetic' NAMEs.

Dear Dave, if they do right now then this may be because there is no web font format yet but they are waiting?

And next you will tell me that Typotheque is developing its web font service because they are so happy with raw TTF/OTF @font-face linking ...

Karsten
Received on Friday, 24 July 2009 22:58:46 GMT

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