RE: EOT-Lite File Format

>From: John Hudson [mailto:tiro@tiro.com]


>I'm not a lawyer, but it seems to me that a browser that fails to follow
>this when encountering an EOT-Classic font is at legal risk. If not, why
>all the fuss about DMCA? At the very least, this seems to me a question
>that needs to be examined by qualified lawyers experienced with this
>kind of issue.
>
>At present, the non-IE browser makers are deliberately not touching EOT
>fonts because they don't want to get entangled with the rootstring
>issue. They're not supporting EOT but ignoring rootstrings: they're
>keeping the heck away from EOT altogether. It seems to me that they must
>continue to do so, because the status of EOT Classic fonts doesn't
>magically change when EOT Lite comes along.  This means that while EOT
>Lite fonts can be backwards compatible with IE<=8, EOT Classic fonts
>must not be forwards compatible with EOT Lite. Somehow the two formats
>need to be clearly distinct at the file level, such that an EOT Lite
>implementing browser can process the one but avoid the other.

John, the latest proposal means that this scenario cannot happen.

Received on Friday, 31 July 2009 13:44:03 UTC