Changes between Version 25 and Version 26 of BluePrint/Translation

Timestamp:

07/11/13 08:43:47 (12 years ago)

Author:

nownikhil

Comment:

--

BluePrint/Translation

@@ -35 +35 @@
 * 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.
-
+    * Use S3BulkImporter to get list of csv files from tasks.cfg file in the template folder.
+    * Use S3Represent to see which all csv files are to be considered for translation.
+    * Only name field is being considered for translation, think of a framework on how to select relevant fields from a csv.
       
 * 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 :
@@ -42 +43 @@
     * 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.
     * Also, an option for uploading ".po" files will be provided (apart from the current ".csv" files). The conflicts arising when merging this can be handled as mentioned before. 
+    * Also, upload the updated .po file back to the server.
 
 Hence, the translations in pootle and web2py will be consistent.