Difference between revisions of "New Translation Process (Pootle server)"
PetrDudacek (Talk | contribs) |
PetrDudacek (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | <font color="red">''' | + | <font color="red">'''...under construction...'''</font> |
| + | |||
| + | This page contains information about the new OOo translation process and about the Pootle server as a central point for storing translatable content. | ||
| + | |||
| + | ==Why a new translation process?== | ||
| + | The main reason of setting up a new translation process was the fact that it's currently hard for Communities to contribute to translation of Sun-supported languages due to various (mostly technical) reasons. The new Pootle-based translation process should overcome these limitations. | ||
| + | |||
| + | ==What is Pootle?== | ||
| + | Pootle stands for '''P'''O-based '''O'''nline '''T'''ranslation / '''L'''ocalization '''E'''ngine. Pootle is a web portal that allows to translate .po files. The translation can be done online or the .po files can be downloaded, translated offline and then uploaded back. Pootle can be integrated with CVS or SVN. | ||
| + | |||
| + | More information about Pootle can be found on the following sites:<br> | ||
| + | http://www.wordforge.org/drupal/projects/wordforge/tools/pootle<br> | ||
| + | http://www.wordforge.org/static/pootle.html<br> | ||
| + | http://pootle.wordforge.org/doc/howto.html<br> | ||
| + | http://translate.sourceforge.net/wiki/pootle/index | ||
| + | |||
| + | ==Workflow== | ||
| + | There are several steps involved in the translation process: | ||
| + | # checkout of OOo sources from the CVS | ||
| + | # extraction of translatable content from the sources | ||
| + | #: '''result:''' 1 .sdf file per language | ||
| + | # each .sdf file converted into .po files | ||
| + | #: '''result:''' directory tree containing many .po files (''1 .sdf file per language'' becomes ''many .po files per language'') | ||
| + | # fixing .po files (some magic done to the .po files) - TBD - add more info | ||
| + | #: '''result:''' fixed .po files (removed duplicates etc.) | ||
| + | # .po files merged with those already stored in Pootle | ||
| + | #: '''result in Pootle:''' set of .po files (those already translated in previous rounds and those waiting for translation) | ||
| + | # translation of untranslated .po files - either directly or offline | ||
| + | #: '''result:''' all .po files translated | ||
| + | # backconversion of .po files into .sdf format | ||
| + | #: '''result:''' 1 .sdf file per language ready to be imported into the translation database | ||
| + | # issue created, .sdf files attached or linked | ||
| + | # .sdf file from the issue imported into the translation database | ||
| + | # build based on latest translations is created | ||
Revision as of 07:47, 18 May 2007
...under construction...
This page contains information about the new OOo translation process and about the Pootle server as a central point for storing translatable content.
Why a new translation process?
The main reason of setting up a new translation process was the fact that it's currently hard for Communities to contribute to translation of Sun-supported languages due to various (mostly technical) reasons. The new Pootle-based translation process should overcome these limitations.
What is Pootle?
Pootle stands for PO-based Online Translation / Localization Engine. Pootle is a web portal that allows to translate .po files. The translation can be done online or the .po files can be downloaded, translated offline and then uploaded back. Pootle can be integrated with CVS or SVN.
More information about Pootle can be found on the following sites:
http://www.wordforge.org/drupal/projects/wordforge/tools/pootle
http://www.wordforge.org/static/pootle.html
http://pootle.wordforge.org/doc/howto.html
http://translate.sourceforge.net/wiki/pootle/index
Workflow
There are several steps involved in the translation process:
- checkout of OOo sources from the CVS
- extraction of translatable content from the sources
- result: 1 .sdf file per language
- each .sdf file converted into .po files
- result: directory tree containing many .po files (1 .sdf file per language becomes many .po files per language)
- fixing .po files (some magic done to the .po files) - TBD - add more info
- result: fixed .po files (removed duplicates etc.)
- .po files merged with those already stored in Pootle
- result in Pootle: set of .po files (those already translated in previous rounds and those waiting for translation)
- translation of untranslated .po files - either directly or offline
- result: all .po files translated
- backconversion of .po files into .sdf format
- result: 1 .sdf file per language ready to be imported into the translation database
- issue created, .sdf files attached or linked
- .sdf file from the issue imported into the translation database
- build based on latest translations is created
