Documentation for Translators
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.
Ways of Translating OpenPetra
There are three different ways to provide some translation.
If you have questions or doubts feel free to contact the translation team: joejoe2010(at)users.sourceforge.net or post on the [1]
How to translate with Weblate
Weblate is a platform for making the process of translating easier. You can find the openpetra project here. Please click on the language for which you want to provide more translations. In order to make changes on a translation a registration is needed. You can register here. If you are not sure with a translation please check "Fuzzy" so that another person can review the item later on.
Using Poedit for translation
Using poedit: The following steps are needed.
- Download Poedit. The Version 1.8.4 is available at Github
- Download the .po-file (not .mo!!) . For Spanish it is available here
- Edit the .po-file offline
- Upload it again here (for Spanish). You will need to have an account on weblate.openpetra.org.
Poedit allows working faster than the first alternative. In order to avoid that work is done double by several translators please contact the translation team before starting: joejoe2010@users.sourceforge.net
Using Excel or LibreOffice Calc for translation
Converting the po-file to csv and open it eg. with Microsoft Excel:
This might be the easiest way to provide the items for translators which are not familiar with 1.) or 2.)
Please follow these steps:
- Download the latest version of toolkit from Sourceforge. 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:\Program Files\Translate Toolkit
- Download the actual .po-file (not .mo!!) . It is available here (for Spanish).
- On the windows command line, move to the folder where the file is saved
- 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 you get it back you need to save the file as csv (using UTF-8); this is especially necessary for ú, é etc used eg. 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 here (for Spanish). You will need to have an account on weblate.openpetra.org.
In order to avoid that work is done double by several translators please contact the translation team before starting: joejoe2010@users.sourceforge.net
Testing the translations
We provide a Nightly Build of OpenPetra. This provides the changes on Weblate that has been made on the day before. You can get the Nightly Build for Windows from our Build server. Please download the exe-file OpenPetraSetup-x.x.xx.xxxx.exe and install it on your computer to see your new translations.
Language specific information
Translation documentation for Developers
- There is documentation for developers, how to handle translations in releases etc, at Translation documentation for Developers