Repository navigation
Conversation
Adds app/web/i18n/it.js with all 557 keys translated, loads it in index.html, and extends tests/test_i18n.py so the consistency checks run over every shipped dictionary instead of en/de only. manual.file points at the English manual until a translated one exists; an it-IT browser gets the Italian UI automatically via resolveLang().
Point the Italian dictionary's manual.file at a full Italian translation of the user manual, keeping every anchor id identical so UI deep links keep working. The deep-link test now resolves the manual each dictionary points to instead of hardcoding the English and German files. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
Added a second commit with the Italian user manual (
All 532 tests pass, including the 16 i18n checks. |
- it.js: "incomplete" tooltips no longer read as a double negative ({what}
arrives as negative English text from the backend, e.g. "no address to
poll"); the live mode is "ARMATO" instead of "ATTIVO", which also meant
"dry-run on" and "enabled".
- Stamp test covers /i18n/it.js; dictionary header comments name all three.
- READMEs and both manuals list Italian as a UI language; the manual stays
English/German, the Italian UI links to the English one.
- CHANGELOG entry under [Unreleased].
|
Hi @paki81, thank you very much for this contribution. I merged your first commit (1eb9ecd) exactly as it is, so it's in main under your name. On top of it there is a small follow-up commit (bdc1966) with two wording fixes from my review. I decided not to take the Italian manual (manuale.html). The manual would have to be updated for every release, and I can't check/verify Italian content myself. Longer term I expect to drop the German manual as well and keep a single English manual for everyone. UI languages like Italian can be added as needed. Until then, the Italian UI links to the English manual. Because the manual commit isn't part of main, GitHub won't mark this PR as merged automatically, so I'll close it by hand. Your translation is in, thanks again! |
What
Adds an Italian (
it) UI dictionary, following the "one dictionary file + one<script>tag" recipe noted ini18n.js:app/web/i18n/it.js— all 557 keys translated; identical key set, order and{placeholder}sets asen.js(verified)app/web/index.html— loadsi18n/it.jsafterde.jstests/test_i18n.py— the consistency checks now iterate aDICTStuple covering every shipped dictionary instead of hard-codingen.js/de.js, so a new dictionary cannot silently drift fromen.jsBehavior
resolveLang()picksitautomatically forit/it-*browser locales; everyone else is untouched (English fallback unchanged).manual.filepoints atmanual.html— an Italian manual can follow as a separate contribution.Testing
pytest tests/— 532 passed (includes alltest_i18n.pychecks, now coveringit.js)it.jsis served, the page renders in Italian with an Italian browser locale