Today an addon translation reaches users only inside a version bump. That ties translators to release cycles and tells users nothing about what changed. Figures from the git history as of Nov 20:
- Translations get stuck: 99 addons on gramps60 have translation updates in addons-source that are in no released package. The last extract-po on gramps60 was April 17.
- Mixed releases: in the past 12 months there were 0 translation-only releases. 71 code releases carried translations too, so a version number never says which kind of change it was.
- Weblate moved to 6.1. For strings identical word for word in 6.0, the 6.1 branch has 18,713 newer core translations and 35,428 newer addon translations. 6.0 users won’t see them.
Two parts:
- make.py. In
as-needed,do_tar()always callsincrement_target(), so a changed.moalone bumps the version. Proposal: when onlylocale/*.mofiles differ, rebuild the.tgz(new installs get current translations) but leave the version unchanged. - Translation Updater (BETA addon) delivers translations out of band:
- A nightly GitHub Action builds per-language packs from the gramps and addons-source maintenance branches. 6.1 supplies only strings that are identical in the older branch.
- The addon layers downloaded packs over the installed translations. Nothing installed is modified. A pack pauses itself when the distro or an addon ships a newer translation.
- Verify shows English, Installed, Downloaded and what Gramps returns now, so you can check it works without reading the language.
https://github.com/emyoulation/CuratedGrampsPlugins/tree/main/gramps61/source/TranslationUpdater
Questions: is such a make.py change acceptable? Should the packs move under gramps-project?
Code and docs by Claude (Anthropic), from my wish-coding.