Changes between Version 55 and Version 56 of BluePrint/Internationalisation


Ignore:
Timestamp:
04/30/13 14:31:43 (11 years ago)
Author:
nownikhil
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Internationalisation

    v55 v56  
    119119* 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:-
    120120
    121     1. Use the parse tree approach to parse out the currently active template from 000_config.py
    122 
    123     2. Next, we parse the eden/private/templates/<current-template>/config.py to get the active modules of that template
    124 
    125     3. So, only these modules will be checked by default (when showing the module selection page)
    126 
    127     4. Hence, we know which modules correspond to the current template and this can be used to extract only the relevant strings.
     121    * Use the parse tree approach to parse out the currently active template from 000_config.py
     122
     123    * Next, we parse the eden/private/templates/<current-template>/config.py to get the active modules of that template
     124
     125    * So, only these modules will be checked by default (when showing the module selection page)
     126
     127    * Hence, we know which modules correspond to the current template and this can be used to extract only the relevant strings.
    128128
    129129* 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:-