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
feature: CSS-like font fallback #4492
Labels
Comments
Well found that I can select all the ASCII pieces one by one and change their font, but obiviously it's is far away from convinence if there are a large amount of text to deal with. CSS behaivor is like "auto fallback". |
madalenapmelo-kp
added
the
managed on taiga
This issue has been moved to our project at Taiga.io
label
Apr 24, 2024
Hi @bsdayo, Thanks for the suggestion! I have created an enhancement in our backlog on Taiga so that we can explore this in the future, details here: https://tree.taiga.io/project/penpot/issue/7603 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
Usually it's useful to mix two fonts in a single text element, as many asian fonts do not have nice-looking ASCII characters.
For example, font
Noto Sans SC
supports both ASCII and Chinese characters, but its ASCII characters... just not that good; while fontRed Hat Display
have nice-looking ASCII characters, but don't support Chinese characters. As for text你好hello
, we want the你好
part in fontNoto Sans SC
,hello
part in fontRed Hat Display
.CSS
font-family
handles this scenario perfectly. Just a single line to achieve it:If a character isn't supported by
Red Hat Display
, then fallback toNoto Sans SC
; If still unsupported, then fallback to system sans-serif font.It will benefit many people if this functionality can be implemented.
Describe the solution you'd like.
Add a fallback option to the font selector.
Describe alternatives you've considered.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: