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 mentioned using PHP, which PHP library are you using and what
version?
» Version is important here so I can check out the code.
2. The signature base string (see issue 433 [1] for examples) is a
great indicator. I don't know the PHP libraries but I'm guessing there
will be a signature method that takes a string like this. Add some log
statements and capture that value.
» Check out issue 433 [1] for examples of what they look like.
Thanks;
– Matt Sanford / @mzsanford
Twitter API Developer
[1] - http://code.google.com/p/twitter-api/issues/detail?id=433
On Apr 24, 2009, at 02:49 AM, alon wrote:
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 me dig into Net::OAuth a
little
more and see what I find.
Quick update: yes, the issue in Net::OAuth was actually identical
to the
issue in the oauth gem reported in the original bug report [1].
I've changed
the regexp used with uri_decode in the Perl Net::OAuth module, and
now
Unicode status updates appear to work fine.
[1]http://code.google.com/p/twitter-api/issues/detail?id=433
