[keycloak-dev] Evaluation of i18n/i10n tools

[Stan Silvert]

I've been evaluating tools to help us localize Keycloak.  The tools I 
looked at were angular-translate, angular-localization, and 
angular-gettext.  All use the MIT license.

I took a static version of our login page and localized with 
angular-translate.  Then I did the same thing using 
angular-localization.  Both worked well and it was pretty cool to see 
the language change between English and French with the click of a 
button.  Both use ordinary JSON files for the translations.

In doing this, I was able to explore the features, strengths, and 
weaknesses of each library.  Of the two, I prefer angular-translate.  
The reason mostly has to do with a greater feature set, maturity, and a 
larger community.  I can go into much greater detail if anyone is 
interested.

For angular-gettext, it seems to be somewhat popular, but it takes a 
very different approach.  I'm rejecting it based on the fact that it 
relies a great deal on tools and automation.  I don't think that 
translators and developers want to learn new tools and a new file format 
for the translations (.po files vs. JSON).  Plus, angular-gettext 
automatically uses the English version of the word or phrase to generate 
keys in the .po files.  The whole process looks error-prone.

If you have any experience using these or other packages please let me 
know.  In researching this topic, I've found that some people even roll 
their own angular translation tools.  So let me know if you have 
experience with that as well.

Stan