Nerd-Fonts Glyphs and Ligatures Not Working

Lord_Devi

Lord_Devi

I can't seem to get font glyphs or ligatures displaying correctly in X on my new FreeBSD install.

I've installed nerd-fonts 2.1.0, and have tried "JetBrainsMono Nerd Font", as well as "Fira Code Nerd Font" but neither seem to work.

Am I missing a step? On Archlinux, it is pretty much install and go.
 
Hello,

are the aforementioned fonts present in your fc-list?
If not, you may need to update the fc-cache
 
Thank you matt_k.

Yes I see them all under fc-list. I was able to add them to alacritty, and to chrome, and firefox as well it seems.

It just seems like the glyph and ligature components of the fonts aren't working. Only the standard non-nerd part of the font kinda thing. =/
 
Thank you for offering your advice though matt_k, it is really appreciated. =)

I did follow the handbook though, and everything _should_ be working as far as I can tell. It just.. isn't. It is like the "JetBrains Mono" font is loaded, not the "JetBrains Mono Nerd" font.
 
Lord_Devi said:
I can't seem to get font glyphs or ligatures displaying correctly in X
Click to expand...
Lord_Devi said:
It just seems like the glyph and ligature components of the fonts aren't working.
Click to expand...
If you are on 12.2 set the locale environment of the login shell to UTF-8.

System wide, login classes method (append to the default class charset and lang, pay attention to end the umask line with a \ ):

/etc/login.conf
Code: 
default:\
    ....
    :umask=022:\
    :charset=UTF-8:\
    :lang=C.UTF-8:
Afterwards run cap_mkdb /etc/login.conf, log out, log in to take effect. login.conf(5) cap_mkdb(1)

For other methods see in handbook chapter
docs.freebsd.org

Chapter 25. Localization - i18n/L10n Usage and Setup

FreeBSD supports localization into many languages, allowing users to view, input, or process data in non-English languages
docs.freebsd.org docs.freebsd.org
 
I guess you have already tried another desktop environments or window managers as well?
Click to expand...

I did try tackling this from the software side actually. And that was it. I found the problem.

Thanks very much Alexander for checkin on the problem with me. I appreciate it.

The problem WAS the software, not the fonts or the font engine.

I was testing for ligatures using alacritty and emacs. Emacs had been configured to use Ligatures on my Linux machine already. And alacritty had to be compiled from git, using the branch with ligature support.

After I custom compiled alacritty with that ligature support, I was able to verify that the font was working as intended. It is the tools I was trying to ues the ligatures inside of that were the issue. They just didn't have that harfbuzz support or whatever it is called.

Really wish Kitty was ported over to FreeBSD! lol.
 
I'm getting ready write a Tutorial on How to make an ASCII image using games/cowsay and graphics/gimp with your own fonts added by root transfer using x11-fm from the usr account into usr/local/share/gimp/font and invoking #rehash.

The new fonts will be available for use by Gimp the next time opened without any other steps involved.
 
You must log in or register to reply here.
Back
Top