I had this same problem. I had to convert all multi-byte characters
>> into their individual bytes.
>> So, for example, for the character "の":
>> Your example has %306E, but the encoding that works for me is
>> %E3%81%AE (three bytes for the three-byte character).
imestamp%3D1253903495%26oauth_token%3D76084396-0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version%3D1.0%26status%3D%25306E%25811A%25672C%255BB6%25304C%258D08%25308B
Do you see anything wrong here?
Thanks!
Satheesh Natesan
On Thu, Sep 24, 2009 at 6:49 PM, Carlos wrote:
>
> Are y
imestamp%3D1253727793%26oauth_token%3D76084396-
0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version
%3D1.0%26status%
3D%25D8%25E1%25C7%25DE%25B5%25E6%25F9%25E7%25B5dw
OAuth client library I am using is in .Net
Could you please help to solve this issue? Also I would like to know
you support all unicode characters.
Your help is greatly appreciated.
Thanks,
Satheesh Natesan
