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.11k stars 796 forks source link

Can't get cursive italics to work #622

Closed BlueDev5 closed 2 years ago

BlueDev5 commented 2 years ago

Cascadia family version

2111.01

Cascadia family variant(s)

Cascadia Code (the version with ligatures)

Font file format(s)

.ttf (variable)

Platform

Linux Mint 20.2 (Ubuntu Based linux distro)

Other Software

Visual Studio Code: Version - 1.63.2

What happened?

Cascadia Code is always picking up the normal italics instead of the cursive ones.

What I've tried:

  1. I've tried installing otf and ttf versions from the releases.
  2. I've built cascadia from the source of the 2111.01 release.
  3. I've tried the pyftfeatfreeze method as mentioned in the docs.
  4. I've even read the build.py file to confirm that it was in fact adding the correct feature files.

Here's my vscode config for the font setup:

"editor.fontFamily": "'Cascadia Code', Consolas, 'Fira Code', 'Input Mono',  'Courier New', monospace",
"editor.fontLigatures": "'calt' on, 'ss01' on",
"editor.fontSize": 14,
"editor.lineHeight": 1.4,
"terminal.integrated.fontFamily": "Cascadia Code PL",
"editor.semanticTokenColorCustomizations": {
    "enabled": true,
    "rules": {
        "comment": {
            "fontStyle": "italic"
        },
        "*.declaration": {
            "fontStyle": "italic"
        },
    }
}

Here's how it looks like: Cursive Not Working

As You can see in the picture the declarations and the comment both are italic and not cursive.

BlueDev5 commented 2 years ago

Got It I had to restart vscode for it to update