> will the OpenOffice.org integration for OdfConverter become obsolete?
Well, the odf-converter (as the preferred spelling/casing is, I think) "integration" into OpenOffice.org is rather loose anyway. There is a patch in ooo-build that enables filters to run a separate preprocessing (when lolading) and postprocessing (when saving) program. When loading and saving OOXML formats this pre/postprocessing is used, and the program in question is the command-line odf-converter.
There is thus no explicit knowledge in OOo code of odf-converter in particular, just a generic mechanism for pre/postprocessing.
Novell builds odf-converter using Mono, and distributes it as a so-called bundled executable (platform-specific executable that includes the Mono runtime, i.e. not a platform-independent managed .NET executable) for Linux and Windows. For Linux the odf-converter is distributed as a .RPM package, for Windows as a OOo extension (.oxt file). These packages add their own xcu configuration snippets that define the OOXML file types and how to load and save them by using the pre/postprocessing stage.
And yes, once the built-in native OOXML support is good enough, there will be no need for odf-converter.
--tml
_______________________________________________
Dev mailing list
Dev@...
http://lists.go-oo.org/listinfo.cgi/dev-go-oo.org
