The panel speaks the page's language, the model answers in the reader's, and greetings and key warnings ship in 18 languages.
Every language
Two languages matter, and DocPilot keeps them apart. The panel's chrome — buttons, headings, hints — follows the lang of the page it sits on. The answer follows the language the reader typed, whatever language your docs are written in.
What ships, and what you supply
| Part | Language | Where it comes from |
|---|---|---|
| Answers | the reader's | the model, told to answer in the question's language |
| Greetings, thanks, goodbyes | the reader's, 18 languages built in | templates, answered with no model call |
| The pasted-key warning | the reader's, 18 languages built in | templates |
| Panel chrome | the page's | English by default; your i18n.locales for the rest |
The 18 built-in languages: English, Russian, Ukrainian, Spanish, Portuguese, French, German, Italian, Polish, Turkish, Japanese, Korean, Chinese, Arabic, Hebrew, Hindi, Greek and Thai.
Translating the chrome
Every reader-facing string has a key, and you override them one at a time — 185 strings in 26 groups. A key you leave out stays English; a key that does not exist is dropped and named in the build output, so a typo cannot pass silently. Strings take {name} placeholders and plural forms like {n, page|pages}.
The full key table, group by group, is in Translating the panel.