make all user visible strings localizable
Currently many strings in Quantum are not defined with gettext and not
localizable. So the main goal of this blueprint is to make user visible
strings localizable.
In order to spread the task and reduce the difficulty of code review, I will split the commit into multiple isolated patches. Each module and each plugin will be a separate patch.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Alex Xu
- Definition:
- New
- Series goal:
- Accepted for grizzly
- Implementation:
-
Implemented
- Milestone target:
-
2013.1
- Started by
- dan wendlandt
- Completed by
- dan wendlandt
Related branches
Sprints
Whiteboard
Alex has made great progress on localization and the review queue is now empty: https:/
Since this item is labeled as 'high' priority, we need to set a milestone target. G-1 is basically, over, so either G-2 or G-3 would be best. See: http://
Gerrit topic: https:/
Addressed by: https:/
make strings under api directory localizable
yong sheng gong: How is the BP going? Do u have any plan?
Addressed by: https:/
Correct i18n message for log
Addressed by: https:/
Correct i18n message for ovs plugin
Addressed by: https:/
Correct i18n message for api and db module
Addressed by: https:/
Add check for i18n message in run_test.sh
Addressed by: https:/
Correct i18n message for linuxbridge plugin
Addressed by: https:/
Correct i18n message for metaplugin
Addressed by: https:/
Correct i18n message for nicira plugin
Addressed by: https:/
Correct i18n messages for bigswitch plugin
Work Items
Work items:
use _() to wrap the message for LOG.xxx(): TODO
in API, the error msg returned from quantum is localized according to client's accept language.: TODO
Generate project pot file: TODO
