This is an old chestnut but I'll throw in my 2 cents worth anyway...
FCKEditor is advertised as being XHTML compliant, but actually the default distribution is not thanks to <u></u> tags for example, although everyone 'knows' that it can be made XHTML compliant by editing the XML Styles structure.
Why don't the developers grip this one and simply distribute a style structure which IS XHTML compliant? We should all be doing our best to promote XHTML and markup validity generally. FCKEditor is being used by lots of beginners who may find it a bit of a struggle setting it up in the first place, let along getting down to setting up XHTML compliant styles buried in a file they might not actually look at. How does that promote compliancy?
FCKEditor is advertised as being XHTML compliant, but actually the default distribution is not thanks to <u></u> tags for example, although everyone 'knows' that it can be made XHTML compliant by editing the XML Styles structure.
Why don't the developers grip this one and simply distribute a style structure which IS XHTML compliant? We should all be doing our best to promote XHTML and markup validity generally. FCKEditor is being used by lots of beginners who may find it a bit of a struggle setting it up in the first place, let along getting down to setting up XHTML compliant styles buried in a file they might not actually look at. How does that promote compliancy?
Re: Constructive suggestion re XHTML
I fail to see how that is really more "xhtml compliant". Instead of using an element with a meaning, you are putting some inline styles that don't provide any extra information and even worse, you can't override them with your stylesheet.
At the very least, if you want to get rid of <b> and use <span> then you should generate <span class="bold">, so in your stylesheet you can control its presentation with span.bold {font-weight:bold} and maybe later you want to adjust it some other way: span.bold {font-weight:bold; text-transform: capitalize} without touching all the pages. (But you could have done the same with b {font-weight:bold; text-transform: capitalize} ).
The problem about generating <span class="bold"> would be of course that about 0.0% of the stylesheets used with FCKeditor does have such a rule, so people wouldn't see it, and that's why you must adjust it to your usage.
All this time I have avoided talking about <u>, because I don't really believe that anyone that says that he cares about XHTML would put such a formating element in the toolbar. Everybody knows that a text with underscore in a web page means a link, so putting it around any other text will lead to end-users confusion.