JetBrainsMono Nerd Font not equals (!=) ligature is broken in Windows Terminal on Windows 11

[vdrandom]

🗹 Requirements

• I have searched the issues for my issue and found nothing related and/or helpful
• I have searched the FAQ for help
• I have searched the Wiki for help

🎯 JetBrainsMono Nerd Font not equals (!=) ligature is broken in Windows Terminal on Windows 11

Experienced behavior:
Some sort of deformed not equals ligature

Expected behavior:
Not equals ligature

Example symbols:
!=

🔧 Your Setup

• Which font are you using (e.g. Anonymice Powerline Nerd Font Complete.ttf)?
  • JetBrainsMono Nerd Font
• Where did you get the file from (download link, self patched, source downloaded from link...)
  • Downloaded from your website, used chocolatey to install it
• Which terminal emulator are you using (e.g. iterm2, urxvt, gnome, konsole)?
  • Windows Terminal
• Are you using OS X, Linux or Windows? And which specific version or distribution?
  • Windows 11

★ Screenshots (Optional)

How it looks like in Windows Terminal:

How it is supposed to look like (WezTerm):

[vdrandom]

Hopefully I've done everything correctly when reporting this.

Also I should note that JetBrains Mono does not have this issue, the ligature in the original font works properly.

[Finii]

That is a bug in the original JetBrainsMono font itself.

See

• 'Not equal (!=)' ligature is broken for all JetBrains Mono Light/ExtraLight weights. #963
• Fix JetBransMono != ligature #964

[Finii]

Thanks for reporting.

Also I should note that JetBrains Mono does not have this issue

Well, I just checked, official is still JetBrainsMono v2.242, and that DOES have the problem (see linked Issue at JetBrains in #963).

Anyhow, we fixed it here (see link below). If you download from the repo directly it should work fine, I guess we did not release yet after the fix.

https:/ryanoasis/nerd-fonts/tree/master/patched-fonts/JetBrainsMono

[github-actions]

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.