One of our clients complaining that their content copied from website is getting reformatted by FCKEditor...... I looked into the problem and they have wrongly nested tags...... IS THERE A WAY TO FORCE FckEditor to ignore those..... I know we used to have FCKConfig.EnableXHTML in old version where you could force to ignore bad formatted html..... I tried FCKConfig.DocType, FormatSource, FormatOutput with not much luck...
BTW great job for providing the best html editor...
This is a sample HTML which gives problem... U tag and A tag are badly nested so when you saving the fckeditor content or moving from source to content view back and forth.... it moves <a> to all the way down making whole sentence as a hyper link.......
<a href="http://xxxxx"><u>Click HERE</a></u> to download and print out the Application. Make as many copies as you think you will need during your registration drive.<br><br>2. Mail your completed application(s) to your local election authority. <a href="zzzz.aspx"><u>Click HERE</a></u> to look up the mailing address. If you are unsure of your election authority, please feel free to contact us.
Re: FCKEditor reformats Text copied from website
I am not on the FCKEditor dev team, but my understanding is that you won't be able to change this. The reason is that the FCKEditor does not actually have an HTML parser built in - it uses the parser built into the host web browser. So, what is happening is that when you save or switch from "Content" to "Source" views - the FCKEditor is actually reading the DOM tree from the browser, and displaying the result. Since the HTML parser in browsers will always attempt to make sense of any malformed HTML that is sent its way, your code will always be reformatted when you go back and forth.
This means that there is no setting within the FCKEditor to preserve, perfectly intact whatever code you might type into the "Source" view. It is not like an IDE (such as Dreamweaver), where the source code is saved somewhere - it is all done from within the browser. This is fundamental to the way that FCKEditor (and pretty much every other in-browser WYWIWYG editor that I know of) works. This also means that you may get slightly different results from different browsers.
I hope that makes sense. It frustrated me a great deal as well, until one of the developers explained it to me.