-
Notifications
You must be signed in to change notification settings - Fork 46
[Linux] Chrome and Firefox do not display number emoji correctly #46
Comments
Thank you for the detailed bug report! This is currently intentional. The glyphs were disabled in e1a34da for #40 [Linux] Inconsistently parsed fontconfig causes font selection problems (Help wanted!) If I revert the commit, then #35, #37, #39 and more will happen again. |
Well, that's a good point, but #40 on my Arch looks like this and everything works fine. ❯ fc-match -s sans
Vera.ttf: "Bitstream Vera Sans" "Roman"
EmojiOneColor-SVGinOT.ttf: "EmojiOne Color" "Regular"
DejaVuSans.ttf: "DejaVu Sans" "Book"
DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold"
DejaVuSans-Oblique.ttf: "DejaVu Sans" "Oblique"
DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique"
n019003l.pfb: "Nimbus Sans L" "Regular"
... etc For #35, #37, #39, I'm really not sure why UTF-8 emoji glyphs would appear instead of numbers - those are separate symbols, I believe. Could this all be something else? |
The programs in those issues all implement their own fontconfig parsing, but as far as I understand, they don't follow the spec for
Run Evolution, MPV or Steam with version 1.1 of the font and you can reproduce these issues.
These numpad emoji require font ligatures to work. Font ligatures only work if all glpyhs used to create the ligature are in the font. I need to have both the empty numpad emoji and a regular non-emoji number so they can be combined to create a numpad number.
Yes, but this is so far the only solution in my tests on all three programs in two Linux distributions. I gladly accept a better solution though. I've suggested a possible solution (or rather long term workaround for the MPV, Evolution, and Steam bugs) in #40 at: #40 (comment) Let's move further discussion on this to #40. Thanks! |
I currently have no issues with this font except for this one. I'm guessing the number emoji are overridden somewhere, but I wonder why no other emojis are. Everything else looks fine.
Chrome
Firefox
The text was updated successfully, but these errors were encountered: