Ensure all mistral projects are ready for i18n and l10n
Add oslo_i18n support to mistral
Currently user-facing strings in mistral are not marked for translation.
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 mistral-project is ready to be translated
We should integrate mistral translation efforts with zanata https:/
Blueprint information
- Status:
- Started
- Approver:
- Renat Akhmerov
- Priority:
- Medium
- Drafter:
- Sharat Sharma
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Blocked
- Milestone target:
- None
- Started by
- Renat Akhmerov
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Initial commit for mistral-i18n support
Gerrit topic: https:/
Addressed by: https:/
Support i18n for LOG.warning
Addressed by: https:/
Support i18n for LOG.warning
Addressed by: https:/
Use i18n for help text
Addressed by: https:/
Initial commit for mistral-i18n support
Addressed by: https:/
Support i18n for LOG.warning
Addressed by: https:/
Support i18n for LOG.warning
