Open Lorp opened 4 months ago
This may be a consequence of missing U+FE0F and the font providing support for all codepoints with or without fully qualified sequences
I suspect it is accidental based on needing these glyphs as components for 0️⃣1️⃣2️⃣3️⃣4️⃣5️⃣6️⃣7️⃣8️⃣9️⃣#️⃣*️⃣
This may be a consequence of missing U+FE0F and the font providing support for all codepoints with or without fully qualified sequences
Not only that - some renderers just don't support/handle VS15 and VS16. :unamused: https://bugreports.qt.io/browse/QTBUG-85744 , https://bugreports.qt.io/browse/QTBUG-97401 ...
I’m curious why the following characters are encoded in Noto Color Emoji:
0123456789#*
(I also note that ©®™️are encoded, but this is good since they are part of emoji.)
The issue makes it problematic to specify CSS font-family as "Noto Color Emoji, Roboto", since all digits will come from the Emoji font. Indeed one could filter out those characters using unicode-range, but that would mean editing the CSS that Google Fonts supplies.
Screenshot from Fontlab with Noto Color Emoji loaded, and encoding set to Type 1/Western Roman.