| | 80 | == User Stories == |
| | 81 | As a translator : |
| | 82 | |
| | 83 | I would not want to translate Deprecated Strings |
| | 84 | |
| | 85 | As a system admin I would want to: |
| | 86 | |
| | 87 | Keep the size of .py files small |
| | 88 | |
| | 89 | Allow integration with pootle |
| | 90 | |
| | 91 | Provide strings only from Active Templates to save time of translators. |
| | 92 | Avoid conflicts when updating. |
| | 93 | |
| | 94 | == Current Implementation == |
| | 95 | The current translation functionality in Sahana-Eden does the following ( Most of these are in s3translate.py file) :- |
| | 96 | |
| | 97 | a) Provide a menu to select a list of modules from which strings are to be translated ( doesn’t default modules corresponding to active template) |
| | 98 | |
| | 99 | b) Extract strings from the selected modules using parse tree approach. Also extracts strings of deployment.settings variables (but not database variables) |
| | 100 | |
| | 101 | c) Strings can be exported in xls and po formats |
| | 102 | |
| | 103 | d) Merges uploaded translations ( in csv) with the existing .py language file ( doesn’t overwrite) |
| | 104 | |
| | 105 | e) Pootle translations are not synced currently. |
| | 106 | |
| | 107 | f) Doesn’t account for conflicts due to pulls and pomerge. |
| | 108 | g) External dependencies due to calls to methods in Translate Toolkit |
| | 109 | |
