Changes between Initial Version and Version 4 of Ticket #6171


Ignore:
Timestamp:
12/19/2017 02:04:34 PM (3 years ago)
Author:
saroyanm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6171

    • Property Cc saroyanm Sebastian tlucas Shikitita greiner added
    • Property Component changed from Automation to User-Interface
    • Property Summary changed from Allow to im-/export translation to a csv file to Allow to import and export translations to a csv file
    • Property Priority changed from Unknown to P1
    • Property Ready set
  • Ticket #6171 – Description

    initial v4  
    11=== Background === 
    2  
    32To streamline the translation process we want to automate the handling of agency translation. 
    43 
    54=== What to change === 
    6  
    7 Allow to export the translations from the JSON files to the following format: 
    8  
    9 - A excel csv file (`csv.writer(csvfile, dialect='excel')`) named ''translations-REPOSITORY-HEAD.csv`` e.g. ''translations-adblockplusui-0e99fec067ea.csv'' 
    10 - A column that contains the SourceString headed SourceString 
    11 - A column that contains the description from the main (en_US) language headed description 
    12 - A additional column for each existing language headed with the language code used in the filename e.g. en_US, de, etc. 
    13  
    14 Example: 
    15 ||SourceString||Description||en_US||de||etc.|| 
    16 ||options_tab_general||Sidebar tab label||General||Allgemein||etc.|| 
     51. Allow to export the translations from the JSON files to CSV containing information below: 
     6- A column that contains String ID 
     7- A column that contains Description Of the String 
     8- A column that contains All placeholders that can be used in the String with examples 
     9- An additional column for each supported languages 
    1710 
    1811 
    19 Allow to import the file described above. 
    20  
    21 - For each SourceString in the file identify the corresponding JSON file of the main language (en_US). If it cannot be found print an error message containing the error and the SourceString. 
    22 - Otherwise for each SourceString update the description in the corresponding JSON file if it's not empty 
    23 - And for each language update the translation (if not empty) in the corresponding language specific JSON file. If the translation doesn't exist add it add it first. If the file doesn't exist create it first. 
     122. Allow importing CSV file structured described above and update JSON files accordingly.