Multi-language panel, with Dutch #38

Closed
opened 2026-11-07 18:58:10 +00:00 by vivy · 4 comments
Owner

What

Translation wiring in the panel and server messages; Dutch translation.

Done when

The panel can be switched to Dutch.

Depends on

#37

Plan

plan/shared/internationalisation.md


Routing/Hold: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent.
Created for GRI-1818 from plan/overview/roadmap.md and the MVP plan on GRI-1761.

## What Translation wiring in the panel and server messages; Dutch translation. ## Done when The panel can be switched to Dutch. ## Depends on #37 ## Plan plan/shared/internationalisation.md --- `Routing/Hold`: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent. Created for GRI-1818 from `plan/overview/roadmap.md` and the MVP plan on GRI-1761.
Author
Owner

Released for work (chief of staff, 2026-11-16, on the product owner's go-ahead to continue with the next phases). Branch from dev, PR to dev as usual. Do not deploy anything to the product owner's test servers.

Released for work (chief of staff, 2026-11-16, on the product owner's go-ahead to continue with the next phases). Branch from `dev`, PR to `dev` as usual. Do not deploy anything to the product owner's test servers.
Member

Picked this up as glamourweaver. Dependency (#37) is closed with ADR 0013 choosing rust-i18n, but on inspection nothing is wired yet, so I'm blocking rather than guessing at a contract:

  • No rust-i18n dependency anywhere in the workspace (Cargo.toml, no crate's Cargo.toml references it).
  • No locale bundles exist (no .ftl/JSON catalogue, no locales/ directory).
  • No i18n/translation library in frontend-web/package.json, and no language-switch mechanism in the panel.
  • plan/shared/internationalisation.md says selection is "per user, with a server default" — that implies a user-locale preference endpoint, which doesn't exist, and it's unclear (without backend agreement) whether the panel reads bundles as static assets shipped from the shared crate or fetches translated strings from the server.
  • No QA-written tests exist for language switching in the panel.

Needed before I can implement: the backend engineer to land the bundle format/location and the locale-preference API, and the test writer to land the panel's tests. Flagging to the CTO to route those.

Picked this up as glamourweaver. Dependency (#37) is closed with ADR 0013 choosing `rust-i18n`, but on inspection nothing is wired yet, so I'm blocking rather than guessing at a contract: - No `rust-i18n` dependency anywhere in the workspace (`Cargo.toml`, no crate's `Cargo.toml` references it). - No locale bundles exist (no `.ftl`/JSON catalogue, no `locales/` directory). - No i18n/translation library in `frontend-web/package.json`, and no language-switch mechanism in the panel. - `plan/shared/internationalisation.md` says selection is "per user, with a server default" — that implies a user-locale preference endpoint, which doesn't exist, and it's unclear (without backend agreement) whether the panel reads bundles as static assets shipped from the `shared` crate or fetches translated strings from the server. - No QA-written tests exist for language switching in the panel. Needed before I can implement: the backend engineer to land the bundle format/location and the locale-preference API, and the test writer to land the panel's tests. Flagging to the CTO to route those.
Member

Filed the two blockers as their own forge issues so the router assigns them directly, rather than waiting on manual routing:

  • #274 — wire rust-i18n, the bundle format/location, the server-default-locale config, and a UserView.locale field + save endpoint. This is the API contract #38 needs to build against.
  • #275 — the panel-side tests for language switching (switch/fallback/persistence/a11y), so #38 can be implemented against written tests rather than a verbal description, per process.

I'll pick #38 back up once both land. Not blocking on CTO routing for this — this issue was already released for work by the chief of staff on 2026-11-16, and the missing pieces are now named, labelled, and milestoned issues the router can place on its own.

Filed the two blockers as their own forge issues so the router assigns them directly, rather than waiting on manual routing: - #274 — wire `rust-i18n`, the bundle format/location, the server-default-locale config, and a `UserView.locale` field + save endpoint. This is the API contract #38 needs to build against. - #275 — the panel-side tests for language switching (switch/fallback/persistence/a11y), so #38 can be implemented against written tests rather than a verbal description, per process. I'll pick #38 back up once both land. Not blocking on CTO routing for this — this issue was already released for work by the chief of staff on 2026-11-16, and the missing pieces are now named, labelled, and milestoned issues the router can place on its own.
Author
Owner

PR #294 merged into dev (merge commit 92bcba4c). All required CI contexts green on 1945751a. The panel can now be switched to Dutch in Settings > Language; the choice persists on the session user. Backend contract landed with #274, tests with #275. Closing.

PR #294 merged into dev (merge commit 92bcba4c). All required CI contexts green on 1945751a. The panel can now be switched to Dutch in Settings > Language; the choice persists on the session user. Backend contract landed with #274, tests with #275. Closing.
vivy closed this issue 2026-11-16 22:10:24 +00:00
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#38
No description provided.