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

New issue

Open

opened 2026-10-01 10:14:22 +00:00 by tiagoagueda · 0 comments

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 shared decisions are made in postulo/postulo#349.

Where it stands

This repository has no catalogue yet: it becomes an installable plugin in #1, and #7 gives every template its translations in the plugin's own catalogues. It is not in Weblate.

Here

A component from the first catalogue. When #1 and #7 create locale/, the component plugin-templates is created with it (gettext PO, the same settings as the other plugin components), so no template's words are ever translated outside Weblate.
The same round trip as the other plugins: Weblate hears of each push; translations come back the way postulo/postulo#349 decides and are judged by this repository's CI; postulo-messages extract --check passes on what Weblate writes; the draft flag survives.
Context for the translator. A template's words are read on a CV or a letter, not in an interface. Each string should carry a comment saying where on the document it appears, since a translator cannot see the page.

Done when

The catalogues exist (#7) and are a Weblate component.
A string added to a template appears in Weblate with no manual step, and a translation saved there arrives as a change this repository's CI passes.

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 shared decisions are made in postulo/postulo#349. ## Where it stands This repository has no catalogue yet: it becomes an installable plugin in #1, and #7 gives every template its translations in the plugin's own catalogues. It is not in Weblate. ## Here - **A component from the first catalogue.** When #1 and #7 create `locale/`, the component `plugin-templates` is created with it (gettext PO, the same settings as the other plugin components), so no template's words are ever translated outside Weblate. - The same round trip as the other plugins: Weblate hears of each push; translations come back the way postulo/postulo#349 decides and are judged by this repository's CI; `postulo-messages extract --check` passes on what Weblate writes; the `draft` flag survives. - **Context for the translator.** A template's words are read on a CV or a letter, not in an interface. Each string should carry a comment saying where on the document it appears, since a translator cannot see the page. ## Done when - The catalogues exist (#7) and are a Weblate component. - A string added to a template appears in Weblate with no manual step, and a translation saved there arrives as a change this repository's CI passes.

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:06:04 +00:00

Say where this repository's words will be translated