Thanks, I will try that!
On Sat, Sep 26, 2009 at 8:11 AM, JDG ghil...@gmail.com wrote:
That's true -- %5BB6, for example, is NOT a UTF-8 encoded codepoint for a
character. It's Unicode (or UTF-16).
On Fri, Sep 25, 2009 at 20:54, Mageuzi mage...@gmail.com wrote:
Hello,
I had this same
That's true -- %5BB6, for example, is NOT a UTF-8 encoded codepoint for a
character. It's Unicode (or UTF-16).
On Fri, Sep 25, 2009 at 20:54, Mageuzi mage...@gmail.com wrote:
Hello,
I had this same problem. I had to convert all multi-byte characters
into their individual bytes.
So, for
Yes, it is UTF-8 encoded.
The request body for の脚本家が贈る is
Hello,
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).
On Sep 25, 5:00 pm, Satheesh Natesan
Are you sure you are encoding your posts as UTF-8?
On Sep 24, 5:16 pm, Satheesh Natesan satheesh.nate...@gmail.com
wrote:
I am getting 401 Unauthorized exception when updating status with
non english characters using my app.
This exception is happening for any Japanese or Korean characters.
