3 ms·
That might be true for the heart, emoticons and several others, but I'm not sure if that statement applies to the taco. Where does it end? Very curious how it'
by treve 11y ago
That might be true for the heart, emoticons and several others, but I'm not sure if that statement applies to the taco.
Where does it end? Very curious how it's determined when something is worthy of inclusion. At what point is unicode no longer an appropriate place to store graphics?
- jpatokal 11y agoGiven that Unicode already encodes things like U+1F365 FISH CAKE WITH SWIRL DESIGN, I think we can squeeze in the taco as well. https://codepoints.net/U+1F365?lang=en https://codepoints.net/U+1F365?lang=en
- chris_wot 11y agoOnly if it goes through the relevant processes. Look at the nightmare they have around racial and gender lines with some of the human characters. Had it gone through better, then it wouldn't have been a problem. Frankly, I'd like to know the names of the people in these ad hoc committees who approve changes to such an important standard. They need to be made accountable.
- colordrops 11y agoWhere are you located? I'm in the south western US and it's extremely clear that that taco is not going away anytime soon. And idiograms in the Unicode set do not have to be universal to be included, e.g. CJK chars are not used in the western hemisphere.
- stubish 11y agoThe Industry determines what is worthy of inclusion in this Industry Standard. If you want to interoperate with Facebook, you need all the Facebook codes. If you want to interoperate with Line, you need all the Line codes, and Wechat, WhatsApp, Ebay, Alibaba and even Github. You want a Taco code point because the data you are being fed contains Tacos, and you want to know it is a Taco rather than a USER_CODEPOINT+XXXXX. And if you don't care about Tacos, you can ignore it because you know it is a Taco and not something important or corruption. And you can just pass it on down the line to some other process that does care about Tacos.