- From: Chris Wilson <Chris.Wilson@microsoft.com>
- Date: Tue, 23 Jun 2009 16:33:50 +0000
- To: Håkon Wium Lie <howcome@opera.com>
- CC: John Daggett <jdaggett@mozilla.com>, "www-style@w3.org" <www-style@w3.org>
Håkon Wium Lie [mailto:howcome@opera.com] wrote: >You could e.g. start by responding to this proposal: > > http://lists.w3.org/Archives/Public/www-style/2008Nov/0412.html 1. I don't think CORS is a good application here, as it seems much more destructive to workflow than generating EOT files. 2. yes, I think this (lightweight obfuscation/compression scheme) is a good idea. That's essentially what EOT does, and checks the embedding bit to see if it can generate embeddings for the font. If the concern is field of use of MTX, then I'd like to see that defined, and then we can ask Monotype to remove that restriction. 3. (linking to "standard" TTF/OTF files) As previously indicated, I don't see any way to make this palatable (without requiring additional bits in the TTF/OTF that say this usage is allowed, that would not be set in most commercial fonts - e.g. "does not work with any current fonts, freeware fonts would have to be updated.") -Chris
Received on Tuesday, 23 June 2009 16:34:38 UTC