Comment by OisinMoran
8 months ago
It seems that of all the numbers (needed here), the symbol for 20 (𒎙) is the only one that doesn't render on Android. Very odd. It does seem to be the last used codepoint (U+12399) in the Cuneiform block (U+12000–U+123FF) and they seem to stop rendering from U+1236E (on Android) which leaves 43 symbols un-rendered.
Anyone any idea why that might be?
See https://en.wikipedia.org/wiki/Cuneiform_(Unicode_block) and https://en.wikipedia.org/wiki/Cuneiform_Numbers_and_Punctuat...
sent at 𒌋𒐖:𒐐𒐕:𒌋𒐗
Okay, in the interim I have a shipped a fix for Android (seems fine on an iPhone emulation) that uses two tens like so "𒌋𒌋" (looks like <<) instead of one twenty "𒎙" (also looks like << but a bit tighter). This is definitely one of the weirdest patches [0] I've ever done—changing how an ancient language is displayed based on the specific type of incomprehensibly advanced technology it's being displayed on—but I guess that's what Sundays are for.
[0] https://github.com/OisinMoran/OisinMoran.github.io/commit/15...
Cuneiform is still a wedge issue.
Because Google has mostly stopped updating the font stack on Android.
See bug report https://issuetracker.google.com/issues/366415133
Well, I can report that 𒎙 isn't rendering on Windows 10 either. Your "sent at" renders fine. Whatever it is, it isn't specific to Android.
I assume it's mostly down to fonts, but I don't know why a font would implement some of the cuneiform block without doing all of it.
U+12399 was not an assigned code point until Unicode 8. The other code points were in Unicode 7.
https://i.ibb.co/6RBrwZpz/firefox.png
Firefox 139.0.4 on Arch Linux
I guess the Arch in Arch Linux isn't for archaeology then :(
You'll need to install the `noto-fonts` package to get NotoSansCuneiform-Regular.ttf (amongst others)l I'd recommend also installing `noto-fonts-cjk` to enhance your web experience.
Can't the web page embed the font?
You just don't have the required font.