Just to follow up on Matt's note, > I'm sorry this never got updated. Some changes have been made and > are waiting to go out now. When I switched from working on the > Platform (formerly API) team to my focus on international I took over > this issue. > Once this current fix is deployed (probably in a week or so since > I'm traveling at the moment) the definition of a character will be > consistent throughout our API. The new change will always compute > length based on the Unicode NFC [1] version of the string. Using the > NFC form makes the 140 character limit based on the length as > displayed rather than some under-the-cover byte arithmetic.
Has this change occurred yet? I have a fix in TTYtter ready to go to enable 140 *character* posts instead of bytes, but I don't want to deploy it until I know the path is clear. -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- armadillo, n. the act of providing weapons to a Spanish pickle. ------------
