Interface translations

[brylie]

Story

As a non-English speaking user
I would appreciate if the userface elements, such as inline-help, were translated
So that I can easily navigate the interface

Example

As a non-English language speaker, I

1. Look for a link to 'change language'
2. Click to select the appropriate language for my needs

Dependencies/relationships

• Internationalization (i18n)
• Localization (l10n)
• Accessibility (a11y)

Support this issue

[kyyberi]

I have experience in this from several projects. I would gladly translate to Finnish. In Rails i18n is in good shape, http://guides.rubyonrails.org/i18n.html. Before going any deeper with the UI development, this might be a good moment to add the translations (.yml) logic in the structure

[GUI]

Great idea. The admin app is a Rails app, but must of the interface is actually being rendered by Ember.js and Handlebars templates. So I think it would be good to implement an i18n solution that will support both Rails and Ember.

There's ember-i18n, but that looks to be Ember only. What looks like a better is the solution the Discourse folks outlined here. They're using i18n-js for the javascript side of things, which hooks into the default yaml localization files from Rails. This would let us maintain only one set of localization files we could maintain regardless of whether the interface is being rendered server-side or client-side.

[ccsr]

I have backed this up with bounty on https://www.bountysource.com/issues/6023540-interface-translations

[GUI]

I forgot to mention this, but a while back, I laid the foundation for both server-side and client-side translations. Both use the Rails config/locales/*.yml files, so all the translations should be consolidated there. When working on new features I've tried to only use localized strings in the UI. There's still a fair bit of work to update all the rest of the existing UI to use localized strings, but some of it is in place (admin menus and I think most of the API Backends form).

Here's the current translations: https://github.com/NREL/api-umbrella-web/blob/master/config/locales/en.yml

I've also been playing with some different services to help manage translations. Here's our project on OneSky: https://nrel-gov.oneskyapp.com/collaboration/project?id=47156 If you signup, they provide an interface for managing translations, tracking progress, dealing with updates, etc. Or if you'd prefer to stick to the raw YAML files and git, pull requests are welcome. Or if you have any other preferred ways of dealing with translations, I'm more than open to suggestions.

So while this isn't done yet, hopefully these pieces are at least a start towards making translating the entire app easier.

[brylie]

Can we use a service such as Transifex to collaborate on these translations? We can help with the Finnish translation.

[GUI]

Did you check out our translations on the OneSky account I linked to? OneSky should be a service that's very similar to Transifex. I had played with both services and mainly used OneSky since it seemed a bit easier to figure out than Transifex, but that's just me. I've never actually done translations before, so if you're familiar with Transifex, or you'd simply prefer that service for any reason, just let me know and I'm happy to get us setup over there instead.

[brylie]

Ah, my bad. I obviously didn't catch that link, sorry.

[perfaram]

Hmmm, I could translate the UI to french.

[kyyberi]

I can do Finnish translation

[GUI]

@perfaram: I saw you added the French translations in OneSky. Thank you! I've pulled those into master at NREL/api-umbrella-web@603a77e

[brylie]

Yay Team Finland (@kyyberi and Vesa)! 62% completed :-)

[kyyberi]

92,8% :D I just got home and had some time to translate a few more