You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Font rendering issue; characters appear at wrong size, position #4367
Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.8.10091.0
Font: JetBrains Mono
Steps to reproduce
Sometimes font doesn't render properly: some characters are too tall or too short. Sometimes it's numbers, sometimes it's capital case letters. Regular conhost window or ConEmu don't have this problem.
Expected behavior
Font characters render properly.
ConEmu example. Everything seems to render properly.
Actual behavior
Some characters are too tall or too short. You can see it in capital case letters.
This might be related to #610, but this seems subtle enough that it might not be. I'm going to leave this open to make sure we address this particular issue.
Aleksey Usatov (@tuscen) that's excellent to hear. I'd usually love to have an actual commit to link this to for future people that run into this issue, but we've changed so much about our rendering stack since 0.8 that it'd be hard to pin this down exactly.
Activity
zadjii-msft commentedon Jan 27, 2020
This might be related to #610, but this seems subtle enough that it might not be. I'm going to leave this open to make sure we address this particular issue.
hnakamur commentedon Feb 15, 2020
I have the same issue for Japanese characters.
I created a gist to reproduce the problem https://gist.github.com/hnakamur/2a123ce7bdc0d7e5070218c258f990a8
I also added some screenshots there.
You can run the following command in a Ubuntu (Windows Subsystem for Linux) shell.
[-]Font rendering issue[/-][+]Font rendering issue; characters appear at wrong size, position[/+]zadjii-msft commentedon Apr 14, 2020
I know Michael Niksa (@miniksa) was mucking with the baselines in #5345, maybe this is related?
tuscen commentedon Apr 14, 2020
Looks like it was fixed. I do use a 4K display with 150% scaling.
zadjii-msft commentedon Apr 14, 2020
Aleksey Usatov (@tuscen) that's excellent to hear. I'd usually love to have an actual commit to link this to for future people that run into this issue, but we've changed so much about our rendering stack since 0.8 that it'd be hard to pin this down exactly.
Thanks for following up though!
hnakamur commentedon Apr 21, 2020
Sorry for late reporting, but my issue was also resolved since version: 0.10.781.0.
Thanks for a great product!