Code Collapse

Would love to have a code collapse feature that would collapse either a random selection, or selected start/end tags

As per my knowledge, that's a Great editor! To make it even better, consider adding live preview with real-time editing, better Git integration, and support for modern frameworks like React or Vue. A dark mode and improved code autocomplete would also be awesome!

Hey, a built-in library of responsive design templates or snippets could also speed up workflow for beginners and pros alike. Finally, tighter integration with version control systems like Git would help teams collaborate more smoothly.

Hi, guys!

Recently, I have come to appreciate the Coffee Cup HTML Editor application.
This application has gained significant popularity in the field of creating websites of various profiles.

There are many discussions on the internet regarding whether Coffee Cup HTML Editor supports UTF-8 encoding.
In my opinion, the question is misguided, and here is why:

UTF-8 is currently the standard for Internet files and editors for Linux and Android, but our editor was created earlier,
so I think it was based on Windows.

Developers work with computers in the broad sense of the term, and depending on the device, they
need to see the results of their work on the screen, which is what the editor provides.

Depending on what kind of computer it is, the HTML page developer must see it on a specific code page.
This could be WIN 1250, 1251, 1252, ..., ISO-8859-1, ... CP-866, ...
The result is saved in a file; UTF-8 encoding is now widespread.

Unfortunately, in the case of the Russian language, Coffee Cup HTML Editor displays UTF-8 codes on the screen in characters from code page 1252, when it should be 1251.
As a result, it is simply impossible to work with the Russian language.

If you change the system locale to Russian, the characters on the screen remain in 1252, but when you save, the result is in UTF-8 encoding
and the page looks normal in the browser, but if you load it into the editor, you will either see a 1252 page or ‘????’.

Therefore, the HTML editor must work in code page 1251 for Russian, or the UTF-8 character of the file must be
converted to the glyph of page 1251.

The editor must provide the developer with the same information on the screen as for the user + HTML codes.

Currently, changing the system locale leads to two changes. The date of page creation during automatic creation and all typed
text in the second language are saved in UTF-8 encoding and can be used as needed on a web server or in another browser, but if you open it
in our editor, everything is again in code page 1252, or in ‘?????’.

It is clear that making corrections to such text is extremely inconvenient.

The disadvantage of setting the system locale to “Russian” is that when developing HTML pages for different countries, it will be necessary to constantly
change the system locale, so it is more convenient to leave this option up to the developer.

We request that the Coffee Cup HTML Editor development team make corrections so that the editor is convenient for this part of the world, in third world countries
where other incomprehensible symbols are used... Success in this area will increase demand for your product.

Sincerely,
Rake48.