- From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
- Date: Fri, 21 May 2010 06:29:33 -0400
- To: Erik van Blokland <erik@letterror.com>
- CC: Jonathan Kew <jfkthame@googlemail.com>, Adam Langley <agl@google.com>, "robert@ocallahan.org" <robert@ocallahan.org>, 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>
This was my understanding as well but I wanted to make sure this is the case. Technically there are no obstacles for UA to show metadata content on user request but for user to have this option UA must enable it. Regards, Vlad Sent from my iPhone On May 21, 2010, at 12:08 PM, "Erik van Blokland" <erik@letterror.com> wrote: > > On 21 mei 2010, at 11:31, Levantovsky, Vladimir wrote: > >> If this is not the case, I would like to explore the possibility of >> providing alternative ways of encoding metadata - e.g. as simple >> HTML in <fontInfoDialog/> element (or whole metadata as pure HTML/ >> CSS content). In this case, for a browser to satisfy user desire to >> see the metadata it would have to do what it already does best - >> show the HTML content provided by a font vendor in a separate pop- >> up window. > > I think there is about a week's worth on enbedding html in the W3 > list archive somewhere. > I don't think a UA will have *any* problem with rendering a couple > of XML fields into html. Let's not go there again, please. > > Erik
Received on Friday, 21 May 2010 10:30:46 UTC