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.64k stars 804 forks source link

2105.24 - Italic Style Groups and Font File Names Incorrect #465

Closed kenmcd closed 3 years ago

kenmcd commented 3 years ago

The style groups are incorrect in the new Italic fonts. This causes the all the Italic fonts to be in their own style group rather than linked with the related Regular. Also causes the font file names to be confused.

And the Italic typographic family is also different.

DHowett commented 3 years ago

Sorry, what platform is this on? Windows seems to tolerate it... and link the fonts just fine!

kenmcd commented 3 years ago

Windows 10. I am seeing the Italic style groups like this: Cascadia Code Italic - which should be Cascadia Code Cascadia Mono Italic - which should be Cascadia Mono

Same with the typographic family Cascadia Code Italic Cascadia Mono Italic

CascadiaMonoItalic-Italic

And the odd file names: CascadiaMonoItalic-Italic.ttf etc. The file name should be: CascadiaMono-Italic.ttf

madig commented 3 years ago

There is something going on indeed. The Italic fonts have "Italic" in the family name when they shouldn't. See e.g. CascadiaCodeItalic-ExtraLightItalic.otf, name table ID 16: "Cascadia Code Italic" -- ID 16, when present, should just be "Cascadia Code" in all statics. This means that fontconfig on Linux does not pick the Italic font up as the italic of the regular. And the file name should be just "CascadiaCode-ExtraLightItalic.otf" :wink:

kenmcd commented 3 years ago

This means that fontconfig on Linux does not pick the Italic font up as the italic of the regular.

These will not work properly in LibreOffice on Linux or Windows. Or MS Word.

aaronbell commented 3 years ago

Interesting. It appears that the static instances are not propagating properly. While I investigate that, I suggest using the variable font version which works as expected.