Keybindings font makes `O` and `0` ambiguous when they are not side by side.

Open
#7,485 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
markdown
Domain
documentation

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.

Description

doc-enhancement

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:
image

image

The file in question: https://github.com/microsoft/vscode-docs/blob/main/docs/getstarted/userinterface.md

Dominant language
Markdown
Stars
6.7k
Forks
5.8k
Avg merge
1d 7h
Merged PRs (30d)
138

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-docs

All issues in microsoft/vscode-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.