Have one issue. When my client www.chickenlikebirds.com is editing their content they are getting these weird glitches that they have to go back repeatedly and edit out. Unfortunately, there are none there now, as I just went in a fixed them, but it will randomly put in an upside down question mark along with some "=" signs etc. Anyone know why this might be happening?

I asked them if they were copying and pasting from another document and they said no. And then I went ahead and tested by typing in an edit and sure enough, it happened to me to. But it seams to be random.

Hey there. Thanks for responding. It is happening right in the content. They go and do an edit and then save and it looks fine, but when they refresh the page these upside down question marks, etc appear. They are using english.

Is this happening on all, one or just some pages? Can you create new page (not linked from the index or any other pages), and reproduce that? Of course, leave the link to that page here so I can see it.

If you take a look at source from your browser - where do they appear? Inside of contents or outside? An if inside, can you see them with backend WYSIWYG editor? Those characters look familiar to me - I'm almost positively sure this is previously mentioned BOM signature, but it usually appears at the beginning of some files if the used text editor was not too smart to omit those characters.

Hmmm... now this is stupid because I think you already know but just to make sure - you are looking at the source from the browser? It must show edited content (if content is saved and page is refreshed) because content is loaded into HTML before it's sent to the browser.

Sorry. You're right on that. I didn't realize I was still logged in. So, yes, when I very the source code, I see the updates. But that's not the problem. The crazy characters are only seen when you are logged in.

And after a loooong private message discussion we came to conclusion that for some reason the web server didn't send any character encoding headers and for some reason Safari and Chrome (tested) ignored the meta tags with specified (utf-8) encoding.