- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Fri, 31 Jul 2009 17:05:00 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, John Daggett <jdaggett@mozilla.com>
- CC: www-font <www-font@w3.org>
> From: www-font-request@w3.org [mailto:www-font-request@w3.org] On > If a file fails these checks, MUST it refuse to load the file, or can > a conforming implementation attempt to parse it as a different file? These checks mean you have an invalid EOTL file. Processing stops, load fails. > 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 ?
Received on Friday, 31 July 2009 17:05:51 UTC