a µ problem
planet apache does not handle utf-8-encoded content correctly. maybe it isn’t planet apache’s fault. it is trying to set the encoding in a <meta http-equiv="Content-Type" ... > header, but camino, safari, ie5/mac, and ie5.5/win all ignore it. i’m not sure what the rules are with regard to the content type being specified with different charsets in the response headers and in a <meta> element.
i’m not surprised it doesn’t work, there’s still a lot of gaps in being able to use utf-8 pervasively. i’m actually generating curly quotes by typing them instead of using something fancy like textile. (and since i’m always having to search to find this: source code for textile 2.)
Comments
doing a little testing with safari, that isn’t the problem. it doesn’t matter whether it is UTF-8 or utf-8, but if the Content-Type header sets the charset to iso-8859-1, it doesn’t matter what the what the charset is set to in the <meta> element.
Add a comment
Sorry, comments on this post are closed.
Planet Apache is trying to set the charset to "UTF-8", which is wrong - it should be "utf-8" in lowercase (yeah, it's confusing as hell, b/c in the Unix locale it's UTF8 in uppercase, and without the hyphen on top of it).
BTW, on a related topic - I discovered that IE (on PC, I don't remember how IE/Mac behaved) will not pick up the charset, when it's sent from PHP with the header() command - only when it's inside the html via meta http-equiv="...