Skip to content
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

macOS: fallback for missing font glyph? #913

Open
raphamorim opened this issue Jan 19, 2025 · 0 comments
Open

macOS: fallback for missing font glyph? #913

raphamorim opened this issue Jan 19, 2025 · 0 comments

Comments

@raphamorim
Copy link
Owner

Discussed in #912

Originally posted by jeffglover January 19, 2025
OS version: macOS Sequoia 15.2
Rio version: 0.2.4 (20230528.115631) & main @ 66257aa

When using a font missing certain glyphs, in my case braille glyphs mostly used in various progress bars, it does not fall back to another source for those glyphs. This very notable in btop and docker commands. This same config works without issue on Linux.

If I use a font that contains braille glyphs as my primary font, such as cascadiacode or Iosevka this is not an issue.

[fonts]
size = 16
family = "JetBrainsMono Nerd Font Mono"

Non nerd font variants have the same issue: family = "JetBrains Mono"

jetbrains-nfm-btop


If I add an extras font with anything that has the missing glyphs, it renders, but does not match the same spacing as the original font.

[fonts]
size = 16
family = "JetBrainsMono Nerd Font Mono"
extras = [{ family = "Apple Braille" }]

Changing extras to another font with braille glyphs such as IosevkaTerm Nerd Font Mono renders the glyphs with the same font spacing mismatch.

jetbrains-nfm-btop-braille


Disclaimer: I'm pretty much exclusively a Linux user for the past 15+ years. I've taken on this Mac for work. My configs were copied over with very little change, where in Linux none of the issues exist. I very well could be missing something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant