The KDE Project today announced the eighth alpha release of KOffice 2, a technology preview of the upcoming version 2.0. Work continues in the same vein as before, with a strong focus on finishing and polishing our new features that will set KOffice. This is a work in progress, showing the changes that have been made over the last month by the KOffice developers. Most features that will be part of the final release are present now, and bug reports are welcome for the more stable components.

OpenDocument Improvements

One of the highlights of this release is the work on saving and loading Open Document Format documents, especially for the text shape, thanks to the sponsoring of Girish Ramakrishnan by the Dutch NLNet organisation. Girish has added scores of tests to check for ODF compliancy.

It is also worthy of note that now KOffice is able to load and save images in
text and presentation documents. Shapes can now be animated and associated with
events such as sounds.

Multiplatform

Importantly, for the first time, KOffice is released simultaneously for the
three main platforms: Unix/X11, Windows and Mac OSX. KOffice is the only office
suite that is available for all three platforms using a single codebase.

Early testers

While KOffice applications, generally speaking, are not ready for bugs reports,
some applications are more ready than others. The developers of KSpread, Krita, Karbon and the report component of Kexi welcome user feedback. The season is open for bug reporting!

There is a testing/compliance suite (can't remember the link). But the work that is done currently on the framework is tied to KOffice, since it's automatic testing, and it basically works by loading a document and checking that the internal state (aka Qt/KOffice structures) is correct, and that part is not sharable.

The results have not been updated, indeed. But the OpenOffice results were re-tested just a couple of months ago (at least all the failing ones, to see if they started passing) there were virtually no changes at all. Only one test started passing. I think the OOo people are not really using the results to find bugs and improve OOo :/

I like to see screenshots too! If possible, from KDE4.x so it's using oxygen ;)
What I am waiting is the paper sheet has space around it so all sheets are not together in one line but there is 1 inch space around it, like on openoffice or on word. Yes, it's just a small outlook wish but it has great meaning for usability when you can feel that sheet is paper and not just a white area what trye to mimic a paper.

So if someone has screenshots from kword with first page top edge seeing and the join part of two sheet.

KOffice running on Windows is so here. Although I have a few crashes, the fact that it is running on Windows excites the living pants out of me.

I'm looking so forward to stable KOffice 2.0 on Windows. This will usher a new era of free software that never foreseen before. The days of Microsoft Office will be numbered. Those who continue to pay for Microsoft Office will be left in the dust as the momentum of KOffice builds.

I don't want to GNOME-ify KDE. I was simply stating, that since GNOME accounts for about half of Linux, GNOME support on OOo was probably part of the reason for OOo's popularity as an Open Source application. I never meant that the KOffice developers should port KOffice to GTK+ (that work is being done by TT ;).

With my LaTeX background, I always relies on heavy use of styles. I cannot live without styles, and OOo make the use of styles a really pleasure.
The M$Office styles implementation is painful, you need to go trough many windows that pops-up every time you need to change one small thing.
But the point that interest here is that the style implementation on koffice is weak: no page styles, no deal.
I would love to use an office suite fully integrated with my kde (forgot the guy to talked about gnome integration), but kword on the 1.6 era is unusable for me, and I'm not sure if version 2 will solve my needs.
The things that a real work processor needs, IMHO, are:
- hierarchical paragraph styles
- hierarchical character styles
- hierarchical page styles (in this point, even OOo have problems with wonderful page styles that _not_ act hierarchically)
- fields of any kind, either automatically generated or custom, that gives simple but yet powerful cross-references, variables (both numerical and textual), tables of contents, table of figures, etc.
- Have I mentioned styles?
I don't like the gtk-java-monky-tonky stuff that is growing inside OOo, nor the way in which the community problems are handled, but Writer is a TEXT processor based on styles, which is quite different than a WORD processor based on frames.
Please, give me strong reasons to believe on kword, OOo looks awful on my kde desktop. Right now, the only koffice app that I use regularly is Krita.

I've been using OO.org up to this point because of it's better functionality. But I've recently tried the koffice 2 spreadsheet and liked it; it basically does everything I need. There were some things that didn't work quite right but that's understandable since it's still in alpha.

I'm looking forward to switching to koffice; for me there are several advantages. I'm using KDE and of course koffice has better KDE integration. And as you say it's faster and lighter; oo.org takes 8 seconds to open on my AMD 64 X2 box which is ridiculously slow. I'll be using KDE apps for almost everything so there should be better sharing of libraries.

pffft... from all the things they did in Redmond, Office is quite o.k. It's working as an office suite. Not the worst peace of software, really. I think, even if Microsoft gives up on the lock-in with stupid file-formats, MS Office would still attract some buyers (but the competition would nevertheless grab its 50% market share)

I would go for KOffice anyway as I like openness in terms of code and content... ;-)

I also like Open Source code. My main problem with both MS-Office and OOo is that they are big. OOo being big is understandable, since it is cross-platform, but Office is not, so it's Just Plain Bloated.

So instead someone who has it, would press print screen and paste few files to image sharing site, they told wanted people to download bigger amont of data and even add cost for share servers what share the KDE4 daily ;-)

Yeah come on KOffice devs... you've (presumably) worked so hard on this new release and we want to see what it does. Some screenshots demonstrating what it looks like would be much appreciated. We want to be koffice fans -- we just need some help :)

This might not be the place to ask this question but I notice in kde4daily that the latest KWord 2.0 alpha 8 can't open MS Word 2003 .doc files nor produce them.
As I'm still unemployed I regularly use OpenOffice to edit application.doc and CV.doc in MS Word .doc format. OpenOffice almost can produce good .doc files but I always have to reboot into Windows Vista to check in MS Word 2003 if it looks okay.
KWord 1.6 can't read my CV.doc correctly.
Are there already MS filters for KWord 2.0? Will they ever be written?
I read somewhere that there is a Google Summer Of Code project:"Improve KWord MS Word filter", but is that only to read .doc files or also to produce them?
I'd like to use KWord only in the future.

Hm, most companies demand a MS Word .doc CV if you sollicitate for a job. Would it be good practice if from now on I write my application letter and CV in ODF (.odt) format and tell the company to who I write a sollicitation email that they must install the ODF plugin for MS Word if they want to read my application letter and CV?
There appear to be three solutions for an ODF plugin:
* Sun ODF Plugin for Microsoft Office (claims to be better than the sourceforge plugin)
* http://odf-converter.sourceforge.net/ : Open XML/ODF Translator Add-ins for Office. Sponsored by Microsoft, the final version is planned for August
* http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormats... : Microsoft Office 2007 Service Pack 2 (SP2), scheduled for the first half of 2009, willl provide support for ODF

I think for my next sollicitations I will attach to my emails both .doc AND .odt files with the request to the company that they should install the Sun ODF plugin as the ODF format will be my preferred way of communication. This means a little more work for me but I'm guessing many companies have not heard much yet about ODF.

How many of you guys use only ODF documents in your communication with companies? Are companies easy to adopt the ODF plugin or are you forced to write a MS Word doc?

So my question whether KWord can produce .doc files is no longer relevant. But KWord should be able to READ them as long as companies send their documents to me in .doc format.

May I suggest that after you're done editing and saving your document in KWord, convert it into a pdf-document. Most companies AFAIK can open a pdf-document. Additionally, you will also be sure that the layout of your document preserved when opened by others.

I was most surprised when recently at a presentation, the computer used with the projector could not be used by most of us as it did not have a way to open pdf files (yes. No acrobat reader!). Of course we could connect our laptops to the projector.

Now this again brings us to "export to PDF" not being the same as "print to PDF". Would koffice give us a way to create pdf files preserving links etc? or would the pdf printer somehow become smarter to it could manage links etc?

The big problem in 1.6 with reading .doc files was tables (they are imported perfectly, but kword cannot handle big tables and certain types of images. KWord 2.0 does not have tables at all, but benjamin call is working on the images problem as part of his summer of code project.

Saving as .doc isn't on the agenda. We do the same thing as Microsoft itself here, when you save a document for another version of word than the one you're using, and save it as rtf but call it .doc.