- From: Tal Leming <tal@typesupply.com>
- Date: Tue, 25 May 2010 13:36:50 -0400
- To: Håkon Wium Lie <howcome@opera.com>
- Cc: Sylvain Galineau <sylvaing@microsoft.com>, "Levantovsky, Vladimir" <Vladimir.Levantovsky@MonotypeImaging.com>, "robert@ocallahan.org" <robert@ocallahan.org>, Jonathan Kew <jfkthame@googlemail.com>, Adam Langley <agl@google.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 May 25, 2010, at 12:58 PM, Håkon Wium Lie wrote: > Also sprach Tal Leming: > >>>> We explored other formats, but we kept coming back to XML for its >>>> extensibility. The nesting came out of the need for enabling >>>> localization, among other things. >>> >>> Could you give some examples? >> >> Of the other formats or the localization needs? > > Mostly the latter. But I'm happy to see your notes on other formats, > too :) Localization: The OTF/OFF name table spec [1] allows for every name ID to be localized. I've seen this functionality used. Formats: XML, HTML, property-list, binary, JSON (I think). I even made an ill-fated attempt to flatten everything into key/value pairs. ;-) Tal [1] http://www.microsoft.com/typography/otspec/name.htm
Received on Tuesday, 25 May 2010 17:37:49 UTC