[solved] Problem with understanding Font Configuration

RollingRaven · 2023-11-07 22:07:36

Greetings Archlinux Community,

I've dug down quite a rabbit hole yesterday, when I tried to have a working font configuration (full emoji support, was my main goal) on my fresh Arch Install.

First of I was using this guide https://dev.to/darksmile92/get-emojis-w … -emoji-2a9. Which basically suggest installing noto-fonts-emoji and create a custom config under /etc/fonts/local.conf

Ok, now most emojis where working in Discord, which was my main goal.

Next of to my Terminal, I like to use CaskaydiaCove Nerd Font as my main Font in my Terminal so I installed it via

pacman -S ttf-cascadia-code-nerd

Then I noticed quite strange behavior using wezterm or konsole ,where the main font was set to CaskaydiaCove and one Glyph (U+F83D) was not displayed correctly, its normally a lock emoji, which shows when you go the root directory with starship prompt.

Then I checked, if I have Fonts installed, which support that unicode character with

fc-match -s monospace:charset=f83d

which showed me plenty of supported fonts including CaskaydiaCove Nerd Font, which is my Font in konsole and wezterm

In wezterm you can check, if you have a supported font for a codepoint by

wezterm ls-fonts --codepoints f83d

which I checked and had no match with CaskaydiaCove Nerd Font.

Then for testing purposes I switched to MesloLGS NF which i downloaded manually from GitHub (https://github.com/romkatv/powerlevel10 … er/font.md) and installed over KDE Plasma Font Manager and voilà the Lock (U+F83D) was displayed correctly in wezterm
and konsole

Which lead me to the following questions:

Are the NerdFonts in the Archlinux community repo not properly patched, because on my other machine I downloaded & installed CaskaydiaCove Nerd Font over https://www.nerdfonts.com/ and had no problem whatsoever.
Do i really need a custom conf in /etc/fonts/local.conf for emoji support? Because I deleted it for testing purposes and everything still works fine, even the wiki says you don't need it.
There are still some unsupported Glyphs in my Discord for example (https://imgur.com/a/y6ThbFc) sadly I cant copy the channel name, or just don't know how >.<
Could there be a problem with installing fonts system-wide with pacman instead of user-wide?

System Configuration:

OS: Arch Linux x86_64Kernel: 6.5.9-arch2-1
Packages: 815 (pacman)
Shell: fish 3.6.1
Resolution: 3440x1440
DE: Plasma 5.27.9
WM: kwin
Theme: [Plasma], Breeze [GTK2/3]
Icons: [Plasma], breeze-dark [GTK2/3]
Terminal: WezTerm
GPU: NVIDIA GeForce GTX 1060 6GB

Last edited by RollingRaven (2023-11-16 16:51:42)

seth · 2023-11-08 08:37:42

fc-list :charset=f83d
FC_DEBUG=4 pango-view --font="monospace" -t "" | grep family: # bbs probably kills that, it's the lock

https://bbs.archlinux.org/viewtopic.php … 0#p2114940

RollingRaven · 2023-11-08 17:56:59

seth wrote:

fc-list :charset=f83d
FC_DEBUG=4 pango-view --font="monospace" -t "" | grep family: # bbs probably kills that, it's the lock

https://bbs.archlinux.org/viewtopic.php … 0#p2114940

for fc-list :charset=f83d :

/home/user/.fonts/m/MesloLGS_NF_Italic.ttf: MesloLGS NF:style=Italic
/home/user/.fonts/m/MesloLGS_NF_Bold.ttf: MesloLGS NF:style=Bold
/home/user/.fonts/m/MesloLGS_NF_Bold_Italic.ttf: MesloLGS NF:style=Bold Italic
/home/user/.fonts/m/MesloLGS_NF_Regular.ttf: MesloLGS NF:style=Regular

for FC_DEBUG=4 pango-view --font="monospace" -t "" | grep family:

pango-view: Invalid byte sequence in conversion input

So its seems like only MesloLGS NF is the only font supporting the lock, I just double checked on my Laptop and the Lock there looks quite different than the Meslo one(thats the system where i use CaskaydiaCove with no issues),I think its because I have more fonts installed on that system, which wezterm can fallback on, because it looks more emoji themend.

The situation seems more clear now, thanks for the answer!

Last edited by RollingRaven (2023-11-08 17:58:50)

seth · 2023-11-08 19:33:53

pango-view: Invalid byte sequence in conversion input

Your locale broken?

localectl
locale
locale -a

RollingRaven · 2023-11-10 17:45:30

seth wrote:

pango-view: Invalid byte sequence in conversion input

I don't think so, when I switch the character to a A for example everything works.

❯ localectl
System Locale: LANG=en_US.UTF-8
    VC Keymap: us
   X11 Layout: us
    X11 Model: pc105+inet
  X11 Options: terminate:ctrl_alt_bksp

❯ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_DE.UTF-8
LC_TIME=en_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT=en_DE.UTF-8
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

❯ locale -a
C
C.utf8
en_US.utf8
POSIX

Last edited by RollingRaven (2023-11-10 17:45:57)

seth · 2023-11-10 18:02:31

I very much think so
1. b/c "locale: Cannot set LC_ALL to default locale: No such file or directory"
2. b/c "en_DE.UTF-8" isn't a thing
3. b/c "A" is an ASCII character

Do you use KDE?
https://wiki.archlinux.org/title/KDE#Pl … e_settings

RollingRaven · 2023-11-11 00:27:53

seth wrote:

I very much think so
1. b/c "locale: Cannot set LC_ALL to default locale: No such file or directory"
2. b/c "en_DE.UTF-8" isn't a thing
3. b/c "A" is an ASCII character
Do you use KDE?
https://wiki.archlinux.org/title/KDE#Pl … e_settings

Yes, I use KDE.

I removed ~/.config/plasma-localerc then logout and login and

FC_DEBUG=4 pango-view --font="monospace" -t "" | grep family:

and the Lock shows, thanks!

Now i have a different "problem"/error, when i run FC_DEBUG=4 pango-view --font="monospace" -t "" | grep family: in wezterm

No fonts contain glyphs for these codepoints: \u{28}\u{29}\u{77}\u{30af}\u{30b4}\u{30b7}\u{30c3}.
Placeholder glyphs are being displayed instead.
You may wish to install additional fonts, or adjust
your configuration so that it can find

locale looks now like this:

❯ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Last edited by RollingRaven (2023-11-11 00:28:28)

seth · 2023-11-11 08:19:09

Please post the entire pango-view output, but those are

()wクゴシト

I see where katakana is a problem (you'll need some cjk font) but you'd likely have some basic ascii coverage?
You can also "fc-list :charset=30f8" to see your katakana coverage

RollingRaven · 2023-11-11 18:22:29

seth wrote:

Please post the entire pango-view output

Here https://pastebin.com/iQXe53YM

seth wrote:

you'll need some cjk font

I installed noto-fonts-cjk now over pacman.

seth wrote:

you'd likely have some basic ascii coverage

Sorry, I'm not sure, where I will find Fonts with basic ascii coverage

seth · 2023-11-11 19:30:12

pango properly resolves the glyph out of "MesloLGS NF"
You can expect pretty much every font to cover ASCII - where exactly and when does the message in #7 appear?
Also

FC_DEBUG=4 pango-view --font="monospace" -t "シ" | grep family:

RollingRaven · 2023-11-16 14:51:44

seth wrote:

where exactly and when does the message in #7 appear?

I'm not exactly sure, what you mean by that.
I just ran FC_DEBUG=4 pango-view --font="monospace" -t "" | grep family: and posted the output.

seth wrote:

Also

FC_DEBUG=4 pango-view --font="monospace" -t "シ" | grep family:

The "シ" shows fine, now that i have noto-fonts-cjk installed https://pastebin.com/k4mK5EnK

RollingRaven · 2023-11-16 14:53:29

The topic is more or less solved for me, thanks to you @seth !

How can I mark the post as "solved"?

seth · 2023-11-16 15:59:42

I wanted to test that glyph (the pango-view call is slightly different in that)

I'm not exactly sure, what you mean by that.

No fonts contain glyphs for these codepoints: \u{28}\u{29}\u{77}\u{30af}\u{30b4}\u{30b7}\u{30c3}.
Placeholder glyphs are being displayed instead.
You may wish to install additional fonts, or adjust
your configuration so that it can find

isn't an output any of the commands I asked for would produce (I suspect it's from your TE?)

Mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

RollingRaven · 2023-11-16 16:56:18

seth wrote:

I wanted to test that glyph (the pango-view call is slightly different in that)
No fonts contain glyphs for these codepoints: \u{28}\u{29}\u{77}\u{30af}\u{30b4}\u{30b7}\u{30c3}.
Placeholder glyphs are being displayed instead.
You may wish to install additional fonts, or adjust
your configuration so that it can find
isn't an output any of the commands I asked for would produce (I suspect it's from your TE?)

It was for the command FC_DEBUG=4 pango-view --font="monospace" -t "" | grep family:
Now I have noto-fonts-cjk installed and the error is gone.

seth wrote:

Mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Thanks, done

seth · 2023-11-16 17:58:28

Frt, the message is actually from wezterm, https://www.google.com/search?q=%22No%2 … ints%3A%22

Arch Linux

#1 2023-11-07 22:07:36

[solved] Problem with understanding Font Configuration

#2 2023-11-08 08:37:42

Re: [solved] Problem with understanding Font Configuration

#3 2023-11-08 17:56:59

Re: [solved] Problem with understanding Font Configuration

#4 2023-11-08 19:33:53

Re: [solved] Problem with understanding Font Configuration

#5 2023-11-10 17:45:30

Re: [solved] Problem with understanding Font Configuration

#6 2023-11-10 18:02:31

Re: [solved] Problem with understanding Font Configuration

#7 2023-11-11 00:27:53

Re: [solved] Problem with understanding Font Configuration

#8 2023-11-11 08:19:09

Re: [solved] Problem with understanding Font Configuration

#9 2023-11-11 18:22:29

Re: [solved] Problem with understanding Font Configuration

#10 2023-11-11 19:30:12

Re: [solved] Problem with understanding Font Configuration

#11 2023-11-16 14:51:44

Re: [solved] Problem with understanding Font Configuration

#12 2023-11-16 14:53:29

Re: [solved] Problem with understanding Font Configuration

#13 2023-11-16 15:59:42

Re: [solved] Problem with understanding Font Configuration

#14 2023-11-16 16:56:18

Re: [solved] Problem with understanding Font Configuration

#15 2023-11-16 17:58:28

Re: [solved] Problem with understanding Font Configuration

Board footer