RE: WOFF and extended metadata

For Håkon 's proposal, to get list of strings to display for "en-US", I'll have to check groups for "en-US", then (if not present) "en" and then fallback to some other language. Or should I merge list of strings from "en" and "en-US"? This already introduces ambiguity and tools will break it almost for sure trying to save space. 

Compare this to: get list of strings by simply enumerating <items>. For each of them walk <name> and <text> tags and choose one with best language. This will be one pass through <extensions>, without ambiguity.

I do not worry about repetition and depth level, if it is easily readable, which it is in this case.

Thanks,
Sergey

-----Original Message-----
From: public-webfonts-wg-request@w3.org [mailto:public-webfonts-wg-request@w3.org] On Behalf Of Dave Crossland
Sent: Wednesday, June 02, 2010 8:57 AM
To: www-font@w3.org; public-webfonts-wg@w3.org
Subject: Re: WOFF and extended metadata

On 2 June 2010 17:17, Håkon Wium Lie <howcome@opera.com> wrote:
> Also sprach Tal Leming:
>
>  > <extensions>
>  >      <group>
>  >              <!--
>  >              The author wants the UI to show:
>  >
>  >              EU Greeting:
>  >              Message: Hello!
>  >              Date: 2010-06-01
>  >
>  >              With an appropriate language chosen from the
>  >              English, Dutch and French localizations.
>  >              -->
>  >              <name lang="en">EU Greeting</name>
>  >              <name lang="nl">EU Groet</name>
>  >              <name lang="fr">EU Salut</name>
>  >              <item>
>  >                      <name>
>  >                              <text lang="en">Message</text>
>  >                              <text lang="nl">Bericht</text>
>  >                              <text lang="fr">Message</text>
>  >                      </name>
>  >                      <value>
>  >                              <text lang="en">Hello!</text>
>  >                              <text lang="nl">Hallo!</text>
>  >                              <text lang="fr">Bonjour!</text>
>  >                      </value>
>  >              </item>
>  >              <item>
>  >                      <name>
>  >                              <text lang="en">Date</text>
>  >                              <text lang="nl">Datum</text>
>  >                              <text lang="fr">Date</text>
>  >                      </name>
>  >                      <value>
>  >                              <text lang="en">2010-06-01</text>
>  >                              <text lang="nl">2010-06-01</text>
>  >                              <text lang="fr">2010-06-01</text>
>  >                      </value>
>  >              </item>
>  >      </group>
>  > </extensions>
>  >
>  > Granted, this is verbose.
>
> Yes. There's much repetition. How about:
>
> <ext lang=en>
> EU Greeting:
> Message: Hello!
> Date: 2010-06-01
> </ext>
>
> <ext lang=nl>
> EU Groet
> Bericht: Hallo!
> Datum: 2010-06-01
> </ext>
>
> <ext lang=fr>
> EU Salut
> Message: Bonjour!
> Date: 2010-06-01
> </ext>
>
> This is the minimalist in me talking, I can probably live with more
> structure, but my experience is that schemas with much structure tend
> to be less understood and, consequently, less used.

Eww no, way to laconic.

I am aware this may be too many levels deep, but I'd like to suggest:


<extensions>
 <group>
  <set lang="en">
   EU Greeting
   <item>
    Message
    <value>Hello!</value>
   </item>
   <item>
    Date
    <value>2010-06-01</value>
   </item>
  </set>

  <set lang="nl">
  EU Groet
   <item>
    Bericht
    <value>Hallo!</value>
   </item>
   <item>
    Datum
    <value>2010-06-01</value>
   </item>
  </set>

  <set lang="fr">
   EU Salut
   <item>
    Message
    <value>Bonjour!</value>
   </item>
   <item>
    Date
    <value>2010-06-01</value>
   </item>
  </set>
 </group>

</extensions>

Received on Wednesday, 2 June 2010 16:24:43 UTC