Repository navigation
Font rendering issues in Terminal #610
Description
I have Terminal up and running under 18362.0, but it seems to have problems with certain types of fonts.
Here it is working fine with the font set to "SF Console":
But it breaks when the font is changed to "SF Console Medium" (but not because the font isn't found or anything). The app doesn't crash but the text is rendered... let's just say extremely incorrectly:
If you focus extremely well and zoom in all the way, you can see that text is being rendered.. just very oddly so. Change the font back and it redraws correctly to what it used to contain.
Here's the same screenshot from conhost with the font set to "SF Console Medium" via the registry:
It's not just an issue with setting a variant of a font, or this particular font. Here's how the default (free) "Roboto Slab" is rendered, but I'm not sure if it's the same problem (it doesn't look like it):
Activity
zadjii-msft commentedon May 9, 2019
Michael Niksa (@miniksa) is the guy who will know why this is happening.
miniksa commentedon May 14, 2019
Is "SF" the San Francisco font from Apple that we're absolutely not authorized nor licensed to use outside of an Apple computer?
If so, I can't investigate this and have to slam it closed. I can't debug/diagnose fonts I'm not licensed to use and I can't condone having other people break that license agreement.
mqudsi commentedon May 14, 2019
No, that is SF Mono. SF Console is a clone intended to look like it but not one I'm authorized to share; which is why I mention Roboto Slab, which is open source and publicly available.
miniksa commentedon May 14, 2019
Where can I get it and confirm the licensing?
mqudsi commentedon May 14, 2019
It's made by Google, released under the Apache 2.0 license. GitHub repo: https://github.com/googlefonts/robotoslab
You can download the prebuilt TrueType files here: https://github.com/google/fonts/tree/master/apache/robotoslab
miniksa commentedon May 14, 2019
OK thanks. I'll take a look at it then when I get around to being able to work on rendering stuff instead of triaging GitHub issues and PRs all day. :P
26 remaining items
shanselman commentedon Mar 3, 2020
Austin Wagner (@austinwagner) The bug (behaviorally) is the small/wrong size. You're saying that Cascadia has a small glyph inside and that is wrong?
austinwagner commentedon Mar 3, 2020
Scott Hanselman (@shanselman) Apologies for being unclear. I was referring to the color difference only. The size is almost certainly wrong.
gitfool commentedon Mar 3, 2020
DHowett-MSFT commentedon Mar 3, 2020
Good, good, y'all can head over to #900
DHowett-MSFT commentedon Mar 3, 2020
This is in fact a bug submitted by Scott Hanselman (@shanselman) himself so 🤷♂
calloncampbell commentedon Mar 5, 2020
I followed the instructions by Scott Hanselman (@shanselman) post https://www.hanselman.com/blog/HowToMakeAPrettyPromptInWindowsTerminalWithPowerlineNerdFontsCascadiaCodeWSLAndOhmyposh.aspx and I still see wonky icons.
Windows Terminal version 0.9.433.0
shanselman commentedon Mar 6, 2020
Callon Campbell (@calloncampbell) I'll help you via twitter, not in a GH issue
calloncampbell commentedon Mar 6, 2020
OK my issue is not related. I had downloaded the wrong font. Thanks Scott Hanselman (@shanselman) for the help.
sergio-u commentedon Mar 27, 2020
miniksa commentedon Apr 22, 2020
Caskaydia Cove. And we've added some PL stuff to Cascadia itself. And the fact the emoji is small is just Certain "emoji" are still half-sized #900.XzAeRo commentedon Apr 23, 2020
Michael Niksa (@miniksa) FYI the wonky icons comment was due to an uninstalled font
miniksa commentedon Apr 24, 2020
With the completion of this checklist: #610 (comment), I am deeming this bug closed and resolved by other issues on the tracker. Thanks. Please file new issues against the latest version if there are still problems not addressed or covered by the open #900 or #455.
tm9k1 commentedon Jun 11, 2020
Michael Niksa (@miniksa) were you able to get around the fontWeight config var?