The KOffice team released the third bugfix package that builds upon the previous 1.3.x versions, with many fixes, mainly in the core libraries and in some filters.
KOffice 1.3.3 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
When koffice will be using OpenOffice import libraries ? I think while koffice will remain with poor M$ Office import capability people not consider it unfortunately.
KOffice 1.4(2.0) and OpenOffice 1.2 will use the same file formats (Oasis). That should make using the OOo import libraries rather seemless.
KOffice 1.4(2.0) and OpenOffice 1.2 will use the same file formats (Oasis). That should make using the OOo import libraries rather seemless.
That is in theory right, but the fact that they use the same file format doesn’t mean that their feature sets are identical. It will undoubtful make it easier to hack in the OOo filters, but i will be very surprised if it is at all seemless.
Personally i would just like to see the import function become STABLE instead of getting more features. It seems to crash on at least half of the office documents i have tested it with.
> When koffice will be using OpenOffice import libraries ?
Probably never, or at least not in the near future. While in KOffice the filters are cleanly separated from the rest and there’s even a command-line tool for conversions between various formats, in OOo the filters are reportedly so glued with the rest of the code that reusing them somewhere else would also require at least a quarter of the other OOo code.
in OOo the filters are reportedly so glued with the rest of the code that reusing them somewhere else would also require at least a quarter of the other OOo code.
—
koffice developers have already announced a move to openoffice filters but like the post above it doesnt mean that the formats will automatically become compatible. there are other issues like font metric compatability and such
Nice, got a link?
I remember reading something by a koffice dev that mentioned the same problems that L.Lunak mentioned in his post, so I’d really like to now what has changed their opinion and maybe even see something like a timeline.
I have a what I hope is not a silly question. I thought I read somewhere where the KOffice team was going to migrate over to using the Open Office code and put a nice KDE interface on it?
Or am I just blowing smoke out my caboose?
> koffice developers have already announced a move to openoffice filters
You apparently fail to see a difference between OOo import/export filters and OOo file format.
OpenOffice.org and KOffice are moving to the Oasis XML format.
If there are compatability problems between the two, they now have something to point to when figuring out who (if anyone) has it wrong.
Keep in mind that XML, similar to it’s cousin HTML, is primarily a data format not a display format though the Oasis XML format does include display and print considerations. Details follow;
http://www.oasis-open.org
http://www.linuxjournal.com/article.php?sid=7159
http://xml.openoffice.org
I’m afraid you’re puffing smoke. There’s a great deal of difference between putting an interface around an application and two applications using the same file format. The latter is what’s being done: both OpenOffice and KOffice are moving towards the same, common file format for native files.