-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Characters with more vertical content (e.g "f") overlap with overhead bar #463
Comments
Hi @darsnack . Please copy and paste the letters. This will be a great help. |
I use these characters in Julia, and I created them using the Julia REPL. I pasted the characters and the sequence I typed into the REPL to generate them below The first screenshot:
The second screenshot:
|
I see what the problem is. Will fix this in the one of the next updates. |
- Added Control code support #241 - Update all # dependent glyphs #275 - Added Ɛ ↋ ↊ ૪ #356 - Changed the look of ~@ ligature #415 - Added EMQuad (u+2001) #439 - The tail of Italic “f” made shorter #441 - Reworked⚠️ #450 - Added SemiBold weight #453 - Added more anchors to the marks #463 - Added replacement (u+FFFD) #461 - Added zeroWidthNoBreakSpace (u+FEFF) #467 - Fixed consistent of J in italic
Hi, please grab files from here https://github.com/JetBrains/JetBrainsMono/tree/master/fonts and confirm/deny postive change. Thanks in advance! |
Ok, thanks for the feedback I will continue to work on that |
Please test again. |
Sorry for the delay. Just tested again, and it looks good. Thanks for your work! |
No worries. I was pretty confident this time .)) |
See the screenshot below. Certain characters when combined with an overhead bar look like they are overlapping with the bar. This is especially hard to read for cases like "f" or "t" where it becomes difficult to see what overhead character is used at a glance.
For example, the following are "f" + "bar" and "f" + "hat/carrot".
Sorry that I am not familiar with the Unicode numbers off the top of my head.
The text was updated successfully, but these errors were encountered: