HTML Editor 2010SE (Second Edition)...

User 103173 Photo


VP of Software Development
0 posts

Jens Otto wrote:
In my opinion the HTML Editor 2010SE (Second Edition) is a downgrading version. The predefined themes are not so nice then in the previous version and the user must move all existing themes to the user directory (documents and settings).

This version offers HTML5 / CSS3 support, but HTML5 and CSS 3 are still a work in progress. Supporting these new web languages is trendy, but not obligatory required. But implementing full utf-8-encoding (encoding/saving files with options like utf-8 with or without bom) is overdue. All other professional editors and dozens of free editors offer a function like this. I don't understand: Why CoffeeCup-Team is so ignorant?

WOW, I think this is the first time we have ever been ridiculed or called ignorant for providing an update and adding new features. Jen, would you just prefer we do not update our software then? HTML5 and CSS3 is still a work in progress, but you don't have to wait to start learning about it now. The Web moves at light speed. Sticking to the principles of 1998 will leave you standing still.

--Ever so confused.....
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.
User 6573 Photo


Ambassador
2,649 posts

Jens Otto wrote:

This version offers HTML5 / CSS3 support, but HTML5 and CSS 3 are still a work in progress. Supporting these new web languages is trendy, but not obligatory required. But implementing full utf-8-encoding (encoding/saving files with options like utf-8 with or without bom) is overdue. All other professional editors and dozens of free editors offer a function like this. I don't understand: Why CoffeeCup-Team is so ignorant?


Hey Jens, You might want to set your settings

Tools > preferences > (under General Tag) Initial DOCTYPE, you can select a ton of different preferences and you don't have to use the HTML5, choose the one you want.

Plus if you go to to the Code tab on your side bar, well it gives you several html options. You don't have to use HTML5

It is a hard to please everyone. They try to meet the general needs of what their customers want and still not leave those who don't want to change behind. That is not ignorance, that is called cultivating.

I see by the number of your post that you are probably new to this forum, but please be kind and don't call people ignorant. Many of us have been here for years and it is a great place to get help and new ideas.

It has been my experience, that the Coffee Cup Team actually listen to their customers and carefully consider the needs and wants. They don't charge a huge price tag and have been successful, because they consider customer wants and find ways to make their upgrades effective. In my opinion, and this is just my opinion, they do a great job at it. Why, because many of the things that I have suggested, they have implemented. Now, I have a list of other wants that have not made their drawing board, yet. But I still post a reminder once in awhile. They probably roll their eyes and say "Another Crazy Kim's ideas". But I know they are listening. They show their customers their appreciation by keeping the prices down. I like that.

I hope you look at the other options and set it to what you want. I don't think you will be disappointed, if you give it a try. I am not using HTML5 at this time. But I am glad it is there, if I ever change my mind.

Have a great wonderful day and hope to see more postings from you.

Kim :)

User 463060 Photo


Registered User
4 posts

Oh, I kicked off a discussion.

At first: I like the CoffeeCup Software and the style of the company (nice newsletter information, well-structured and open forum, style of software). I explicitly respect the work of the developer team. Perhaps my posting was inartfully expressed. Sorry!

But nevertheless I don't understand why "ignoring" the utf-encoding, a standard feature.
In the past I asked the support team, suggested that point directly there and by posting in the forum.
I read other postings in that direction too.

HTML5/CSS3 is ok, but no utf-encoding, that's "confusing".

I like the HTML Editor and want to use it much more or perhaps as favorite.
That was the reason for my posting - with true content (my opinion), but unlucky expression.
Once again: Sorry!
User 103173 Photo


VP of Software Development
0 posts

Jens

I am not sure your comment though makes sense. One of the features of this new version was adding support for UTF-8. This is actually a good thing and not something to complain about right?.

Now if you would like, I can make you a special build without that feature.... ;)
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.
User 122279 Photo


Senior Advisor
14,461 posts

Scott Swedorski wrote:

Let me know if you can reproduce a good page this way and then we can work from there to see if I can get it to fail using the steps you are taking.

Download video (9.2MB).

Update: If I use iso-8859-1, then I do see those strange characters you are describing. Is there any reason to use that character set over UTF-8? Once I switch back from iso-8859-1 to UTF-8, everything worked again.

I did find this article which may help explain things: http://www.webmasterworld.com/forum23/4227.htm


I have viewed the video and read the postings in the link you provided.

I get a bit confused as to whether it is the new Editor, the code cleaner in it, IE that can't understand charset declarations coming before the doctype or whatever else it is that messes up the text in Norwegian. It looks like I can't use xhtml for any site...

Here is what I'm doing:

1. Create a page with these settings:

<?xml version="1.0" encoding="utf-8"?>
<!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">


2. Paste in a block of Norwegian text.
3. before saving, preview in the Editor: all is ok
4. save, preview in Editor again: The text looks like my index2.html that I have mentioned earlier in this thread, with yen, Â, broken vertical bars - you name it.
5. checking the text in code view: nothing wrong there.
6. preview in FF: All is good. Charset encryption is utf-8
7. preview in IE: same errors as in the browser preview. Charset encr. still at Western Europe ISO
8. Manually changing the encryption to utf-8: text is ok.
9. applying the code cleaner to change to Latin-1, doctype at auto
10. checking the code: æøå have become &aelig;. &oslash; and &aring; but no change in the doctype or charset decl.!
11. before saving, preview in the Editor: all is ok
12. after saving: re-read # 4, 6, 7 and 8 above
13. applying the code cleaner again to change it back to utf-8 (just for the record; I wouldn't do that in 'real life'...): No change in the head section - again, but instead of the weird characters I had before, I now have this instead: '�'.
14. The same characters show up in built-in preview before saving.
15. preview in IE/utf-8 produces a lot of squares, with Latin-1 the same as in #13 , in FF I have these rhombes with a question mark.
16. Then save and everything gets weirder still: � in built in preview, same as # 15 in the browsers.

I think this is enough testing for an xhtml file to say that I can't use that format. It used to be ok in the old version. Normally I would not use the code cleaner to go back and forth as I have done here, so the # 13 and onwards would not happen.

I'll have a go at html5 after a break...

Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 122279 Photo


Senior Advisor
14,461 posts

Jens Otto, where are you from? Norway or Denmark?
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 103173 Photo


VP of Software Development
0 posts

Here is something that *may* help Inger:

http://www.w3.org/International/tutoria … #Slide0250
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.
User 103173 Photo


VP of Software Development
0 posts

Inger

Our guru Jeff seems to have found the way to fix it and I have been able to confirm that it works every time this way. Can you give it a try and let me know.

Look for this line:

<meta http-equiv="content-type" content="utf-8">


Change it to this for HTML 4.01:


<meta http-equiv="content-type" content="text/html; charset=utf-8">


Change it to this for XHTML:


<meta http-equiv="content-type" content="text/html; charset=utf-8" />


Change it to this for HTML5:


<meta charset="utf-8">


I am looking into getting the Quick Start Guide updated appropriately.
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.
User 122279 Photo


Senior Advisor
14,461 posts

I'll try that...
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 122279 Photo


Senior Advisor
14,461 posts

We seem to be getting the thing with the Norwegian characters solved! I tried some German umlauts too, and they came out ok. I have previewed both saved and unsaved files, and nothing wrong happens.
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com



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.