Repository navigation
[FEATURE]: Land TUI i18n groundwork adapted from #48731 #53857
Description
Activity
Thanks for picking up the TUI i18n work and carrying #48731 forward!
I think this is a duplicate of #37216. That issue is still open and asks for the same thing: moving the hardcoded TUI strings into per-locale dictionaries with a language/locale setting. Your PR #52000 can link #37216 as the issue it closes, so the discussion stays in one place.
Possible duplicates and related issues, ordered by likelihood:
- [FEATURE]: i18n support for TUI (terminal interface) #37216: open request for TUI i18n (hardcoded TUI strings moved to i18n keys, plus a locale config option). Same scope as this issue.
- [FEATURE]: Russian (ru) localization / i18n support for the TUI interface #43533: open request for Russian TUI localization, which needs the same i18n groundwork.
- [FEATURE]: Plugin hook for localizing built-in TUI text (command titles and UI strings) #45490: open request for a plugin-API hook to localize built-in TUI text. Related, but a different approach.
- [FEATURE]: Add TUI/Chamber interface localization (i18n) support #39846: earlier TUI localization request, closed after 60 days of no activity.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how it differs from #37216.
Thanks for the triage — agreed, this is the same scope as #37216 (extract
packages/tuihardcoded strings into per-locale dictionaries + a language/locale config option). I opened this issue to carry #48731's stalled work forward and to give PR #52000 an issue-first link; no difference worth keeping separate. Closing as duplicate of #37216 is fine — I've updated PR #52000 to close #37216 instead.
Feature hasn't been suggested before.
Describe the enhancement you want to request
The TUI (
packages/tui) currently ships zero i18n: roughly 700–1000 user-facing strings are hardcoded English, while the app/desktop side already has per-locale dictionaries.#48731 by @neriousy laid down the full groundwork (lazy per-locale dictionaries,
t()/plural()/number()helpers, language picker,config.language) and the architecture looked solid in review, but the PR has been stalled — no updates since 2026-09-23 and no response to the collaboration comment on the PR.Rather than let that work rot, I would like to carry it forward:
v2branch (it had fallen ~550 commits behind).fail/attempthelpers) while keeping the PR'slanguage.t(...)wiring.All of @neriousy's original commits are preserved via a merge commit, so authorship stays intact.
Related: #48731
Follow-up PR: #52000
Note: this supersedes #51998, which was auto-closed by the issue-compliance workflow before its body was converted to the feature-request template structure. The original request is preserved there; this issue carries the same scope in template form.