i18n support

[cmbirk]

It looks like we have 2 good options for i18n, angular-translate and angular-gettext.

There's a debate between the two creators on this GH issue:

rubenv/angular-gettext#3

and a decent post on the subject here

http://blog.trifork.com/2014/04/10/internationalization-with-angularjs/

@eduard-k and @savajr does this approach work for you guys as well?

[Vanuan]

As I see Madison is not a single page application, so I don't see advantage over Lavarel i8n

[cmbirk]

The 1.8 milestone includes a single page application structure for Madison.

[cmbirk]

Moving this to 2.0 milestone

[Vanuan]

Another option is built-in angular 1.4 support: https://github.com/angular/i18n

[barryvdh]

So, is there any update on this?

[krusynth]

Actually, yes! I got most of this figured out over on the editor in opengovfoundation/madison-editor@9f2f080 and I'm implementing this in Madison today.

[krusynth]

Ok, I've made a big dent in this. You should be able to create your own locale files and add them in the public/locales folder, matching the format of the en_US.json one I've created.

There are a few outstanding pieces of this that I haven't had time to deal with, and I could certainly use some help on these.

Remaining Work

• Add internationalization for emails Add internationalization for emails #658
• Check internationalization for datepicker Check internationalization for datepicker #659
• Add internationalization for serverside errors. Add internationalization for serverside errors. #660
• Internationalization for database content. Internationalization for database content. #661
• Internationalization for intro message. Internationalization for intro message. #662
• Emails: Internationalization & Templates Emails: Internationalization & Templates #975
• User notification settings User notification setting descriptions need to be localized #974
• Artisan CLI commands need internationalization Artisan CLI commands need internationalization #982
• Annotator needs internationalization Annotator internationalization #987

There are, of course, probably other issues I haven't thought of or encountered yet as well. I also need to write up documentation on the translations, but we're using Angular Translate for this if that helps.

[krusynth]

This is all in the i18n branch at the moment, but will get merged into master very soon.

[krusynth]

This is now in master, but this issue will remain open until those five items are resolved. Also - if you do create a new locale file please contribute it back via a Pull Request to the main repo! We really could use a lot of help on this front!

[krusynth]

Updated this with new items.

[sethetter]

In v4, site is fully i18n'd, just lacking translations.