W3C home > Mailing lists > Public > www-style@w3.org > April 2006

Re: Downloadable fonts and image replacement

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Tue, 25 Apr 2006 22:11:34 +0200
Message-ID: <444E8276.8090402@students.cs.uu.nl>
To: Håkon Wium Lie <howcome@opera.com>
Cc: www-style@w3.org
Håkon Wium Lie schreef:
> 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?

Yes, right, that makes sense. I suppose browsers adding ZIP or TAR as 
supported compression methods in HTTP wouldn’t really work? :)

But why are they distributed as separate files anyway? Is there some 
technical limitation that prevents them from being combined into one big 
font file? Could a tool be used to combine separate fonts? Why not just 
add the fonts as fallbacks for eachother (so what if there are four 
instead of one file requests)?


~Grauw

-- 
Ushiko-san! Kimi wa doushite, Ushiko-san!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Laurens Holst, student, university of Utrecht, the Netherlands.
Website: www.grauw.nl. Backbase employee; www.backbase.com.




Received on Tuesday, 25 April 2006 20:11:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:44 GMT