On 22 June 2014 22:59, steve-ALUG@hst.me.uk wrote:
If it doesn't, post a link to a website that doesn't work and we may be able to see if it doesn't work for us and what to do about it.
Having worked on lots of websites over the years it is incredibly easy to cause this problem at the developer end and nothing you can do at the browser end will fix it.
The "source code" for a typical webpage may comprise dozens of text files (at the server end, this is mostly unrelated to the source you see in the browser when you "view source"). The file encoding of each of those text files can be different, meaning that when they are combined you can get weird results. Add to that the fact that much of the content itself will come from a database and can again be encoded differently...
And then there's what happens when you copy+paste from one source into another.
In theory, unusual entities should be encoded in the code in a non-ambiguous form, eg "£" for the pound sign, but often they're not, and even that has issues if not properly tracked.
That doesn't mean the issues you see aren't configuration issues at your end, but equally I wouldn't assume they are unless I have tested on multiple browsers on multiple operating systems and it's only the multiple browsers on my Linux box that have the problem.