Hiya Normandie,
I suggest opening another support ticket or reopening the previous one you had to rehash this issue with the CC devs and have them get to the bottom of this issue. It does look like others are experiencing this problem too so I don't think there are "answers" here on the user to user forums at this point.
I realize you already did a ticket with them, but if it was a year ago now is the perfect time to reopen it and let them know the issue is still there and they can let you know if it's got a fix coming or not. We have a new version coming very soon, but I don't know if that issue has been fixed or not so please ask them to look into it so we all know if it's being addressed or not. Come back and let us all know please if you would.
Good luck on it and hopefully they have it in the todo list if it's not already addressed.
I suggest opening another support ticket or reopening the previous one you had to rehash this issue with the CC devs and have them get to the bottom of this issue. It does look like others are experiencing this problem too so I don't think there are "answers" here on the user to user forums at this point.
I realize you already did a ticket with them, but if it was a year ago now is the perfect time to reopen it and let them know the issue is still there and they can let you know if it's got a fix coming or not. We have a new version coming very soon, but I don't know if that issue has been fixed or not so please ask them to look into it so we all know if it's being addressed or not. Come back and let us all know please if you would.
Good luck on it and hopefully they have it in the todo list if it's not already addressed.
Hi Jo,
I have already re-open the ticket... haven't got any solid answer. In my understanding they haven't even tried to fix it - at least that's the impression I got. Anyway, just wanted to "open" this issue to wider audience in case others have similar issues. Maybe this also speedens up things a little bit in R&D wise? Don't expect to find a solution via forum.
I have already re-open the ticket... haven't got any solid answer. In my understanding they haven't even tried to fix it - at least that's the impression I got. Anyway, just wanted to "open" this issue to wider audience in case others have similar issues. Maybe this also speedens up things a little bit in R&D wise? Don't expect to find a solution via forum.
normandie wrote:
Ron: My computer does support and my browser is set to correct encodings. The point is: ..."it should support..." but it doesn't and it also "corrupts" the files by "forcing" them back to utf-8.
Ron: My computer does support and my browser is set to correct encodings. The point is: ..."it should support..." but it doesn't and it also "corrupts" the files by "forcing" them back to utf-8.
Sometimes it may be related to the language pack installed. If you see squares or question marks instead of the symbol you need to make sure you have the language pack installed necessary to show the symbols.
Ron
Just to make this clear... This does not happen with any other sw but cc's html editor.
I must be dense as a rock, because I use UTF-8, and the editor is set for ANSI character set, yet I have no problems viewing the characters in IE 9 Preview (Ctrl F12), therefore don't really understand your problem with the CC editor.
There are a few other character sets the editor can be set at from the Tools>Preferences>Customization tab>HTML/PHP Modify Highlighting button. I use a Unicode font also for the editor.
Be nice to be able to copy/paste one of your pages in your language into my editor and see if it gives a problem using my settings.
There are a few other character sets the editor can be set at from the Tools>Preferences>Customization tab>HTML/PHP Modify Highlighting button. I use a Unicode font also for the editor.
Be nice to be able to copy/paste one of your pages in your language into my editor and see if it gives a problem using my settings.
Ron
Ron it is a pleasant surprise to see logic at work. If the problem is not demonstrated how can it be fixed.
Which just goes to show if everyone used English there would be no problems. I bet that opens a can of worms.
I have a Russian mate who complains he has problems putting those do dar's on top of letters.
Thanks for the heads up mate, I have learnt something.
I am puzzled ä ö å chars never even thought you could type them and my default Chrome browser can view them, therefore methinks maybe it is a matter of getting a default browser working as normandie's apparently doesn't. Don't you just hate it when it does that. Something does not gel.
I would follow Jo's suggestion first why? if those characters can be typed in and they can be viewed here they can be viewed in the default viewer. Thinking, Oh! it hurts. Remove and reinstall your favourite browser it should establish itself as the default browser. The Editor does not choose it. It is same as when you call a page with a ShellExecute command you get the page open in you guessed it. Browsers have a big fight when you install them and sometimes you get a choice. I do not think IE does however. Shame on it.
Which just goes to show if everyone used English there would be no problems. I bet that opens a can of worms.

I have a Russian mate who complains he has problems putting those do dar's on top of letters.
Thanks for the heads up mate, I have learnt something.
I am puzzled ä ö å chars never even thought you could type them and my default Chrome browser can view them, therefore methinks maybe it is a matter of getting a default browser working as normandie's apparently doesn't. Don't you just hate it when it does that. Something does not gel.
I would follow Jo's suggestion first why? if those characters can be typed in and they can be viewed here they can be viewed in the default viewer. Thinking, Oh! it hurts. Remove and reinstall your favourite browser it should establish itself as the default browser. The Editor does not choose it. It is same as when you call a page with a ShellExecute command you get the page open in you guessed it. Browsers have a big fight when you install them and sometimes you get a choice. I do not think IE does however. Shame on it.
The Guy from OZ
Curiosity has the cat. Off topic I just looked at the Editor's Document Properties and see a choice of two Cyrillic types and a whole heap of others. Never having to know any more than two languages I have never had a problem English and Strine(Australian) if you are interested. I do syphathise. But how do you type those characters in. Does it require a special font, methinks it does.
The Guy from OZ
Prism wrote:
Curiosity has the cat. Off topic I just looked at the Editor's Document Properties and see a choice of two Cyrillic types and a whole heap of others. Never having to know any more than two languages I have never had a problem English and Strine(Australian) if you are interested. I do syphathise. But how do you type those characters in. Does it require a special font, methinks it does.
Curiosity has the cat. Off topic I just looked at the Editor's Document Properties and see a choice of two Cyrillic types and a whole heap of others. Never having to know any more than two languages I have never had a problem English and Strine(Australian) if you are interested. I do syphathise. But how do you type those characters in. Does it require a special font, methinks it does.

The web page should have the character set tag along with the language used and direction document read. Example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" http://www.w3.org/TR/xhtml1/DTD/xhtml1- … ">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
CC's Editor gives you a choice to display in split screen view using IE 8 or IE 9. I have no problems seeing these characters in split screen view using either. The same for all my other browsers I have installed.
Ron
Thanks for the explanation Ron now filed away for reference if needed.
The Guy from OZ
I have the same Problem and fully agree with normandie!
The fact that CC html editor forces saving in UTF-8 is "sometimes" a big problem. It is NOT a problem when creating plain HTML pages to be published on a webserver and browsed in a std. internet browser. BUT IT IS A BIG PROBLEM IF THE HTML document is to be published as an e-newsletter. Here the document may have to be either unicode or ASCI encoded in order to show scandinavian characters correctly in the html e-mail.
This is not a question of meta-tag encoding, but it is a question of document encoding. The actual document encoding can easily be viewed. Just open the html. document in notepad and select "save as". Then you will se the doc. encoding (ref. attached file).
I fully agree it is a serious flaw that the CC html editor don't offer the user the same encoding option as the very simple notepad appl. does. Inexperienced html delvelopers will easily get in troubles due to this missing feature. Anyway you can "just" convert the document encoding by opening the CC created html-doc. in notepad and "save as" in another encoding format !!!
The fact that CC html editor forces saving in UTF-8 is "sometimes" a big problem. It is NOT a problem when creating plain HTML pages to be published on a webserver and browsed in a std. internet browser. BUT IT IS A BIG PROBLEM IF THE HTML document is to be published as an e-newsletter. Here the document may have to be either unicode or ASCI encoded in order to show scandinavian characters correctly in the html e-mail.
This is not a question of meta-tag encoding, but it is a question of document encoding. The actual document encoding can easily be viewed. Just open the html. document in notepad and select "save as". Then you will se the doc. encoding (ref. attached file).
I fully agree it is a serious flaw that the CC html editor don't offer the user the same encoding option as the very simple notepad appl. does. Inexperienced html delvelopers will easily get in troubles due to this missing feature. Anyway you can "just" convert the document encoding by opening the CC created html-doc. in notepad and "save as" in another encoding format !!!
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.