-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some Emoji will fallback to Noto Sans CJK on Android #191
Comments
These characters were not added in 2.002. They have always been in there (including 2.001) so that can't be the cause of what you're seeing. |
I find out that NotoSansCJK-Regular.ttc (version 2.001) in Android is different to this repository. SHA256 of NotoSansCJK-Regular.ttc (version 2.001) in this repository: SHA256 of NotoSansCJK-Regular.ttc (version 2.001) in Android 11: And I use Google's font tool to search |
Here you can find more details about the modification by Android. subset_noto_cjk.py: https://cs.android.com/android/platform/superproject/main/+/main:external/noto-fonts/scripts/subset_noto_cjk.py;drc=d8536c6637d9506ccd8ffb09810ceb7e864e20d8 You might also interesting about |
We need NOTO COLOR EMOJI!!! |
And also soccer ball and baseball. And more. |
|
|
We set the value to -1 not... |
Twenty-four glyphs are available but we set the value to -1. |
I discover that those Emoji was added in version 2.002:
🆕 (U+1F195), 🆓 (U+1F193), 🆙 (U+1F199), 🆗 (U+1F197), 🆒 (U+1F192), 🆖 (U+1F196), 🈁 (U+1F201), 🈳 (U+1F233), 🆎 (U+1F18E), 🆑 (U+1F191), 🆘 (U+1F198), 🉐 (U+1F250), 🈴 (U+1F234), 🈵 (U+1F235), 🈹 (U+1F239), 🈲 (U+1F232), 🉑 (U+1F251), 🈶 (U+1F236), 🈚 (U+1F21A), 🈸 (U+1F238), 🈺 (U+1F23A), 🆚 (U+1F19A)
When I try to replace NotoSansCJK-Regular.ttc (version 2.001) in Andorid system by version 2.003. Seems that Android prefer to display those Emoji by Noto Sans CJK instead of Noto Color Emoji.
Before modified:
After modified:
Why adding those Emoji to Noto Sans CJK?
Related issue: https://issuetracker.google.com/issues/185155368
The text was updated successfully, but these errors were encountered: