[bug] Cannot use different styles of Input Mono font #12572

Closed
opened 2026-01-31 03:19:04 +00:00 by claunia · 12 comments
Owner

Originally created by @WojciechThomas on GitHub (Feb 14, 2021).

Environment

Windows build number: Microsoft Windows NT 10.0.19042.0
Windows Terminal version: 1.5.10411.0

Steps to reproduce

Use any editor to configure fontFace setting.

Expected behavior

Accept different versions of Input Mono font, e.g.:

        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
            "fontFace": "Input Mono Narrow"  // or Condensed or Compressed
        },

Actual behavior

With font faces different than "Input Mono" Terminal falls back to Consolas font.
image

With "Input Mono" font everything works correctly:
image

Originally created by @WojciechThomas on GitHub (Feb 14, 2021). # Environment ```none Windows build number: Microsoft Windows NT 10.0.19042.0 Windows Terminal version: 1.5.10411.0 ``` # Steps to reproduce Use any editor to configure **fontFace** setting. # Expected behavior Accept different versions of Input Mono font, e.g.: ```none "defaults": { // Put settings here that you want to apply to all profiles. "fontFace": "Input Mono Narrow" // or Condensed or Compressed }, ``` # Actual behavior With font faces different than "Input Mono" Terminal falls back to Consolas font. ![image](https://user-images.githubusercontent.com/15376250/107875447-2ba5e280-6ec0-11eb-9665-9ad6c2782f38.png) With "Input Mono" font everything works correctly: ![image](https://user-images.githubusercontent.com/15376250/107875496-96efb480-6ec0-11eb-9165-dfba72ce6a8e.png)
Author
Owner

@skyline75489 commented on GitHub (Feb 19, 2021):

I've tried installed all 3 variants of Input Mono:

image

The DWrite API actually reports that Input Mono Condensed does not exist in the system. However Input Mono does exist. @zadjii-msft @DHowett any idea why this is happening?

@skyline75489 commented on GitHub (Feb 19, 2021): I've tried installed all 3 variants of Input Mono: ![image](https://user-images.githubusercontent.com/4710575/108460032-bae13a80-72b2-11eb-88d4-bc35510e6766.png) The DWrite API actually reports that `Input Mono Condensed` does not exist in the system. However `Input Mono` does exist. @zadjii-msft @DHowett any idea why this is happening?
Author
Owner

@epyonavenger commented on GitHub (Mar 2, 2021):

It's not just "Input Mono", the same behavior can be seen with Hack. I normally use "Hack Regular", but since the update that falls through to Consolas.

@epyonavenger commented on GitHub (Mar 2, 2021): It's not just "Input Mono", the same behavior can be seen with Hack. I normally use "Hack Regular", but since the update that falls through to Consolas.
Author
Owner

@DHowett commented on GitHub (Mar 2, 2021):

It's more probable that since the update it tells you that it fell back to Consolas. That error dialog is hooked up to the renderer actually failing to find the font, even after it's tried a couple different ways. It was perhaps never working properly, and the dialog only now alerts you to that fact. 😄

@DHowett commented on GitHub (Mar 2, 2021): It's more probable that since the update it _tells you_ that it fell back to Consolas. That error dialog is hooked up to the renderer actually failing to find the font, even after it's tried a couple different ways. It was perhaps never working properly, and the dialog only now alerts you to that fact. :smile:
Author
Owner

@epyonavenger commented on GitHub (Mar 2, 2021):

Well, it was definitely using Hack Regular at some point, though to your point, it's possible it was never quite right, and only now is it notifying me. Still, I'd trade not being notified for using the right font again. 🤔

@epyonavenger commented on GitHub (Mar 2, 2021): Well, it was definitely using Hack Regular at some point, though to your point, it's possible it was never quite right, and only now is it notifying me. Still, I'd trade not being notified for using the right font again. 🤔
Author
Owner

@zadjii-msft commented on GitHub (Mar 4, 2021):

This looks like a real bug, but I've got no idea why this isn't working. I'll stick it in 2.0 - we'll figure it out eventually 😄

@zadjii-msft commented on GitHub (Mar 4, 2021): This looks like a real bug, but I've got no idea why this isn't working. I'll stick it in 2.0 - we'll figure it out eventually 😄
Author
Owner

@derekslenk commented on GitHub (Oct 15, 2022):

Hmm - this has been making Windows Terminal unusable. So much for WSL.

Not understanding why this issue was closed with no linked ticket or workaround

@derekslenk commented on GitHub (Oct 15, 2022): Hmm - this has been making Windows Terminal unusable. So much for WSL. Not understanding why this issue was closed with no linked ticket or workaround
Author
Owner

@Diablo-D3 commented on GitHub (Nov 7, 2022):

The workaround, currently, is only install the variant of Input you want. This works in Windows Terminal but sometimes not other apps.

A working example of another terminal would be Alacritty, where if I want, say, narrow, I can set the four styles as "Narrow", "Narrow Bold", "Narrow Italic", "Narrow Bold Italic". There is no equivalent in Windows Terminal yet to set a raw style string, and can only use the weight enums.

@Diablo-D3 commented on GitHub (Nov 7, 2022): The workaround, currently, is *only* install the variant of Input you want. This works in Windows Terminal but sometimes not other apps. A working example of another terminal would be Alacritty, where if I want, say, narrow, I can set the four styles as "Narrow", "Narrow Bold", "Narrow Italic", "Narrow Bold Italic". There is no equivalent in Windows Terminal yet to set a raw style string, and can only use the weight enums.
Author
Owner

@derekslenk commented on GitHub (Nov 7, 2022):

If you use oh-my-posh, it seems to download and install the fonts correctly
image

@derekslenk commented on GitHub (Nov 7, 2022): If you use oh-my-posh, it seems to download and install the fonts correctly ![image](https://user-images.githubusercontent.com/42957/200391134-eed63e34-3af9-4336-9aca-1befe37024db.png)
Author
Owner

@falleng0d commented on GitHub (Nov 10, 2022):

Screenshot1853
Font is recognized in other apps and it has a lot of weights such as "compressed" that are not recognized by windows terminal

@falleng0d commented on GitHub (Nov 10, 2022): ![Screenshot1853](https://user-images.githubusercontent.com/3948733/201119405-55ce4903-20a5-47e9-a4bc-3af3ed379b0a.png) Font is recognized in other apps and it has a lot of weights such as "compressed" that are not recognized by windows terminal
Author
Owner

@DHowett commented on GitHub (Nov 10, 2022):

Huh, thanks! I believe that "Compressed" (like "Condensed") is a name for the width axis, not the weight axis.

You can use custom font axes like width (wdth) by adding an "axes" field to your "font" like this:

"font": {
    "axes": {
        "wdth": 100 // Width axis; 100 is regular width; values range from 0 to (unknown)
    }
    ...
}
@DHowett commented on GitHub (Nov 10, 2022): Huh, thanks! I believe that "Compressed" (like "Condensed") is a name for the _width_ axis, not the _weight_ axis. You can use custom font axes like [width (`wdth`)](https://learn.microsoft.com/en-us/typography/opentype/spec/dvaraxistag_wdth) by adding an `"axes"` field to your `"font"` like this: ```jsonc "font": { "axes": { "wdth": 100 // Width axis; 100 is regular width; values range from 0 to (unknown) } ... } ```
Author
Owner

@DHowett commented on GitHub (Nov 10, 2022):

For font names that contain axis tags in general, we're tracking that in /dup #9744 (because it has more technical information on the problem, even though it is a newer issue than this one). Some preliminary work was done in #10777, but it proved difficult to work into our font selection engine at the time. We're in a better place now 😄

That having been said, please subscribe to #9744 for updates. In the meantime, you can use the axes override to specify specific widths.

@DHowett commented on GitHub (Nov 10, 2022): For font names that contain axis tags in general, we're tracking that in /dup #9744 (because it has more technical information on the problem, even though it is a newer issue than this one). Some preliminary work was done in #10777, but it proved difficult to work into our font selection engine at the time. We're in a better place now :smile: That having been said, please subscribe to #9744 for updates. In the meantime, you can use the `axes` override to specify specific widths.
Author
Owner

@ghost commented on GitHub (Nov 10, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 10, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12572