* * * * *

                  UTF-8 is hard. Let's write device drivers!

Nice. I switch my Stupid Twitter Trick [1] to use UTF-8, and this is what I
get for my trouble:

> HTTP/1.1 401 Unauthorized
> Date: Mon, 03 Jan 2011 12:29:02 GMT
> Server: hi
> Status: 401 Unauthorized
> WWW-Authenticate: Basic realm="Twitter API"
> Content-Type: application/json; charset=utf-8
> Content-Length: 70
> Cache-Control: no-cache, max-age=300
> Expires: Mon, 03 Jan 2011 12:34:02 GMT
> Vary: Accept-Encoding
> Connection: close
>
> {"request":"\/1\/statuses\/update.json","error":"Incorrect signature"}
>

No UTF-8 characters, posts fine. Any UTF-8 characters, I get this. I think
the problem is that the character set isn't being sent along with the post
and I don't have a clue about how that's done. Nor do I think there's an
actual standard for this (I don't recall ever coming across one).

Sigh.

This UTF-8 stuff is hard. No, I mean hard [2]. I wish I was making that up.

[1] http://twitter.com/siwisdom
[2] http://www.unicode.org/reports/tr14/

Email author at [email protected]

You are viewing proxied material from gopher.conman.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.