There you go. The key "editors" today are MSOffice and OpenOffice, neither of which supports advanced W3C formats. Especially XHTML-CSS.
XHTML-CSS is a highly interoperable XML based structuring that effectively separates content and presentation layers. In particular, CSS is a highly portable "presentation" layer. Especially when compared to the wholly application speciifc "presentation" layers in MSOffice XML and OpenOffice OpenDocument XML.
The key is that MSOffice and OpenOffice are powerful desktop "editors" of much of the world's business rich compound documents. With the recent ISO approval of MSOffice XML, billlions of these business process rich "client/server" documents will now become Web Ready and useful to the emerging "client/Web-Stack/server models common to SOA, WOA and Cloud Computing initiatives.
The December 2007 MSOffice SDK contained an important conversion component for the easy conversion of MSOffice XML <> XAML. "fixed/flow". XAML is part of the proprietary WPF (Windows Presentation Foundation) set of technologies which inlcude XAML, Silverlight, Smart Tags and LINQ.
The proprietary WPF technologies are alternatives for W3C XHTML-CSS, CDF, SVG, XForms, RDF and SparQL.
Neither desktop "editors" produce advanced W3C XHTML-CSS, SVG, Xforms, RDF, SparQL ready docuemtns. OpenOffice OpenDocument is capable of producing application specific supersets of W3C technologies, but does not fully implement interoperable instances. MSOffice is of course in a world owned entirely by Microsoft and the Microsoft Web-Stack.
No surpirses there. A W3C compliant OpenOffice would not doubt change the world. But then, so would a W3C compliant plug-in for MSSOffice!!!!!! Hello WikiWORED!