i18n(slash): localize 4 lagging slash handlers#448
Merged
Conversation
Most handler files were already 80%+ i18n'd from prior work, but
four files had drift:
- web-search-engine.ts — 0 t() calls, the entire help text plus
switch confirmation was hardcoded English. Whole new
handlers.webSearchEngine namespace (~12 keys).
- mcp.ts — 5 hardcoded usage / unknown-server / "(none)" /
reconnect-not-wired strings; added under handlers.mcp.
- plans.ts — the archive row template ("✓ {when} {N} steps · …"),
"complete" verb, and the /stop abort line. Added under
handlers.plans.
- semantic.ts — code-mode-only refusal + "checking…" status.
Added under handlers.semantic. Note this file uses two t()
instances side-by-side — the local @/index/semantic/i18n one
stays for the existing slashHeader/slashEnabled keys, and the
main @/i18n/index t (aliased as tMain) is added for the two new
strings.
zh-CN translations included for all ~22 new keys.
Test plan: full suite 2301 pass, tsc + biome clean.
This was referenced May 8, 2026
ChasLui
pushed a commit
to ChasLui/DeepSeek-Reasonix
that referenced
this pull request
May 23, 2026
Most handler files were already 80%+ i18n'd from prior work, but
four files had drift:
- web-search-engine.ts — 0 t() calls, the entire help text plus
switch confirmation was hardcoded English. Whole new
handlers.webSearchEngine namespace (~12 keys).
- mcp.ts — 5 hardcoded usage / unknown-server / "(none)" /
reconnect-not-wired strings; added under handlers.mcp.
- plans.ts — the archive row template ("✓ {when} {N} steps · …"),
"complete" verb, and the /stop abort line. Added under
handlers.plans.
- semantic.ts — code-mode-only refusal + "checking…" status.
Added under handlers.semantic. Note this file uses two t()
instances side-by-side — the local @/index/semantic/i18n one
stays for the existing slashHeader/slashEnabled keys, and the
main @/i18n/index t (aliased as tMain) is added for the two new
strings.
zh-CN translations included for all ~22 new keys.
Test plan: full suite 2301 pass, tsc + biome clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Most handler files were already 80%+ i18n'd from prior work, but four files had drift / gaps. Quick survey of `grep -c 't("' src/cli/ui/slash/handlers/*.ts` flagged the laggers; this PR closes them.
What
zh-CN translations included for all ~22 new keys.
Note on `semantic.ts`
This file already uses `t` from `@/index/semantic/i18n.js` for its rich status renderer (slashHeader, slashEnabled, etc.). The new two strings need the main `@/i18n/index` instead, so I aliased it as `tMain` rather than rename the existing `t`. Two t() instances side-by-side looks odd but the alternative would have been a 50-line rename.
Test plan
Status of the i18n sweep
After this lands, the surface that was flagged in the original audit is fully covered:
Plus the 5xx friendly error UX from the original red-apple bug report (#440).
Anything still hardcoded after this is incidental (small-bite next-time fixes), not the systemic class of "Chinese user sees raw English."