- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Fri, 31 Jul 2009 02:43:49 +0000
- To: John Hudson <tiro@tiro.com>, "Levantovsky, Vladimir" <Vladimir.Levantovsky@MonotypeImaging.com>
- CC: Tab Atkins Jr. <jackalmage@gmail.com>, Thomas Lord <lord@emf.net>, "robert@ocallahan.org" <robert@ocallahan.org>, John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
>From: John Hudson [mailto:tiro@tiro.com] > >But that implies that it may treat an EOT font as if it were EOTL, if >TTEMBED_TTCOMPRESSED and TTEMBED_XORENCRYPTDATA flags check out, and >that seems to me problematic if it means that a non-nil rootstring with >meaningful content relative to that EOT font -- and perhaps to the >license for that EOT font -- is ignored. The whole point of the EOTL >format is to make a new format that is not burdened by rootstrings, not >to treat all existing old-format EOT fonts with rootstrings as if they >were EOTL. > Rootstrings are used to restrict the use of the font to the current origin. Which is what Firefox already does by default.
Received on Friday, 31 July 2009 02:44:32 UTC