Hi maintainer,
I'm a LoopX user (and potential contributor) looking to localize the dashboard UI into Chinese. Before opening a PR, I want to confirm the preferred direction so I don't go against the project's intent.
What I observed (v0.4.3):
dashboard-page.tsx already hardcodes Chinese for status/priority/connection mapping tables (e.g. user_or_controller: "用户 / 控制者", high: "高优先级", connected: "已连接").
- But many other surfaces are still English:
frontstage-page.tsx (~3951 lines, the largest view), ui/* components, data/status.ts, router.tsx, etc.
- No i18n library is present; the only i18n touch is
Intl.NumberFormat("en-US", …).
- No i18n/localization issue exists in the tracker;
docs mentions of "localized" refer to data-layer labels, not a UI framework.
Question: Which do you prefer for community-contributed localization?
- Introduce a proper i18n framework (e.g.
react-i18next) with zh-CN + en catalogs and a language switcher — multilingual, more work, adds a dependency.
- Continue the current inline-Chinese approach (extend
dashboard-page.tsx's existing style) — simpler, matches today's code, but no language toggle.
I'll follow whichever you prefer and align terminology with the existing Chinese docs. Thanks!
(中文说明:我是 LoopX 用户/潜在贡献者,想把仪表盘 UI 中文化。发现主仪表盘 dashboard-page.tsx 已硬编码中文,但 frontstage-page.tsx 等其余视图仍是英文,且仓库无 i18n 框架、issues 中也无 localization 讨论。想确认上游更倾向"引入 i18n 框架实现多语言"还是"延续当前内联中文"路线,以免 PR 被拒或重复造轮子。)
Hi maintainer,
I'm a LoopX user (and potential contributor) looking to localize the dashboard UI into Chinese. Before opening a PR, I want to confirm the preferred direction so I don't go against the project's intent.
What I observed (v0.4.3):
dashboard-page.tsxalready hardcodes Chinese for status/priority/connection mapping tables (e.g.user_or_controller: "用户 / 控制者",high: "高优先级",connected: "已连接").frontstage-page.tsx(~3951 lines, the largest view),ui/*components,data/status.ts,router.tsx, etc.Intl.NumberFormat("en-US", …).docsmentions of "localized" refer to data-layer labels, not a UI framework.Question: Which do you prefer for community-contributed localization?
react-i18next) withzh-CN+encatalogs and a language switcher — multilingual, more work, adds a dependency.dashboard-page.tsx's existing style) — simpler, matches today's code, but no language toggle.I'll follow whichever you prefer and align terminology with the existing Chinese docs. Thanks!
(中文说明:我是 LoopX 用户/潜在贡献者,想把仪表盘 UI 中文化。发现主仪表盘
dashboard-page.tsx已硬编码中文,但frontstage-page.tsx等其余视图仍是英文,且仓库无 i18n 框架、issues 中也无 localization 讨论。想确认上游更倾向"引入 i18n 框架实现多语言"还是"延续当前内联中文"路线,以免 PR 被拒或重复造轮子。)