Space Mono pre-patched font displays weird glyph for characters 'fl'

[HuM4NoiD]

🎯 Subject of the issue

The Characters f and l combine into a weird glyph, this only happens for lower case. I needed a monotype font, so I installed mono variant. Installing any other variant leads to non detection of the font when mono variants are strictly required I have attached screenshots of Android Studio, VSCodium and Notepad. I have installed mono variants of other fonts, none of them face such problems

🔧 Your Setup

Installed pre-patched font Space Mono from downloads SpaceMono Nerd Font Mono variant. Link VSCodium, Android Studio, Notepad Windows 10

★ Optional

[hakamadare]

this seems similar to #469.

[demfabris]

Been having this issue with most nerd fonts... What's the proper workaround?

[polyzen]

https://github.com/ryanoasis/nerd-fonts/issues/254#issuecomment-626362197

[HuM4NoiD]

Thank You I'll update once I have tried the fix

[Interesting-name]

Any news on how it worked out @HuM4NoiD? I've been having the same issue, but was hesitant to mess around with fonts since I have no experience there.

Edit: Also, this issue should be left open as it isn't yet fixed.

[HuM4NoiD]

Any news on how it worked out @HuM4NoiD? I've been having the same issue, but was hesitant to mess around with fonts since I have no experience there.

Edit: Also, this issue should be left open as it isn't yet fixed.

I downloaded the original Space Mono from Google Fonts, Copied the specified glyphs in FontForge (U+FB01, U+FB02) and deleted the next few glyphs, saved the edit as sfd. I will generate otf/ttf and then notify.

[ryanoasis]

Short term solution would seem to be not overwrite codepoints used for ligatures. Long term would be moving codepoints 🤔

[HuM4NoiD]

The generated fonts after removing symbols obviously work @Interesting-name @ryanoasis Should I keep this issue open till it is fixed or close it?

[Epholys]

I have a similar issue with the nerdfont-provided Ubuntu font: every fi ligature is displayed as nf-mdi-phone_classic. It drove me crazy because of course this ligature isn't used consistently :)

[AliMejbar]

Any update on this ? The ligature is still showing incorrectly.

[Finii]

This should have been fixed by #711.

I'm not sure which files are patched with that PR in place, maybe the v2.2.0RC has them already, else please use the font files directly from the repo: https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts

[KaranAhlawat]

Can confirm that the issue is fixed in the v2.2.0RC. Although getting it directly from https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts did not work. So hopefully tools life getnf will be able to get the correct ones when v2.2.0 goes live :)

[nicolasshu]

Sorry, so what's the best way to fix this?

[KaranAhlawat]

Sorry, so what's the best way to fix this?

Go to the releases page, download the v2.2.0RC or above, extract the package, and then copy the font to the desired location. That should be it.

[sh1zicus]

under "fi" also gives the symbol

[Finii]

All fi renders as phone should be fixed now with v2.2.1. Please reopen if I err ;-)

[ayush-seth]

I am still facing this issue, I installed spacemono nerd font using homebrew. For example writing amplify configure

I also installed jetbrains mono nerd font using homebrew and that works fine

[Finii]

~~Can you give the version of the file? Where you downloaded it?~~ Oh, you already gave it :grimacing: Let's see, I'm working on homebrew currently anyhow...

Ah, you see the homebrew stuff has not been updated. This will be fixed together with #1003. Currently the casks are not maintained by Nerd Fonts but by whoever has interest in maintaining :grimacing: Obviously noone had interest in updating SpaceMono.

I'm currently writing the stuff needed that we (i.e. Nerd Fonts) automatically maintains the casks.

[ayush-seth]

@Finii oh, sorry I should have checked the version in homebrew myself. Thank you for responding. I installed v2.2.0 manually and can confirm that this is issue is resolved

[github-actions[bot]]

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.