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. Rob -- "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 53:5-6]
Received on Thursday, 20 May 2010 23:20:38 UTC