Changes between Version 56 and Version 57 of BluePrint/Internationalisation


Ignore:
Timestamp:
04/30/13 14:32:30 (9 years ago)
Author:
nownikhil
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Internationalisation

    v56 v57  
    117117* Removal of Deprecated Strings : Size of  “.py ” files will keep on increasing if the new strings are merged with the existing strings. As changes are made to code some strings become deprecated while some new strings are introduced.  So we can run the code with all the modules selected periodically and replace the existing files. This will remove all the deprecated strings and new strings will be available for translation. This can be done by using the “-o” option in the existing translation module which will overwrite the existing “.py” files instead of merging with them. This can be made into a scheduler job which can run periodically or it can be manually triggered by the admin as and when appropriate.
    118118
    119 * 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:-
    120 
    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.
     119* 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:
     120
     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:-