Release a Localized Build of Apache OpenOffice

Pootle User Guide

{{{parttitle}}}

[[{{{PrevPart}}}|< Previous Section ]]

[[{{{NextPart}}}|Next Section >]]

• Registration and Login
• Overview Pootle UI
• Offline Translation
• Quality Assurance
• Releasing a Localized Build
• Technical Helpers
• Translation of the User Interface
• Translation of the Built-in Help
• General Problems

[[{{{PrevPage}}}|< Previous Page ]]

[[{{{NextPage}}}|Next Page >]]

We have agreed to release a localized version of Apache OpenOffice, if the UI is 100% translated.

And for long-term maintainability we also recommend that:

• the UI is translated to 100% and
• the help is translated to 100% too and
• there is a small team (even just two members) to maintain the translation and ensure QA.

When you are ready, write an issue in Bugzilla in the product Native-Language. Also write an issue, if you later on make changes to the translation and want them to be integrated into the next release.

Once your issue is filed, there are some additional steps that are needed to integrate Pootle translations into OpenOffice. These are typically done by a developer who can commit changes to the source tree and include:

• conversion of Pootle files for a language to OpenOffice SDF format (see reference at http://translate.sourceforge.net/wiki/toolkit/oo2po)

These are basically database files that will reside in /extras/l10n/source under the ISO code for the language.

• Some (new) languages might also provide dictionaries as extensions. In this case, the the extensions.lst file in the source tree under /main will need to be updated.

If you edit strings in Pootle you need to explicitly ask on the mailing list, for them to be integrated into OpenOffice. Integration is not automatic.