Hi there, I too have problems with pound symbols coming out as £11.95 and see that when I change my own browsers character encoding to unicode rather than western the strange symbols disappear. Would anyone please tell me if I can output the pages so this happens automatically?
thank you in advance.
I’ve found that by switching every page to Western (windows latin 1) in the inspector/ page encoding selector it stops the strange symbols - just hope it’s alright for everything else to work ok, it does so far but I’ve only tested it on a pc running the latest explorer and vista and my own intel mac running leapord. sorry to all those very clever people out there going ‘doh’ now but to non coders it can be quite baffling when this happens!!
Thanks for the update, did leaving the encoding option on automatic not work? Freeway should choose the encoding required for it to work.
Joe
On 19 Jan 2010, at 10:01, Richard Knight wrote:
ok I’m replying to my own post!
I’ve found that by switching every page to Western (windows latin 1) in the inspector/ page encoding selector it stops the strange symbols - just hope it’s alright for everything else to work ok, it does so far but I’ve only tested it on a pc running the latest explorer and vista and my own intel mac running leapord. sorry to all those very clever people out there going ‘doh’ now but to non coders it can be quite baffling when this happens!!
Hi Joe, no it didn’t - I’m using mal’s e-commerce actions on the whole site - hence needing pound symbols if that is any clue to why it didn’t work on automatic.
I’ve had this problem in the past. Automatic encoding doesn’t work, I’ve always changed the character set to UTF-8 which is fine. However this problem has extended itself in that if I now change the encoding to UTF-8 in the Document Set up it ignores it and sticks with ISO-8859-1 meaning I have to change each file, not a disaster, but a pain! Does anyone have any ideas about making the encoding stick?
I’ve sorted the issue out. Despite changing the Document set up the UTF-8 encoding was being ignored, I have just noticed that all these settings are repeated in the Inspector when a page is selected, changing them there has sorted it.
Remember – changes made in the Document Setup only affect things you
create after you make that change. Any existing page would already
have its settings, and each page stands alone in this regard.
Walter
On Nov 18, 2010, at 1:09 PM, PixelAce wrote:
I’ve sorted the issue out. Despite changing the Document set up the
UTF-8 encoding was being ignored, I have just noticed that all these
settings are repeated in the Inspector when a page is selected,
changing them there has sorted it.