RE: EOT-Lite File Format 1.2 (was RE: EOT & DMCA concerns)

> From: Levantovsky, Vladimir
> [mailto:Vladimir.Levantovsky@MonotypeImaging.com]
> Sent: Tuesday, August 04, 2009 1:17 PM


> Introducing the new version number for EOT-Lite and requiring all EOT-
> Lite compliant implementations to support the new files with version
> number *only* should eliminate any concerns about hypothetical presence
> of rootstrings in padding, IMO. We define a new format with no notion
> of rootstrings, and the new version number provides a clear way to
> differentiate any and all prior EOT formats and the new EOT-Lite.

There can't be any such concerns with 0x00020000 as that header version has
zero rootstring space. No one can ship EOT files using this version number and
demand restrictions to be respected. There aren't any.

Received on Tuesday, 4 August 2009 20:55:50 UTC