KOffice 1.5 Released

ingwa writes to tell us that the KOffice team has released version 1.5 which offers, among other things, default OpenDocument file format, new project planning tool KPlato, professional color support and adjustment layers in Krita and the long awaited Kexi 1.0. From the announcement: "KOffice was the first office suite that announced support for OpenDocument and now the second to announce it as the default file format after OpenOffice.org. This makes KOffice a member of a very select group and will lead to new deployment opportunities. Great care has been taken to ensure interoperability with other office software that also use OpenDocument."

Comments

Re:ko or ooo?

[ingwa]

You will when KO 2.0 comes out around new year 2007 or soon thereafter. KOffice 2.0 will run natively on Unix, Windows and MacOS X. The reason I can promise that is that kdelibs and Qt4 already are ported to and GPL:ed on those platforms.

But it still can't print!

[Just Some Guy]

I like KWord - really, I do - but I can't use it because the printed results are awful. Basically, no matter how good the documents look on my screen, the kerning of their printed versions is completely broken (under both Gentoo and FreeBSD with two different laser printers). The problem supposedly lies with QT3, or so I've read, but that doesn't change the fact that I currently cannot use KWord for anything that will end in a hardcopy.

I know this sounds like a troll but I don't mean it that way. I'd switch from OpenOffice to KOffice in a heartbeat if I could, but I just can't do it right now. Please, please! make printing work right and I'll be eternally grateful.

Re:I still don't get it......

[Just Some Guy]

Therefore, even a dumbass can figure out they want OpenOffice rather than KOffice.

Go ahead and explain to this dumbass why I want to give up a program that fits in with the rest of my desktop, supports KIOslaves, and is document-compatible with your office suite of choice. Really, I'm waiting...

The reason for their coexistence is that they have two different design philosophies, two different styles of programming, are built on two completely different frameworks, and appeal to two different groups of people (KDE users versus everyone else). How would you expect them to reconcile those differences? Do you also want KHTML to merge with Gecko? After all, they both do the same thing.