Repository navigation
Replies: 4 comments
|
这个提案的验收条件已经比“翻译文件存在”完整很多。为了让外部语言包走向内置 locale 时仍可回归,建议把以下内容写成可重复的 release gate:
独立社区手册维护了多语言入口和社区插件审计说明:https://github.com/sandbaseai/deepseek-harness-handbook/blob/main/docs/en/security/community-plugin-audit.md 。它不是 DeepSeek AI 官方项目;建议在最终 PR 中继续标注 upstream revision 与验证日期。 |
|
谢谢!这些 release gate 建议基本都已实现或已规划:
若内核采纳内置 ru,社区字典可直接按包拆分贡献,验收门槛以上述 gate 为准。 (EN: most gates already implemented — pinned-revision key manifest with bidirectional placeholder checks in CI, a real plural-agreement defect class found and fixed, clean-room install/rollback tests for the external path. If core bundling is accepted, the community dictionaries can be contributed per-package against these gates.) |
|
I support adding Russian as a built-in language in the Harness UI, available out of the box without installing a third-party plugin. Please include Russian translations for menus, buttons, settings, and user-facing messages, while keeping English available. Please also add an “Auto” language option that selects the UI language based on the browser’s preferred language in the Web UI or the operating system’s language in the desktop app. For Russian browser/system locales (including ru-RU), it should automatically use Russian. Users should still be able to choose a language manually in Settings, with English as the fallback when a translation is unavailable. Thank you for considering this! |
|
Related proposal, may matter for how this one ships: make the UI locale an ordered preference list (e.g. Details and a link list of the other language threads: #11699 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
一句话说明预期结果:Web UI 的语言选择器在 zh / en 之外提供「Русский」(俄语),与内置语言一样随内核发布。
验收与细节
cd5ef81通过;一条命令即可安装验证:dsh plugin --profile web add github:warment/deepseek-harness-locale-ru。English summary. Proposal: ship Russian as a third built-in UI locale alongside zh/en. A complete, CI-verified corpus (33 namespaces, 1061 keys, formal register, unified glossary) already exists in the community pack deepseek-harness-locale-ru and can be contributed upstream as a reviewed PR series (locale definition first, then per-package dictionaries). Two additional options if core bundling is out of scope: (a) a docs link to community locale packs, and (b) a small refactor — moving slash-command descriptions and command settlement texts (currently source constants in host packages such as plan-mode, compaction, feedback, goal, session-log-export) into the client locale registries, which would let any locale pack translate them.
All reactions