i18n: more zh-CN gaps in settings and issue detail (placeholders, toasts, sidebar headers)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
- I have searched the existing issues
Summary
Follow-up to #9777: another batch of user-visible strings still renders in English under the zh-CN locale — settings sidebar headers, profile/preference form placeholders, validation errors and toast messages, project feature toggles, issue link/reaction/relation toasts.
Why should this be worked on?
These are the most-touched surfaces for daily use (settings and issue detail). Mixed-language UI is jarring for non-English teams and inconsistent with the rest of the translated interface.
The fix routes ~50 hardcoded strings through i18n keys (34 new keys, en + zh-CN translations; other locales synced with English values to satisfy the i18n sync-check CI).
Working implementation in the linked PR.
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.
Research direction
Start with the working implementation referenced in the issue and inspect the settings and issue-detail surfaces listed in the summary. Verify that the roughly 50 hardcoded strings use the 34 new i18n keys, that English and zh-CN translations are present, and that the i18n sync-check CI passes for other locales.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, internationalization, localization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100