Missing Emoji (Newer Unicode version?) #2
Comments
|
As can be seen above, after some tinkering I've come to the conclusion that the issue does in fact actually lie with EmojiSwitcher. After setting the EmojiOne font manually, and abiding by the additional instructions stated at the bug report I made on the EmojiOne tracker (regarding black-and-white emoji fallbacks), I get the expected emoji replacement behaviour in Telegram.
I think this bug can be safely closed, as the fault does not lie here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using TgEmojiReplacer 1.0 on my CM 13 device (Android 6.0.1), with Telegram 3.11.2, and (seemingly regardless of which emoji set I'm using, set using EmojiSwitcher), there are a ton that don't seem to get properly replaced, instead displaying simple black-and-white versions of them.
I don't /think/ this is the fault of EmojiSwitcher, as I get this effect even when I stay on the default Android emojis (pictured is of course EmojiOne), but that's something I'm willing to experiment with more thoroughly if you need me to. However, I did have problems before with /manually/ replacing Emoji (a similar issue resulted), which so I'm going to go check with EmojiSwitcher what they're doing, and also test to see if I still get the issue if I replace the emoji font manually.
My very superficial guess is that the emoji that are not being correctly replaced are ones which are somehow "new" in Telegram, and thus not yet being properly replaced by the xposed module. But I was able to make a list of the affected emoji:
I can't guarantee that I didn't miss one, but I think it's mostly comprehensive.
The text was updated successfully, but these errors were encountered: