Translation documentation for Developers

Documentation for Translators

There is a separate page with Documentation for Translators.

Synchronising Launchpad with version in Git

The synchronisation process needs to be done by someone of the Core development team. The goal is to get the latest translations into the official packaged version, and to update the template on Launchpad with new strings to translate.

First download the latest translations, in this case for german, in .po format:

https://translations.launchpad.net/openpetraorg/trunk/+pots/template1/de/+export

You will get an email once the download is ready.

Then generate a new template file:

1. Delete the file i18n/template.po, if it exists
2. make sure that your OpenPetra.build.config has <property name="Translation.TargetLanguage" value="template"/>
3. nant translation will create the file U:\openpetraorg\i18n\template.po. Rename it to template.pot and commit template.pot.
4. Upload the new template.pot file to Launchpad, using https://translations.launchpad.net/openpetraorg/trunk/+pots/template1/+upload
5. a few hours later, the new template will be available (if it needs a manual review, it might take a day)

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.

Testing a translation

• TODO: describe how to use nant to generate the appropriate resource dll containing the translations
• TODO: describe how to set the Environment Variables to switch to another language than the system language to test other language files
• TODO: this might be interesting for translators too so that they can test their translation even before a release? but it is probably too complicated to configure and use nant?