Another part of day 3 -
I know that when I used to use Typepad, that the rich text editor I had was pretty good about stripping out tags and attributes that were weird. Font tags disappeared, for instance, which made it possible to be sure that stuff didn't show up as Comic Sans unless I really wanted them to be in Comic Sans.
Here's what I've found out so far.
MT supports multiple kinds of rich text editor abstractions. There's currently support for the YUI editor, for TinyMCE, and for FCK. The relevant bit of configuration code is wrapped in
Here's the TinyMCE MT plugin source posted on Google Code. The current release, supporting Japanese and English, is in active development and is at version 0.1.11 as of 29 hours ago.
Richard Benson wrote and supports the YUI MT plugin, which is at version 1.3.
Now, to the actual MT rich text editor:
A rant from François Nonnenmacher about the HTML generated by the MT rich text editor:
And generally that's my experience to date; weird tags, bad semantics, and unpredictable behavior. What I don't know yet (and hope to figure out) is what the data path is through the system that would let things be cleaned up and filtered on the back end so that they are consistent, or fixed on the front end so that the generated code from the rich text editor is better.
The funny thing is, this used to work better: old versions of Typepad, and old versions of MT, both had a very conservative rich text editor that denatured the text quite a bit, removing a lot of tags and operating in "safe mode" much more so than "rich mode".