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

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.

Vladimir


> -----Original Message-----
> From: Sylvain Galineau [mailto:sylvaing@microsoft.com]
> Sent: Tuesday, August 04, 2009 4:10 PM
> To: Levantovsky, Vladimir
> Cc: www-font@w3.org
> Subject: RE: EOT-Lite File Format 1.2 (was RE: EOT & DMCA concerns)
> 
> Should font vendor and author feedback indicate the ability to use
> rootstrings to enforce same-origin restrictions in IE to be required
> for deployment then 1.2 would be the way to go. Until we have clear
> consensus that this will be needed and have established it does not
> introduce (or reintroduce) issues we sought to eliminate by doing away
> with rootstrings, I'm fine with 1.1 as the path is no less clear for
> IE9 in that case.
> 
>

Received on Tuesday, 4 August 2009 20:17:31 UTC