@@ -9,10 +9,10 @@ We rely on an army of volunteer translators and we **thank them for their work**
...
@@ -9,10 +9,10 @@ We rely on an army of volunteer translators and we **thank them for their work**
What follows is a short summary of the translation workflow for existing resources.
What follows is a short summary of the translation workflow for existing resources.
* Users translate our apps on [Transifex](https://www.transifex.com/projects/p/torproject/) and our websites at [transifex tor web](https://www.transifex.com/otf/tor-project-support-community-portal/).
* Users translate our apps on [weblate](https://hosted.weblate.org/projects/tor/)
* Each translation resource has two branches in the [translation](https://gitweb.torproject.org/translation.git) repository
* Each translation resource has a branch in the [translation repository](https://gitlab.torproject.org/tpo/translation/)
*A [cronjob](https://gitweb.torproject.org/translation-tools.git/tree/update_translations) will pull new and updated translations from Transifex and add them to the translation repository
*Weblate sends new and updated translations to the translation repository
* Developers clone the [translation repository](https://gitweb.torproject.org/translation.git/), check out branches, validate the translations, and include them in new releases
* Developers clone the translation repository, check out branches, validate the translations, and include them in new releases. They can also use the Weblate API to download only complete translations, or translations without failing checks. See [this script from rdsys](https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/blob/main/scripts/fetch_translations.py?ref_type=heads) as an example.
