This should work fine -- how are you %-encoding the UTF-8 characters in your
POST body?
For example, in your POST body it should look something like:
status=%d0%bf%d1%80%d0%be%d0%b2%d0%b5%d1%80%d0%ba%d0%b0
And in your signature base string:
POSThttps%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fupdate.jsonoauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DZwmxIz73x3qI8bvNA9LF71IzfAXF0ZdGNw37iyo1B2g%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1296248907%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3D%25D0%25BF%25D1%2580%25D0%25BE%25D0%25B2%25D0%25B5%25D1%2580%25D0%25BA%25D0%25B0
Which results in this (segment of) JSON response:
text:\u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430
Which looks like this when rendered:
http://twitter.com/#!/oauth_dancer/status/31096289030578176
проверка
Taylor
On Fri, Jan 28, 2011 at 12:18 PM, zendocon kristof...@pokermemento.comwrote:
Most Russian letters are correct in my tweets, but for certain letters
I get garbage...
If I tweet this through my Twitter application: испытания
I get this: испÑ39Ñ1Aания
And if I tweet this: проверка
I get this: пÑACовеÑACка
Which is sent as UTF8: d0 bf d1 80 d0 be d0 b2 d0 b5 d1 80 d0 ba d0 b0
Where's the error? I have verified the UTF8 string with multiple
converters. It is indeed correct!
Please help!
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
