403 errors => Unauthorized. I'd assume that the problem is in your Base
String.
Try recreating this example. Post a Tweet with
"setting up my twitter 私のさえずりを設定する".
* Put "status=setting%20up%20my%20twitter%20私のさえずりを設定する" in
the POST body.
* The Base String *must* have (case-sensitive, etc) :
status%3Dsetting%2520up%2520my%2520twitter%2520%25E7%25A7%2581%25E3%2581%25AE%25E3%2581%2595%25E3%2581%2588%25E3%2581%259A%25E3%2582%258A%25E3%2582%2592%25E8%25A8%25AD%25E5%25AE%259A%25E3%2581%2599%25E3%2582%258B
in it.
Please confirm that you are getting the same values. If you do not, you
should look at how you encode UTF8 data.
Tom
On 12/30/10 4:53 PM, Ryan Bell wrote:
Hi,
A few months ago, Twitter stopped accepting messages from our
application that contained special language characters. We assume
that the API is now very strict on character encoding. We have
analyzed our code and we are following the best practices of character
encoding into utf8. Just before we send the message to the API, we
encode it into utf8, then place the text into the url and send it. We
receive back 403 errors for any messages that contain special
characters (like umlauts).
We've tried everything that we can think of. Can you please send us
an example of how to properly encode the message? We are using c#.
Any help is greatly appreciated.
Thank You,
Ryan Bell
--
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
