Re: EOT-Lite File Format

On Thu, Jul 30, 2009 at 6:46 PM, Sylvain Galineau<> wrote:
>>If the EOT file also qualifies as a valid EOTL file (which is very
>>possible), then it gets displayed.  If not, it doesn't, just like any
>>other random blob of data that doesn't comprise a recognized font
> I think there is an interesting scenario there. Imagine I license
> an EOT from Monotype, set rootstrings then deploy it without compression
> or XOR encoding. If its version matches whatever existing EOT version EOTL settles on
> then it will load in the EOTL client despite the rootstring and possibly in violation
> of its license.
> So either EOTL clients check for nil-rootstrings (wrecking the possibility of
> hijacking them for same-origin checks in legacy IE) or we use a new version number
> for EOTL to disambiguate the latter from EOT.
> Makes sense ?

What's the effect on legacy IE of a new version number?


Received on Thursday, 30 July 2009 23:52:52 UTC