W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

Re: Merits and deficiencies of EOT Lite

From: John Hudson <tiro@tiro.com>
Date: Tue, 28 Jul 2009 15:45:04 -0700
Message-ID: <4A6F7F70.5050807@tiro.com>
To: John Daggett <jdaggett@mozilla.com>
CC: www-font <www-font@w3.org>
John Daggett wrote:

> Maybe this is just me but implementing EOT-Lite in non-IE browsers
> without revving IE effectively handicaps CFF fonts, TTF fonts would
> be favored for market reasons rather than on technical merits. CFF
> font vendors would be under market pressure to offer TTF versions of
> their fonts and switch to using a TTF tool chain.  Clients would be
> advised, "you should use TTF fonts because IE doesn't support CFF
> fonts" and I'm guessing that stigma would outlive it's validity.

There is already a TT bias for the web, just as there are the remnants 
of a once strong PS bias for imagesetters. I think web designers will be 
advising their clients 'You should use TTF fonts because CFF fonts look 
like crap and are hard to read at text sizes' long before they get 
around to saying 'And IE doesn't support CFF fonts'.

Without significant improvement in CFF rasterisation, I think a natural 
divide will emerge between CFF fonts for headlines and display 
typography and TTF for text. This won't be the first time that a format 
distinction has split along these lines: in the old days, you might get 
your headline set at one typesetting shop with one machine, and your 
text set at another shop on a different machine.

On the subject of better rasterisation of CFF fonts, I'm looking forward 
to the Win7 compatible Firefox written to make use of DWrite instead of 
GDI :)

Received on Tuesday, 28 July 2009 22:45:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:40 UTC