Just to confirm: "EXTREME prejudice" as in "140 *bytes* as defined by UTF-8 with HTML entity encoding only for special (< > &) characters?
So my tweet should *NOT* have worked? http://twitter.com/atebits/status/1286199010 Would love to see some kind of official *this is how we determine how long some hunk of unicode is* blurb on the API docs. Loren On Mar 9, 3:17 pm, Alex Payne <[email protected]> wrote: > Just to keep the group updated: one of our engineers has claimed this > issue. It will be dealt with with EXTREME prejudice. > > > > > > On Fri, Mar 6, 2009 at 12:47, Cameron Kaiser <[email protected]> wrote: > > >> 2) 140 Unicode _multi-byte_ characters: <http://twitter.com/atebits/ > >> status/1286199010> > > >> What's curious is that Loren's example with 140 characters uses the > >> Unicode 27A1 glyph. It uses 3 bytes in UTF-8. Why didn't it get > >> truncated? This seems to contradict Alex's statement in the thread > >> mentioned above. > > >> As people start to use things like Emoji, tinyarro.ws and generally > >> figure out that Unicode (UTF-8) is a valid type of data on Twitter, > >> our clients should adapt and display more accurate "characters > >> remaining" counts. I can count bytes instead of characters, but I'm > >> not sure if I should or not. > > > FWIW, I had a number of users complain about truncated UTF-8 sequences a > > while back, which may be a symptom of this same problem. TTYtter now counts > > bytes explicitly, and this seems to have dealt with the issue. > > > -- > > ------------------------------------ > > personal:http://www.cameronkaiser.com/-- > > Cameron Kaiser * Floodgap Systems *www.floodgap.com* [email protected] > > -- Make welfare as hard to get as building permits. > > --------------------------- > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
