joomlafreak wrote on 6/3/2007 8:20 PM:
I don't know if it should be utf-8 or something anywhere in this. I
read on this thread or some other thread that the javascript will deal
with this encoding in utf-8.
Where you see the following in the response header:
Content-Type: text/html
It should be this in order for the browser to correctly use the charset being
sent:
Content-Type: text/html; charset=ISO-8859-1
I set up a little test, curious to see how the browsers would handle various
charsets on one page:
<http://www.corry.biz/charset/>
What you're looking at is four .load()s, each one specifying (or not) the
charset of the text. The text is the same for all four, but in their
respective charsets. I also have the em-dash in both UTF-8 and Windows-1252 in
all four as well.
Testing it with FF2 and IE7, I see that not specifying a charset in the response
header defaults to UTF-8. Specifying it as the correct charset causes it to work
properly. Specifying ISO-8859-1 but including the extended chars from Windows-1252
(smart quotes, em-dash, etc) causes FF2 to render the text as Windows-1252 even
though ISO-8859-1 was specified. However, IE7 is less forgiving and (correctly)
renders the em-dash as an unknown character (em-dash doesn't exist in ISO-8859-1!).
So if you're serving ISO-8859-1, it's probably better to serve it using
Windows-1252 as the charset so that both FF2 and IE7 will render the characters the
same when those sneaky smart quotes slip in (ala copy&paste from Word).
- Bil
