search

googlefonts / noto-emoji

Noto Emoji fonts
SIL Open Font License 1.1
3.81k stars 458 forks source link

Pre-Unicode 6.0 symbols & coloring emojis on Android (e.g. coloring of ♦) #291

Open leonyu opened 4 years ago

leonyu commented 4 years ago

I am not sure if this is the right place to mention this. I am raising it here, as I think it can effect many other users/websites.

I discovered an issue with "♦" (BLACK DIAMOND SUIT) on Wikipedia with Android.

Prior to introduction of emoji (Unicode 6.0), "♦" was simply a Unicode symbol for the card suit, as such text-color it can be applied re-colored the symbol to any color. Some Wikipedia articles leveraged this for map legends. (Link to wiki history) However, this is no longer possible with colored emojis, as the colored emoji symbols cannot be re-colored. This lead to odd case in the following screenshot: https://imgur.com/QFD3fRp .

For now this appears to only effect Android. I have replaced the diamond with "⧫" (BLACK LOZENGE) instead to workaround the issue.

ChiefMikeK commented 4 years ago

INVALID: Wikipedia articles should use SVG for map markers not a
Unicode character :neckbeard:

Template:Maplink - Wikipedia :eyes: marker & marker-color

leonyu commented 4 years ago

@ChiefMikeK Thank you for fixing the Wikipedia case.

The general case (<span style="color: red;">♦</span>) predates Noto Emoji, and is still valid on non-Androids. So I am sure there are other instances of it on the web.

ChiefMikeK commented 4 years ago

Just saying IMHO not an Android issue for this or any font, see also #290 in Linux font-config(Android sometimes in etc/font.xml) manpage fonts-conf 5 can substitute an emoji for a symbol from another font or via an OpenType feature ss01-ss20, cv01-cv99...

leonyu commented 4 years ago

If this was OpenSymbola, I would agree, and go file an issue with Canonical/RedHat.

However, Google controls both Noto and Android. The end-user has no control over font config (/etc). The only other players are the OEM and potentially phone repair shops. So I would inclined to believe if this is an actionable issue, it would be Google's.

Of course, it might not be actionable, as we might consider aforementioned use case legacy.

On Tue, Feb 18, 2020, 10:21 GSMC Mike A. Kouklis USN-Retired < notifications@github.com> wrote:

Just saying IMHO not an Android issue for this or any font, see also #290 https://github.com/googlefonts/noto-emoji/issues/290 in Linux font-config(Android sometimes in etc/font.xml) manpage fonts-conf 5 https://manpagez.com/man/5/fonts-conf/ can substitute an emoji for a symbol from another font or via an OpenType feature ss01-ss20, cv01-cv99...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/googlefonts/noto-emoji/issues/291?email_source=notifications&email_token=AACKOBXYJZUA5RBUGD7RJNTRDP4HPA5CNFSM4KW46O62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMCMGJY#issuecomment-587514663, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACKOBQHAL3T45FHAJPNKBLRDP4HPANCNFSM4KW46O6Q .

juju2143 commented 4 years ago

Normally, U+2666 (and other emojis in that range) should display as text, and as an emoji if you add U+FE0F. It works for me on my computer using Noto, so the bug must be with Android.