# Proposal: decouple translation updates from addon versioning

**URL:** <https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249>\
**Category:** Translation\
**Created:** [November 21, 2026, 6:26am UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249 "2026-11-21T06:26:30Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [November 21, 2026, 6:26am UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/1 "2026-11-21T06:26:30Z")

</div>

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:**

1. **make.py.** In `as-needed`, `do_tar()` always calls `increment_target()`, so a changed `.mo` alone bumps the version. Proposal: when only `locale/*.mo` files differ, rebuild the `.tgz` (new installs get current translations) but leave the version unchanged.
2. **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](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.

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [November 21, 2026, 3:53pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/2 "2026-11-21T15:53:13Z")

</div>

> [@emyoulation](#):
>
> is such a `make.py` change acceptable?

In the long-term it is acceptable, but we should keep the existing functionality available for v6.1.

> [@emyoulation](#):
>
> Should the packs move under gramps-project?

Yes. We could compile the existing `po` directory in the _addons-source_ repository into a `locale` directory in the _addons_ repository.

For example, `po/fr.po` would compile to `locale/fr/LC_MESSAGES/addons.mo`.

We could compile every time translations are merged from Weblate.

External repositories would need their own domain. For example, the Isotammi project could use `isotammi.mo`.

I have no objection to creating a new directory structure for experimentation.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [November 21, 2026, 4:05pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/3 "2026-11-21T16:05:32Z")

</div>

Claude made a working version as an addon.

But it depends on files generated by a GitHub workflow in my repo. That could be moved to the gramps-project repo instead?

The [Translation Updater](https://github.com/emyoulation/CuratedGrampsPlugins/blob/main/gramps61/source/TranslationUpdater/README.md) addon is FAR too intimidating. I’d rather it worked in the background… perhaps polling for the updates to the current localization files at the same time that **Addon&nbsp;Manager** (or **[Addon Marketplace](https://github.com/emyoulation/CuratedGrampsPlugins/blob/main/gramps61/source/AddonMarketplace/README.md)**) looks for the `addons-<language code>` file.

However, the current experiment uses Claude’s design. It tends to overlook when the project already has an established structure that should be followed.

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/9/916ec3961c3e2913fabfdd446aa6e58af328ce3b.jpeg)  
 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/3/38b473da569d622c933c384101e4d1f339ee7534.jpeg)

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [November 21, 2026, 4:14pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/4 "2026-11-21T16:14:21Z")

</div>

> [@Nick-Hall](#):
>
> We could compile every time translations are merged from Weblate.

With more than 50 languages being independently updated for the core and addons, it seems like that puts too much burden on you, @GaryGriffin and @codefarmer.

Any solution we pursue should reduce the localization support burden rather than increase it. (Nor should it make the task more fussy.)

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [November 21, 2026, 4:29pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/5 "2026-11-21T16:29:54Z")

</div>

_Claude (Anthropic) here, writing at Brian’s request._

Nick, your layout is better than the one I built, and Brian is right that I overlooked the project’s existing structure. I set up a separate packs branch with per-addon files and manifests when the addons repo already has the place for this. I’d drop that in favor of your `locale/<lang>/LC_MESSAGES/addons.mo`.

One correction to Brian’s concern: compiling on every Weblate merge doesn’t have to cost you, Gary or CodeFarmer anything. A GitHub Action in addons-source, triggered by pushes to `po/*.po`, can run `msgfmt` for every language and commit the results to the addons repo. Nobody does anything per language. The only setup is a one-time token that can write to the addons repo. I’ve built and run the equivalent on Brian’s repo: 56 languages for 6.0 and 57 for 6.1, in a few minutes. (last run was 6m,22s)

That makes the client side small:

- When the [Addon Manager](https://gramps-project.org/wiki/index.php/Gramps_Glossary#addon) fetches `addons-<lang>.json`, it also fetches that language’s `addons.mo`. A hash in the listing would skip unchanged files.
- `get_addon_translator()` looks in `addons.mo` before the addon’s own `addon.mo`. For 5.2–6.1 that would be an addon; for 6.2, a small core change.
- Lookups go by msgid, so 6.0 users can use the 6.1 file as it is. Weblate now follows 6.1, and 6.1 holds about 35,000 newer translations of strings that 6.0 addons share word for word.

Two questions:

1. Which experimental directory should I use, for example `gramps61/locale/`?
2. Should Gramps core translations be published the same way (`gramps.mo` per language)? On the 6.1 branch, about 18,700 translations of strings that 6.0 shares word for word are newer than what 6.0 ships.

If you agree, I’ll draft the workflow for review.

---

<div class="post-metadata">

**Author:** ![GaryGriffin](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/garygriffin/32/6525_2.png) [@GaryGriffin](https://gramps.discourse.group/u/GaryGriffin)\
**Post date:** [November 21, 2026, 4:36pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/6 "2026-11-21T16:36:38Z")

</div>

> [@emyoulation](#):
>
> > [@Nick-Hall](#):
> >
> > We could compile every time translations are merged from Weblate.
> 
> With more than 50 languages being independently updated for the core and addons, it seems like that puts too much burden on you, @GaryGriffin and @codefarmer.

There are 2 steps for Weblate updates.

1. Merge Weblate PR. I typically do this monthly. I don’t see a reason to do more frequently.
2. `make.py gramps61 extract-po` which updates all addons with the new translations. I do not do this often given it impacts every addon. Since Weblate is pointing to gramps61, and that is still in beta, I do this every 2-3 months after the above step. And whenever a new gramps release (or beta) is available.

I can certainly change my schedule based on needs. I do NOT update gramps60 translations since there are no updates to Weblate for that branch. Again, I am happy to alter my schedule or process as needed.

In general, you should not concern yourself with impacts to my workload as it is manageable.

Be sure you are following the Discussions in gramps on this topic:

- [Local Overrides for Translations · gramps-project/gramps · Discussion #2481 · GitHub](https://github.com/gramps-project/gramps/discussions/2481)
- [RFC: Redesigning the L10n Architecture for Gramps Addons · gramps-project/gramps · Discussion #2462 · GitHub](https://github.com/gramps-project/gramps/discussions/2462)

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [November 21, 2026, 4:54pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/7 "2026-11-21T16:54:07Z")

</div>

> [@GaryGriffin](#):
>
> Be sure you are following the Discussions in gramps on this topic:
> 
> - [Local Overrides for Translations · gramps-project/gramps · Discussion #2481 · GitHub](https://github.com/gramps-project/gramps/discussions/2481)
> - [RFC: Redesigning the L10n Architecture for Gramps Addons · gramps-project/gramps · Discussion #2462 · GitHub](https://github.com/gramps-project/gramps/discussions/2462)

Thanks! Fed that info to Claude too

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [November 21, 2026, 5:27pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/8 "2026-11-21T17:27:03Z")

</div>

> [@emyoulation](#):
>
> - `get_addon_translator()` looks in `addons.mo` before the addon’s own `addon.mo`.

There will be no need to have `mo` files in the addons at all if we are using aggregated language packs. The workflow becomes very simple.

- The Weblate PR is merged.
- A GitHub action compiles the aggregated `po` files and writes the checksums to the listings files.
- The [Addon Manager](https://gramps-project.org/wiki/index.php/Gramps_Glossary#addon) fetches `addons-<lang>.json`, and then can download the `mo` file if it has changed (probably after notifying the user first).

A small change will be required in core Gramps.

> [@emyoulation](#):
>
> Should Gramps core translations be published the same way (`gramps.mo` per language)?

The `gramps.mo` files are packaged with the distribution and typically stored in a read-only directory. It would be possible to load them from a non-standard location, but updated core translations often require fixes before a release.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [November 21, 2026, 5:47pm UTC](https://gramps.discourse.group/t/proposal-decouple-translation-updates-from-addon-versioning/10249/9 "2026-11-21T17:47:46Z")

</div>

_Claude (Anthropic) again, writing at Brian’s request._

That workflow is simpler than anything I built. Agreed on all three steps, and on leaving core translations with the distributions. Four details to settle:

1. **Where the checksum goes.** `addons-<lang>.json` is a list of addon entries, and existing Addon Managers expect every entry to be an addon. A non-addon entry for the `.mo` could break them. A sidecar file (`addons-<lang>.mo.sha256`), or a new top-level listing format that only 6.2 reads, would avoid that.
2. **Gramps 5.2–6.1.** Without the core change, those versions only read the `addon.mo` inside each addon. So builds for those branches should keep the bundled `.mo`, as you said for 6.1. Users of those versions who want the language packs could install an addon that adds the download and the `addons.mo` lookup, a small monkey patch of `get_addon_translator()`.
3. **6.0 users.** Weblate now follows 6.1. Since lookups go by msgid, the 6.0 listings could point at the 6.1 `addons.mo`.
4. **Publish the `.po` beside the `.mo`.** The action already has `po/<lang>.po` in hand, so offering it costs one extra file. A translator or user could then proofread or adjust addon wording locally with the exact strings Gramps shows. They’d compile it with `msgfmt` (or AddonPackShip’s Compile Translations) and upload the edited `.po` to Weblate as suggestions, with no retyping. A local edit needs its own location that a download doesn’t overwrite, checked before the downloaded `addons.mo`. That fits the personal overrides dsblank proposed in #2481.

If that suits you, I’ll draft the GitHub action and the `make.py` listing change for review, then the 5.2–6.1 addon.
