Conversation
The font's family name contains a space, so Rio reported "font(s) not found: Noto Sans Symbols2". Fixes Yazelix#704 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Rio symbol map in
defaults/rio/config.tomlmaps U+1F5B0–1F5C0 to"Noto Sans Symbols2". The actual family name ofNotoSansSymbols2-Regular.otfinnoto-fontsisNoto Sans Symbols 2, with a space, so Rio reportsfont(s) not found: Noto Sans Symbols2.This changes the entry to
"Noto Sans Symbols 2".fc-scanconfirms the family name. I haven't run the flake checks.Existing installs keep the old name in their seeded
rio/config.tomluntil users edit or regenerate it.Fixes #704
🤖 Generated with Claude Code