Difference between revisions of "Translation from 4.2"

From Apache OpenOffice Wiki
Jump to: navigation, search
(From Pootle Web Frontend to SVN)
 
(8 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
This will be a brief documentation of the translation process
 
This will be a brief documentation of the translation process
 
There are two steps doing at different time 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.
+
== 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.
 
The following graphic shows it. Please click on it to get a larger one.
Line 20: Line 21:
 
#*:
 
#*:
 
# Checkout the recent code base (normally the trunk branch)
 
# 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)
 
#*:
 
#*:
 
# Build AOO successfully
 
# Build AOO successfully
 +
#*:
 +
# Repeat the first build preliminaries (autoconf, configure, bootstrap, source LinX86-64Env.Set.sh)
 
#*:
 
#*:
 
# Create the template as ''en-US.sdf''
 
# Create the template as ''en-US.sdf''
#* Detailed description using [[Localization_for_developers#Extraction|solenv/bin/localize]]
 
 
#* Command: ''localize -e -l en-US -f en-US.sdf''
 
#* 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 ([https://translate-vm.apache.org translate-vm.apache.org])
 
#* The Pootle server runs under Ubuntu, so you have to be familiar with GNU/Linux.
 
 
#*:
 
#*:
 
# Creating templates as POT-Files
 
# Creating templates as POT-Files
Line 44: Line 42:
 
#*:
 
#*:
 
The steps on the Pootle server can be done with the script ''UpdateTranslation.sh''. This script will be published soon.
 
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].
 
Now the teams can translate the [https://translate.apache.org/projects/aoo40 AOO UI] and the [https://translate.apache.org/projects/aoo40help AOO HELP].
Line 55: Line 58:
 
=== Steps to do it ===
 
=== Steps to do it ===
  
# Synchronize translation database with PO-Files
+
# 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 [http://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
 
#*:
 
#*:
# Create SDF from PO-Files
+
# Commit new SDF files into the code
 
#*
 
#*
 
#*:
 
#*:
  
This can be done with scripts at Pootle, too.
+
This can be done with scripts, too. the paths have to be adapt to the path
  
 
<!-- translation from/for? -->
 
<!-- translation from/for? -->

Latest revision as of 07:13, 19 January 2020

Description

This will be a brief documentation of the translation process There are two steps doing at different time 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 LinX86-64Env.Set.sh)
  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)

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

  1. 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.

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

From Pootle Web Frontend to SVN

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

Personal tools