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

Re: A way forward

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 25 Jul 2009 09:47:48 +1200
Message-ID: <11e306600907241447j60b461a0jb097b342e277f345@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: HÃ¥kon Wium Lie <howcome@opera.com>, John Hudson <tiro@tiro.com>, www-font <www-font@w3.org>
On Sat, Jul 25, 2009 at 6:41 AM, Sylvain Galineau <sylvaing@microsoft.com>wrote:

> To make sure we are on the same page, EOT-Lite means:
> 1. Raw font files are prefixed with a well-known binary header;
> 2. The user agent reads the parts of the header necessary to:
>        a. Determine its length;
>        b. Verify its validity e.g. ensure the rootstring field is null;
> 3. The user agent then proceeds to skip this header and treat the remainder
> of the resource as
> it would a reference to its raw equivalent.

Is "XOR encryption" permitted by EOT-Lite? Because Ascender's just-announced
"EOT Lite Wrap Tool" optionally applies "XOR encryption", and presumably
authors will expect the results to still be "EOT Lite".

"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 Friday, 24 July 2009 21:48:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:40 UTC