Hi - when I publish a page that contains the more unusual punctuation marks like £ EE replaces them with with characters like: “
Is there a cure for this?
Cheers, Liam
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
June 26, 2007 12:15pm
Subscribe [3]#1 / Jun 26, 2007 12:15pm
Hi - when I publish a page that contains the more unusual punctuation marks like £ EE replaces them with with characters like: “
Is there a cure for this?
Cheers, Liam
#2 / Jun 26, 2007 12:26pm
What version/build are you running? And what’s your setting in ‘Admin- System Prefs- General Config’ ‘Default Character Set’? Are the characters goofed when you go to edit the entry in the control panel? Or are they just ‘off’ on the front end?
#3 / Jun 26, 2007 12:34pm
Running 1.6.
Default Char-set is utf-8
Only visible client side. OK when I view the entry via the edit panel. Hyphen, period, emdash, comma, colon are all OK..? - £ sign and a fair few others are showing foreign characters - any ideas?
#4 / Jun 26, 2007 12:36pm
seem to have solved it.
In: CP Home › Admin › Weblog Administration › Global Weblog Preferences
set: Automatically Convert High ASCII Text to Entities to yes - edited the entries (opened, changed nothing and updated) and the problem has gone 😊
#5 / Jun 26, 2007 1:04pm
Are you, by any chance, displaying your pages as ISO-8859-1? I mean, you are not likely to notice now, because all the high ascii characters will be converted now, but it would still break on umlauts and such.
#6 / Jun 26, 2007 1:18pm
Thanks, yeah - <meta http-equiv=“Content-Type” content=“text/html; charset=iso-8859-1” /> is in the head of all my pages called through a static-head include
It’s an old habit, Dreamweaver default. Should I scrap this?
#7 / Jun 26, 2007 1:24pm
If you are using utf-8 as your character set for EE’s control panel, I’d use it on the front-end as well, and recommend not auto-converting characters to entities.
#8 / Jun 26, 2007 1:29pm
What Derek says. Actually, the recommended way is to simply use
<meta http-equiv="Content-Type" content="text/html; charset={charset}" />#9 / Jun 26, 2007 3:15pm
Thanks. Just what the doctor ordered.