W3C home > Mailing lists > Public > www-style@w3.org > May 2009

Re: CSS3 Web Fonts issue with ‘block on download’

From: Adam Twardoch <list.adam@twardoch.com>
Date: Thu, 07 May 2009 19:58:08 +0200
Message-ID: <4A032130.20706@twardoch.com>
To: "Levantovsky, Vladimir" <Vladimir.Levantovsky@MonotypeImaging.com>
CC: Brad Kemper <brad.kemper@gmail.com>, David Hyatt <hyatt@apple.com>, w3-style@boblet.net, www-style@w3.org
Levantovsky, Vladimir wrote:
> Adam, this is a brilliant idea. A significant part of EOT is the font-specific lossless MTX compression, and the reason MTX compression is on average 30% better than generic zip is because the compressor optimizes the source data, and separates and groups different types of data in a font into three separate data blocks (http://www.w3.org/Submission/2008/SUBM-MTX-20080305/). The first block contains all the metrics and layout data, and can be decompressed and used for page processing while other two blocks containing glyph information are downloaded. Not only the fonts will be downloaded twice as fast because you have less data to download, you can process the page layout while the significant chunk of glyph data is being downloaded.

Excellent. I was not even aware that a "streaming-like"/"progressive"
structure of EOT is already part of the spec, but I agree that this fact
makes a compelling argument supporting the claim that in many cases, EOT
is a much better choice for web font use than TTF or OTF.

A.

-- 

Adam Twardoch
| Language Typography Unicode Fonts OpenType
| twardoch.com | silesian.com | fontlab.net

The illegal we do immediately.
The unconstitutional takes a little longer.
(Henry Kissinger)
Received on Thursday, 7 May 2009 17:58:54 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:18 GMT