Changes between Version 2 and Version 3 of Message_Extraction


Ignore:
Timestamp:
Apr 25, 2014, 11:54:35 AM (10 years ago)
Author:
sanderd17
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Message_Extraction

    v2 v3  
    22
    33'''Message extraction''' is the process of parsing the source files searching for strings that need to be translated, and generating a translation template file (POT) that contains those strings. Translators can use the generated POT file to create a translation file (PO) for a specific locale.
     4
     5= Generating Translation Templates =
     6
     7When you only want to update the translations (i.e. you have good `messages.json` files described below), you can run the `source/tools/i18n/updateTemplates.py` script to generate the defined translation template files (POT). Each file is generated on the `l10n` folder where it is defined, with the name specified in the `messages.json` file.
     8
     9When you updated the POT files locally, be sure to pull the existing PO files from Transifex as backup before you upload the POT (using the pullTranslations.py tool). As the PO and POT files are under version control, you can see the difference in the SVN diff output. If you have assured yourself that the changes to the POT files are sensible, you can just commit all POT and PO files. Transifex is configured to pull the changes to the POT files from our SVN once a day. So the translators will receive your updates with a small delay.
    410
    511= Configuring the Generation of Translation Templates =
     
    242248If you want to force the extracted messages ''not'' to have a format identifier, specify the special format identifier `none` as the value of the `format` property.
    243249
    244 = Generating Translation Templates =
    245 
    246 Once you have the `messages.json` files in their `l10n` folders, you can run the `source/tools/i18n/updateTemplates.py` script to generate the defined translation template files. Each file is generated on the `l10n` folder where it is defined, with the name specified in the `messages.json` file.
     250
     251
     252To extract the actual messages with the given rules, please see the top of the page.
     253