Add another emoji file option with digits font

[Sponge-o1919]

Sorry for my bad English skill...
In some cases when I choose this font to any app which can change font, digits ("0"(U+0030) to "9"(U+0039)) will disappear and can't read anything uses digits (e.g. "Sponge-o1919" is shown as "Sponge-o").

I know it is because I choose this emoji-only .ttf file to the custom font selector which designed for normal characters (Alphabet, number, and Hiragana / CJK in my cases...).
I should rebuild this emoji font with digits font by myself, but since I don't have any python skill, I couldn't do that...

If you don't mind, Would you add the optional .ttf file which also contains any digits font?

[C1710]

Yeah, I already had this issue myself, but didn't get to fix it yet 😅

[Sponge-o1919]

Oh... I see. I wait the fixed version with 5ch community who love yellow blob boy🤗

[C1710]

Wait, the issue is not related to EmojiCompat/Android?

[C1710]

So, what I thought of was that keycap emojis like 4️⃣2️⃣ don't work e.g. in Tusky (see tuskyapp/Tusky#2407)...

[Sponge-o1919]

Well... it is probably not related to EmojiCompat, but maybe related to Android.
The app which I want to use this font is "chmate", and you can change font by accessing "･･･" at the bottom right → "設定" → "画面(向き、広告の位置、スクロール)" → "フォント・AA（アスキーアート）" → "デフォルトフォント" and choose the file.
The issue I mentioned is when I choose this font as デフォルトフォント(means "default font"), what it should be shown as like this will turn into like this, and can't see any numbers.

[Sponge-o1919]

If you want to check whether any characters are shown properly or not, access "･･･" → "URLを指定して開く" → put "https://nova.5ch.net/novatr/" → "OK" and watch some pages.

[Sponge-o1919]

Well... I tested some emojis and normal characters here, and found out an issue below;

･"#, *, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 (U+0023, U+002A, U+0030 ~ U+0039)" will disappear when use latest blobmoji font

I guess this is because those characters are used in respective keycap emojis (#️⃣, *️⃣, 0️⃣ ~ 9️⃣) as components (like 0️⃣ is made of "0"(U+0030), U+FE0F, and "⃣"(U+20E3)).
You might add some kinds of processing that U+0023, U+002A, U+0030 ~ U+0039 are forced to be shown as blobmoji font, but since there is no respective font picture in the file, they will disappear.
So I think easiest solution I can come up with is that you just add font picture of U+0023, U+002A, U+0030 ~ U+0039 in "Blobmoji.ttf"and rename it like "BlobmojiWithKeycapFont.ttf".

Maybe there are more characters those will disappear, if they are normal characters but are used as emoji components.

[C1710]

My problem here is that I can't really test it.
I can test the font in a browser (or even my system), but there it correctly falls back to the normal font for numbers.

But I have now created a version that includes the numbers again. However, they are all white and will therefore not display correctly on a light background. And all numbers have a full emoji width, which looks very weird.
https://github.com/C1710/blobmoji/tree/numbers/fonts

[Sponge-o1919]

I'm sorry that I couldn’t find out other solution by myself anymore...
However, I found the custom NotoColorEmoji.ttf file (click "フォントデータはこちら" to download) that can show numbers properly in my environment, so comparing that NotoColorEmoji.ttf and your Blobmoji.ttf, you may find the solution of this issue...
Edit: Well, that custom NotoColorEmoji.ttf file does not contain keycap emojis to show normal numbers appropriately...
So my proposal is as follows;
・Make optional Blobmoji.ttf file that doesn't contain any keycap emojis besides "🔟", for some environment that normal numbers will be glitched when using normal Blobmoji.ttf file, and name it like "BlobmojiNoKeycap.ttf".