LAION-AI / LAION-AI/Open-Assistant
Monospace font does not render Morse code correctly (and will have other issues).
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 37.4k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
The monospace font used by the web client cannot render Morse code properly. The dots are sometimes rendered level with the dashes (in the middle, like a multiply operator), and other times, level with the line (at the bottom, like a period).
This seems to be caused by using a font with ligatures that were optimized for rendering code. If so, there will be other corner-cases, so we should switch to something more general purpose (I would recommend IBM Plex Mono).
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
Start in the web client's font configuration and reproduce the Morse code rendering shown in the issue. Check the current monospace font's treatment of dots and dashes, then verify that the selected general-purpose font renders Morse code correctly without introducing the reported font issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100