Ensure all murano projects are ready for i18n and l10n
Currently not all user-facing strings in murano are marked for translation. Moreover even if the strings are marked for translation — the tools to perform the translation are not always there.
We should ensure, that we use oslo_i18n to mark all user-facing strings for translation
We should ensure, that we use correct tools (for example horizon switched from makemessages to babel and django-babel, to facilitate js translation)
We should ensure, that every murano-project is ready to be translated
We should integrate murano translation efforts with zanata https:/
We should allow convenient and easy extraction and translation of MuranoPL strings. Users locale should be captured at deploy time and messages should be translated accordingly. .mo or similar files should be supplied with the apps themselves.
Blueprint information
- Status:
- Complete
- Approver:
- Serg Melikyan
- Priority:
- Medium
- Drafter:
- Kirill Zaitsev
- Direction:
- Approved
- Assignee:
- Kirill Zaitsev
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Kirill Zaitsev
- Completed by
- Kirill Zaitsev
Related branches
Related bugs
Bug #1311084: [dashboard] Strings in dynamic UI are not passed through standard gettext machinery | Invalid |
Bug #1377883: Localization in murano doesn't work | Invalid |
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Adds i18n machinery similar to the one used in horizon