Feature request : managing static translations

[jloosfelt]

After a short experience with translated websites, and reading some interesting remarks in the Google Group, here is my feedback and feature request to help manage them.

There are 2 types of content that must be translated :

• "static data", that should be considered as part of design, like "learn more" links, non-editable bloc titles ("news"), "x comments", "is invalid"...
• "editable data", which concerns the editor role.

For the first one I would like to use tags like

{{ 'general.learn_more' | translate [locale: en] }}

(i18n style, with fallback to default_locale)

The translations could be pushed using yaml files with the editor, and in the backoffice we would have a controller to manage them in any language. I guess only designer and administrator roles are authorized to change them.

This way it would make it possible to avoid html duplication to manage every language.

I'd like to hear some feedbacks of this idea ? What should be the right practice ?

[gabrielnau]

Great idea ! Still I think there is some edge cases where it would be needed to be able to define an entire different template per locale, but it would be a great start !

[jloosfelt]

Exactly! we need to choose for each page if we prefer to use a different template per locale or not.

[did]

Santa Claus is coming sooner this year. Someone will implement it next week :-)

[gabrielnau]

Great !

[kenglishhi]

This would be awesome to have.

[Papipo]

Done in my fork (https://github.com/Papipo/engine/tree/translations), but I need UI advice. I'm new to locomotive and all views are quite hardcoded, so even if the feature works, the list and form look awful.

[did]

great job Rod ;-)

[did]

this commit enhances Rod's pull request.