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

Re: FW: EOT-Lite File Format

From: Anton Prowse <prowse@moonhenge.net>
Date: Tue, 04 Aug 2009 18:45:04 +0200
Message-ID: <4A786590.6070500@moonhenge.net>
To: www-font@w3.org
Am I understanding the following correctly, then?

1.) EOTL1.1 allows web authors to create and link to font files in such 
a way that the same syntax and file will work  both in EOTL1.1-compliant 
browsers and in legacy IE browsers which are fooled into thinking that 
they're processing some kind of EOT file.  However, existing web pages 
which utilize EOT+rootstrings will "break" in EOTL1.1-compliant 
browsers; authors of such sites will need to update their 
stylesheets/files to employ a different technique if they wish to use 
linked fonts in future browsers.  (If authors choose EOTL1.1 for this 
purpose, they merely need to regenerate their font file according to the 
rules of EOTL1.1; they won't necessarily need to change their stylesheet 
since the existing syntax and filename can be preserved if desired.)

2.) EOTLwrip ("EOTL with rootstring in padding") offers the same 
cross-browser compatibility advantages as EOTL1.1 and additionally 
avoids "breakage" in EOTLwrip-compliant browsers of existing web pages 
which utilize EOT+rootstrings.  This is because the presence, in the 
currently-linked font file, of some fluff which has a passing 
resemblance to a "rootstring" in some other file format (EOT) does not 
"corrupt" the file for EOTL1.1 implementations.

Cheers,
Anton Prowse
http://dev.moonhenge.net
Received on Tuesday, 4 August 2009 16:46:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:03 GMT