[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-24 Thread alon
can someone assist with the php library? what todo? On Apr 16, 6:18 pm, Mario Menti mme...@gmail.com wrote: On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti mme...@gmail.com wrote: Thanks Guan - perhaps it's an issue with the signature base string not being encoded correctly at my end... let

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-24 Thread Matt Sanford
Hi Alon, The main issue we've seen with extended UTF-8 is incorrect URL encoding of the values. We discussed this in depth in issue 433 [1], which I see you commented on. Without a little more information I can't really help. The information that would be most helpful is: 1. You

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-16 Thread Mario Menti
On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti mme...@gmail.com wrote: Thanks Guan - perhaps it's an issue with the signature base string not being encoded correctly at my end... let me dig into Net::OAuth a little more and see what I find. Quick update: yes, the issue in Net::OAuth was

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-15 Thread Mario Menti
This issue [1] is marked fixed, but for some reason I still have problems with some characters: I have a status update that contains \xc2\xa0 (which I believe is Unicode representation of nbsp;), and trying to update the status with this always results in error 401. If I remove the \xc2\xa0 the

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-15 Thread Guan Yang
On Wed, Apr 15, 2009 at 07:35, Mario Menti mme...@gmail.com wrote: This issue [1] is marked fixed, but for some reason I still have problems with some characters: I have a status update that contains \xc2\xa0 (which I believe is Unicode representation of nbsp;), and trying to update the

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-15 Thread Mario Menti
On Wed, Apr 15, 2009 at 3:47 PM, Guan Yang g...@yang.dk wrote: I was able to post this here: http://twitter.com/guan/status/1525625497 The non-breaking space is right after the colon; try to save the HTML and check in a hexdump ;-) Normalized query string:

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-13 Thread Chen Jie
I have the sample problem too, can't post update with Chinese.. On Apr 13, 1:56 am, Guan g...@yang.dk wrote: On Apr 12, 8:08 am, Cmdr J0hn kazuhiro.is...@gmail.com wrote: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) Signed on a string:

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-13 Thread minimoo...@gmail.com
Same problem here. I can't post update too, with cyrillic characters.

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-13 Thread Matt Sanford
Hi all, Anyone having the problem please add a comment to the Google Code issue [1]. Please include the following if possible: 1. What language, library and version are you using? » For Example: Ruby oauth gem v0.2.7, or PHP oauth-php r50 2. What application is this for? » For

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-12 Thread Julio Biason
2009/4/12 Cmdr J0hn kazuhiro.is...@gmail.com: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) [...] status=%E3%81%82 (It's utf-8, I guess. 3 bytes needed for one Japanese charactor) I think you're not encoding this properly. You're sending one

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-12 Thread Cameron Kaiser
(I have the slight impression that it should be something like status=%4054 or some other very right value, but, again, just one character, not three.) Correcting myself: status=#12354; http://www.danshort.com/HTMLentities/index.php?w=hirag NO! The original poster is correct --

[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet

2009-04-12 Thread Guan
On Apr 12, 8:08 am, Cmdr J0hn kazuhiro.is...@gmail.com wrote: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) Signed on a string: POSThttp%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 And a body is: status=%E3%81%82 Any suggestion