DailyDi, don't know if you're reading this...
I think I figured out what the problem is. The story pages (at least all the ones I looked at) contain "content-type" meta tags containing the correct "charset" info for those pages (Windows-1252). However, when the page is served, the server is sending a "content-type" HTTP header with incorrect information... it specifies the charset as "UTF-8" which causes the pages to display improperly. Apparently in browser-land, HTTP headers trump meta tags.
Yes I'm a geek!
Moi