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.
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.
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...