Translation documentation for Developers: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
Line 8: Line 8:
Using the [https://weblate.openpetra.org Weblate]. To be able to make changes on the translation a registration is needed. If you are not sure with a translation please check "Fuzzy".
Using the [https://weblate.openpetra.org Weblate]. To be able to make changes on the translation a registration is needed. If you are not sure with a translation please check "Fuzzy".


== 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 [http://sourceforge.net/projects/translate/files/Translate%20Toolkit/ 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 [https://weblate.openpetra.org/download/openpetra/openpetra/es/ 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 [https://weblate.openpetra.org/projects/openpetra/openpetra/es/#upload 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: [mailto:joejoe2010(at)users.sourceforge.net joejoe2010@users.sourceforge.net]


= Testing a translation =
= Testing a translation =

Revision as of 11:43, 23 September 2015

Documentation for Translators

There is a separate page with Documentation for Translators.

The translation process

There are actually 3 different ways to provide some translation.

Using Weblate for translation

Using the Weblate. To be able to make changes on the translation a registration is needed. If you are not sure with a translation please check "Fuzzy".


Testing a translation

We provide a Nightly Build of OpenPetra. This integrates the changes on Github that has been made on the last 24 hours. You can get the Nightly Build here. Please download the exe-file OpenPetraSetup-x.x.xx.xxxx.exe and install it on your computer to see your new translations.

Update translation template

The synchronisation process needs to be done by someone of the Core development team. The goal is to update the template on Weblate with new strings to translate.

Make sure that you have pushed all changes on Weblate to our Github repository for the translations, at https://weblate.openpetra.org/projects/openpetra/openpetra/#repository.

The next steps have been automated with the command nant buildTranslationTemplate.

This command will:

You should commit the updated template.pot and the updated .po files to https://github.com/openpetra/openpetra-i18n again, and make sure you do a pull on Weblate, and then a reset, losing all local changes, but getting all new strings

All .po files in the i18n directory will be added to the installer automatically. OpenPetra will use the language settings on the workstation for determining which language file should be used.

Reviewing the translation template

Please have a look at Reviewing the translation template

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