W3C home > Mailing lists > Public > www-font@w3.org > April to June 2010

Re: WOFF and extended metadata

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 21 May 2010 11:18:48 +1200
Message-ID: <AANLkTinr3ld5hUga9HcSF9UTvwbrXnwB7lmIptKCDzz4@mail.gmail.com>
To: Adam Langley <agl@google.com>
Cc: "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotypeimaging.com>, John Daggett <jdaggett@mozilla.com>, Christopher Slye <cslye@adobe.com>, "www-font@w3.org" <www-font@w3.org>, "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>
On Fri, May 21, 2010 at 12:25 AM, Adam Langley <agl@google.com> wrote:

> On Thu, May 20, 2010 at 6:19 AM, Robert O'Callahan <robert@ocallahan.org>
> wrote:
> > Lobby UAs to do that. For open-source UAs, contribute patches to do that.
> > That's really all you can do. Trying to legislate it through spec text is
> > going to be painful, clumsy and ineffective.
> If it helps settle the question then I can state that Chrome, for one,
> will never try to drag an XML parser into the font rendering pipeline
> just to validate metadata; irrespective of the spec.
> Nor will we accept patches to do so.

Nor would we in Firefox.

We might, however, accept patches to expose font metadata through scriptable
APIs, and patches to display that data in tools like Firebug or even the
Page Info feature in Firefox.

"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, 20 May 2010 23:20:41 UTC

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