Simplified Chinese GitHub Mobile article displays an untranslated English body
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation, localization
Research direction
Open the affected entry point at https://docs.github.com/zh/get-started/using-github/github-mobile and compare its title, introduction, table of contents, and body with the English article. Locate the Simplified Chinese source for this page and translate the content beginning with “About GitHub Mobile” through the remaining sections. Done means the headings and article body display in Simplified Chinese under the /zh/ locale.
Written by the indexing model from the issue text.
Description
What article on docs.github.com is affected?
https://docs.github.com/zh/get-started/using-github/github-mobile
What part(s) of the article would you like to see updated?
The Simplified Chinese version of the “GitHub Mobile” article has a translated title and introduction, but its table of contents and almost the entire article body are still displayed in English.
The untranslated content starts with “About GitHub Mobile” and continues through the remaining sections of the article.
Expected outcome: The article body and section headings should be displayed in Simplified Chinese, consistent with the selected /zh/ locale.
Additional information
The issue is consistently reproducible by opening the URL above with the Simplified Chinese locale selected. The page also displays the notice that some content may be machine- or AI-translated, but in this case the body does not appear to have been translated at all.
- Dominant language
- TypeScript
- Stars
- 20.9k
- Forks
- 68.8k
- Avg merge
- 13h 55m
- Merged PRs (30d)
- 105
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 github/docs
-
content triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
builder persona triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
content localization
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
content localization
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
content dependabot needs SME
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·