Why Is Swift's String API So Hard?

Re:Why Is Swift's String API So Hard? by mikeash on Friday November 06, 2015 @11:24AM (#10520257)

I'm actually not sure what Twitter is doing, now. Putting Emoji into the box decreases the remaining character count by one for each Emoji. But putting Zalgo into the box decreases the remaining character count by several for each grapheme cluster. My head hurts.

[ Parent | on HN ]

Re:Why Is Swift's String API So Hard? by TazeTSchnitzel on Friday November 06, 2015 @11:39AM (#10520342)

Twitter actually counts codepoints, but after normalisation, so it doesn't matter which of the two ways you represent é: https://dev.twitter.com/overview/api/counting-characters

[ Parent | on HN ]

Re:Why Is Swift's String API So Hard? by mikeash on Friday November 06, 2015 @11:52AM (#10520410)

Right, stupid me, emoji are still a single code point. Put a flag in the box, and the count decreases by two.

[ Parent | on HN ]

Re:Why Is Swift's String API So Hard? by TazeTSchnitzel on Friday November 06, 2015 @03:44PM (#10521899)

Well, depends on the emoji. Some use combing characters, e.g. a red heart is the black heart character plus some invisible joiner IIRC, and some of the family emoji are composed of their individual components (mom/dad/girl/boy) with joiners.

[ Parent | on HN ]

Re:Why Is Swift's String API So Hard? by mikeash on Friday November 06, 2015 @04:22PM (#10522125)

Yes, you're right. In a fit of silliness I was testing only with the ones that are a single code point, though.

[ Parent | on HN ]