News for hackers. Stuff that matters.
Re:YAML: Probably not so great after all by johnchristopher on Sunday August 18, 2019 @04:04PM (#20732486)
What if it's to be used by french speaking software/people ?

    <lunch
      env="outside"
      envfr="dehors"
      food="sandwiches"
      foodfr="sandwichs"
      drink="cola"
    />
Or

    <lunch
      env="outside"
      food="sandwiches"
      drink="cola">
          <label type="env" language="fr">Dehors</label>
          <label type="env" language="de">Außenseite</label>
          <label type="env" language="en">Outside</label>
    </lunch>
Quite curious about it.
Re:YAML: Probably not so great after all by yosamino on Sunday August 18, 2019 @05:18PM (#20732950)
I guess this way:

  <lunch
    env="outside"
    food="sandwiches"
    drink="cola">
    <label xml:lang="fr">Dehors</label>
    <label xml:lang="de">Draußen</label>
    <label xml:lang="en">Outside</label>
  </lunch>
says[0]the w3.

[0]https://www.w3.org/TR/REC-xml/#sec-lang-tag

Re:YAML: Probably not so great after all by johnchristopher on Monday August 19, 2019 @11:40AM (#20738710)
I see, thanks. (I also see you corrected my broken German ^^).
Re:YAML: Probably not so great after all by snuxoll on Sunday August 18, 2019 @05:05PM (#20732854)
Putting l10n/i18n data inline is generally not a pleasant experience, and this problem persists regardless of what serialization format you are using. Either have separate data files per-locale that are merged with the defaults or store the localized strings in a central location (ala your usual gettext setup).