View source for Translation from 4.2


== Description ==

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.
<gallery>
File:UpdateTranslation.png|Graphical illustration of the technical workflow of the update of the translation
</gallery>

=== Steps to do it ===

# Create a build system
#* You can use your preferred Operating System
#* You can use this [https://wiki.openoffice.org/wiki/Building Building Guide] and the [https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step Step-by-Step Guide] to do it.
#*:
# Checkout the recent code base (normally the trunk branch)
#* ''git clone https://gitbox.apache.org/repos/asf/openoffice.git'' #(Since 2019-08.03)
#*:
# Build AOO successfully
#*:
# Repeat the first build preliminaries (autoconf, configure, bootstrap, source LinX86-64Env.Set.sh)
#*:
# Create the template as ''en-US.sdf''
#* Command: ''localize -e -l en-US -f en-US.sdf''
#*:
# Creating templates as POT-Files
#* Detailed description using [https://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html oo2po]
#* ''oo2po --progress=verbose --pot en-US.sdf PotFiles-UI''
#* Now ''PotFiles-UI'' also contains ''helpcontent2''. This is the content for the [[Localization_for_developers#Upload|separate project]] ''Apache OpenOffice 4.x Help''. The subdirectory ''helpcontent2'' has to be moved into the directory ''PotFiles-HELP''. 
#*:
# Updating the database with the template files (UI and HELP)
#* Detailed description using [https://pootle.readthedocs.io/en/stable-2.5.1/server/commands.html#update-stores pootle update-stores]
#* To be prepared for creating new languages
#*:
# Merge templates with existing PO-Files for each language (UI and HELP)
#* Detailed description using [https://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/pomerge.html?highlight=pomerge pomerge]
#*:
The steps on the Pootle server can be done with the script ''UpdateTranslation.sh''. This script will be published soon.

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

Now the teams can translate the [https://translate.apache.org/projects/aoo40 AOO UI] and the [https://translate.apache.org/projects/aoo40help AOO HELP].

== From Pootle Web Frontend to Git ==

<gallery>
File:UebersetzungsProzess_Finish.png|Graphical illustration of the technical workflow of the translation process
</gallery>

=== Steps to do it ===

# Synchronize translation database with PO-Files for each language (UI and HELP) 
#* Detailed description using [https://pootle.readthedocs.io/en/stable-2.5.1/server/commands.html#sync-stores pootle sync_stores]
#*:
# Create SDF from PO files
#* Detailed description using [https://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html?highlight=po2oo po2oo]
#*:
# Test SDF files with ''gsicheck''
#* This has to be done in a build environment after a successful build
#* Detailed description using [https://wiki.openoffice.org/wiki/Gsicheck#help gsicheck]
#* gsicheck -c -t -l ${Language} ${Language}/localize.sdf 
#*:
# Commit new SDF files into the code
#*
#*:

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

<!-- translation from/for? -->

[[Category:DE]] <!-- author language -->
[[Category:EN]] <!-- text language -->