Shouldn't unrecognized sequences render as white box with hex code? I thought FFFD was for invalid sequence
-
-
Replying to @myrrlyn @FakeUnicode
"used to replace an incoming character whose value is unknown or unrepresentable in Unicode" I would think "unknown" is the right term to use here
1 reply 0 retweets 0 likes -
Replying to @sgrif @FakeUnicode
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 though1 reply 0 retweets 0 likes -
Replying to @myrrlyn @FakeUnicode
Out of date OS is the best OSpic.twitter.com/dhJ8tTLVYb
1 reply 0 retweets 2 likes -
Replying to @sgrif @FakeUnicode
Haha what Shrug is only a year old but that shouldn't become mojibake...
1 reply 0 retweets 0 likes -
-
(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.
1 reply 0 retweets 1 like -
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.
3 replies 0 retweets 1 like -
Replying to @FakeUnicode @myrrlyn
So is that "1 inside a square" just how Mac deals with the .notdef glyph? Any idea why the ZWJ is being rendered?
1 reply 0 retweets 0 likes -
Replying to @sgrif @FakeUnicode
I'd guess because my keyboard printed "shrug zwj female"?
1 reply 0 retweets 0 likes
Right, but ZWJ should never be rendered as far as I know
-
-
Replying to @sgrif @FakeUnicode
It's a valid glyph even if the predecessor isn't I think
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.