search

microsoft / cascadia-code

This is a fun, new monospaced font that includes programming ligatures and is designed to enhance the modern look and feel of the Windows Terminal.
Other
25.76k stars 803 forks source link

Variable font is not recognized by JetBrains Rider #566

Closed FUJonathan closed 3 years ago

FUJonathan commented 3 years ago

Cascadia family version

2106.17

Cascadia family variant(s)

Cascadia Code (the version with ligatures)

Font file format(s)

.ttf (variable)

Platform

Windows 10 Pro 21H1 19043.1202

Other Software

JetBrains Rider 2021.2.1 Build RD-212.5080.71

What happened?

After installing the variable font in the TTF directory, Cascadia Code is not listed in Rider's editor font selection dropdown. I don't know if this is a problem with Cascadia Code or Rider itself, but other variable fonts such as Inconsolata seem to be recognized (admittedly, only some of its weights are available).

image

On the other hand, if I install the italic version of the variable font (CascadiaCodeItalic.ttf), Rider does recognize it, but only the italic version is available. The regular version of the font (CascadiaCode.ttf) just seems to be completely ignored.

image

FUJonathan commented 3 years ago

I just discovered these issues reported for IntelliJ IDEA, also from JetBrains, so I suspect both IDE's enumerate fonts in much the same way:

I haven't yet checked if the workaround for IntelliJ IDEA in the link above will also work for Rider. For now I may just stick with the static fonts instead.

aaronbell commented 3 years ago

Yes, I suspect that this is the same issue as previously described. This should be partially fixed by PR #538.

Unfortunately, at this time JetBrains doesn't really properly support variable fonts. So you'll have to use the static instances.