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.
Translation team
If you have questions or doubts feel free to post on the Forum
How to translate
We used to have Weblate, and used to work with .po files. We are not doing that anymore.
Since we dropped the Winforms client, the javascript client has much less functionality. This means, that the strings to be translated are not so many in number anymore.
So you just translate the file https://github.com/openpetra/openpetra/blob/master/js-client/locales/en/common.json, and create a pull request at Github. If you need help with that, please let us know on the forum.
Once we have a thriving OpenPetra community, we can consider improving the translation process to work with tools that would work for non-developers again.
Testing the translations
You can get a test installation, by running
curl https://getopenpetra.com | 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
- There is documentation for developers, how to handle translations in releases etc, at Translation documentation for Developers