openclaw - 💡(How to fix) Fix [Bug]: Glossary zh-CN has untranslated entries (Status, Gateway); zh-TW glossary is English-only stub [1 pull requests]

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…

Two entries in the zh-CN glossary (docs/.i18n/glossary.zh-CN.json) are wrong, and the zh-TW glossary (docs/.i18n/glossary.zh-TW.json) is empty — all 19 entries only have English text.

Root Cause

Two entries in the zh-CN glossary (docs/.i18n/glossary.zh-CN.json) are wrong, and the zh-TW glossary (docs/.i18n/glossary.zh-TW.json) is empty — all 19 entries only have English text.

Fix Action

Fixed

Code Example

{ "source": "Status", "target": "Status" },

---

{ "source": "Gateway", "target": "Gateway 网关" },

---

{ "source": "ACP", "target": "ACP" },
{ "source": "Active Memory", "target": "Active Memory" },
{ "source": "CLI", "target": "CLI" },
{ "source": "Gateway", "target": "Gateway" },
{ "source": "Node", "target": "Node" },
...
RAW_BUFFERClick to expand / collapse

Summary

Two entries in the zh-CN glossary (docs/.i18n/glossary.zh-CN.json) are wrong, and the zh-TW glossary (docs/.i18n/glossary.zh-TW.json) is empty — all 19 entries only have English text.

Steps to reproduce

Problem 1: zh-CN has wrong/English-only entries

Open docs/.i18n/glossary.zh-CN.json. You will find:

{ "source": "Status", "target": "Status" },

"Status" is not translated — it should be "状态".

And:

{ "source": "Gateway", "target": "Gateway 网关" },

"Gateway" has an English prefix before the Chinese — it should just be "网关".

Problem 2: zh-TW has zero translations

Open docs/.i18n/glossary.zh-TW.json. Every entry looks like this:

{ "source": "ACP", "target": "ACP" },
{ "source": "Active Memory", "target": "Active Memory" },
{ "source": "CLI", "target": "CLI" },
{ "source": "Gateway", "target": "Gateway" },
{ "source": "Node", "target": "Node" },
...

All 19 entries are English-only — none have Traditional Chinese translations.

Expected behavior

  • glossary.zh-CN.json: "Status""状态", "Gateway""网关"
  • glossary.zh-TW.json: All 19 entries should have proper Traditional Chinese translations (e.g., "Gateway" → "閘道", "Node" → "節點", "CLI" → "命令列", etc.)

Actual behavior

As shown above — two wrong entries in zh-CN, zero translations in zh-TW.

OpenClaw version

main branch (commit 2f0b0bef)

Operating system

N/A

Install method

N/A

Model

N/A

Provider / routing chain

N/A

Logs, screenshots, and evidence

Files:

  • docs/.i18n/glossary.zh-CN.json (lines for "Status" and "Gateway")
  • docs/.i18n/glossary.zh-TW.json (all 19 entries)

Impact and severity

  • Affected: Chinese-speaking docs readers
  • Severity: Low — cosmetic, does not block usage
  • Frequency: Every time the glossary is viewed
  • Consequence: zh-CN readers see 2 incorrect entries; zh-TW readers see only English

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…

FAQ

Expected behavior

  • glossary.zh-CN.json: "Status""状态", "Gateway""网关"
  • glossary.zh-TW.json: All 19 entries should have proper Traditional Chinese translations (e.g., "Gateway" → "閘道", "Node" → "節點", "CLI" → "命令列", etc.)

Still need to ship something?

×6

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

Back to top recommendations

TRENDING