Charset Encodings Doesn't Work - Page...

User 41910 Photo


Registered User
17 posts

Ok. Did some testing briefly... Few pointers:

- Why IE is the only browser allowed to be use in internal previews?
-Local preview doesn't work at all - can't do preview with any browser (Made a simple .html file and tried to preview it. Didn't make a project of it...)

Then the main thing...

I just can't believe that you guys haven't fix that charset encoding problem I reported to you a year ago! :mad: How hard can it be?

If I open a new empty document with charset encoding I want and put a simple test line with some ä ö å chars and view it via browser, it STILL doesn't show the chars correctly. It also still corrupts the other files made for e.g. gedit and replaces its charset encodings to UTF-8!

I'd suggest that you'd took a good look on REMOVED SOFTWARE NAMEfor windows REMOVED SOFTWARE LINK and study how they have implemented some language/charset specific features and functionalities.

The main difference is that it _really_ supports different languages and charset encodings.

Feature I'm especially looking for is that one can choose the charset encoding when saving the file(s). This is a BIG con for CC's editor! Due this simple reason I haven't been able to use CC's editor for a year and you guys have done absolutely nothing to fix this!!

This is a real shame since I'd like to use it but it's just not worth the bother... I don't have the time or will to open every single file I've created or modified with CC's editor and re-save it with gedit to make it work. It's just stupid. So I'll just keep using REMOVED SOFTWARE NAME until you fix this. Shame... I've been using CC's editor since 1997...

I truely hope that CC would stand up and say: "Yes, we will fix it because we value ALL of our clients". Will you...? :|
User 1948478 Photo


Senior Advisor
1,850 posts

normandie wrote:
...If I open a new empty document with charset encoding I want and put a simple test line with some ä ö å chars and view it via browser, it STILL doesn't show the chars correctly. It also still corrupts the other files made for e.g. gedit and replaces its charset encodings to UTF-8!...

Not sure what you mean here. See attached screenshot for my simple test of some Swedish and some Portuguese characters. They seem to look OK to me in the split-screen preview and the same when I preview in IE9, Chrome, Firefox and Opera.

If you are mixing bits and pieces of "gedit" and the CC Editor in the same file, it may not be immediately clear "who is corrupting whom"...

As for previewing options in different browsers, you can specify up to ten different browsers of your choice here: Tools > Preferences > Browser Testing.

Maybe if you could be a bit more specific - more detailed, with screenshots, etc. - about some of the problems you seem to be having, it would be easier for the rest of us to understand. I'm saying this because the various preview options, as well as the representation of non-English characters, work just fine for me here.

BTW, what version of the Editor are you using?
User 1948478 Photo


Senior Advisor
1,850 posts

Seems that i left out the screenshot. Here it is...
Attachments:
User 41910 Photo


Registered User
17 posts

Not mixing anything with gedit. This is very simple. When you create a new .html file with scandinavian chars, save it and open up your browser, opening the .html file and the chars looks uncorrectly with "fill chars". It also doesn't matter what is the encoding - same issue always. If I make an identical file with gedit and save it, open it up with browser, chars looks correct. There's no doubts about where the problem is. I have used both of these sw's for years and I have a pretty good understanding about their functionalities.

This issue has been on and off in support room and I put it in here also merely to others to notice - in case they have similar issues.

Yes, I know how I can specify different browsers - my point was that it doesn't work. Preview doesn't open at all.

Current version is the latest available one.
User 38401 Photo


Senior Advisor
10,951 posts

Have you tried reinstalling? Sounds like you have some actual "issues" there other than just the possible bug with the charset. Your previews should all work fine and if they aren't then your install has some issues. Try redownloading it and reinstalling it and see if that helps at all.

If it doesn't, then I think you need to bring this to the attention of CC rather than posting it here on the "user to user" forums. Although we do get Scott and other CC staff in occasionally, this is definitely not the place to direct something to them at all, a support topic is the way to get the message to them.
User 1950693 Photo


Registered User
29 posts

Hi Normandie,
I am having the same basic set of issues that you are as of recently. Namely charset encoding and inability to preview my code in any browser within the program. For convenience I've been having to take it to Word to preview and that is not adequate. I'm starting to lose my enthusiasm for Coffeecup software and support.
Very disappointed,
Kris
"Become the change you wish to see in the world." -Mahatma Ghandi
Kris
User 601710 Photo


Registered User
114 posts

Some symbols may not show because your computer does not contain the font set and/or your browser is not set to the correct Character Encoding. Changing browser's encoding is usually done from its View Menu. Unicode browser display test: http://home.tiscali.nl/t876506/entitiesTips.html

I've had to use a Unicode font in IE and Firefox, but I still have problems seeing characters while coding the HTML page itself. If it doesn't understand the character entity, I get a question mark in its place. The editor uses ANSI (Windows-1252 on Western/U.S. systems. It can represent other Windows code pages on other systems. Real ANSI). The editor should be able to support more than the listed encodings, but there is none I saw for UTF-8 although you can set your doctype to it.
Ron
User 1948478 Photo


Senior Advisor
1,850 posts

normandie wrote:
....This is very simple. When you create a new .html file with scandinavian chars, save it and open up your browser, opening the .html file and the chars looks uncorrectly with "fill chars". It also doesn't matter what is the encoding - same issue always. If I make an identical file with gedit and save it, open it up with browser, chars looks correct. There's no doubts about where the problem is. I have used both of these sw's for years and I have a pretty good understanding about their functionalities....

However hard I try, I still cannot replicate your problem here.
I use a small html test file containing one line with some Swedish characters and one line with some Portuguese characters. You can see my test file in its entirety on the attached screenshot, which also includes three simultaneous previews:
1. Split-screen in editor
2. Local preview in IE9
3. Local preview in Firefox

The second screenshot shows the saved html file viewed in Chrome (based on your description: "When you create a new .html file with scandinavian chars, save it and open up your browser,..")
I'm using the HTML Editor version 12.5 Build 418.
All the information about my simple test case is contained in the screenshots.
Please let me know in what way, if any, my test case differs from your cases, - or if i have misunderstood your issue in some manner.
Attachments:
User 41910 Photo


Registered User
17 posts

I have made a support ticket for this over a year ago and nothing has been done. While browsing the forums, it's clear that this issue exists to other users also. I know the meta tags, charset encodind options etc etc. That's not the case. Html editor simply doesn't do the encoding correctly. Like said before, while using gedit text editor - where you can choose the correct encodings before saving the file - everything works just fine - with the same files!

Scott, nice touch to put an egg in my own topic! :lol: Sadly, it was taken already when I noticed it for the first time...
User 41910 Photo


Registered User
17 posts

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.

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.