As near as I can tell, this is happening because the source files are encoded in Western (ISO-8859-1) and the server is mistakenly claiming to your browser that they're Unicode (UTF-8). Until I can get with the server admin to see if this can be sorted out on the backend, here's a workaround: If your browser has a "force this encoding" function, use it to force the browser to view the files as ISO-8859-1 anyway, and the strangeness should go away.

(In Firefox, for instance, this is accomplished with View -> Character Encoding -> Western (ISO-8859-1). Just setting the default encoding to this won't help, I think because the server is making some kind of incorrect encoding declaration. When I pull my View -> Character Encoding tab down, it's always preset to Unicode (UTF-8) regardless.)

Hopefully this is a simple server config issue that can be cleared up in short order. I'll keep you posted.

--G.
-><-
Benjamin D. Hutchins, Co-Founder, Editor-in-Chief, & Forum Admin
Eyrie Productions, Unlimited http://www.eyrie-productions.com/
Ceterum censeo Carthaginem esse delendam.

--G.
-><-
Benjamin D. Hutchins, Co-Founder, Editor-in-Chief, & Forum Admin
Eyrie Productions, Unlimited http://www.eyrie-productions.com/
Ceterum censeo Carthaginem esse delendam.

t.
whose firefox is set to Western.

Trigger Argee
trigger_argee@hotmail.com
Manon, Maccadon, Orado, etc.
Denton, never leave home without it.

"I hate to advocate drugs, alcohol, violence, or insanity to anyone, but they've always worked for me." - HST