Changes between Version 120 and Version 121 of Event/2011/GCI

Timestamp:

12/14/11 10:36:37 (13 years ago)

Author:

Fran Boon

Comment:

Improve wording

Event/2011/GCI

@@ -334 +334 @@
 PLEASE STATE WHICH LANGUAGE YOU WISH TO TRANSLATE INTO WHEN YOU CLAIM THIS TASK.
 
-=== Review code for quality of localized strings ===
-'''''Migrated'''''[[br]]
-You will need to review all the localised strings in the model and controller files for a single module, eg:
-* controllers\gis.py & models\gis.py
-* controllers\hrm.py & models\hrm.py
-* controllers\default.py (not a module, but still important)
+=== Review code for quality of internationalized strings ===
+'''''Migrated'''''[[br]]
+All Strings which appear in the user interface, such as in menus and forms and help info, should be Internationalized, so that they are available to be Localised into different languages. This is done bty wrapping the strings in T(), e.g. T("This string is Internationalized and so can be translated")
+
+Strings inside T() should, by default, be in US English.
+
+For GCI, you will need to review all the internationalized strings in the model and controller files for a single module, eg:
+* {{{controllers\gis.py}}}, {{{models\gis.py}}}, and {{{views/gis/*.html}}}
+* {{{controllers\hrm.py}}}, {{{models\hrm.py}}}, and {{{views/hrm/*.html}}}
+* {{{controllers\default.py}}} and {{{views/default/*.html}}}
 
 Check for:
-* Identify any strings that have not been properly marked to be localised:
- * Strings that users will see need to be localized -- these are strings that appear in the user interface, such as in menus and forms and help info.
- * Not all strings need to be localized, and some definitely should not be.
-  * Strings that are used as keys in dicts, e.g. `{"this_is_a_key": 5}`, should not be localized.
-  * A string that is intended to be in one specific language should not be localized.
- * Strings that need to be localized should have `T( )` around them.
 * Avoid concatenation of localized strings with variables - use %s or %(key)s instead.  That is, instead of:[[br]]
   {{{T("My name is ") + name}}}[[br]]
@@ -357 +355 @@
   {{{T("The item %(item)s is not available in %(place)s.") % {"item": item, "place": location.name}}}}[[br]]
   This is better because the word order is not the same in all languages -- in the second form, the translator can move where the variables are inserted.
-* Avoid non-keyboard, non-English characters.
- * The strings in {{{T( )}}} are keys that are used to look up translated strings. By convention, the key strings are in English.
- * Excel doesn't handle non-English characters well when it is used to manage translations.
-* Make sure wording / terminology is consistent -- don't use different strings that mean the same thing, e.g. if there is {{{T("My name is")}}} in one place, don't use {{{T("I am called")}}} somewhere else.
+* Identify any strings that have not been wrapped in T()
+ * Note: Not all strings need to be localized, and some definitely should not be:
+  * Strings that are used as keys in dicts, e.g. `{"this_is_a_key": 5}`, should not be localized.
+  * A string that is intended to be in one specific language should not be localized (e.g. the Language names in the Language selector in {{{deployment-templates/models/000_config.py}}}).
+* Consider improving consistency of wording / terminology - don't use different strings that mean the same thing, e.g. if there is {{{T("My name is")}}} in one place, avoid using {{{T("I am called")}}} somewhere else.
 
 You will need to download a working branch of Sahana Eden code for this task and push the changes you make to your own branch on Launchpad.
-
 
 == '''User Interface & Usability''' ==