Why we can't process Emoji anymore
gist.github.com
Why we can't process Emoji anymore
1–10 of 162 posts
Re: Why we can't process Emoji anymore
#2Took me a bit to realize that this is talking about the Voxer iOS app (http://voxer.com/), not Github (https://github.com/blog/816-emoji).
Re: Why we can't process Emoji anymore
#3TLDR: node sucks
Re: Why we can't process Emoji anymore
#4If you search for V8 UCS-2 you'll find a lot of discussion on this issue dating back at least a few years. There are ways to work around V8's lack of support for surrogate pairs. See this V8 issue for ideas: https://code.google.com/p/v8/issues/detail?id=761
My question is why does V8 (or anything else) still use UCS-2?
Re: Why we can't process Emoji anymore
#5TLDR: node sucks
TLDR: The V8 engine can't (supposedly) encode Unicode codepoints that are over 16-bits in length, because it uses the UCS-2 encoding.
Re: Why we can't process Emoji anymore
#6The quick summary, for people who don't like ignoring all those = signs, is that V8 uses UCS-2 internally to represent strings, and therefore can't handle Unicode characters which lie outside the Basic Multilingual Plane -- including Emoji.
Re: Why we can't process Emoji anymore
#7Here's the thread in the v8 bug tracker about this issue: http://code.google.com/p/v8/issues/detail?id=761
Is there a reason that the workaround in comment 8 won't address some of these issues?
Re: Why we can't process Emoji anymore
#8TLDR: node sucks
It's v8's fault, and v8 does not suck.
Re: Why we can't process Emoji anymore
#9Sometimes you need to know about encodings, even if you're just a consumer. Putting just one non 7-bit character in your SMS message will silently change its encoding from 7-bit (160 chars) to 8-bit (140 chars) or even 16 bit (70 chars) which might make the phone split it into many chunks. The resulting chunks are billed as separate messages.
Re: Why we can't process Emoji anymore
#10[deleted]