On June 18th 2003, the KDE Project released the second beta version of KOffice 1.3. It comes with a lot of bugfixes and a couple of new features such as a PDF import filter, new OpenOffice.org filters and more stencils for Kivio. Kexi isn't part of this version nor will it be in the final KOffice 1.3 but it's slated for a stand-alone release later this year and will re-integrated into KOffice in the next major version. Read more in the KOffice 1.3 Beta 2 release notes and in the detailed KOffice 1.3 Beta 2 changelog. Binary packages are expected to be available soon, for now you can only grab the source. Next step is a release candidate planned for 8th August.
Dot Categories:
Comments
I don't think I'll have time to make an import filter for Visio myself, but if someone else steps up good luck to him/her. (Currently there are to many other things that needs to be done to get stuck with filter development). Exporting to pdf is already possible via KDEPrint using the print to pdf option.
//Peter Simonsson, Kivio maintainer
When we get a standardized Office DTP format that both KOffice and OO can use it won't matter what you use. The days of locking people into software through particular formats are over. Anyone know what the status of the Oasis format is with KOffice?
The OASIS format isn't ready yet... And switching formats isn't done over night :)
Agreed.
I do hope thatt here will be at least a Beta 3 because AFAICS, printing in KOffice still needs a lot of work:
http://lists.kde.org/?l=koffice-devel&m=105609957315405&w=2
http://bugs.kde.org/show_bug.cgi?id=60105
--
JRT
The things discussed in the mailinglist thread isn't anything that can be implemented between two betas and the bug isn't really a koffice issue but a qt bug... So these print issues probably will have to wait until the next koffice or qt version...
The point is that KWrite is going for 1.3 and it still won't print correctly. It also appears that a major rewrite of part of it will be needed to get it to print correctly.
I consider this to be a serious problem.
--
JRT
The printing issue is one of the things that holds off a 2.0 release... We can't just not stop developing because somethings isn't optimal yet (and no you don't want me trying to develop a better printsystem...)
> We can't just not stop developing because somethings isn't optimal yet.
What am I missing here. It is much more (much worse) than not being "optimal". (We have) a wordprocessor program that won't print correctly, and the problem appears to be that it wasn't designed correctly -- or perhaps just wasn't designed. Shouldn't that have been correctly implemented before 1.0? And why isn't it a "show stopper" bug?
--
JRT
Because many people don't care about it as much as you do.
Ever heard of worse is better?
http://www.jwz.org/doc/worse-is-better.html
Okay, okay. I'm baiting you cause I know you like it. It's still an interesting read though.
What´s really the deal with the PDF import filter? What is the intended use once it matures enough? I'm asking as I really miss a good replacement for the Adobe Acrobat program (You know edit PDF-files, merge documets, re-arrange etc) in the KDE/Linux world. Should I get my hopes up?