Proposal: Russian (ru) as a third GUI locale #3390
Ragnoryok1
started this conversation in
Ideas
Replies: 2 comments 1 reply
|
This proposal is superseded by #4172 — the branch was rebased onto the latest master (dsh-v0.1.1-rc.2), all upstream conflicts resolved, and new RU strings added for the keys upstream introduced since. Please use that discussion for the current state of the Russian localization: #4172 |
0 replies
|
Я для себя сделал тоже самое :) |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Proposal: Russian (ru) as a third GUI locale
I implemented a complete Russian localization of the Web UI and would like to offer it to the project (per CONTRIBUTING.md, external PRs are not accepted at the moment, so I am posting it here).
What it includes
ruadded toLOCALE_IDS/ the shipped locale list + host settings schema — the Language row, browser auto-detection and the persisted preference all pick it up.rudictionaries for every client namespace (chat, workspace browser, subagents, goals, jobs, model selector, sidebar, settings, permission presets, plan, directory picker, trajectory, session-log export, agent presets, commands, skills, deliverables, input triggers, theme, message feedback, user questions, workflow runs, cordis panel).one/few/other) in the five selection sites (1 задача / 2-4 задачи / 5+ задач).Verification
typecheck:contracts-readypasses — the typedregister(ns, { zh, en, ru })contract enforces completerucoverage.rukeys fall back to the existingFALLBACK_LOCALE(zh).Where the code is
Branch
feat/ru-locale(commitd5bfa20a88, rebased on the latestmaster) in my fork:https://github.com/Ragnoryok1/deepseek-harness_ru/tree/feat/ru-locale
Happy to rework anything (naming, key organization, splitting into a plugin once the core locale-id change is possible) — the goal is to get Russian into the harness however fits the project best.
All reactions