W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

RE: EOT-Lite File Format

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Fri, 31 Jul 2009 01:44:13 +0000
To: Thomas Lord <lord@emf.net>
CC: John Hudson <tiro@tiro.com>, John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
Message-ID: <045A765940533D4CA4933A4A7E32597E02133286@TK5EX14MBXC111.redmond.corp.microsoft.com>
>From: Thomas Lord [mailto:lord@emf.net]


>A browser, X, is presented with a perfectly
>render-able EOT font that happens to have
>a non-nil root string.  The prohibition "must not
>render" in that case is either DRM or so close
>to DRM that costly court battles can be anticipated
>for the implementer who disregards the restriction.

First, there is no rootstring check. Currently, a
conforming EOTL client does not know anything about
rootstrings. EOTL generators *may* know.

EOT clients of course do.

Second, the current EOT header version does not include
any rootstring space. It doesn't exist.

Let us stick to what is known and relevant here.
Received on Friday, 31 July 2009 01:44:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:03 GMT