Re: CSS3 @font-face / EOT Fonts - new compromise proposal from John Daggett on 2008-11-11 (www-style@w3.org from November 2008)

From: John Daggett <jdaggett@mozilla.com>
Date: Mon, 10 Nov 2008 20:36:12 -0800 (PST)
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Cc: Sylvain Galineau <sylvaing@microsoft.com>, www-style@w3.org
Message-ID: <176606.46571226378172627.JavaMail.root@cm-mail01.mozilla.org>

> > I don't think this is right.  An obfuscated version of a font would
> > not use .ttf or .otf, nor would it use a TT MIME type if one
> > existed.  It would/should be a distinct data type.
> 
> I'd think that using a TT MIME type and a Content-Encoding indicating
> the compression would be a perfectly valid way of serving up
> compressed TT files.

Really?  Even though that compression type would only apply to TT data?  Are there other examples of compression schemes used with Content-Encoding that are data specific?

Received on Tuesday, 11 November 2008 04:36:53 UTC