Changes in TranslationMaintenance
Editor Comment
We need clang-format too.
Revision Differences of Revision 10
[TOC] ¶¶
# Preparing for Transifex ¶
¶
This can only be done if you have appropriate powers in our Transifex project. Before you can get started, you will need to ¶
¶
¶
* [install the Transifex client](https://docs.transifex.com/client/installing-the-client) on your machine. ¶
* create a [.transifexrc](https://docs.transifex.com/client/client-configuration) file in your home directory, which will be used as login credentials with Transifex, and ¶
¶
# Installing the Appstream Validator ¶
¶
During the translation update process, we also validate the `debian/appdata.xml` file. in order for this to work, you will need to install the `appstream` package. ¶
¶
# Installing
¶
sudo pip install pyformat
sudo apt install clang-format ¶
~~~~ ¶
¶
# Synchronizing the translations and updating the source code ¶
¶
A guide on how to set up new templates and push/pull translations is provided on the [Transifex Docs page](http://docs.transifex.com/guides/client). For routine translation maintenance, these are the steps you will need to take: ¶
¶
1. `cd` to *trunk*. ¶
2. Run `utils/merge_and_push_translations.sh`. This will pull current *trunk* and the translations from Transifex, update the developers list and appdata translations, then update and merge the translation catalogs and push everything to *trunk* and Transifex. ¶
¶
# Validating translations ¶
¶
Once in a while, and during the [release process](https://wl.widelands.org/wiki/ReleasingWidelands/), our translation validation script should be run. It is located in `utils/validate_translations.sh`. ¶
¶
You will need the `i18nspector` and `translate-toolkit` packages to run this. ¶
¶
The result should be checked and issues that might be false positives passed on to the translators for review. Do **not** blindly "fix" everything - translators' judgement is needed here. The `printf` and `nplurals` checks need to be clean though - `printf` errors can cause crashes.