Changes between Version 28 and Version 29 of BluePrint/Translation


Ignore:
Timestamp:
08/19/13 14:00:47 (8 years ago)
Author:
nownikhil
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Translation

    v28 v29  
    8080   * Initially we merge the translations between pootle and py such that translations in py are given preference. If pootle has translations that py doesn't,  then those get added. This merged set of strings is reflected in both pootle and py. This creates an initial sync between the two.
    8181
    82    * now when someone requests for an Excel file for translation, we check pootle for any updated strings since last sync. If any, we merge them to py files and provide the translator with an updated set of strings in the Excel file. Hence this way py is kept in sync with pootle regularly.
     82   * Now when someone requests for an Excel file for translation, we check pootle for any updated strings since last sync. If any, we merge them to py files and provide the translator with an updated set of strings in the Excel file. Hence this way py is kept in sync with pootle regularly.
    8383
    84    * after a csv file is submitted to Eden after translations,  we update both py and pootle with the changes. (Anything changed in csv implies earlier translation from pootle has to be overwritten).
    85 There might be small chances of conflict here in case pootle is updated between the time when Excel file was requested and csv file was submitted.  In this case we can probably prefer the csv strings or maybe store conflicts in a separate file to be manually sorted out.
     84   * After a csv file is submitted to Eden after translations,  we update both py and pootle with the changes. (Anything changed in csv implies earlier translation from pootle has to be overwritten).
    8685
    87 
     86   * Implementation Details:
     87       * first --
    8888
    8989== Other Links ==