The interface speaks Slovak

969 strings, an instance default and a per-person choice, and no half-done corner: the admin prose is translated too. Design and reasoning: LLeMbas.wiki/Translations. KEYED BY THE ENGLISH SENTENCE A missing entry renders the key, which is the English -- so an untranslated string looks as it always did, an English instance is byte-for-byte 1.6.0, and a half-finished catalogue is a half-translated page rather than a page of dotted key names. The cost is that editing an English sentence orphans its translation silently, which is what tests/test_translations.py asserts in both directions. No gettext: .po -> .mo is a build step and this project does not have one. A JINJA GLOBAL, AND THEREFORE A CONTEXTVAR `t()` is a global for the reason `brand` already documents -- render() is bypassed by 25 TemplateResponse calls and 8 get_template().render() calls, the latter being the SSE frames, which have no Request at all. A global is bound once at import and the language is per person, so the active language is a ContextVar set per request. 🚨 `get_current_user` had to become `async def`. FastAPI runs a sync dependency in a threadpool, and anyio copies the context in and discards it on the way out -- so the language was set where nothing could see it and every page rendered in the instance's language whatever anybody had chosen, with no error anywhere. NOT TRANSLATED, ON PURPOSE Everything a model reads: the 60 prompt fragments, and the dates in harness.py, schedule/runner.py and schedule/compile.py. Only `i18n.stamp` is localised, and only where a person reads it -- with the *format* translatable as well as the words, because "26. septembra 2026" is a different pattern rather than the same one with different words in it. A process locale is not an option: global, not thread-safe, two people's pages at once. A second fragment telling models to answer in the reader's language was written during this work and removed: `core.style` has said it since long before, and test_an_empty_override_turns_a_fragment_off caught the duplicate. THE BULK PASS 1213 sites wrapped by a one-off script that only touched patterns it could not misread. It got three wrong in a way that mattered -- `t('…')` inside `attr="…"` where the sentence held an apostrophe, closing the Jinja string and 500ing two pages whose partials no test renders. tests/test_translations.py now compiles all 110 templates. It also wrapped the product's own name, an SSH key header, a keystroke hint and an example URL, all taken back out: a string is not translatable just because it is a string. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-26 14:46:33 +00:00
parent da0797ccad
commit a16510aba8
104 changed files with 3833 additions and 1788 deletions
@@ -16,6 +16,36 @@ for 1.0.0 have something to be assembled from.

 ## Unreleased

+## 1.7.0
+
+- **The interface speaks Slovak.** Pick a language under **Appearance** in your
+  own settings, or set what everybody else gets under Admin → General. Your own
+  choice wins over the instance's, it is saved to your account rather than to one
+  browser, and `<html lang>` finally says what the page is actually in.
+
+  All 969 translatable strings are translated, including the long explanatory
+  paragraphs on the admin pages — there is no half-done corner where a Slovak
+  instance falls back to English. Dates follow too: a month name is a month name
+  in the language you are reading, which `strftime` cannot do without a process
+  locale that this application must not set.
+
+  **What is deliberately still in English**: everything a *model* reads. The
+  prompt fragments under Admin → Prompts are instructions written for models, and
+  translating them would change what the models are told rather than what you
+  see. Models answer in whatever language you write to them in — they already
+  did, and that line is editable where all the others are.
+
+  An English instance is byte-for-byte what shipped in 1.6.0. That is a property
+  of the design rather than a claim: a string with no translation renders the
+  English it was written in, so a language added later cannot leave holes in a
+  page.
+
+- Fixed: **every page was rendered in the instance's language, whatever anybody
+  had chosen.** Found while building the above and worth naming because it would
+  have been invisible: the language was resolved in a dependency that FastAPI runs
+  in a threadpool, and the context it was set in is discarded on the way out. Now
+  it is resolved in the request's own task.
+
 ## 1.6.0

 - **A chat can have a crowd.** Switch it on under Admin → Agents, and each chat's