The KDE Project today
announced the release of KOffice 1.2beta1.
While the "final" 1.2 release is not scheduled for another 5 months, this
is a great chance to see what the active KOffice developers are up to,
and also a great time for new developers / companies to join the KOffice
project to accelerate the ascendence of KOffice into the
market-leading office suite position <grin>.
The highlights of this release are WYSIWYG in KWord, KPresenter and formula objects,
much enhanced scriptability via DCOP, and a number of new and enhanced
filters, including an XSLT framework for mapping between different
XML office formats. Read the announcement for the many details,
and feel free to give
thanks to those awesome
KOffice developers!
Dot Categories:
Comments
No, imagine you have 60 numerated Endnotes/References and you want to add
one at position 34. If you dont have an endnote function, you have to rename all
the ones which have shifted.
Shouldn't the page number function (found under insert->variable->page) be enough for this?
Well, you really have never ever in your life seen a footnote? Have you ever read a book?
A footnote, for instance, can put a superscript number in a word, and that number is a reference to a note, at the foot of the page.
No, page numbers are not good, because you can have many footnotes in a single page, or no footnote at all.
This is what I call footnotes, and (for me) this is OK, however:
if I insert some text into the beginning of the document, the footnote must change page, with the point that it was entered.
Also this does not address the issue of end-notes, and references (which, if made configurable enough amount to the same thing)
Is someone working on making something like framemakers cross-reference? (will solve the problem of end-notes)
I believe everyone will agree with me when I say Word will go the way of the dinosaur. We really need to get KOffice up and running with QT for Windows. People are afraid of switching because they don't know if they will be abl to do their work. I'll admit, it was a concern of mine as a student. I like the idea of making one universal translation for M$ files. We should definitely work together.
With the interest in graphics, I think Adobe will have to take us seriously too. We may really start to give them a run for their money.
Why aren't the rpms offered by application? I think providing the base compnents with kword or kchart, and then letting people download the other applications they want would be nice for people who don't have fast connections.
>Why aren't the rpms offered by application?
KDE provides source code. KDE does not provide packages or binaries. Packagers do that. Thus, how RPMs and DEBs are created is not something that is a responsibility of KDE, so go talk to the packagers for the various distributions. Also, the Debian packages are offered app by app in this fashion.
I was told Conectiva offers applications packaged into single RPMs.
As a Linux user you are free to choose whatever distribution you like.
So if you think you want small packages and your distributor doesn't want to offer them, switch.
Cheers,
Kevin
Why aren't the rpms offered by application?
Because not every one uses RPM, let alone Linux. RPMs for a Linux binary of a KDE application would be as useless to me as tits on a boar. They won't work for me on my Solaris box and they won't work for me on my FreeBSD box. I've got RPM ability on my Slackware partition, but unless that RPM was made for Slackware, it will have dependencies on packages not named in the Slackware style. Packages are meant for specific distributions, and KOffice is not limited to a specific distribution. If you want RPMs, talk to your distributor. Or use the source code, the ultimate in portable packaging.
KOffice for Windows (or Mac, as an earlier poster mentioned) would be neat, but there are two problems with such an effort, one technical and one legal.
First, kdelibs was written to work on unix. I think some people have managed to compile kdelibs on Windows by using cygwin and Qt/X11, but this is probably only because cygwin supports all of the unixness needed by kdelibs. Compiling kdelibs with Visual C++ using Qt/Windows may not be possible at all.
Second, KOffice is GPL and there is no open source distribution of Qt/Windows. This means that the licenses are incompatible and it is not really legal for someone to distribute a resulting build between these two. The KDE team ought to change their license to allow linking to Qt, commercial or not, so that the possibility of a KOffice on Windows or OSX is at least legal.
-Justin
A GPL version of QT for windows has been available for a while
http://www.trolltech.com/products/qt/windows.html
http://www.trolltech.com/developer/download/qt-win-noncomm.html
Will someone please enlighten me and the rest of us as to why a change in
file format from tar and gzip to Zip is necessary?
What exactly breaks without this change?
How easy is it for a user of KOffice 1.1 to read 1.2 files?
I believe it is a part of the move of the open office suites (OO, Abi, Koffice
and some others) towards a common file format. A lot of discussion seems to have gone into deciding stuff like that recently.
tar-gzip only allows sequential access. If you want to extract a file from a tgz-file that contains 10 files, you have to process the whole file. Zip on the other hand allows more or less random access, if you want to extract a single file you can look it up in the index and just pull out that one file.
That gives more flexibility to process such files.
Cheers,
Waldo
With tar you have to know the size of a file before you can write it into the tar archive.
So you have to write the document into a buffer to see how large it will get and then you have to write it into the archive as a whole.
With zip you can just start writing and finish whenever you're at the end of your dokument,
Kevin
Isn´t it a good idea to make Windows-viewers for popular Koffice-programs like Kword, Kspread and Kpresenter? the problem is that when I want to use Koffice for proffesional work other people have to be able to open the documents made with this stuff.
Unfortunatly most people are still working with MS-Windows and can´t open Koffice-files. Remeber alo that MS-Office may have come so populair because of the fee viewers availeble from Microsoft.
If there is already some development is going on on this point I really like to know. I think it could boost up the succes of Koffice and the entire open-soure.
Thanks anyway for the nice office-suite so far!
I think that's a superb idea. It will make viewing my kword files in windows much easier (I keep forgetting to export to abiword format) and would mean not losing any formatting.
IMO Kword is THE Killer Linux app (OoO is ok but KWOrd is much better and more fun to use)
Anything that would enable it to be more widely used would fantastic
To certain extent, you can always export your document to RTF (Rich-text) which is of course readable by MS Word.