Missing glyphs (consolidated)

[simoncozens]

These codepoints were either in Symbols at one point and got moved out somewhere (we lost them), or else were never in there and someone thinks they should be:

• U+20D* (e.g 20d0, 20d2, 20d4, 20d6, 20d8, 20da, 20dc)
• U+2900-2AFF
• U+1D000-1D300
• U+1D400-1D7FF
• 2591, 2592, 2593, 2502, 2524, 2561, 2562, 2556, 2555, 2563, 2551, 2557, 255D, 255C, 255B, 2510, 2514, 2534, 252C, 251C, 2500, 253C, 255E, 255F, 255A, 2554, 2569, 2566, 2560, 2550, 256C, 2567, 2568, 2564, 2565, 2559, 2558, 2552, 2553, 256B, 256A, 2518, 250C, 2588, 2584, 258C, 2590, 2580, 25A0,
• U+1F1E6-1F1FF
• 23EB, 23EC, 23F0, 2705, 270A, 270B, 2728, 274C, 274E, 2753, 2754, 2755, 2757, 27B0, 27BF,
• U+1F10D-1F10F, 1F16D-1F16F
• U+1F12F
• U+1F1AD
• U+1F23B
• U+1F260-1F265
• U+1F900-1F90C

(From #32, #28, #19, #4 and #16.)

[Mercury13]

U+20D* implemented in Math, almost unusable here
U+2900-2AFF yes
U+1D000-1D300 some present in Sym2, some in Music
2591 etc — possibly, but make them consistent with Legacy computing
1F1E6 etc — maybe yes
23EB etc — abstain here
1F10D etc — standard CC images, not much work
1F12F — implemented in your CJK font, but yes
1F1AD — yes
1F23B — maybe
1F260 etc — yes
1F900 etc — I drew, but w/o umlauts (heard there are some)

Also 1F774…76, 7B…7F — I drew, but just normal, w/o bold, and I had some issues with Quaoar that I fixed with rounded corners

[verdy-p]

U+2FFC-2FFF, U+31EF: Five additional "Ideographic description characters", newly assigned in Unicode 15.1.0 (September, 2023). #80

[nardholio]

U+1F581, Clamshell Mobile Phone, is part of Unicode 7.0 and was previously in Noto. It renders on modern Android phones as a blank space, not even as a broken symbol.
https://github.com/notofonts/noto-source/blob/main/src/NotoSansSymbols2/NotoSansSymbols2-Regular.ufo/glyphs/clamshellM_obileP_hone.glif

SVG rendering from Wikimedia https://commons.wikimedia.org/wiki/File:NotoSans_-_Clamshell_Mobile_Phone_-_1F581.svg

[Mercury13]

@nardholio Present for now, what’s the thing?

[nardholio]

Must be a bug elsewhere in Android then, thanks for confirming