« Return to Thread: OOo Status digest Volume 2, issue #3- January 21st 2008
Re: OdfConverter
by Bugzilla from ahz001@gmail.com
::
Rate this Message:
Tor Lillqvist wrote:
>> 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.
>
Hi Tor,
Yes, I noticed how the integration works, and I appreciate its
simplicity. I am disappointed the preprocessing/postprocessing is not
yet (or ever will be?) integrated into the mainstream OpenOffice.org.
It would be a solution to provide additional support such as Microsoft
Works word processor .wps which I developed in libwps. Fridrich helped
and provided integration for upstream, but it was not accepted there for
various reasons. As an alternative, it would have been relatively easy
to add .wps support as an extension the same way as odf-converter if the
pre-/post-processing support were upstream.
> 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.
>
I was not aware of Mono bundled executables. The OdfConverter binary
looks reasonably small, so I would not have guessed.
> And yes, once the built-in native OOXML support is good enough, there will be no need for odf-converter.
>
Thanks. I'm writing an article on the various options for OOXML support
for OpenOffice.org now (before OOo 3.0.0 is released).
Andrew
_______________________________________________
Dev mailing list
Dev@...
http://lists.go-oo.org/listinfo.cgi/dev-go-oo.org
>> 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.
>
Hi Tor,
Yes, I noticed how the integration works, and I appreciate its
simplicity. I am disappointed the preprocessing/postprocessing is not
yet (or ever will be?) integrated into the mainstream OpenOffice.org.
It would be a solution to provide additional support such as Microsoft
Works word processor .wps which I developed in libwps. Fridrich helped
and provided integration for upstream, but it was not accepted there for
various reasons. As an alternative, it would have been relatively easy
to add .wps support as an extension the same way as odf-converter if the
pre-/post-processing support were upstream.
> 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.
>
I was not aware of Mono bundled executables. The OdfConverter binary
looks reasonably small, so I would not have guessed.
> And yes, once the built-in native OOXML support is good enough, there will be no need for odf-converter.
>
Thanks. I'm writing an article on the various options for OOXML support
for OpenOffice.org now (before OOo 3.0.0 is released).
Andrew
_______________________________________________
Dev mailing list
Dev@...
http://lists.go-oo.org/listinfo.cgi/dev-go-oo.org
« Return to Thread: OOo Status digest Volume 2, issue #3- January 21st 2008
| Free embeddable forum powered by Nabble | Forum Help |
