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
Emojis are displayed with ugly fallbacks in the classic theme (probably others too) #7024
Comments
|
+1; Reasonable. But I don't know what font is better for emojis. Is your list of CSS also good for Sphinx? |
|
Hmm... it seems there are no default font settings in basic theme. So adding fallback fonts affects to default font... |
|
We could prepend the list of emoji fonts with a list of system fallbacks from here https://devhints.io/css-system-font-stack. The trick is to have emoji fallbacks last in the list and having system fallbacks before should be fine.
I suppose so. I've tested it on Alabaster (sanitizers/octomachinery@787226b / https://docs.octomachinery.dev/) and also I used DevTools on packaging.python.org to inject these fonts at the end of the existing list. N.B. Some emoji fonts (if they contain only emojis) are okay to bring to the front row but there's others that have emoji-like numbers that appear in place of legitimate digits that are expected to appear in the same style as the surrounding text. For texting, I just edited CSS rules via DevTools by removing fonts from the list one by one to see what happens... Some refs: |
Describe the bug
$subj. I usually add
"apple color emoji", "segoe ui emoji", "android emoji", "emojisymbols", "emojione mozilla", "twemoji mozilla", "segoe ui symbol", "noto color emoji"in the end of the font lists and it works perfectly.Current CSS only list fonts that don't implement emojis at all.
To Reproduce
N/A
Expected behavior
There's different emoji fonts that could be used if they were mentioned in CSS.
Your project
https://packaging.python.org/
Screenshots

no fallback fonts:
with fallback fonts:

Environment info
Additional context
N/A
The text was updated successfully, but these errors were encountered: