openclaw - 💡(How to fix) Fix [Feature]: Translate Control UI chat panel (welcome, run controls, message placeholder) via i18n

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The Control UI chat panel (welcome screen, run control buttons, message placeholder) uses hardcoded English strings, and the locale files are missing the corresponding translation keys.

Root Cause

The Control UI chat panel (welcome screen, run control buttons, message placeholder) uses hardcoded English strings, and the locale files are missing the corresponding translation keys.

RAW_BUFFERClick to expand / collapse

Summary

The Control UI chat panel (welcome screen, run control buttons, message placeholder) uses hardcoded English strings, and the locale files are missing the corresponding translation keys.

Problem to solve

Three issues in the chat UI:

  1. Welcome screen (ui/src/ui/chat/chat-welcome.ts): "Ready to chat" and hint text are hardcoded English, not using t()
  2. Run controls (ui/src/ui/chat/run-controls.ts): All button tooltips (New session, Export, Send, Stop, Queue, Attach file) are hardcoded English title/aria-label attributes
  3. Message input (ui/src/ui/views/chat.ts): Placeholder text like "Message {name} (Enter to send)" and talk button labels are hardcoded

Additionally, ui/src/i18n/locales/en.ts and ui/src/i18n/locales/zh-CN.ts are missing the chat.welcome.* translation keys needed by these components.

Proposed solution

  1. In ui/src/i18n/locales/en.ts — add chat.welcome translation keys: ready, hint, attachFile, startTalk, newSession, exportChat, sendMessage, queueMessage, stopGenerating, stopTalk, messagePlaceholder, chatSession, chatModel, thinkingLevel
  2. In ui/src/i18n/locales/zh-CN.ts — add the same keys with Chinese translations; also fix 6 instances where skills: "Skills" should be skills: "技能"
  3. In ui/src/ui/chat/chat-welcome.ts — add import { t }, wrap strings with t()
  4. In ui/src/ui/chat/run-controls.ts — add import { t }, wrap title/aria-label strings with t()
  5. In ui/src/ui/views/chat.ts — wrap placeholder and talk button strings with t() (the import { t } already exists)

Alternatives considered

Could hardcode Chinese text in zh-CN.ts without adding English keys to en.ts, but that would break the pattern used elsewhere (English keys in en.ts are the source of truth).

Impact

  • Affected: Chinese-speaking Control UI users; non-English users in general
  • Severity: Low (cosmetic — buttons still work, text is just in English)
  • Frequency: Every time a user opens the chat panel
  • Consequence: Chinese users see English-only text for chat controls and welcome messages, even when the rest of the UI is in Chinese

Evidence/examples

Confirmed by reading current source: chat-welcome.ts line 69, run-controls.ts lines 25-76, views/chat.ts lines 808-1309 all have hardcoded English. Locale files en.ts and zh-CN.ts have no chat.welcome section.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Feature]: Translate Control UI chat panel (welcome, run controls, message placeholder) via i18n