Changes between Version 60 and Version 61 of BluePrint/Internationalisation

Timestamp:

04/30/13 14:36:58 (12 years ago)

Author:

nownikhil

Comment:

--

BluePrint/Internationalisation

@@ -125 +125 @@
 * Including database variables : We need to extract the strings in database variables so that they too can be translated. Currently, these variables are excluded from translation. Hence, one approach to extract these strings is as follows:
     * Use the prepop csv files in privates/templates/<current-template> and mark them to be considered for translation.
-    *Provide a “Select all templates” option on the module selection page (similar to select all modules) to specify if all prepop files are to be considered. This option will be helpful when introducing new variables and discarding deprecated strings using the overwrite option as mentioned earlier.
+    * Provide a “Select all templates” option on the module selection page (similar to select all modules) to specify if all prepop files are to be considered. This option will be helpful when introducing new variables and discarding deprecated strings using the overwrite option as mentioned earlier.
 
       
-
-* Pootle Integration : We need to make sure that the translation in pootle is kept in sync with that in the “.py” languages file. Below are few points to help us achieve this :-
-
+* Pootle Integration : We need to make sure that the translation in pootle is kept in sync with that in the “.py” languages file. Below are few points to help us achieve this :
     * As and when we use the overwrite option to remove deprecated strings,(as explained earlier)  reflect these changes in pootle too. This will ensure that pootle doesn’t have any old strings and that new strings are also added.
     * When merging from pootle, we might receive some conflicts ( just as through pull request). One possible solution is to create a script that identifies and stores all such conflicts in a file which can then be manually handled by translators.