Translating LibreOffice

From The Document Foundation Wiki
Revision as of 2012-01-18T16:05:19 by Rq (Talk | contribs) (added link to the LibreOffice Localization Guide)

Jump to: navigation, search

LibreOffice translation process is quite straightforward. The suggested way to work on it is to use Pootle (our online translation portal). All you need to localize using this method is a browser and an Internet connection. If you prefer to work offline, it also is possible, see below.


See the Release Plan. Release Plan shows the dates when the source code is tagged for beta, RC or release. Translation deadline is always 2 days before the announced tagging date.


TDF Pootle always contains up-to-date localizable strings. Pootle administrators update them rather frequently.

On the right hand side of Pootle home page, you will see a list of projects (modules) currently available for translation. Their names are self-explanatory. To localize LibreOffice, you'll have to work on projects called LibreOffice x.x.x – UI and LibreOffice x.x.x – Help. In general, if you're just starting, it probably makes most sense to work on the version with the highest number, but if you want to fix some nasty L10n bug in the current version of LibO, you can do that in the older branch too.

If you prefer to translate offline, you can download full or partial ZIP archives with PO files (or just separate PO files) from Pootle and use your favorite tool(s) to work on them. You'll find the links in Translate and Review tabs of the desired language/project combination. Assuming you have the appropriate rights for your language, you should be able to upload PO or ZIP files back anytime (in case of ZIP, just make sure to keep the initial directory structure intact).

You'll notice there are a few more modules available in Pootle. Here's a short overview of them:

  • Terminology: this is a Pootle helper module which makes localization somewhat easier. If the Terminology module is present and not empty in your language, Pootle will show you hints for terms that exist in the Terminology file when you come across those terms while translating other modules.
  • Website: this small module contains a few custom localization files of the content management system (CMS) that the website of LibreOffice runs on. This module is really tiny, because most of this CMS is being localized elsewhere.
  • Extensions for LibreOffice: this module holds localization for a few extensions that are NOT shipped with LibreOffice by default.
  • Askbot: this project was set up to allow localization of Askbot Q&A software (which is somewhat similar to StackOverflow). Askbot is a third party product, but because we plan to use it, we have set this project up to help it get more localizations.

SDF, POT and PO files

Latest SDF file and POT files extracted from the source can always be found here:

PO files for each supported language are stored in the source code repository in the module called 'translations'. This module is maintained by Andras Timar, who will get translations from Pootle (or alternative sources) before each release and will push them to git.


  • You are encouraged to subscribe to mailing list. Apart from being a support channel for localizers, it's also the medium where important information for translators (such as string updates and deadlines) is announced. You can also ask 'timar' or 'RQ' on in the #libreoffice-dev channel.
  • Check for L10n bugs and fix them!

Other Aspects of Localization

More aspects of LibreOffice localization are covered in the LibreOffice Localization Guide.