I am not using HTML editor for few months now because I can not save my work as UTF-8 code. Could we expect this save-option soon?
Janez Toplisek
Saving as UTF-8 code - Post ID 161645
Janez Toplisek
Registered User
8 posts
Scott Swedorski
VP of Software Development
0 posts
The software automatically saves as UTF-8 now. That was one of the big features in the 2010SE version.
Learn the essentials with these quick tips for Responsive Site Designer, Responsive Email Designer, Foundation Framer, and the new Bootstrap Builder. You'll be making awesome, code-free responsive websites and newsletters like a boss.
Rolf Schriemer
Registered User
2 posts
Hi
hm ... I have CoffeeCup HTML Editor Version 14.1 build 741.
After saving the file and open it again in Notepad++ its telling me file format is UTF-8 w/o BOM.
And this without BOM makes firefox (38.0.5) to show special German charaters wrong.
I have to convert the file in to UTF-8 (with BOM) then it works.
How can I save this kind of UTF-8 format with CoffeeCup?
Thank youi and best regards
Rolf
hm ... I have CoffeeCup HTML Editor Version 14.1 build 741.
After saving the file and open it again in Notepad++ its telling me file format is UTF-8 w/o BOM.
And this without BOM makes firefox (38.0.5) to show special German charaters wrong.
I have to convert the file in to UTF-8 (with BOM) then it works.
How can I save this kind of UTF-8 format with CoffeeCup?
Thank youi and best regards
Rolf
Per
Senior Advisor
1,850 posts
Rolf,
I routinely use northern European umlaut characters as well as southern European accented characters and have never encountered the problem you are describing with the HTML Editor.
Did you specify the character set in a <meta> tag, e.g. like this, or similar:
Does the problem show up in local preview as well as in uploaded pages? Is this a problem only with Firefox or with other browsers also?
Did you validate the html file to make sure that there is no glitch in the markup that may prevent the character set from being properly recognized?
Briefly scanning a Google search, it seems that the BOM should not be needed, or is even "not recommended", for a file where utf-8 is explicitly specified.
I routinely use northern European umlaut characters as well as southern European accented characters and have never encountered the problem you are describing with the HTML Editor.
Did you specify the character set in a <meta> tag, e.g. like this, or similar:
<!DOCTYPE html>
<html lang="de">
<head>
<meta charset="utf-8">
.....
<html lang="de">
<head>
<meta charset="utf-8">
.....
Does the problem show up in local preview as well as in uploaded pages? Is this a problem only with Firefox or with other browsers also?
Did you validate the html file to make sure that there is no glitch in the markup that may prevent the character set from being properly recognized?
Briefly scanning a Google search, it seems that the BOM should not be needed, or is even "not recommended", for a file where utf-8 is explicitly specified.
Per
www.mingas.com
www.mingas.com
Rolf Schriemer
Registered User
2 posts
Hi Per,
Thank you for the answer.
No, I havened and it is not neccessary when the file is saved as utf-8 and not aas utf-8 w/o BOM
I have .php
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<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" />
----
So language is en but as I said saving as clease utf-8 will handle both correctly en and de.
My question is still: Is it possible to do save in format utf-8 and not utf-8 w/o BOM?
thank you and best regards
Rolf
Thank you for the answer.
No, I havened and it is not neccessary when the file is saved as utf-8 and not aas utf-8 w/o BOM
I have .php
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<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" />
----
So language is en but as I said saving as clease utf-8 will handle both correctly en and de.
My question is still: Is it possible to do save in format utf-8 and not utf-8 w/o BOM?
thank you and best regards
Rolf
rakenurp
Guest
5 posts
Coffee Cup HTML Editor is interesting.
However, the position of users of this product is not entirely clear.
It is clear that users who use only one language do not experience any difficulties, but those who use two or more languages want to type code in English and text in their native language, and bilingual users are in the same position.
CC HTML Editor uses a single-byte alphabet on its screen, but bilingual developers need to use a double-byte alphabet, namely UTF-8. In my case, CC HTML Editor always works with the Win-1252 page, regardless of what is in the page header:
<head>
<meta charset="UTF-8">
<title></title>
</head>
For example:
When entering Russian text into the CC HTML Editor screen using the keyboard, or copying text via the Windows Clipboard:
“После” (on English it means “after”, Russian cause it uses UTF-8, 10 bytes)
The following appears in the editor:
Ïîňëå
On code page 1252, their decimal codes are:
207 238 235 229
hexadecimal values are:
CF EE 0148 EB E5
and in Russian, this word is “После” (After).
That is, the codes are correct, but the code page is wrong: 1252 instead of 65001.
Of course, you can replace CC HTML Editor with an external HTML editor, but simply correcting minor typos will cause pages to be transferred from one editor to another, corrected, transferred back, resulting in a huge drop in performance...
We need to solve this problem somehow and post the final solution...
Sincerely,
Rake48.
However, the position of users of this product is not entirely clear.
It is clear that users who use only one language do not experience any difficulties, but those who use two or more languages want to type code in English and text in their native language, and bilingual users are in the same position.
CC HTML Editor uses a single-byte alphabet on its screen, but bilingual developers need to use a double-byte alphabet, namely UTF-8. In my case, CC HTML Editor always works with the Win-1252 page, regardless of what is in the page header:
<head>
<meta charset="UTF-8">
<title></title>
</head>
For example:
When entering Russian text into the CC HTML Editor screen using the keyboard, or copying text via the Windows Clipboard:
“После” (on English it means “after”, Russian cause it uses UTF-8, 10 bytes)
The following appears in the editor:
Ïîňëå
On code page 1252, their decimal codes are:
207 238 235 229
hexadecimal values are:
CF EE 0148 EB E5
and in Russian, this word is “После” (After).
That is, the codes are correct, but the code page is wrong: 1252 instead of 65001.
Of course, you can replace CC HTML Editor with an external HTML editor, but simply correcting minor typos will cause pages to be transferred from one editor to another, corrected, transferred back, resulting in a huge drop in performance...
We need to solve this problem somehow and post the final solution...
Sincerely,
Rake48.
Cary
Ambassador
1,089 posts
Hopefully, if they do release a new version of the HTML Editor, they will finally include support for unicode just as they managed to do with RSD.
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.
