Ligatures for #( and #{ are very difficult to read
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 82k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
I am working on a Python project whose documentation often include LilyPond code, which contains Scheme-like syntax. The ligatures for #( and #{ are very difficult to read. See red arrows below (green arrow shows that #} behaves fine):
Is this the intended output?
Contributor guide
No contributing guide indexed for this repository
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 attached image and compare the rendering of #( and #{ with the #} example. No source file or test is named, so locate the relevant ligature definitions and determine whether the output is intended. Done means the expected rendering is established and the readability issue is addressed or clearly explained.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100