- From: Hakon Wium Lie <howcome@opera.com>
- Date: Tue, 25 Apr 2006 21:57:14 +0200
- To: Laurens Holst <lholst@students.cs.uu.nl>
- Cc: www-style@w3.org
Also sprach Laurens Holst:
> > Yes, this could work. UAs should also be able to handle this:
> >
> > font-family: "TSCu_Comic", url(TSCu_Comic.zip), sans-serif;
> >
> > That is, zip files should be uncompressed in the client.
>
> Not through HTTP? I don$,1ry(Bt know much about the details of gzip, but
> wouldn$,1ry(Bt simply sending an Content-Encoding: gzip header with the file
> suffice?
That could work, too. The reason for supporting zip-files directly is
that this is the how fonts are published on the web today. Here are
some samples:
http://www.fontfreak.com/fonts-g2.htm
http://www.1001freefonts.com/fonts/pfonts5.htm
Zip does two things here. First, it bundles a set of TTF files
together (often along with a README of some sorts). This is a good
thing as one font family typically consists of four different files.
Second, it applies compression.
By using HTTP-level compression, you replace one part of zip -- how
would you replace the other?
-h&kon
H,Ae(Bkon Wium Lie CTO ,A0~(Be,A.*(B
howcome@opera.com http://people.opera.com/howcome
Received on Tuesday, 25 April 2006 19:57:04 UTC