The portal in English and Turkish: a catalogue per language, a switcher at the foot of every page, landing.language, Turkish numbers and dates

Every template and handler message in internal/web goes through a JSON
catalogue under internal/web/locales/<code>/, with English as the fallback.
The language is the person's choice (a cookie set by /_lang/{code}), else
Accept-Language, else landing.language. Tests refuse a key some language
lacks, a translation with other arguments than English, and template text
left in English.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-05 00:12:53 +02:00
1 parent 30f7f3474a
commit 11231d8c2b
113 files changed
+8091 -1981

No files matched your search

+28
View File
@@ -1337,6 +1337,34 @@ thing to get right is the health check: point it at `/ready`, not `/health`.
so a load balancer using it would send half the traffic to something that
refuses every request.
## The portal's language
The web portal — the landing page, sign-up and sign-in, the account and chat
pages, and the administrators' pages — speaks English and Turkish. Each person
gets, in this order:
1. the language they chose with the switcher at the foot of every page, which
is remembered in a cookie (`llmgw_lang`) for a year;
2. otherwise the first language their browser asks for that the portal speaks;
3. otherwise the server's own default:
```yaml
# /etc/llmgw/server.yaml
landing:
language: tr # en or tr; empty is English
```
A code the portal does not speak stops the server starting, rather than
quietly serving English. Figures and dates follow the page's language: a
Turkish page writes 1.234,5 and 04.10.2026. Messages that come from the
control plane itself — a node's warnings, an engine's errors — are shown as
they were written, in English. The API, the CLI and the console are English.
Adding a language is adding a directory: `internal/web/locales/<code>/` with
the same files and keys as `locales/en/`, and its `_meta.*` entries saying how
it writes numbers and dates. The tests refuse a catalogue that lacks a key a
page uses.
## Single sign-on
People can sign in through your identity provider — Keycloak, Entra ID,