How can I configure the editor to emit HTML 4.1?

I was hoping that there's a way to configure the editor so that it would produce valid HTML rather then having to fix the text after the fact.

This is a reply to the post in this thread:

http://www.fckeditor.net/forums/viewtopic.php?p=24558#p24558

mosipov wrote:There is not even one good reason to use HTML at all. XHTML is a clean, script definition. Better for humans and way better for machine processing.
If FCKeditor would produce HTML, I would never use it.

I appreciate your passion for XHTML. I was hoping for a more technical reply, though.

I took a quick look at the code and it appears that there is no way to produce HTML, as the editor manipulates text elements through DOM, which serializes as XML. Those who would like to use regex to convert XHTML to HTML need to be mindful of what's in the attributes of elements that are being converted. For example, this XHTML will break most regex-based replacements: <input value="2>1"/>. So, it appears that the only safe way to convert editor output to HTML is to run it through an XML parser in the back end and use something like XSLT to produce HTML.

The > character is valid in attribute values. You also cannot just replace /> without using some pattern because it may be a in a CDATA section (e.g. in a script). Anyway, you are right, in most blog-type environments simple search and replace will work just fine. I just wanted people to be aware that replacing /> without parsing XML may produce unexpected results.