microsoft / microsoft/vscode-docs
Keybindings font makes `O` and `0` ambiguous when they are not side by side.
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 5.8k
- Avg merge
- 11h 43m
- Merged PRs (30d)
- 123
Description
The font used for the commands makes O look like 0 to inexperienced users. I'm sure that 0 actually has a slash through it, but when first navigating to a page, it's ambiguous. I was stuck wondering why Ctrl+Shift+0 wasn't working.
A possible work around that doesn't involve changing the font, would be to use o instead of O. That is "o" instead of "O".
Compare the html element's font to the tooltip font:
The file in question: https://github.com/microsoft/vscode-docs/blob/main/docs/getstarted/userinterface.md
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
Open docs/getstarted/userinterface.md and inspect the keybindings HTML element alongside the tooltip shown in the issue images. Compare their fonts and determine whether the page should use a less ambiguous character or font; done means the keybinding no longer makes O and 0 difficult to distinguish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100