Changes between Version 65 and Version 66 of BluePrint/Internationalisation

Timestamp:

01/05/15 14:51:51 (10 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/Internationalisation

@@ -132 +132 @@
 * Retrieval of strings from currently active template :  Currently, we don’t have an option to check which strings are present in the active template. This can be done as follows:
     * Use the parse tree approach to parse out the currently active template from 000_config.py
-    * Next, we parse the eden/private/templates/<current-template>/config.py to get the active modules of that template
+    * Next, we parse the eden/modules/templates/<current-template>/config.py to get the active modules of that template
     * So, only these modules will be checked by default (when showing the module selection page)
     * Hence, we know which modules correspond to the current template and this can be used to extract only the relevant strings.
 
 * 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.
+    * Use the prepop csv files in modules/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.