Multi-language panel, with Dutch #38
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage#38
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.mdand the MVP plan on GRI-1761.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 todevas usual. Do not deploy anything to the product owner's test servers.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:rust-i18ndependency anywhere in the workspace (Cargo.toml, no crate'sCargo.tomlreferences it)..ftl/JSON catalogue, nolocales/directory).frontend-web/package.json, and no language-switch mechanism in the panel.plan/shared/internationalisation.mdsays 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 thesharedcrate or fetches translated strings from the server.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.
Filed the two blockers as their own forge issues so the router assigns them directly, rather than waiting on manual routing:
rust-i18n, the bundle format/location, the server-default-locale config, and aUserView.localefield + save endpoint. This is the API contract #38 needs to build against.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.
PR #294 merged into dev (merge commit
92bcba4c). All required CI contexts green on1945751a. 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.