Font rendering issues in Terminal #610

mqudsi · 2019-05-09T05:32:55Z

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):

zadjii-msft · 2019-05-09T13:47:10Z

@miniksa is the guy who will know why this is happening.

miniksa · 2019-05-14T18:03:07Z

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 · 2019-05-14T18:22:44Z

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 · 2019-05-14T19:36:58Z

Where can I get it and confirm the licensing?

mqudsi · 2019-05-14T21:32:45Z

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 · 2019-05-14T21:38:46Z

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

iKlsR · 2019-06-10T02:32:37Z

I'm having a similar issue, I can only seem to use the base regular font, any medium or other variation and the app won't start and changes to a very tiny clipped variation if already running similar to the 4th screenshot. Font is Fira Code. Fira Code Medium works fine everywhere else.

mdtauk · 2019-06-10T03:13:04Z

If the new terminal is going to support Bold and Italic fonts, shouldn't the font picker be showing Font Families, rather than individual fonts?

DHowett-MSFT · 2019-06-10T03:35:50Z

I mean, there isn’t a font picker right now, so it isn’t showing anything?

mdtauk · 2019-06-10T03:38:11Z

I mean, there isn’t a font picker right now, so it isn’t showing anything?

True, but the fact the font picked is not of a regular weight, it could be part of the problem. But I assume the plan is to have a font picker in an app setting dialog of some kind :)

mqudsi · 2019-06-10T03:55:43Z

I think a good question is whether individual fonts within a family are looked up by their common name or their postscript name.

zadjii-msft · 2019-06-10T21:21:18Z

Also maybe related: #1163

vsalvino · 2019-06-13T18:34:37Z

This issue occurs with any font using the non-regular weight. For Example, IBM Plex Mono provides a ton of weights, none of them work in the terminal except regular specified with "fontFace": "IBM Plex Mono". Specifying "fontFace": "IBM Plex Mono Medium" produces the same rendering issue above.

bmo-at · 2019-07-15T09:45:36Z

This issue occurs with any font using the non-regular weight. For Example, IBM Plex Mono provides a ton of weights, none of them work in the terminal except regular specified with "fontFace": "IBM Plex Mono". Specifying "fontFace": "IBM Plex Mono Medium" produces the same rendering issue above.

Same for Nerd Fonts. As long as regular is installed, regular will be used. If you uninstall everything but, say for example bold, bold is used instead. This should instead be configurable in the settings file, with another attribute (e.g. fontWeight) for the profile:

        {
            "acrylicOpacity" : 0.5,
            "closeOnExit" : true,
            "colorScheme" : "One Dark Pro",
            "commandline" : "wsl.exe -d Debian",
...
            "fontFace" : "Hack NF",
            "fontSize" : 11,
            "fontWeight": "bold",
...
            "useAcrylic" : true
        }

miniksa · 2019-07-15T20:00:41Z

This issue occurs with any font using the non-regular weight. For Example, IBM Plex Mono provides a ton of weights, none of them work in the terminal except regular specified with "fontFace": "IBM Plex Mono". Specifying "fontFace": "IBM Plex Mono Medium" produces the same rendering issue above.

Thanks for the datapoint. I don't think I tried non-"regular" font weights yet while originally writing the renderer. This is probably just something I overlooked and need to finish writing.

Same for Nerd Fonts. As long as regular is installed, regular will be used. If you uninstall everything but, say for example bold, bold is used instead. This should instead be configurable in the settings file, with another attribute (e.g. fontWeight) for the profile:

I agree, it should be configurable. I just haven't got around to it yet.

bmo-at · 2019-07-15T20:57:36Z

Just had to give a shoutout to you guys for how ballin this Terminal is already. Performance is like greased lightning, visuals are terrific and stability is very good for such an early preview.
The switching for different kinds of shells (PS, cmd and wsl) is terrifc also.

Keep it going! 💪🏻

shanselman · 2020-03-03T07:56:25Z

Not sure where to file this. Could be in Cascadia Code itself @cinnamon-msft or could be Terminal Version: 0.9.433.0.

Repro is easy. "echo ⚡" with Cascadia Code PL vs using the patched DelugiaCode NF.

Note it on the command line vs when used in a prompt. This is DelugiaCodeNF 1909.16 (just a patched Cascadia). It's not in color on the prompt, then it's color in the prompt. But the size is right.

And this is Cascadia Code PL 1911.21. It's color everywhere but tiny.

austinwagner · 2020-03-03T11:38:38Z

@shanselman Is the color part a bug? It looks to me like a lightning bolt glyph was added into the patched font and that the unpatched font is falling back on the default Windows emoji glyph.

shanselman · 2020-03-03T18:05:48Z

@austinwagner The bug (behaviorally) is the small/wrong size. You're saying that Cascadia has a small glyph inside and that is wrong?

austinwagner · 2020-03-03T18:32:23Z

@shanselman Apologies for being unclear. I was referring to the color difference only. The size is almost certainly wrong.

DHowett-MSFT · 2020-03-03T18:50:00Z

Good, good, y'all can head over to #900

DHowett-MSFT · 2020-03-03T18:50:28Z

This is in fact a bug submitted by @shanselman himself so 🤷‍♂

calloncampbell · 2020-03-05T16:19:54Z

I followed the instructions by @shanselman post https://www.hanselman.com/blog/HowToMakeAPrettyPromptInWindowsTerminalWithPowerlineNerdFontsCascadiaCodeWSLAndOhmyposh.aspx and I still see wonky icons.

Windows Terminal version 0.9.433.0

shanselman · 2020-03-06T00:03:29Z

@calloncampbell I'll help you via twitter, not in a GH issue

calloncampbell · 2020-03-06T02:19:25Z

OK my issue is not related. I had downloaded the wrong font. Thanks @shanselman for the help.

miniksa · 2020-04-22T22:13:54Z

- I believe a combination of Avoid splitting surrogate pairs when breaking runs for scaling #4731 and Improve glyph scaling correction #4747 should have resolved the issue with certain fonts not displaying correctly at all and the weird scaling seen between different characters.
- The weird emoji sizes are definitely Certain "emoji" are still half-sized #900, so not considering them here.
- (Font rendering issues in Terminal #610 (comment))
- The different colors of ⚡ I need to check into. (Font rendering issues in Terminal #610 (comment)) - This isn't reproing for me anymore... it's been a while. And Delugia is gone in favor of the official Nerd Font 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.
- The gapping seen between lines was Set DxRenderer non-text alias mode #5149 (Font rendering issues in Terminal #610 (comment))
- The pixel bleed on scrolling should be fixed with Render row-by-row instead of invalidating entire screen #5185 and Adjusts High DPI scaling to enable differential rendering #5345 (Font rendering issues in Terminal #610 (comment))
- Wonky icons I need to identify (Font rendering issues in Terminal #610 (comment)) - EDIT 4/24 per Font rendering issues in Terminal #610 (comment) I'm not going to dig further.

XzAeRo · 2020-04-23T15:52:40Z

@miniksa FYI the wonky icons comment was due to an uninstalled font

miniksa · 2020-04-24T22:30:50Z

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 · 2020-06-11T09:31:01Z

@miniksa were you able to get around the fontWeight config var?

zadjii-msft assigned miniksa May 9, 2019

zadjii-msft added this to the Windows Terminal v1.0 milestone May 9, 2019

zadjii-msft added Area-Fonts Related to the font Area-Rendering Text rendering, emoji, complex glyph & font-fallback issues Issue-Bug It either shouldn't be doing this or needs an investigation. labels May 9, 2019

zadjii-msft mentioned this issue May 13, 2019

unbroken runs containing ligatures occasionally cause font size flickering #696

Closed

miniksa added the Mass-Chaos label May 17, 2019

ghost added the Needs-Tag-Fix Doesn't match tag requirements label May 17, 2019

miniksa added Product-Terminal The new Windows Terminal. and removed Mass-Chaos labels May 17, 2019

ghost removed the Needs-Tag-Fix Doesn't match tag requirements label May 17, 2019

zadjii-msft mentioned this issue May 28, 2019

Display a dialog when the user selects an invalid font #1017

Closed

This comment has been minimized.

Sign in to view

zadjii-msft mentioned this issue Aug 8, 2019

Bug Report - Windows Terminal doesn't start with some characters #1961

Closed

zadjii-msft added the Priority-3 A description (P3) label Jan 22, 2020

This was referenced Jan 27, 2020

Font Size Mixed Rendering in WSL2 #4369

Closed

Font rendering issue; characters appear at wrong size, position #4367

Closed

cinnamon-msft added v1-Scrubbed Priority-2 A description (P2) and removed Priority-3 A description (P3) labels Jan 28, 2020

This comment has been minimized.

Sign in to view

This was referenced Mar 19, 2020

Issues with font #5012

Closed

Some color emojis are scaled too small #4672

Closed

This comment has been minimized.

Sign in to view

miniksa closed this as completed Apr 24, 2020

ghost added the Needs-Tag-Fix Doesn't match tag requirements label Apr 24, 2020

github-actions bot mentioned this issue Jan 8, 2024

Incorrect font characters rendered after running simple terminal stress program for a long time #16543

Closed

Font rendering issues in Terminal #610

Font rendering issues in Terminal #610

Comments

mqudsi commented May 9, 2019

zadjii-msft commented May 9, 2019

miniksa commented May 14, 2019

mqudsi commented May 14, 2019 • edited Loading

miniksa commented May 14, 2019

mqudsi commented May 14, 2019

miniksa commented May 14, 2019

iKlsR commented Jun 10, 2019

mdtauk commented Jun 10, 2019

DHowett-MSFT commented Jun 10, 2019

mdtauk commented Jun 10, 2019

mqudsi commented Jun 10, 2019

zadjii-msft commented Jun 10, 2019

vsalvino commented Jun 13, 2019

bmo-at commented Jul 15, 2019

miniksa commented Jul 15, 2019

bmo-at commented Jul 15, 2019

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

shanselman commented Mar 3, 2020 • edited Loading

austinwagner commented Mar 3, 2020

shanselman commented Mar 3, 2020

austinwagner commented Mar 3, 2020

This comment has been minimized.

DHowett-MSFT commented Mar 3, 2020

DHowett-MSFT commented Mar 3, 2020

calloncampbell commented Mar 5, 2020

shanselman commented Mar 6, 2020

calloncampbell commented Mar 6, 2020

This comment has been minimized.

miniksa commented Apr 22, 2020 • edited Loading

XzAeRo commented Apr 23, 2020

miniksa commented Apr 24, 2020

tm9k1 commented Jun 11, 2020

mqudsi commented May 14, 2019 •

edited

Loading

shanselman commented Mar 3, 2020 •

edited

Loading

miniksa commented Apr 22, 2020 •

edited

Loading