Translations: a working round trip between this repository and its Weblate project on translate.tiagoagueda.com #6

New issue

Closed

opened 2026-10-01 10:14:22 +00:00 by tiagoagueda · 1 comment

tiagoagueda commented

2026-10-01 10:14:22 +00:00

Owner

Requested by the maintainer on 2026-10-01, for every repository: integration and a fully working workflow of string translation with the corresponding translation project hosted on translate.tiagoagueda.com (Weblate). The work for the extension's sentences is postulo/postulo-chromium#13; the shared decisions are in postulo/postulo#349.

Where it stands

This repository holds no catalogue. The package is built from the commit of postulo-chromium that source.json pins and ships that commit's _locales/. There is nothing here for Weblate to read or write, and there should not be: a second component for the same sentences would have them translated twice.

Here

No component of its own, said in the README, with a pointer to where the extension is translated (the postulo-chromium component).
A translation reaches Firefox through the pin. After translations land in postulo-chromium, the pin has to move for a Firefox release to carry them; #5 already asks that a release be refused when the pinned commit lacks a language the release selects. Together those two are this repository's whole part in the round trip.

Done when

The README says where the Firefox extension is translated and how a translation reaches a release.
A release built here carries the translations merged in postulo-chromium at the pinned commit, checked as #5 describes.

Requested by the maintainer on 2026-10-01, for every repository: **integration and a fully working workflow of string translation with the corresponding translation project hosted on translate.tiagoagueda.com (Weblate).** The work for the extension's sentences is postulo/postulo-chromium#13; the shared decisions are in postulo/postulo#349. ## Where it stands This repository holds no catalogue. The package is built from the commit of postulo-chromium that `source.json` pins and ships that commit's `_locales/`. There is nothing here for Weblate to read or write, and there should not be: a second component for the same sentences would have them translated twice. ## Here - **No component of its own**, said in the README, with a pointer to where the extension is translated (the postulo-chromium component). - **A translation reaches Firefox through the pin.** After translations land in postulo-chromium, the pin has to move for a Firefox release to carry them; #5 already asks that a release be refused when the pinned commit lacks a language the release selects. Together those two are this repository's whole part in the round trip. ## Done when - The README says where the Firefox extension is translated and how a translation reaches a release. - A release built here carries the translations merged in postulo-chromium at the pinned commit, checked as #5 describes.

tiagoagueda added this to the 0.5.0 milestone

2026-10-01 10:14:22 +00:00

tiagoagueda added the

enhancement

label

2026-10-01 10:14:22 +00:00

tiagoagueda referenced this issue from Postulo/postulo

2026-10-01 10:14:23 +00:00

Translations: a working round trip between this repository and its Weblate project on translate.tiagoagueda.com #349

tiagoagueda referenced this issue from a commit

2026-10-10 12:03:11 +00:00

Build from the chromium commit that takes translations from Weblate only

tiagoagueda commented

2026-10-10 15:37:14 +00:00

Author

Owner

Done, as postulo/postulo#349 decided: this repository is a component in Weblate (translate.tiagoagueda.com) that follows main through a Forgejo webhook, drafts new strings by machine, and sends translations back as a pull request from the weblate branch; CI refuses a translation written outside Weblate. See this repository's commit referencing this issue, and postulo/postulo#829 for the first round trip, merged green.

Done, as postulo/postulo#349 decided: this repository is a component in Weblate (translate.tiagoagueda.com) that follows main through a Forgejo webhook, drafts new strings by machine, and sends translations back as a pull request from the `weblate` branch; CI refuses a translation written outside Weblate. See this repository's commit referencing this issue, and postulo/postulo#829 for the first round trip, merged green.

tiagoagueda closed this issue

2026-10-10 15:37:15 +00:00