Translations of OpenBoard are often lagging behind the releases. There are for sure several reasons for that, but some of them we could address.
Update of .ts files
The .ts files are often lagging behind the actual status of the code. Often the update is done just before the release of a new version. So translation contributors have no chance to add or update the translations for a release. Their changes will just hit the next release, which however might again have additional or changes translation strings.
This is especially problematic with large releases, as the upcoming 1.8.0.
To catch up with development, translation files should be updated after each merge of a PR or set of PRs, which might affect translation strings. This way, translation contributors could have a chance to provide their input already before the next release.
High entry barrier
Many people good at translation have probably never heard of git and Qt. Forking, checkout, Qt Linguist and PR might hinder them to contribute.
A simple-to-use, web based translation tool is much easier to use. One could also start translating just a few words or sentences, as time permits, without prior preparation or setup.
My proposal
During this year's openSUSE conference, I attended a talk by Weblate co-founder Benjamin Jamie. Afterward, I also had the opportunity to talk with him at length. So I got some insight how flexible Weblate is and how it could be used.
- Weblate is free for open source projects like OpenBoard.
- Weblate can scan a git repository and detect changed
.ts files. They are then automatically transferred to the Weblate internal translation data base.
- Weblate is highly configurable on how it transfers the translations back to the project. It can e.g. create PRs, or push the updated translations to a dedicated branch.
Using Weblate will not significantly change the project workflow. We just need to make sure to update the .ts files after every major merge. The updated translations can then be merged immediately before a release.
However by moving translations to Weblate we will also invite translators to OpenBoard which have never heard of that project. There are many people willing to help with translations, and they just browse around the Weblate UI to find any project needing help. So the contributor community could grow significantly.
Translations of OpenBoard are often lagging behind the releases. There are for sure several reasons for that, but some of them we could address.
Update of .ts files
The
.tsfiles are often lagging behind the actual status of the code. Often the update is done just before the release of a new version. So translation contributors have no chance to add or update the translations for a release. Their changes will just hit the next release, which however might again have additional or changes translation strings.This is especially problematic with large releases, as the upcoming 1.8.0.
To catch up with development, translation files should be updated after each merge of a PR or set of PRs, which might affect translation strings. This way, translation contributors could have a chance to provide their input already before the next release.
High entry barrier
Many people good at translation have probably never heard of git and Qt. Forking, checkout, Qt Linguist and PR might hinder them to contribute.
A simple-to-use, web based translation tool is much easier to use. One could also start translating just a few words or sentences, as time permits, without prior preparation or setup.
My proposal
During this year's openSUSE conference, I attended a talk by Weblate co-founder Benjamin Jamie. Afterward, I also had the opportunity to talk with him at length. So I got some insight how flexible Weblate is and how it could be used.
.tsfiles. They are then automatically transferred to the Weblate internal translation data base.Using Weblate will not significantly change the project workflow. We just need to make sure to update the .ts files after every major merge. The updated translations can then be merged immediately before a release.
However by moving translations to Weblate we will also invite translators to OpenBoard which have never heard of that project. There are many people willing to help with translations, and they just browse around the Weblate UI to find any project needing help. So the contributor community could grow significantly.