I found the problem.
Okay, I've figured out what's going on.
EN World emits the following HTTP header for its pages (at least in the
message boards):
Code:
Content-Type: text/html; charset=ISO-8859-1
However, the actual character set used is CP1252, a.k.a. "Code Page 1252",
also known as
Windows-1252.
This is not the same character set as ISO-8859-1.
The reason this works for most of the people most of the time is that like
practically every successful Western character encoding since 1968,
Windows-1252 is a superset of ASCII. That is, the first 128 codepoints of
Windows-1252 are identical to ASCII (which only has 128 codepoints, being a
7-bit standard).
It would be helpful to people's browsers if EN World would issue a correct
charset attribute in the HTTP Content-Type header. Is this possible?
If not, I can work around it by manually overriding the character set used to
render the page in my browser. Kinda tedious for me, but I recognize that
I may be a minority of one as EN World users go.
For a lot more about this issue, see the following:
http://www.cs.tut.fi/~jkorpela/www/windows-chars.html