W3C home > Mailing lists > Public > www-font@w3.org > January to March 2010

eotfast, ttf2eot, mkeot (was: Webfonts from FontFont)

From: Bert Bos <bert@w3.org>
Date: Tue, 2 Mar 2010 16:22:31 +0100
To: "'www-font'" <www-font@w3.org>
Message-Id: <201003021622.31739.bert@w3.org>
On Monday 01 March 2010 13:48:51 Adam Twardoch (List) wrote:

> As for the comparison between ttf2eot and eotfast.exe, it's fair to
> point out that ttf2eot does not incorporate the patented Monotype
> MicroType eXpress (MTX) compression while eotfast.exe does (as MTX is
> used by Windows). Typically, EOTs created with eotfast.exe will be
> smaller than those created with ttf2eot.

The EOT files from ttf2eot didn't work for me, so I decided to write my 
own converter. My mkeot program writes EOT version 2.2. Unlike ttf2eot, 
it fills in *all* the fields in the EOT header, adds URLs ("root 
strings"), and respects the embedding bits of the original font. Unlike 
WEFT, it doesn't do any subsetting and doesn't compress the font 
data(*). It's written in C and is Open Source:


There is a companion program eotinfo in the same package to display 
what's in an EOT header.

No binaries for the moment, you need to compile it yourself. Tested on 
Linux and Mac OS X. It uses the non-POSIX err() function from BSD, 
which I could remove if needed, but otherwise it should compile 
anywhere with a standard C compiler.

*) If the EOT file is served by HTTP, and depending on the configuration 
of the server, you may be able to gzip the file, or maybe the server 
even does it automatically.

  Bert Bos                                ( W 3 C ) http://www.w3.org/
  http://www.w3.org/people/bos                               W3C/ERCIM
  bert@w3.org                             2004 Rt des Lucioles / BP 93
  +33 (0)4 92 38 76 92            06902 Sophia Antipolis Cedex, France
Received on Tuesday, 2 March 2010 15:22:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:34 UTC