Various unicode symbols fail to display anywhere in the application after being displayed in italics
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
Tested on Windows 11 with Racket 8.8
Steps to reproduce:
- Open DrRacket
- Create a new racket file
- Paste 𝕣 into it
Once this is done, every 𝕣 character within the current window, as well as any 𝕣 characters displayed in new windows, will experience the bug until the application is completely restarted.
To confirm that italics are specifically the cause, you can reproduce the bug with comments if you change their style settings. Conversely, you can eliminate the bug from the REPL if you change it to not italicize errors.
Originally I encountered this problem just with the less conventional double struck letters (i.e everything but ℂ, ℍ, ℕ, ℙ, ℚ, ℝ, and ℤ), but looking into it further it seems to affect other characters like ⟜⌾◶⎉⍟⎊⥊⌽⍉⍋⍒⍷. They're all mathematical so far, but that could just be because I haven't tested much else. As for how broken italics breaks every other instance of the character, that's still a complete mystery to me.
For the time being, is there a way to disable italics for status bar error messages like there is for REPL ones?
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 by reproducing the issue in DrRacket on Windows 11 with Racket 8.8, using the pasted 𝕣 character and then comparing italicized comments, errors, and status-bar messages. Trace the italic rendering path and verify that mathematical Unicode symbols continue displaying correctly across the current and newly opened windows after the fix.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100