Translated or localized titles and descriptions

[zejn]

Titles and descriptions should support more than one language.

One possible (not necessarily best) solution is the title being either a string

{
    "title": "Foo Package"
}

or an object:

{
    "title": {
        "en": "Foo Package",
        "de": "Foo Paket"
    }
}

[Stiivi]

Good idea to have a localization. On the other hand, from my experience with localizable metadata, it is good to have it separate from the main metadata structure for multiple reasons:

1. makes parsing the main metadata way much easier (in this case it makes much easier to conform to the standard)
2. makes inclusion of other translations very easy – just add another translation file

Have it a separate JSON, for example: locale_XX.json or locales/XX.json with contents:

{
    "fields": [
        "NAME" : { "label": "TRANSLATED_LABEL", "description": "TRANSLATED_DESCRIPTION" }
    ]
}

Someone supplies a translation? Just include the file in the data package and you are ready to deploy!

[rufuspollock]

See also #42 (i18n for data package)

[rufuspollock]

DUPLICATE of #42