From Sound & Fury, another TypePad blogger writes:
Due the problems and errors introduced by TypePad's new Compose editor (see this S&F post), blogging on Sounds & Fury will cease except for the most pressing items until those problems and errors have been resolved by TypePad as at this point in time we don't know just how those problems and errors will be resolved.
The formatting of all posts prior to the introduction of the new Compose editor are formatted using one consistent set of source HTML formatting code which is incompatible with the source HTML formatting code required by the new Compose editor in its present state. Specifically, the delineation of paragraphs requires the explicit presence of certain formatting tags in the source HTML for the new editor that were not required by the previous editor as the new editor does not recognize the "Convert line breaks" option recognized by the old editor. Additionally, the new editor does not recognize the "justify" text formatting specified in our theme Design, and insists on formatting all text as "left align". Until those major errors are corrected, the HTML formatting of any posts made in the new editor will be incompatible with the HTML formatting of all prior posts resulting in a "broken" blog should the blog have to be republished to accommodate the requirements of certain TypePad functions. As things stand now, if we had to republish Sounds & Fury for any reason, every single post (1096 of them at last count) would have its formatting "broken" irretrievably by the republish; a prospect we don't want to even think about.
Stay tuned for further developments.I can only sort of follow what the heck this means. I know this much: Someone is NOT HAPPY over at Sounds & Fury, but he or she is a whole lot classier than I am in how they are expressing frustration at TypePad's major gaffe. Suffice to say, though, that I no longer am wondering "Is it me?" with all these problems.
One helpful note... Firefox seems a little better than Safari in making this "upgrade" work. So for now I will probably just use it, stop bitching, and stop including photos and other elements that were once simple and now make me want to throw my MacBook across the room. (Don't worry, little MacBook. I know it isn;t your fault that TypePad apparently doesn't feel the need to include Mac OS in its "upgrade" for now. And why should they. It's not as if Macs and the so-called creative class have any connection, snark you very much.)
OK. I'll shut up about this problem and move on. But one last thing. TypePad: you suck. There. Done with it.