cv60 not working

[chtenb]

Tested on wezterm:

Regardless of whether ss02 is on or off, I don't get the back arrow for <=

[kenmcd]

Try ss02. That turns <= into a ligature called less_equal (which looks similar to ≤) and then cv60 turns that ligature into the arrow (less_equal.alt). So enable both ss02 and cv60.

[chtenb]

That didn't work for me, like I said 😄

[kenmcd]

That didn't work for me, like I said 😄

For some reason I had ss06 in my head. Must have been doing too many things at once. So... What application are you using? Does it support Character Variants? Some applications do not support them even though they do support Stylistic Sets.

[chtenb]

I didn't know that was a distinct feature. I'm using WezTerm (terminal): https://wezfurlong.org/wezterm/config/font-shaping.html#advanced-font-shaping-options

[idan]

Investigating!

[kenmcd]

I didn't know that was a distinct feature. I'm using WezTerm (terminal): https://wezfurlong.org/wezterm/config/font-shaping.html#advanced-font-shaping-options

I did test this yesterday in The FontCreator OpenType Designer. And it appeared to work fine.

WezTerm does mention using Harfbuzz in their docs, but nothing specific about supporting Character Variants. Harfbuzz supports cvNN, but the app also has to support it. Nothing in the WezTerm issue tracker here in GitHub mentions character variants that I could find. You may want to ask there if it is supported.

Also tested in LibreOffice - which also uses Harfbuzz. And it works as expected.

So it appears to be an issue in WezTerm.

[kenmcd]

@chtenb Does it work if you only enable ss02 and cv60? There is mention in another issue that there may be some unwanted interactions between the stylistic sets. I checked to see if other stylistic sets appeared to disable cv60, but that was in isolation, not within a run of text which may be affected by other features. So try it with only ss02 and cv60 to see if WezTerm works. That should answer the question if it supports cvNN.

[chtenb]

It seems not. I will raise an issue for wezterm.

[chtenb]

Maybe it's not a wezterm problem after all. I installed VSCode to test this font with a different application, and this is what I see:

[heathercran]

@chtenb I can't seem to replicate this issue in VS Code, even with your exact settings. Could you try pasting "" to ensure you have the latest version of the fonts installed? It should appear as "v1.100" in the latest Monaspace fonts.

[chtenb]

That's a handy feature! And it revealed to me that the older version of monaspace was also still installed the newer version, and that the older version was chosen by the applications. I deleted all fonts starting with "mona" from my system and reinstalled again. Now it works!