Changes between Version 132 and Version 133 of Event/2011/GCI

Timestamp:

12/17/11 05:57:12 (13 years ago)

Author:

Michael Howden

Comment:

--

Event/2011/GCI

@@ -325 +325 @@
 === Translating key phrases ===
 '''''Migrated'''''[[br]]
-Each task consists of a language file (a spreadsheet) of about 100 phrases, see the attachments at the bottom of this page, masterLanguageFile1.csv, masterLanguageFile2.csv and masterLanguageFile3.csv. This file needs to be translated to the target language, with the translation in the target column.
+Each task consists of a language file (a spreadsheet) of 100 or 200 phrases (depending on the difficulty of the task), see the attachments at the bottom of this page, masterLanguageFile1.csv, masterLanguageFile2.csv and masterLanguageFile3.csv. This file needs to be translated to the target language, with the translation in the target column.
 
 Each phrase is related to data displayed on screens on the default home page, the registration page the login and out process and the personnel profile.
+
+If there are phrases which you don't understand, for example incomplete sentences, please identify these separately from your translation when you submit your task. This may indicate poor internationalization of the phrases in the code which our team will need to improve. These strings can still count towards your total.
 
 Depending upon the target language some of these phrases have already been translated but you don't need to worry about what has and what has not been translated.
@@ -369 +371 @@
 
 Check for:
-* Incomplete or cut-off sentences in the translation strings
+* Incomplete or cut-off sentences in the translation strings 
 * Avoid concatenation of localized strings with variables - use %s or %(key)s instead.  That is, instead of:[[br]]
   {{{T("My name is ") + name}}}[[br]]