openclaw - 💡(How to fix) Fix Question: preferred approach for Chinese (zh-CN/zh-TW) docs localization? [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…

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Hi team, first of all thank you for this amazing project.

I've been contributing Chinese localization (zh-CN/zh-TW) for the CLI install wizard in PR #79175. While working on it, I noticed the docs website (docs.openclaw.ai) has hundreds of pages, and the current .i18n/glossary.zh-CN.json and .i18n/glossary.zh-TW.json files still have many untranslated or imprecise entries that affect the automated Mintlify translation output.

I'd like to help improve the Chinese language experience further, but I want to ask for the team's guidance on the preferred approach:

Option A: Expand the glossary – Continue adding entries to .i18n/glossary.zh-CN.json and .i18n/glossary.zh-TW.json to improve the automated Mintlify pipeline output. This is low-maintenance and works with the existing workflow, but the quality depends on the pipeline.

Option B: Manual Chinese annotations – Add Chinese explanations/annotations directly in the English docs (e.g., parenthetical Chinese notes for key terms). This gives precise control but adds inline noise to the English source.

Option C: Full doc translation – Maintain separate Chinese versions of the docs pages. This is the most complete but also the most maintenance-heavy, and the docs are updated frequently.

Which approach would the team prefer or accept contributions for? I'm happy to follow whatever direction you think is sustainable.

Also, if there's any specific section of the docs that you'd prioritize for Chinese coverage (e.g., Getting Started, channel setup, CLI reference), please let me know.

Thank you for your time and consideration.

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 Question: preferred approach for Chinese (zh-CN/zh-TW) docs localization? [1 pull requests]