3 ms·
Interesting, every font I've seen renders them like this: https://imgur.com/a/ZPBfaK0 https://imgur.com/a/ZPBfaK0 I thought it was suggested to render them li
by banana_giraffe 6y ago
Interesting, every font I've seen renders them like this: https://imgur.com/a/ZPBfaK0 https://imgur.com/a/ZPBfaK0
I thought it was suggested to render them like that from Unicode somewhere, but it's 100% possible I'm making that part up.
- lilyball 6y agoMy recollection is for the textual characters that got repurposed as emoji, it’s implementation-defined as to whether the character defaults to text or emoji but that most renderers opt for emoji (which I believe is copying Apple’s decision here). There are variation selectors you can use to force textual or emoji presentation.
- kps 6y agoIt's not implementation defined, i's defined by the Emoji_Presentation property in https://www.unicode.org/Public/13.0.0/ucd/emoji/emoji-data.txt https://www.unicode.org/Public/13.0.0/ucd/emoji/emoji-data.t... Some implementations are just wrong.
- lilyball 6y agoThat file is new in Unicode 13. Also I think it might be based on Apple's behavior. I just tested every single emoji codepoint listed there, and it's almost entirely consistent with Apple's default rendering. And the very few exceptions (like ) actually seem to depend on whether the text renderer is styled or not, where it becomes emoji in styled fields (like Spotlight) and text in plain-text fields (like this comment box). This seems to only be done for the small handful of pre-existing text symbols that got turned into emoji and given the Emoji_Presentation property.
- AnssiH 6y agoOn my Android Chrome those characters are indeed not rendered specially.