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

Fallback fonts #304

Open
Uberoverlord opened this issue Aug 15, 2023 · 0 comments
Open

Fallback fonts #304

Uberoverlord opened this issue Aug 15, 2023 · 0 comments

Comments

@Uberoverlord
Copy link

The Problem

Fonts which aim to have support for as many languages as possible (Noto, IBM Plex, etc) break their font up into multiple files for the different languages. Emojis, as well, are often in a separate font file to the primary font file.

Current workaround

The only solution I am aware of at the moment would only work for text labels and not user inputted text. The solution would be to have separately named fonts for each language and then read through the text to be rendered and break it up into chunks for each language and then render each chunk in a separate label with the appropriate font. This induces additional problems like that line wrapping must now be dealt with by the developer and is overall a very outwardly complex solution

Proposed solution

Within the same font name (i.e. "Regular") the font manager should be able to fall back down a list of font files if it cannot render a glyph with the primary font file. This would not incur any additional complexity to application developers while solving the issue.

@Dretch Dretch mentioned this issue Aug 24, 2024
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