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

Re: EOT-Lite File Format v.1.1

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 31 Jul 2009 12:15:08 -0500
Message-ID: <dd0fbad0907311015m78a41e0ene0c3362edb1cf947@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
On Fri, Jul 31, 2009 at 12:05 PM, Sylvain
Galineau<sylvaing@microsoft.com> wrote:
>> That is, do these checks occur past the point of no return, or can
>> they be part of the "check what kind of font this file is" algorithm,
>> allowing a conforming implementation to then attempt to load it as a
>> different kind of font (such as EOT-Classic)?
>
> If you support EOT-Classic then you will load any EOTL. A core requirement
> of this proposal is that all EOTLs are valid EOTs. So maybe I'm missing the
> question ?

Valid EOTLs are a strict subset of valid EOTs.  Can an implementation
conform to the EOTL spec while still successfully processing those
files which are valid EOT but not EOTL?  You can qualify your answer
with any sets of features differing between EOT and EOTL if you wish.

~TJ
Received on Friday, 31 July 2009 17:16:05 GMT

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