-
Notifications
You must be signed in to change notification settings - Fork 34
Improper Glyphs #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
not sure if I understand your problem, but I'm betting you specified the font as "Siji" and it's not getting found. You can use the output of above command for my Arch Linux install: output of above command for my Void Linux install: I cannot reason why this happens, I used the install script for both. Check the output of |
So I have it installed, but when I try using like the first 20 glyphs copied from gucharmap they show up as something else. In polybar it's fine because I haveSiji set as my first font, but I can't do that in a bash script. How do I get it so that the Wuncon Siji glyphs take priority over the ones included with Iosevka (Nerd Font Patched)? |
as far as my understanding for X fonts goes, X will always search for a character until it finds one. If a font doesn't cover a specific char, X will search for that char in all subsequent fonts, until it either finds one or defaults to some other char. This means that you could probably specify Siji as your first font, Iosevka as your second, as Siji only has glyphs, no chars of the latin alphabet. However, if Siji and Iosevka have conflicting glyphs, which means glyphs that map to the same char, the situation gets much more complicated. You'd have to create a non overlapping version of Siji and Iosevka. I don't have any expertise on that though. |
I'm trying to use the glyphs but besides my polybar config where I specify the font, the fonts show up as something else entirely when I use them in scripts. For example, in my time script, the circle clock shows up as a curly a. How can I fix this?
The text was updated successfully, but these errors were encountered: