We want your ideas, suggestions, and comments about
CoffeeCup HTML Editor or
CoffeeCup Free HTML Editor. So tell us: How can we make the software even better? Remember, our products are here for you guys, so we want to make them the very best we can
~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~
Scott A. Swedorski - VP of Product Development
CoffeeCup Software Inc.
Phone: 678.495.3480
"Want to update your website from anywhere? Check out our new free service, S-Drive Streams. Visit http://www.coffeecup.com/sdrive for more information."
Probably been suggested before, but collapsible DIV sections.
Volunteering to help 
http://www.tbaygeek.org
or even better setting a collapse point yourself.
Volunteering to help
http://www.tbaygeek.org
When clicking on a start tag, let is highlight the corresponding end tag. Or even if you are working somewhere within say <table></table> those tags should be highlighted.
Ha en riktig god dag!
Inger, Norway
http://www.eikweb.com
http://www.horgenhonning.net/
http://www.norwayroots.com
http://www.johnsflats.com
From trying the preview version...
1. The UTF-8 encoding should be removed from the list of choices because it's still not supported. Or, even better, add unicode support.
2. It still doesn't support Vista correctly and allow the user to run from a user account rather than having to run as administrator.
Cary, I've not seen a problem running HTML Editor from Vista User account... It's all I tend to use for school. I did have the problem with VSD on Vista, but haven't checked recent release.
As far as UTF-8 encoding, why can't HTML Editor support it? Can we talk ya into enabling it to be supported?
And add a vote for unicode support too.
Who needs sleep?
From the W3C website:
Last word... for HTML authors
If you create content on the Web and never have to read and parse content on the web, and if you have read that far, you are probably considering yourself very lucky right now. But you can make a difference by making sure the content you put on the web is using consistent character encodings, and declare them properly. Your job is actually much easier than the tricky winding road to determining a document's encoding. In the proverbial three steps:
1. Use utf-8. Unless you have very specific needs such as very rare character variants in asian languages, this should be your charset of choice. Most modern text, web or code editors are likely to support UTF-8, some actually only support this encoding. If possible, choose an editor or set up that will not output a BOM in UTF-8 files, as this is known to cause some ugly display issues with some agents, and can even crash php includes.
2. If you have access to the configuration of your web server, make sure that it serves html as utf-8
3. That's all.
at the bottom of the page, just before the comments that take issue with the entry.
Bill R.
First Baptist Church
Brighter Day Charities
Roberson Family
Cary wrote:
From trying the preview version...
1. The UTF-8 encoding should be removed from the list of choices because it's still not supported. Or, even better, add unicode support.
2. It still doesn't support Vista correctly and allow the user to run from a user account rather than having to run as administrator.
Using the latest version posted here, I have no problems at all running the editor under a limited user account under Vista. Do you receive any sort of error message?
~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~
Scott A. Swedorski - VP of Product Development
CoffeeCup Software Inc.
Phone: 678.495.3480
"Want to update your website from anywhere? Check out our new free service, S-Drive Streams. Visit http://www.coffeecup.com/sdrive for more information."
Scott Swedorski wrote:Cary wrote:
From trying the preview version...
1. The UTF-8 encoding should be removed from the list of choices because it's still not supported. Or, even better, add unicode support.
2. It still doesn't support Vista correctly and allow the user to run from a user account rather than having to run as administrator.
Using the latest version posted here, I have no problems at all running the editor under a limited user account under Vista. Do you receive any sort of error message?
But what about the UTF-8 encoding? Is this something that will be addressed?
Who needs sleep?
Scott Swedorski wrote:
Using the latest version posted here, I have no problems at all running the editor under a limited user account under Vista. Do you receive any sort of error message?
Did you have to disable any features of Vista? The HTML Editor is still asking for my adminstrator password before running, unlike any other program I have. And when it is running, it's pointing at the administrator folders rather than my limited user account folders. I haven't changed anything. This is the same way the 2008 version worked and the same way VSD is working.
