zai-org / zai-org/feedback

[建议 / Feature] improve UI with i18n

Open
#151 15 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2 status: 待评估 type: 功能建议
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

提交前确认 · Pre-submission checklist
  • 我已搜索过现有 issue,确认这不是重复提议 / I searched existing issues and confirmed this isn't a duplicate.
  • 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category

UI / 界面体验 · UI / UX

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

使用场景 · Use case

I would like to suggest adding Korean language support to the ZCode UI. Currently, the i18n implementation on ZCode is incomplete or unsmooth, which makes the user experience slightly disappointing for Korean users when navigating the interface.

建议方案 · Proposal
  • Provide an official localization for the ZCode UI.
  • Optimize the general multi-language (i18n) rendering so that text layouts flow smoothly without any formatting breaks.
预期价值 · Expected value

It will significantly lower the entry barrier for Korean developers and improve the overall day-to-day workflow comfort.

你认为的优先级 · Your perceived priority

None

你使用的 ZCode 版本 / 环境 · ZCode version / environment

No response

补充材料 · Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the ZCode UI's existing i18n implementation and determine how locale resources and text layout are handled; done means Korean localization is available and multilingual text renders without formatting breaks.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, internationalization
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.