Re: FW: EOT-Lite File Format

Dave Crossland wrote:

> Given many case studies of how DMCA-style laws are used to attack free
> software projects, and given browser developers said that EOT of yore
> posed too much DMCA risk, why does EOTL that allows ignoring
> rootstrings when present pose less risk?

This is the point I made a couple of days ago. Note, however, that the 
EOTL version currently proposed does not contain rootstrings, cannot 
contain rootstrings and be considered valid EOTL.

So the only issue re. rootstrings seems to be what a conforming browser 
does with non-valid EOTL fonts (including EOT Classic fonts). I believe 
the answer has to be 'flush them'. Ignoring the rootstring and 
pretending that the EOTL is valid is too risky.


Received on Monday, 3 August 2009 17:33:53 UTC