Ensure all mistral projects are ready for i18n and l10n

Registered by Sharat Sharma on 2016-11-28

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://translate.‚Äčopenstack.‚Äčorg and allow easy and automatic translation imports.

Blueprint information

Status:
Started
Approver:
Renat Akhmerov
Priority:
Medium
Drafter:
Sharat Sharma
Direction:
Approved
Assignee:
Sharat Sharma
Definition:
Approved
Series goal:
None
Implementation:
Blocked
Milestone target:
None
Started by
Renat Akhmerov on 2016-11-28

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-i18n,n,z

Addressed by: https://review.openstack.org/403639
    Initial commit for mistral-i18n support

Gerrit topic: https://review.openstack.org/#q,topic:supporti18n,n,z

Addressed by: https://review.openstack.org/413965
    Support i18n for LOG.warning

Addressed by: https://review.openstack.org/414498
    Support i18n for LOG.warning

Addressed by: https://review.openstack.org/414893
    Use i18n for help text

Addressed by: https://review.openstack.org/417833
    Initial commit for mistral-i18n support

Addressed by: https://review.openstack.org/417851
    Support i18n for LOG.warning

Addressed by: https://review.openstack.org/430866
    Support i18n for LOG.warning

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.