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

RE: EOT-Lite File Format v.1.1

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Fri, 31 Jul 2009 18:04:48 +0000
To: Thomas Lord <lord@emf.net>
CC: Tab Atkins Jr. <jackalmage@gmail.com>, John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
Message-ID: <045A765940533D4CA4933A4A7E32597E02138670@TK5EX14MBXC111.redmond.corp.microsoft.com>
>From: Thomas Lord [mailto:lord@emf.net]
>Sent: Friday, July 31, 2009 11:00 AM

>> I hope so as that's what the next release of IE must do :)
>> Version 2 files that match all the EOTL criteria will be treated
>> as EOTL including same-origin/CORS. Anything that is not a valid EOTL
>> but a valid EOT will be treated as such.
>
>That would seem to evade the question because
>future IE will presumably honor root strings
>in EOT classic files.

I honestly don't understand what's being evaded. EOTL files
have no rootstrings. There is not space for them in the header.
EOT files with rootstrings are, per the current definition,
not EOTL files. IE will still support those. But an EOTL-only
implementation will treat any EOT files with rootstrings as
invalid since the header version number will be != 0x00020000.

Sorry for being dense. I don't understand what the issue is.
Received on Friday, 31 July 2009 18:05:31 GMT

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