If you check the page in question, it did fix the weird characters, but not fully. I just turned them all into two question marks, one of them with a diamond around it.
You’re being bit by the Word style double quotes.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
September 18, 2009 12:23pm
Subscribe [3]#16 / Sep 25, 2009 4:55pm
If you check the page in question, it did fix the weird characters, but not fully. I just turned them all into two question marks, one of them with a diamond around it.
You’re being bit by the Word style double quotes.
#17 / Sep 25, 2009 5:22pm
If you check the page in question, it did fix the weird characters, but not fully. I just turned them all into two question marks, one of them with a diamond around it.
You’re being bit by the Word style double quotes.
That’s what I figured it was, but I also thought that by checking that “Automatically Convert High ASCII Text to Entities” would take care of that?
#18 / Sep 25, 2009 5:24pm
When you initially enter them, not so sure about existing entries. I just find and replace them in the db. 😊
#19 / Sep 25, 2009 5:28pm
When you initially enter them, not so sure about existing entries. I just find and replace them in the db. 😊
Yeah I guess that’s what is throwing me off. I’m wondering why they were not fixed when I entered them initially? That setting has been set to “yes” since the site went live over a year ago.
What is the SQL command that you use for finding and replacing them?
#20 / Sep 25, 2009 5:37pm
I just went into the original entry, found the character, and did a search and replace from inside EE.
#21 / Sep 25, 2009 6:06pm
The host finally was able to change the encoding on the server. They said that they changed it to be blank so that it would use whatever was specified in the templates but when I check the header info, it’s now showing UTF-8 instead of iso-8859-1. If they left the setting blank or turned it off, wouldn’t the header check display nothing?
I don’t think so, not if you use the
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />header in your code.
He said too that the setting he changed was in the PHP ini file on the server?
I am not too sure about server configuration, so I’ll just accept that at face value.
If you check the page in question, it did fix the weird characters, but not fully. I just turned them all into two question marks, one of them with a diamond around it.
Not all of them, I think, just those two. You had other issues there (probably pasted from Word?) Just edit the article again in the control panel, replace those two and you should be all set.
I’ve got the setting set to yes for “Automatically Convert High ASCII Text to Entities” but I don’t know if that even matters in this case.
Since you went utf-8 all the way I actually recommend to turn off auto-conversion.