- From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
- Date: Wed, 24 Jun 2009 12:05:29 -0400
- To: "Brad Kemper" <brad.kemper@gmail.com>
- Cc: "Aryeh Gregor" <Simetrical+w3c@gmail.com>, "Jonathan Kew" <jonathan@jfkew.plus.com>, <www-style@w3.org>
> -----Original Message----- > From: Brad Kemper [mailto:brad.kemper@gmail.com] > Sent: Wednesday, June 24, 2009 11:49 AM > To: Levantovsky, Vladimir > Cc: Aryeh Gregor; Jonathan Kew; www-style@w3.org > Subject: Re: New work on fonts at W3C > > > On Jun 24, 2009, at 7:42 AM, Levantovsky, Vladimir wrote: > > > So, maybe instead of trying to come up with a way to make authors > > jump through the hoops *all the time* > > I am an author who has yet to see the competing proposal as ever > jumping through hoops, to any extent beyond the "hoops" of what you > are proposing for your wrapper version. The same-origin technical > restrictions, on the other hand, go beyond the goal of "no > trespassing" signs that communicate the broad strokes of the license > with links to the finer strokes, and would be significant "hoops" to > jump through. So you are saying that - you would rather continue serve EOT to IE and raw TrueType to other browsers, and - you would rather be in a position where in order to do that you'd have to rename each font file, or - you would rather rely on a third-party solutions like TypeKit to do it for you, and - you don't mind having uncompressed font files being served from your site. You would really prefer to do all this rather than - compress a font "as is" and create a single CSS module that works the same way in all browsers. Is this what you are saying?
Received on Wednesday, 24 June 2009 16:06:12 UTC