[Documentation] Three English menu entries fall back to Chinese-only content
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Start with the English and Chinese menu entries and the listed source files: docs/assets/guide/zh/tutorial_docs/Chart_Types/Candlestick.md and the corresponding FAQ files under docs/assets/faq/zh and docs/assets/faq/en. Compare the locale source trees and review the live English routes before choosing whether to add reviewed translations or adjust the English menu. Done means the three English entries no longer display Chinese article bodies.
Written by the indexing model from the issue text.
Description
Documentation URL
- https://www.visactor.io/vchart/guide/tutorial_docs/Chart_Types/Candlestick
- FAQ menu entry
145- How to show the full content of abbreviated text when hovering with the mouse - FAQ menu entry
186- How to add custom content to the bottom of a tooltip card in vChart
Description
The English menus advertise all three pages, but the fixed develop snapshot (0750d74cd6ea734e66897876506c78ca12680676) has only their Chinese source files:
docs/assets/guide/zh/tutorial_docs/Chart_Types/Candlestick.mdhas noencounterpart.- FAQ entries 145 and 186 exist under
docs/assets/faq/zhbut notdocs/assets/faq/en.
On the live English routes, the page titles are English while the article bodies fall back to Chinese. English-language navigation therefore leads to untranslated content.
Expected: add reviewed English versions for the three advertised pages, or hide/mark the entries in the English menu until translations are available.
I fetched all 4,627 open/closed issues and pull requests and searched their current titles and bodies for the Candlestick English page and FAQ 145/186. I also compared every menu leaf against the locale source trees and reviewed the relevant history. There are no Discussions and I found no current owner, linked PR, commit, or duplicate. I have not proposed machine-generated translations because these pages need terminology and example review.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 219
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 VisActor/VChart
-
[Bug] 官网文档的图片挂了Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
[Bug] openinula-vchart ignores data prop when spec is providedPossibly taken @dyk1454683243-sudo claimed this 21 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
VisActor/VChart#4657 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cameri/nostream#811 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dam-agents/dam#4562 ·
Maintainers usually reply within 1 day
-
bug p3 triaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug javascript P2-medium python release:v3.1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
adrirubio/claude-deck#546 ·
Maintainers usually reply within 1 day