Different languages/Translations

[The One]

Sencha Architect 2.2 (coming soon) will include a new feature called process config.

This allows you to integrate ideas like Localizer much more easily. More details to come from the author of this feature.

Wonderful. Worth the two year wait I guess. Can't wait to hear more.

[Zeigon]

In my opinion, using a localization system with the English (or any other language) translation as the key of the translations file is wrong. I'm all for string keys with generic names that make life easier and (among other things) don't bloat the files with unnecessary text . Like in Android and, as far as I know, unlike in iOS, which also uses translations as keys.

Looking at the code of the Localizer class, the format of the locale files could be changed to something like <ComponentID>.<PropertyName>, i.e.:

//en.js
{key: "buttonBrowse.text", value: "Browse..."},
{key: "buttonBrowse.tooltip", value: "Browse for a file."},

//es.js
{key: "buttonBrowse.text", value: "Explorar..."},
{key: "buttonBrowse.tooltip", value: "Elige un archivo."},

So you could continue iterating through the localizable properties but instead of checking for the English string you would do it exactly for the element and property that you want. You could even implement a fallback method where in the case that you couldn't find a translation in a certain locale (replace==null) you could still use the English text as a last resort. This might require to load the English strings no matter what the current locale were or implement some kind of on-the-fly string loading, although I don't think this would be necessary.

[ssamayoa]

In my opinion, using a localization system with the English (or any other language) translation as the key of the translations file is wrong.

Could be but Localizer is, as I said, for all those exiting applications which must be translate without too much coding or for those generated with *CURRENT* version of Architect.

Regards.

[Zeigon]

Well, I was just saying because now that someone took the time to create this class, github project, etc. to share the Localizer with everyone, maybe we could all contribute with some ideas that might improve it. Besides, now that the big effort is already made I don't think it'd require too much extra coding.

[ssamayoa]

FWIW, after almost a year I wrote the original code, I will start to use Localizer.

Regards.