It's me again

At the expense of appearing an interfering busy-body (well, I am but please don't tell anyone); and because the site admins are obviously up to their eyeballs in work (just look at how long since the last stories were processed) I hope you don't mind that I investigated this a bit more.

Trolling for info on how this problem may occur, I find a typical description such as:
<quote>
Firefox say it regards the character encoding as being ISO-8859-1 1). That’s actually coming from an HTTP header - if you click on the “Headers” tab you see;
Content-Type: text/html;charset=ISO-8859-1

Meanwhile amongst the HTML meta tags (scroll down past the whitespace) though you find;
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
Now that’s not a train smash (yet) but it should raise the flag that something isn’t quite right. The meta tag will be ignored by browsers so content will be regarded as being encoded as ISO-8859-1, thanks to the HTTP header.
</quote>

Now this looks to be similar to the problem here - just that the "encoding switch" is upside-down (we view as utf-8 what its s'posed to be the other).

So it looks as if the fault lies not (necessarily) within the web pages themselves but the HTTP header - this is "invisible" even to standard sleuthing tools - it is provided when your PC first talks to the website, for example.

If the website is running an Apache server the http header encoding can be specified in a .htaccess file. Or if using PHP apparently there is a setting in the PHP ini which can override it. There's pro'lly loads more places - this is just a sample.

Once again I hope this isn't "treading on toes" and interfering - I'm only trying to be helpful.

All the best
VV