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

Re: EOT-Lite File Format

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 31 Jul 2009 11:12:07 +1200
Message-ID: <11e306600907301612t3f8e5416q8d4985a7a7ad4a2a@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
On Fri, Jul 31, 2009 at 10:59 AM, Sylvain Galineau

>    On Fri, Jul 31, 2009 at 10:04 AM, Sylvain Galineau <
> sylvaing@microsoft.com> wrote:
> 2. We recommend using 0x00020000 for EOTL files as that version has no
> rootstrings nor EUDC. This means step #2 checks for that value
> only.
> What do you mean "has no rootstrings"? You'd want IE (<=8) to process
> rootstrings contained in EOTL, to make it easier for authors to comply with
> font licensing.
> If licenses do require that, we’ll revisit. Ascender made the proposal and
> does not require them.
Bill seems to be saying that they do, in fact, require *some* kind of access
Although even his clarification isn't as clear as I would like.

Bill, can you answer this question: if I put a null-rootstring Ascender EOT
font on my public server, does Ascender consider me to be compliant with the
font license, or not?

"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
Received on Thursday, 30 July 2009 23:12:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:33 UTC