- 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>
>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 UTC