Documentation for Translators: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
 
(31 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== General information ==
== General Information ==
There are acutally 3 different ways to provide some translation.
The team behind OpenPetra doesn't plan particular translations of OpenPetra - rather, '''the OpenPetra application can be translated voluntarily''' by people who want to either contribute to OpenPetra with their skills in this way and/or have a particular interest in having the application in their 'heart language'.


1.) Using the [https://translations.launchpad.net/openpetraorg/trunk/+pots/template1 launchpad-platform]. To be able to make changes on the translation a registration is needed.
* The people who do the translation should be good in English and translate the application out of English into their mother tongue, ''but they don’t need to be computer specialists for that!''
* One doesn't need to take on the task of translating the whole application into another language as the translations are done incrementally - sentence for sentence.  
* One can translate as much or as little as he desires, and one doesn't even need to notify us if he/she starts translating, though it would be kind if that would be done.


2.) Using poedit: The following steps are needed.
''You are very welcome to help in translating OpenPetra into other languages.''


- Download poedit. The Version 1.4.6 is available [http://prdownloads.sourceforge.net/poedit/poedit-1.4.6-setup.exe here]
==Translation team==


- Download the .po-file (not .mo!!) . It is available [https://translations.launchpad.net/openpetraorg/trunk/+pots/template1/es/+export here] (after a registration at launchpad)
If you have questions or doubts feel free to post on the [https://forum.openpetra.org Forum]


- Edit the .po-file offline
== How to translate ==
We are using Weblate for managing the translations of the javascript client.


- Upload it again [https://translations.launchpad.net/openpetraorg/trunk/+pots/template1/es/+upload here]
Just go to https://weblate.openpetra.org to our own Weblate installation.


Poedit allows working faster than the first alternative. In order to avoid that work is done double be several translators please contact the translation team before starting.
== Testing the translations ==
You can get a test installation, by running


3.) Converting the po-file to csv and open it for example with Microsoft Word
curl https://get.openpetra.org | bash -s test


This might be the easiest way to provide the items for translators which are not familiar with 1.) or 2.)
Then just replace your language file in /home/op_test/client/locales, and reload your browser.
 
Please follow the following steps:
 
- Download an actual version of toolkit [http://sourceforge.net/projects/translate/files/Translate%20Toolkit/ here]. The file should be named translate-toolkit-…-setup.exe.
 
- Install toolkit
 
- Open a windows command line (Win+R) and adapt your path: for example with PATH=%PATH%;E:\Archivos de programa\Translate Toolkit
 
- Download the actual .po-file (not .mo!!) . It is available [https://translations.launchpad.net/openpetraorg/trunk/+pots/template1/es/+export here] (after a registration at launchpad)
 
- Move to the folder where the file is safed on the windows command line
 
- Execute po2csv. For example po2csv template1_template1-es.po template1_template1-es.csv --progress=verbose --errorlevel=message
 
- eventually: save the csv as xls
 
- provide the csv or xls-file to your translators
 
- when it comes back you need to save the file as csv (using UTF-8); this is especially necessary for ú, é etc used in Spanish
 
- Execute csv2po. For example csv2po template1_template1-es.csv template1_template1-es_rückkonvertiert.po --progress=verbose --errorlevel=message
 
- Upload the po-file [https://translations.launchpad.net/openpetraorg/trunk/+pots/template1/es/+upload here]


== Language specific information ==
== Language specific information ==


* [[Spanish translation]]
* [[Spanish translation]]
== Translation documentation for Developers ==
* There is documentation for developers, how to handle translations in releases etc, at [[Translation documentation for Developers]]

Latest revision as of 08:03, 19 Mayıs 2022

General Information

The team behind OpenPetra doesn't plan particular translations of OpenPetra - rather, the OpenPetra application can be translated voluntarily by people who want to either contribute to OpenPetra with their skills in this way and/or have a particular interest in having the application in their 'heart language'.

  • The people who do the translation should be good in English and translate the application out of English into their mother tongue, but they don’t need to be computer specialists for that!
  • One doesn't need to take on the task of translating the whole application into another language as the translations are done incrementally - sentence for sentence.
  • One can translate as much or as little as he desires, and one doesn't even need to notify us if he/she starts translating, though it would be kind if that would be done.

You are very welcome to help in translating OpenPetra into other languages.

Translation team

If you have questions or doubts feel free to post on the Forum

How to translate

We are using Weblate for managing the translations of the javascript client.

Just go to https://weblate.openpetra.org to our own Weblate installation.

Testing the translations

You can get a test installation, by running 

curl https://get.openpetra.org | bash -s test

Then just replace your language file in /home/op_test/client/locales, and reload your browser.

Language specific information

Translation documentation for Developers

Retrieved from ‘https://wiki.openpetra.org/index.php?title=Documentation_for_Translators&oldid=4917’