I'd be very interested in seeing your solution.

I'm having this very problem in my OAuth implementation and I can't
seem to find a good solution.

On Nov 2, 7:15 am, Kalpesh <kalp.meh...@gmail.com> wrote:
> Done!
> It's now updating status successfully for ascii as well as non-ascii
> characters..
> the problem was my oAuth.. i downloaded the latest code and it's
> working flawlessly..
> thx for ur help!
>
> On Nov 2, 4:27 pm, Kalpesh <kalp.meh...@gmail.com> wrote:
>
> > I have tried two things to get my non-english characters status update
> > to work:
> > 1.) Using meta tag in the head as <meta http-equiv="Content-Type"
> > content="application/x-www-form-urlencoded; charset=UTF-8" />
> > 2.) Using utf8_encode for status and posting
>
> > None of the above works. I get "incorrect signature" trying to post
> > non-english characters. English characters works fine.
> > I am able to update non-english status with direct status posting from
> > cURL, problem is with oAuth..
> > Can anyone provide a working example code using oAuth for this?
>
> > On Oct 29, 12:35 am, Cameron Kaiser <spec...@floodgap.com> wrote:
>
> > > > What encoding function to use for postingnon-englishcharacters ??
> > > > i am using urlencode but it is not postingnon-englishcharacters to
> > > > twitter
>
> > > Are you properly encoding the characters as UTF-8? That should occur
> > > before you URL-encode your payload.
>
> > > --
> > > ------------------------------------ 
> > > personal:http://www.cameronkaiser.com/--
> > >   Cameron Kaiser * Floodgap Systems *www.floodgap.com*ckai...@floodgap.com
> > > -- The gift of death metal does not smile on the good looking. -- S.B. 
> > > #141 ---

Reply via email to