[bug] Cannot use different styles of Input Mono font

[WojciechThomas]

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.

With "Input Mono" font everything works correctly:

[skyline75489]

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

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?

[epyonavenger]

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.

[DHowett]

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. 😄

[epyonavenger]

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. 🤔

[zadjii-msft]

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 😄

[derekslenk]

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

[Diablo-D3]

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.

[derekslenk]

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

[falleng0d]

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

[DHowett]

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]

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.

[ghost]

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!