[Feature Request] Add Chinese (zh-CN) localization for Edge Tools sidebar UI
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript, vscode
- Domain
- localization
Research direction
Start by inspecting the existing files under src/i18n/ and the VS Code localization guide linked in the issue. Add the zh-cn.json translation alongside the existing locale files, covering the Edge Tools sidebar strings, and verify that the extension loads the Chinese translations correctly.
Written by the indexing model from the issue text.
Description
Summary
The Edge Tools extension UI (e.g., "Launch Instance", "Generate launch.json", "Documentation") is currently English-only. As a Chinese-speaking developer, I find it challenging to use the tool efficiently without translation.
Why this matters
- VS Code has strong Chinese community support (official Chinese language pack available)
- Edge Tools is widely used for debugging modern web apps
- Many developers in China rely on this extension daily
Proposed solution
Add zh-cn.json under src/i18n/, following VS Code's localization guide. The extension already has i18n infrastructure — only translation strings are missing.
Example translations needed:
| Key | English | Suggested Chinese |
|---|---|---|
launchInstance |
Launch Instance | 启动实例 |
generateLaunchJson |
Generate launch.json | 生成 launch.json |
documentation |
Documentation | 文档 |
reportBug |
Report a Bug | 报告问题 |
requestFeature |
Request a Feature | 提出功能建议 |
targets |
TARGETS | 目标 |
helpfulLinks |
HELPFUL LINKS | 有用链接 |
I am willing to contribute the full Chinese translation if the team approves this request.
Related
- Existing i18n structure: https://github.com/microsoft/vscode-edge-devtools/tree/main/src/i18n
- VS Code localization best practices: https:
- Dominant language
- TypeScript
- Stars
- 828
- Forks
- 359
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-edge-devtools
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-edge-devtools#4085 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/vscode-edge-devtools#5025 · 1 comment ·
-
f Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
microsoft/vscode-edge-devtools#5024 ·
-
xg Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
microsoft/vscode-edge-devtools#5023 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/vscode-edge-devtools#4970 · 1 comment ·
All issues in microsoft/vscode-edge-devtools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·