The facility search should support different languages based on locale
All text presented to the end user should be translatable, so that it can be presented in the users native language.
All strings in the program should be marked as translatable, and a directory with sample i18n.properties should be created.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Hans Joachim Desserud
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
m4-2010
- Started by
- Hans Joachim Desserud
- Completed by
- Hans Joachim Desserud
Whiteboard
i18n is back on track! From looking at another module and experimenting with changing this I discovered the translation templates needs to be placed in the folder
org/hisp/dhis/de/
This will cause dhis2 to automatically inject the correct string in $i18n.getString(). I have now implemented this, and replaced #stext were it had been used. We stick to getString for the future.
Remaining:
All strings should have been added to the template to be translatable.
As far as I can tell, are strings which should be translatable, are present in the template. We have also included norwegian translations as a proof-of-concept it works.
There have been some minor issues, where some of the strings have been misleading, though I these have been fixed when they were spotted.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
