Jump to: navigation, search

Difference between revisions of "I18n/Tools"

(Tools related with document translation)
Line 14: Line 14:
 
=== Slicing script ===
 
=== Slicing script ===
  
The [[https://github.com/openstack/openstack-manuals/blob/master/tools/generatepot slicing script]] has dependency to package "xml2po". So you have to install gnome-doc-utils before running it.
+
The [https://github.com/openstack/openstack-manuals/blob/master/tools/generatepot slicing script] has dependency to package "xml2po". So you have to install gnome-doc-utils before running it.
  
 
<pre><nowiki>
 
<pre><nowiki>
Line 30: Line 30:
 
=== Merging script ===
 
=== Merging script ===
  
The [[https://github.com/openstack/openstack-manuals/blob/master/tools/generatedocbook merging script]] has dependency to package "xml2po". So you have to install gnome-doc-utils before running it.
+
The [https://github.com/openstack/openstack-manuals/blob/master/tools/generatedocbook merging script] has dependency to package "xml2po". So you have to install gnome-doc-utils before running it.
  
 
<pre><nowiki>
 
<pre><nowiki>
Line 44: Line 44:
 
=== Uploading script ===
 
=== Uploading script ===
  
The uploading script is an automation job running in Jenkins, which will be triggered by "commit" event of openstack-manuals repository. See [[https://github.com/openstack-infra/config/blob/master/modules/jenkins/files/slave_scripts/upstream_translation_update_manuals.sh here]].
+
The uploading script is an automation job running in Jenkins, which will be triggered by "commit" event of openstack-manuals repository. See [https://github.com/openstack-infra/config/blob/master/modules/jenkins/files/slave_scripts/upstream_translation_update_manuals.sh here].
  
 
=== Downloading script ===
 
=== Downloading script ===
  
The downloading script is an automation job running daily in Jenkins. See [[https://github.com/openstack-infra/config/blob/master/modules/jenkins/files/slave_scripts/propose_translation_update_manuals.sh here]].
+
The downloading script is an automation job running daily in Jenkins. See [https://github.com/openstack-infra/config/blob/master/modules/jenkins/files/slave_scripts/propose_translation_update_manuals.sh here].
  
 
== Tools related with message translation ==
 
== Tools related with message translation ==
 +
 +
For most of the Python projects, the preferred tools for I18N are gettext and babel. The gettext module provides internationalization (I18N) and localization (L10N) services for your Python modules and applications. Babel are a collection of tools for internationalizing Python applications.
 +
 +
You can extract the messages in code to PO template with pybabel:
 +
<pre><nowiki>
 +
pybabel extract -o nova/locale/nova.pot nova/
 +
</nowiki></pre>
 +
 +
=== Uploading script ===
 +
 +
For each Python project in OpenStack, there is an automation job to extract the messages , generate PO template and upload to Transifex, which is triggered by the "commit" event. See [https://github.com/openstack-infra/config/blob/master/modules/jenkins/files/slave_scripts/upstream_translation_update.sh here].
 +
 +
=== Downloading script ===
 +
 +
For each Python project in OpenStack, there is an automation job daily to download the translations in po file to the "locale" folder under the source folder of each project. See [https://github.com/openstack-infra/config/blob/master/modules/jenkins/files/slave_scripts/propose_translation_update.sh here]. It will generate a review request in Gerrit. After review, the translation in po file will be merged.

Revision as of 22:15, 17 July 2013

I18N uses many different tools, across several OpenStack Projects to meet its goals.

Tools related with document translation

OpenStack documents are in DocBook format. In order to make the document translation management consistent with message translation, we need to convert DocBook into PO format.

The document translation management include following steps:

  • Slicing: slice DocBook into string segment with a Python script, and generate a PO template
  • Uploading: Upload the translation resources to Transifex by automation scripts
  • Translating: manage the translation in Transifex, including the translation memory and glossary management
  • Merging: merge the translated string into Docbook with a python script
  • Uploading: Download the translated results by automation scripts.

Slicing script

The slicing script has dependency to package "xml2po". So you have to install gnome-doc-utils before running it.

 sudo apt-get install gnome-doc-utils

The script can scan a specific folder under openstack-manuals/doc/src/docbkx, collect all the text segment in *.xml and combine them into a PO template, with command:

./tools/generatepot [foldername]

The PO template will be put in a "locale" folder under the specific docbook folder, i.e. openstack-manuals/doc/src/docbkx/[bookname]/locale.

Merging script

The merging script has dependency to package "xml2po". So you have to install gnome-doc-utils before running it.

 sudo apt-get install gnome-doc-utils

The script can merge the translation strings into DocBook and generate a DocBook in the specific language.

./tools/generatedocbook -l [language] -b [book_name]

Uploading script

The uploading script is an automation job running in Jenkins, which will be triggered by "commit" event of openstack-manuals repository. See here.

Downloading script

The downloading script is an automation job running daily in Jenkins. See here.

Tools related with message translation

For most of the Python projects, the preferred tools for I18N are gettext and babel. The gettext module provides internationalization (I18N) and localization (L10N) services for your Python modules and applications. Babel are a collection of tools for internationalizing Python applications.

You can extract the messages in code to PO template with pybabel:

pybabel extract -o nova/locale/nova.pot nova/

Uploading script

For each Python project in OpenStack, there is an automation job to extract the messages , generate PO template and upload to Transifex, which is triggered by the "commit" event. See here.

Downloading script

For each Python project in OpenStack, there is an automation job daily to download the translations in po file to the "locale" folder under the source folder of each project. See here. It will generate a review request in Gerrit. After review, the translation in po file will be merged.