On my super out of date mac, Allo renders an unrecognized emoji as U+25A1 WHITE SQUARE, not U+FFFD REPLACEMENT CHARACTER as it should. Anyone know if this is Mac's fault, Chrome's, or Allo's? (/cc @FakeUnicode)pic.twitter.com/DdTMjoFJ7L
-
Haha what Shrug is only a year old but that shouldn't become mojibake...
maybe? I mean, we have a lot of codepoints whose values are known but have no assigned meaning
Maybe it depends on how the implementor reads the spec
Plain white square is still hella wrong though
-
-
(This is how virtually all ZWJ female emojis render for me >_<) Shrug is fun since it's one of the rare few that doesn't default to male, so it never renders at all.
-
Unsupported glyphs ("tofu") should be shown as plain white boxes. Sometimes with hex, or X, or ?, or as plain ?. These are valid unicode codepoints or sequences with no font support. Invalid code point references or byte sequences (not tofu) become � REPLACEMENT CHARACTER.
- 4 more replies
New conversation -
-
-
I figured, but still We've had high codepoints for a while; it should be able to parse 1F937 into something besides mojibake
-
Yeah I'm surprised that the ZWJ character is rendering there at all. Interestingly if I copy the text, the ZWJ disappears when I delete the unrecognized character, or replace it with something else
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.