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 menti
can someone assist with the php library? what todo?
On Apr 16, 6:18 pm, Mario Menti wrote:
> On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti 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 lit
On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti 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 actually identic
On Wed, Apr 15, 2009 at 3:47 PM, Guan Yang 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:
>
>
> oauth_consumer_key=rNc2JuVC6N
On Wed, Apr 15, 2009 at 07:35, Mario Menti 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 status with th
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" t
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 Exampl
Same problem here. I can't post update too, with cyrillic characters.
http://code.google.com/p/twitter-api/issues/detail?id=433 <--?
On Apr 13, 10:23 am, Chen Jie wrote:
> I have the sample problem too, can't post update with Chinese..
>
> On Apr 13, 1:56 am, Guan wrote:
>
> > On Apr 12, 8:08 am, Cmdr J0hn wrote:
>
> > > Now, I send a Unicode charactor, "あ "
> >
I have the sample problem too, can't post update with Chinese..
On Apr 13, 1:56 am, Guan wrote:
> On Apr 12, 8:08 am, Cmdr J0hn wrote:
>
> > Now, I send a Unicode charactor, "あ "
> > (not sure displayed on your screen properly, it's Japanese)
>
> > Signed on a string:
>
> > POST&http%3A%2F%2F..
On Apr 12, 8:08 am, Cmdr J0hn wrote:
> Now, I send a Unicode charactor, "あ "
> (not sure displayed on your screen properly, it's Japanese)
>
> Signed on a string:
>
> POST&http%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582
>
> And a body is:
>
> status=%E3%81%82
> Any suggestion anyone?
I hav
2009/4/12 Cmdr J0hn :
> 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
character, so you
On Sun, Apr 12, 2009 at 11:35 PM, Julio Biason wrote:
> (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=あ
http://www.danshort.com/HTMLentities/index.php?w=hir
> > (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=あ
>
> http://www.danshort.com/HTMLentities/index.php?w=hirag
NO! The original poster is correc
14 matches
Mail list logo
