6 ms·
It always feels like the most amount of work goes to the least used emoji. So many revisions and additions to the family emoji and yet it’s one of the ones I do
by Gigachad 5y ago
It always feels like the most amount of work goes to the least used emoji. So many revisions and additions to the family emoji and yet it’s one of the ones I don’t recall anyone ever using.
I think the trap Unicode got in to is technically they can have infinite emoji so they just don’t ever have a way to say no to new proposals.
- laumars 5y agoThey do say no though. Frequently too. The problem with Unicode is simply that it’s trying to solve a very hard problem.
- tialaramex 5y agoExactly this. Humans have incredibly complicated writing systems, and all Unicode wants to do is encode them all. Keep in mind that the trivial toy system we're more familiar with, ASCII, already has some pretty strange features because even to half-arse one human writing system they needed those features. Case is totally wild, it only applies to like 5% of the symbols in ASCII, but in the process it means they each need two codepoints and you're expected to carry around tech for switching back and forth between cases. And then there are several distinct types of white space, each gets a codepoint, some of them try to mess with your text's "position" which may not make any sense in the context where you wanted to use it. What does it mean to have a "horizontal tab" between two parts of the text I wanted to draw on this mug? I found a document which says it is the same as "eight spaces" which seems wrong because surely if you wanted eight spaces you'd just write eight spaces. And after all that ASCII doesn't have working quotation marks, it doesn't understand how to spell a bunch of common English words like naïve or café, pretty disappointing.
- xxpor 5y ago>Humans have incredibly complicated writing systems Not only that, there isn't even agreement about what's correct all the time! >it doesn't understand how to spell a bunch of common English words like naïve or café, pretty disappointing. A perfect example of this, since I would argue English doesn't have any diacritics at all. So the use of café is code switching. :)
- mattkrause 5y agoNot a New Yorker writer, I see....
- xxpor 5y agoThank God! (seriously, every time I read an article from them I get distracted/nerd sniped by their diaeresis use...)
- brimble 5y agoIt's still "rôle" to me, damnit.
- deleted 5y ago[deleted]
- jfk13 5y agohttps://dictionary.cambridge.org/dictionary/english/resume https://dictionary.cambridge.org/dictionary/english/resume, for example, makes the distinction between "resume" and "résumé" pretty clear.
- masklinn 5y ago> It always feels like the most amount of work goes to the least used emoji. I always feel like those emoji were added on purpose in order to force implementations to fix their unicode support. Before emoji were added, most software had completely broken support for anything beyond the BMP (case study: MySQL's so-called "UTF8" encoding). The introduction of emoji, and their immediate popularity, forced many systems to better support astral planes (that is officially acknowledged: https://unicode.org/faq/emoji_dingbats.html#EO1 https://unicode.org/faq/emoji_dingbats.html#EO1) Progressively, emoji using more advanced features got introduced, which force systems (and developers) to fix their unicode-handling, or at least improve it somewhat e.g. skintones for combining codepoints, etc.... > I think the trap Unicode got in to is technically they can have infinite emoji so they just don’t ever have a way to say no to new proposals. You should try to follow a new character through the process, because that's absolutely not what happens and shepherding a new emoji through to standardisation is not an easy task. The unicode consortium absolutely does say no, and has many reasons to do so. There's an entire page on just proposal guidelines (https://unicode.org/emoji/proposals.html https://unicode.org/emoji/proposals.html), and following it does not in any way ensure it'll be accepted.
- mike_hock 5y agoWTF business do emojis have in Unicode? The BMP is all there ever should have been. Standardize the actual writing systems of the world, so everyone can write in their language. And once that is done, the standard doesn't need to change for a hundred years. What we need now is a standardized, sane subset of Unicode that implementations can support while rejecting the insane scope creep that got added on top of that. I guess the BMP is a good start, even though it already contains superfluous crap like "dingbats" and boxes.
- kingcharles 5y agoHave emoji not become part of our writing structure though? A decent percentage of online chats and comments, especially on social networks, includes at least one emoji that couldn't be easily or accurately represented in the regular written language.
- jonas21 5y agoThis work wasn't done for emoji. They use the same zero-width joiner character [1] that exists to support Indic scripts like Devanagari, and any system that properly handles these languages will also properly handle the emoji. Yes, this adds a lot of complexity, but it's really a question of whether that complexity is justified in order to support all of the world's languages. And I think many would argue that it is. [1] https://en.wikipedia.org/wiki/Zero-width_joiner https://en.wikipedia.org/wiki/Zero-width_joiner
- jahewson 5y agoEmoji has turned out to be a great way to enhance complex script support in much real-world software and they get my full support for that reason too.