Does Noto Color Emoji support emoji color sequence?
See original GitHub issuehttps://unicode.org/Public/emoji/12.0/emoji-test.txt
I found in Linux + Chromium, some emoji are still monochrome even if with \uFE0F
variation sequence, like copyright sign ©️
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (2 by maintainers)
Top Results From Across the Web
Noto Color Emoji - Google Fonts
Noto Color Emoji is an open-source emoji font. It supports the latest Unicode specification (15.0) and features 3,664 emoji. Supported writing systems. Emoji....
Read more >Why do I see a black-and-white emoji in console with Noto ...
The emojis are shown by the font selected in the terminal/console and the ones from the emoji fonts in color are not taking...
Read more >Google Developers Blog: Updates to Emoji: New Characters ...
Look no further than Emoji Kitchen available on Gboard: type a sequence of emoji including a colored heart to change its color.
Read more >Noto Emoji Font - Emojipedia
As per standard variable text fonts, the Noto Emoji Font allows users to change each emoji character's color, size and weight. The font's...
Read more >How to give Noto Color Emoji highest precedence for ...
The system already has Noto Color Emoji installed. How do I give Noto Color Emoji precedence? I've followed several fontconfig tutorials, but ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am reporting this bug to fontconfig https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/179
@guoyunhe Try this with your codepen on Android:
That should make the first 2639(
☹
) render as the emoji version 2639(☹️
/☹️), and no difference to the copyright characters.Now remove the default
serif
(or try withsans-serif
if you like, this seems to be the difference between firefox and chrome) font, and the copyright characters should change to the Noto Color Emoji VS16 version for both. What this shows, is that Roboto was used to provide the copyright glyph by default, as mentioned.The fallback for the 2639(
☹
) appears to be “Noto Sans Symbols”(no 2), if you apply that font, you’ll see both versions become this, even though you have one defined with VS16 codepoint to ask for colour. So you see, it’s all about the font ordering/priority for fallback fonts.For the copyright symbol, both serif/sans-serif(whichever font is used by default for those on Android, I have no idea) appears to have the copyright glyph, so takes priority, no other font is used.