Why not use the OpenOffice MSOffice filters?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Why not use the OpenOffice MSOffice filters?
by CPH on Wednesday 27/Aug/2003, @02:50

I know it would involve some work getting these filters into a reasonably independent state from OOo, but at least this way you would have both an import and an export filter. I'm sure that the OOo and Abiword people would be interested in this.
Also since all of the important office suites for the desktop would be using the same filter code, it can only improve the filter.
My 0.02 c

CPH

Related Links

·   Articles on KDE Office Suite
·   Also by CPH
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Why not use the OpenOffice MSOffice filters?
by Nicolas GOUTTE on Wednesday 27/Aug/2003, @04:28

Sorry, but I doubt that it will be the same code. All three word processors use very different libraries. (See also the many discussions on the koffice mailing list about why we do not take OO's code.)

However what can be done is to create libraries to ease the programming of filters. That what has been done for the MS Word import.

Have a nice day!

[ Reply To This | View ]

Re: Why not use the OpenOffice MSOffice filters?
by Holger Schroeder on Wednesday 27/Aug/2003, @07:08

Hi,

the switch to the ooo fileformat offers us the possibility to use openoffice as a nice import filter for ms office files. switching our internal file format is a lot of work, but trying to separate the openoffice filters out of openoffice is only time-consuming, and not probale to work out at all.

openoffice is able to be scripted, and transforming a ms .doc file into a .sxw file is as simple as taking a template document containing a transform-script, executing openoffice with that script file from the command line.

after that you can simply open that sxw file, either with an openoffice import filter, or in the future you will be able to simply open it as it is then the native format.

(any people interested in hacking on this are very appreciated :-)

Holger

[ Reply To This | View ]

Re: Why not use the OpenOffice MSOffice filters?
by anon on Wednesday 27/Aug/2003, @07:22

I'm sure everyone would love to do this, but the OOo MSOffice filters are _very_ linked to OOo specific code, and not only that, it's a plain mess to work with (not that it isn't a wonderful piece of technology, but after years of work, and I can imagine only a few people working on it, it's gotten really obfuscated) :)

[ Reply To This | View ]

Re: Why not use the OpenOffice MSOffice filters?
by Maiko on Thursday 04/Sep/2003, @23:09

I am not sure what this forum is for (KDE?) but I do care about openoffice filters.
Just for your information, there is a little application using openoffice macros to convert files and fired with a command line through openoffice. If you want to check this try at http://oooconv.free.fr/ . It is quite fast (the time for openoffice to open then convert, save and close), but it would be faster if someone can extract the filters code. I do not know if the related Ooo filters code is bound to Ooo specific code and I do not really want to jump into openoffice source code to verify this. Anon, Have you got any links which explain this very precisely or did you verify it yourself? Thanks for replying.

Maiko

[ Reply To This | View ]

Re: Why not use the OpenOffice MSOffice filters?
by Tiep on Monday 13/Dec/2004, @20:50

Can you compare OpenOffice with MSOffice ?

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"That's something I don't know." -- David Faure
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.