Difference between revisions of "Translation from 4.2"
From Apache OpenOffice Wiki
(→Steps to do it: (Zwischenspeicherung)) |
(→Steps to do it) |
||
| Line 34: | Line 34: | ||
# Creating templates as POT-Files | # Creating templates as POT-Files | ||
#* Detailed description using [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html oo2po] | #* Detailed description using [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html oo2po] | ||
| − | #* ''oo2po --progress=verbose --pot | + | #* ''oo2po --progress=verbose --pot en-US.sdf PotFiles-UI'' |
| − | #* This | + | #* 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] | |
| − | + | #*: | |
| − | + | # Merge templates with existing PO-Files for each language (UI and HELP) | |
| + | #* Detailed description using [https://pootle.readthedocs.io/en/stable-2.5.1/server/commands.html#update-against-templates 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 [https://translate.apache.org/projects/aoo40 AOO UI] and the [https://translate.apache.org/projects/aoo40help AOO HELP]. | Now the teams can translate the [https://translate.apache.org/projects/aoo40 AOO UI] and the [https://translate.apache.org/projects/aoo40help AOO HELP]. | ||
Revision as of 19:56, 6 January 2019
Contents
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 stings for translation. You prepare a template file with all strings to have 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
- 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.
- Checkout the recent code base (normally the trunk branch)
- Build AOO successfully
- Create the template as en-US.sdf
- Detailed description using solenv/bin/localize
- Command: localize -e -l en-US -f en-US.sdf
- 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.
- 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.
- Updating the database with the template files (UI and HELP)
- Detailed description using pootle update-stores
- Detailed description using pootle update-stores
- Merge templates with existing PO-Files for each language (UI and HELP)
- Detailed description using pootle update-against-templates
- 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
