Translation from 4.2

From Apache OpenOffice Wiki
Jump to: navigation, search


This will be a brief documentation of the translation process. There are two steps to be done at different times of the translation process.

From GIT to Pootle Web Frontend

In this step you prepare the recent code strings for translation. You prepare a template file with all strings that need to be translated. They will be imported into Pootle then.

The following graphic shows it. Please click on it to get a larger one.

Steps to do it

  1. Create a build system
  2. Checkout the recent code base (normally the trunk branch)
  3. Build AOO successfully
  4. Repeat the first build preliminaries (autoconf, configure, bootstrap, source
  5. Create the template as en-US.sdf
    • Command: localize -e -l en-US -f en-US.sdf
  6. Creating templates as POT-Files
    • Detailed description using oo2po
    • oo2po --progress=verbose --pot en-US.sdf PotFiles-UI
    • Now PotFiles-UI also contains helpcontent2. This is the content for the separate project Apache OpenOffice 4.x Help. The subdirectory helpcontent2 has to be moved into the directory PotFiles-HELP.
  7. Updating the database with the template files (UI and HELP)
  8. Merge templates with existing PO-Files for each language (UI and HELP)
    • Detailed description using pomerge

The steps on the Pootle server can be done with the script

  1. Copy the file en.US.sdf to the Pootle backend
    • You need an access to the Pootle server (
    • The Pootle server runs under Ubuntu, so you have to be familiar with GNU/Linux.

Now the teams can translate the AOO UI and the AOO HELP.

From Pootle Web Frontend to Git

Graphical illustration of the technical workflow of the translation process

Steps to do it

  1. Synchronize translation database with PO-Files for each language (UI and HELP)
  2. Create SDF from PO files
    • Detailed description using po2oo
  3. Test SDF files with gsicheck
    • This has to be done in a build environment after a successful build
    • Detailed description using gsicheck
    • gsicheck -c -t -l ${Language} ${Language}/localize.sdf
  4. Commit new SDF files into the code

This can be done with scripts, too. The paths have to be adapted to the path

Personal tools