Difference between revisions of "Translation from 4.2"

Revision as of 17:52, 4 August 2019

Description

This will be a brief documentation of the translation process There are two steps doing at different time of the translation process.

From SVN 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 are imported into Pootle.

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

• 

  Graphical illustration of the technical workflow of the translation process

Steps to do it

1. Create a build system
   • You can use your preferred Operating System
   • You can use this Building Guide and the Step-by-Step Guide to do it.

2. Checkout the recent code base (normally the trunk branch)
   • svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo
   • git clone https://gitbox.apache.org/repos/asf/openoffice.git #(Since 2019-08.03)

3. Build AOO successfully

4. Create the template as en-US.sdf
   • Detailed description using solenv/bin/localize
   • Command: localize -e -l en-US -f en-US.sdf

5. Copy the file en.US.sdf to the Pootle backend
   • You need an access to the Pootle server (translate-vm.apache.org)
   • The Pootle server runs under Ubuntu, so you have to be familiar with GNU/Linux.

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)
   • Detailed description using pootle update-stores

8. Merge templates with existing PO-Files for each language (UI and HELP)
   • Detailed description using pootle update-against-templates

The steps on the Pootle server can be done with the script UpdateTranslation.sh. This script will be published soon.

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

From Pootle Web Frontend to SVN

• 

  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)
   • Detailed description using pootle sync_stores

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 adapt to the path