Slashdot Mirror


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."

61 of 296 comments (clear)

  1. KPlato by Svenne · · Score: 5, Funny

    I bet that's klingon for something.

    K'Platoh!

    --

    Slagborr
    1. Re:KPlato by TClevenger · · Score: 2, Funny

      I think Plato sounds better in the original Klingon.

    2. Re:KPlato by Arandir · · Score: 2, Funny

      KPlato Barada Nikto!

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  2. OpenDocument As Default is Great! by PurpleMonkeyKing · · Score: 5, Insightful

    This is great news. More choices is always better. This might even convince a few people to use KOffice as their Office Suite of choice, as it is native to KDE, and it'll be easier than ever to share documents with others.

    1. Re:OpenDocument As Default is Great! by runningduck · · Score: 4, Interesting

      What I find odd is that KOffice now uses ODF which is native to OpenOffice.org. But according to the KOffice 1.5 import/export filters the support for the format is not quite there yet. http://www.koffice.org/filters/1.5/

      OpenOffice Writer Import: The filter generally works well, however some features might be missing or might not work correctly yet.

      OpenOffice Writer Export: The filter generally works although it is not finished, and it may suffer from some instability.

      This certianly raises some questions.

      --
      -rd
    2. Re:OpenDocument As Default is Great! by archen · · Score: 5, Informative

      Keep in mind that ODF is a spec not a law. By supporting ODF you are not required to support all features the format is capable of. Simplistic example: I create a text reader for blind people, I can probably ignore 80% of the ODF spec and be compliant in reading (and writing) it for my needs. I'm sure Open Office will support everything including the kitchen sink, while Koffice will support mostly a subset of that - so I would expect some features may be missing. ODF is also pretty flexible so it can support stuff we haven't even thought of yet.

      I've moved away from Open Office because of the bloat, so if Koffice skips some of the more obscure parts of the format that Open Office supports, that's okay by me.

    3. Re:OpenDocument As Default is Great! by NereusRen · · Score: 3, Informative

      OpenOffice format is different from OpenDocument format (confusing, I know). I presume the filter on that page refers to the old-style OpenOffice formats which used extensions like .sxw, .sxc, etc. The new OpenDocument format, which OpenOffice has now switched to, uses extensions like .odt, .ods, etc.

      Since KOffice saves in OpenDocument format by default now, I would guess they don't list it as an "import/export filter."

    4. Re:OpenDocument As Default is Great! by ingwa · · Score: 2, Informative
      This sounds more like a bug to me. Two questioins:

      1. Was this KWord 1.5 or an earlier version? 1.5 has had many fixes for OpenDocument and might very well work if you used an older version in your example.

      2. If it WAS 1.5, could you report the bug to bugs.kde.org? If possible, attach the document, as this will make it easier for us to fix the bug.

      Last, but not least, don't forget that OpenOffice.org does also contain bugs.

    5. Re:OpenDocument As Default is Great! by zander · · Score: 2, Interesting
      I'm sure Open Office will support everything including the kitchen sink, while Koffice will support mostly a subset of that

      There are various little things that KWord does support that OOo does not (yet) support. The ODF standard was created by both office suits and KOffice people did request features like Frames and some numbering-types , as a fast example, that made it into the spec but that OOo still does not support. I'm sure there is more.

  3. Mixed Bag by nursegirl · · Score: 4, Interesting

    I'm very excited about Kexi. We've needed an open standards equivalent to Access/Filemaker Pro for businesses who want something small and don't want to hire a database programmer for MySQL or something. Not so excited about KPlato. Most project management software is inherently broken - not in terms of the technology, but in terms of the essential vocabulary of projects and project management. It's one of those times that I wish the Linux world felt more comfortable about innovating. Thank goodness there's basecamp, at least.

    1. Re:Mixed Bag by Anonymous Coward · · Score: 3, Insightful

      If you use similar programs, why don't you make suggestions on what you would expect them to have? I'm sure the KPlato team would love to hear what actual users would like their program to do. You do have a say. If you need more or more flexible functionality, try to explain to the team what you want. Innovation is not generated in a vacuum. Necessity is the mother of invention. In the cases where the one feeling the need and the one having the tools to fulfill it are different people, then they need to communicate otherwise the need will never be fulfilled.

      (a.k.a where's the patch?)

  4. Congrats... by Ecko7889 · · Score: 3, Interesting

    Congrats on the release, but I have to say that OO.o still is the leader in OSS office suites.

    ODF has pushed a long way since I first heard about it, but without support from the industry, their will be no pressure against Microsoft to implement it into MSOffice.

    Hopefully Google and Writely will tip the edge toward ODF.

    --
    $sig$
    1. Re:Congrats... by Ostsol · · Score: 3, Interesting

      I found myself really disappointed by OO.o -- at least the Windows version. For all its faults, I found MS Office cleaner and much more responsive. Basically: as far as Windows office products go, I'm shafted.

    2. Re:Congrats... by Kjella · · Score: 5, Insightful

      Congrats on the release, but I have to say that OO.o still is the leader in OSS office suites.

      Well, as long as they're properly compatible - pick the one that suits your personal preference. Or even the right tool for the right task, if one does something well that the other doesn't (or not at all). I'm perfectly happy that Firefox is more popular than Opera (my preference), because if you've built a site to work in one it's 99% sure to work in the other.

      If we see competition on features rather than on format and compatibility, nothing is better than that in my opinion. If it isn't clear what I mean by that, let's for the moment assume that one of them offered regex search & replace, and the other did not. The results, before and after are both valid ODF documents - the difference is how you get there. Same with layout, which offers good layout management? Spell check and grammar?

      Besides, I think the only way to have a format implemented according to spec is to have at least two implementations. They're sure to run into many of the other's bugs resulting in better standards compliance to benefit all. In short, I don't care if OpenOffice is "leading", I think "local competition" is just as excellent as motivator as the big competition against MS Office.

      --
      Live today, because you never know what tomorrow brings
    3. Re:Congrats... by cozziewozzie · · Score: 3, Insightful

      Well, to be completely honest, OpenOffice is also developed by a very large software company: Sun Microsystems.

      They have many full-time programmers working on it (about 40-50, if I'm not mistaken) and they are doing most of the work.

      Sure, openness is good and we have many really cool things as a result of this -- see KDE integration for a very important example -- but Oo.org is hardly the shining example of hobbyists coming together to build a great product.

      Actually, KOffice is a far better example for this.

    4. Re:Congrats... by Kadin2048 · · Score: 2, Insightful

      Pity there's no functional screen-top, context sensitive menubar, though.

      Right now I'm using Kubuntu and it's not exactly the world's most stable piece of software; I'd like to use Gnome, but they insist on using Windows-style menubars for everything. It's a crummy design[1] and I don't understand the resistance to having alternatives like KDE does.

      [1] If you like it, more power to you; I think they suck and just want a choice, I don't care if you use it or not. The only good argument I've heard in favor of window-top menubars is that they're easier to use with multiple monitors, but really I think Linux could outdo MacOS in this respect and have an application's menubar jump to the top of the screen on which it was located, if people were bothered by this.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    5. Re:Congrats... by big+tex · · Score: 4, Informative

      As for styles, Word has them, but they don't work well, IMO. (yes, the sidebar helps a lot.)

      Example: I write more technical-type documents instead of prose. That is, with headers, lists, bullet points, stuff that should summarize into a table of contents nicely.
      If I am typing along and want to insert a list, I can hit either the button on the toolbar or select the style that's something like 'Normal, Numbered.' All of a sudden, the entire damn document gets numbered, not just creating an indented 1) where the cursor is. If i hit CRTL-Z, it then behaves normally. Does this every time on any of the computers over the last five years or so. The style functions are borked so badly that I actually write all of my big reports in OO.o.

      Very frustrating, and is my most occurring 'I hate Microsoft' moment.

      --
      I think I need a new sig here.
  5. Re:Kcrappy Knaming Kscheme by Anonymous Coward · · Score: 5, Funny

    iAgree.

  6. Re:ko or ooo? by ingwa · · Score: 5, Interesting

    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.

  7. But it still can't print! by Just+Some+Guy · · Score: 5, Interesting
    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.

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:But it still can't print! by Just+Some+Guy · · Score: 4, Interesting
      the pdfs that I export with koffice look exactly like the document on the screen

      My PDF output looks nothing at all like my KWord screen. To make those images, I imported a Word doc that our transcriptionist emailed to us, then printed to PDF. I took a screenshot of KWord and KPDF using The Gimp, and cropped each shot to show a representative snippet of text.

      Unfortunately, the PDF looks much more like my printed output that I'd like. I have no idea why my printing looks so awful (only through KWord; oowriter2 looks fine), but that's a pretty accurate example of how bad it is.

      Other than the fact that I can't print from it, I love KWord. Of course, that's like asking Mrs. Lincoln how she liked the play.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:But it still can't print! by mortonda · · Score: 2, Informative
      PDF on the left and the on-screen on the right


      I'm usually really bad at seeing the difference between fonts, and yet, I can say that the text on the left still looks horrible. You can see it most in the word "be".
    3. Re:But it still can't print! by jbolden · · Score: 2, Informative

      Open the .pdf in a text editor. .pdf is a forth like language. Search for the text from your document and look for a font setting. You may be getting a very bad bitmap export. I think you have the printer setup wrong rather than a KWord problem (though the setup may be at the KDE level).

    4. Re:But it still can't print! by Anonymous Coward · · Score: 3, Informative

      i had the same problem trying to print to a pdf in any kde program, until i did this: in qtconfig, in the printer tab, i disabled "enable font embedding".

    5. Re:But it still can't print! by sootman · · Score: 3, Funny

      Just take screenshots of each page and print those. Duh. :-)

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
  8. Re:I still don't get it...... by Just+Some+Guy · · Score: 5, Interesting
    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.

    --
    Dewey, what part of this looks like authorities should be involved?
  9. Large documents by MagerValp · · Score: 3, Interesting

    How does KWord compare to MS Word when it comes to writing large documents? Our PhD students always run into problems with MS Word when they work on their dissertations. As the document grows larger, more and more weird things happen: footnotes jump around, images move to other pages, tables get resized for no apparent reason, and so on. We're mostly a Mac shop, so when Adobe decided not to make an OS X version of FrameMaker we kind of ran out of a decent alternative, but since there seems to be a native Mac port of KOffice I guess we should take a closer look.

    --

    READY.
    #
    1. Re:Large documents by wrong+un · · Score: 3, Informative

      Trust me, If you are writing a PhD thesis then a word processor is last thing you want to use. Open up a text editor and use LateX.
      It will save you loads of time and grief in the long run. Word documents are fine for 1 page memo's and the like, but if you want a beautiful looking manuscript there is only one option.
      I've seen people literally go mad trying to write their thesis in Word once the page count gets high.

    2. Re:Large documents by alexhs · · Score: 3, Informative

      I agree with the sibling AC : LaTeX is the perfect tool to write scientific publications.
      And if you don't like the "coding style" of LaTeX, you can use LyX.

      --
      I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    3. Re:Large documents by andersa · · Score: 2, Insightful

      I tried to write my bachelor thesis in KWord, but I had to give it up after 10 pages or so. Page breaks would happen inconsistently, so paragraphs would jump from page to page in an unpredictable manor. Also inline math looked increasingly bad as more formulas were added to the document. It also slowed down considerably.

      I went to Lyx instead. I didn't want to learn pure latex, and lyx worked like a charm, once you got the hang of it's little qirks.

    4. Re:Large documents by XchristX · · Score: 2, Informative

      Get kile (Latex frontend for KDE) from http://kile.sourceforge.net/ . It's latex rendering is clean, and you can look up latex markups from the menus (instead of having to break out Leslie Lamport's book every time you forget how to include well-indented graphics or whatever).

      --
      l'Homme n'est Rien l'Oeuvre Tout: Gustave Flaubert to George Sand
    5. Re:Large documents by XchristX · · Score: 2, Interesting

      Well, let me elaborate.

      I was at a seminar by an APS (American Physical Society) editing committee guy once, and he said that certain typesets render better on their mass printing systems than others (we are talking a worldwide distribution numbering in the hundreds of thousands), so they have been known to reject latex submissions with unnecessarily long or redundant typesettings (like people who use lots of $$ $$ instead of eqnarray{} and so on). He did not provide details.

      Don't look at me. He said so. Usually, they try to make the changes themselves. However, for very long papers (review articles etc) they don't bother, they just send 'em back until the author(s) fix them.

      I wrote my first paper in Lyx, converted it to Latex and submitted it to elsevier science in 1999. The rendering into dvi and postscript was fine . They sent it back, saying that the latex 'formatting' was poor and I had to do it 'better'. I took it to my research group secretary and he said the latex has to be much cleaner (I was only an undergrad back then and was new to latex). He re-edited the typesets and made it render the same content in the same way only the source was much cleaner and more organized (properly tabulated figures according to global templates, instead of what Lyx does, which is just \includegraphics followed by lots of \hspace* \vspace* for indentation).

      Of course, bear in mind that this was way back in 1999. I haven't used Lyx since, preferring to stick to original latex. I dunno if the latex export thingie in Lyx has improved or not. It's not a big deal for me anymore since I have a lot of predefined stuff in latex for my papers and just recycle those.

      --
      l'Homme n'est Rien l'Oeuvre Tout: Gustave Flaubert to George Sand
    6. Re:Large documents by colinrichardday · · Score: 2, Informative

      It's not too difficult to make a LaTeX stylesheet to satisfy your university's dissertation-formatting requirements.

  10. Re:Kcrappy Knaming Kscheme by tepples · · Score: 5, Insightful

    As long as they keep giving their software stupid names by sticking a "k" or a "g" on the front of it this software will never appeal to anyone but the Linux zealots (a.k.a. "Power" users).

    As long as they keep giving their software stupid names by sticking a "microsoft" or a "i" on the front of it this software will never appeal to anyone but the Windows and Mac OS zealots (a.k.a. "Least Common Denominator" users).

  11. Uh.... by Sir+Unimaginative · · Score: 5, Insightful
    The really awesome thing about OpenDocument is that the suites never have to merge.

    And you're right, it won't ever happen. Because some people will want some killer feature only KOffice has, and some people will want some feature only OpenOffice has.

    Unity? Pah. The whole point of open source is that unity is neither necessary nor (typically) desirable. If you CAN use the same stuff in ANYTHING, ON anything, WHY would you want to use it in only ONE thing?

    --
    The problem with your idea is that it makes sense.
  12. Krita by psocccer · · Score: 4, Informative

    Anyone who's ever complained about the gimp needs to check out Krita, the paint application in KOffice. As of 1.5, it now has support for adjustment layers and layer groups, 2 of the things I missed most in the gimp. It also has CMYK support and does not have separate windows for all the tools (something that never bothered me but soooo many people complain about it). The difference between 1.4 and 1.5 of Krita is absolutely amazing, I figure give them 6 more months and they will have passed gimp in functionality. Too bad Krita is KDE only though, so no help for windows users looking for a good free photo editing suite.

    1. Re:Krita by Kjella · · Score: 4, Informative

      Too bad Krita is KDE only though, so no help for windows users looking for a good free photo editing suite.

      Yet. Qt4 for Windows is GPL, KDE is moving to Qt4 which means it'll run on Windows eventually. You can still make it happen today with Cygwin, but that's not a consumer-friendly solution. Give it 12 months and you can probably run Krita on Windows.

      --
      Live today, because you never know what tomorrow brings
    2. Re:Krita by vurian · · Score: 2, Informative

      Er, Krita does support RAW pictures. I should know, I coded the support myself. You need to have dcraw installed, though.

  13. Poor table support by GeekBoy · · Score: 2, Informative

    I'd love to use it, but the table support is sooooo bad compared to OOW or MS Office that I just can't use it.

    1. Re:Poor table support by zander · · Score: 2, Informative

      No, we didn't work on Table support very much, we just made it crash less on tables. You, for example, still can't have a table bigger then a page.

      Tables will be re-done in 2.0, most probably.

  14. Re:Kcrappy Knaming Kscheme by Kjella · · Score: 2, Insightful

    As long as they keep giving their software stupid names by sticking a "k" or a "g" on the front of it this software will never appeal to anyone but the Linux zealots (a.k.a. "Power" users).

    Aww, that isn't even a good troll anymore. At least you could take it one step further to the root of the issue and say it'll never appeal to anyone but Linux zealots as long as you need to prefix it with "k" or "g" to indicate what toolkit it uses, which endusers shouldn't have to give a fuck about. If it was just the name it wouldn't be any greater issue than iMacs with iLife, the iUniverse and iEverything.

    --
    Live today, because you never know what tomorrow brings
  15. LaTeX? by rmcd · · Score: 5, Informative

    This is off-topic but may be a help to you. I don't know what academic area your ph.d students are in, but in the sciences, math, and economics, the use of LaTeX is very common. (I'm guessing if you were in one of those areas you would already know about it.) LaTeX performs wonderfully with arbitrarily huge documents --- I published a 900-page book using it. On the other hand, if you need to do a lot of fine-grained page-by-page formatting, it probably isn't for you. There are LaTeX solutions for the Mac, but I haven't used them.

    To be honest I find Word to be a mess. I know some people love it but I find it unusable.

    1. Re:LaTeX? by brwski · · Score: 5, Informative

      Mac solutions rock: TeXShop + XeTeX is a powerful combination. LaTeX simply can't be beat for consistency and ease of use once the basics are put to memory.

      --

      brwski
      "Because without beer, things do not seem to go as well''

  16. Re:what i'd like to see.. by Motley+Phule · · Score: 2, Informative

    Of course adding together two pieces of software and two software teams does not automatically create a superior product - despite what Darth Gates and Micro$oft would have you believe.

  17. Re:I still don't get it...... by cozziewozzie · · Score: 4, Insightful

    People are a bit confused about this "KOffice is only KDE" business.

    A modern office suite needs to build on top of a really solid foundation in terms of widgets and supporting library.

    OpenOffice (and StarOffice before it) chose to design everything from scratch. Every menu, every window, every pixel is hand-drawn by the program itself. They have a very powerful toolkit in VCL which DUPLICATES all that a toolkit should do. They coded all their dialogs from scratch, font handling from scratch, print support from scratch. Skins and themes - from scratch.

    Basically, OpenOffice folks wrote half an operating system to make their office suite. Mozilla did something very similar. And then people wonder where the bloat is coming from!

    There is another way to write applications. You look around, and see that there is a very very powerful library foundations out there. You get menus for free. Dialogs. Font handling. Network transparency. Buttons. Canvas. Printing. Image input/output. Sound. This set of libraries is called KDE, although you could use GNOME to a similar extent.

    Why on Earth should KOffice people reinvent the wheel yet another time, when there is a very powerful library that does all of this already?

    If you download OpenOffice.org, in its 300 MB, you download a whole toolkit plus half an operating system in bloat.

    If you download KOffice, just download kdelibs while you're at it. You don't need the rest of KDE! Just look at it as another library providing functionality.

    We shouldn't go back in time and recode each menu pixel-for-pixel in every single application. StarOffice did this out of legacy reasons and now we're stuck with it. But in this day and age, people use libraries which take care of this stuff, so you can concentrate on functionality.

  18. Re:KOffice by cozziewozzie · · Score: 2, Informative

    It will when version 2.0 (built on KDE 4 and Qt4) comes out.

  19. Re:what i'd like to see.. by rduke15 · · Score: 2, Insightful

    if I saw koffice and openoffice merge

    I certainly hope they don't. KOffice may be one of the very few chances we have to escape the awful bloatwares and clumsywares that are both MS-Office and OpenOffice. I haven't tried KOffice yet, but I sure wish it is very different.

    (BTW, TextMaker despite it's drawbacks (not free, not Open Source, proprietary file format) is the only usable Linux/Windows word processor I have seen so far. Before Linux there was Ami Pro, but unfortunately that is long dead)

  20. Re:ko or ooo? by gnud · · Score: 3, Informative

    Natively, through QT4. No X server, but not on Aqua.

  21. Why I'm using KOffice by Anonymous Coward · · Score: 4, Interesting

    I'm running Debian Sarge, so my version of KOffice is a bit dated compared to the bleeding edge out there. But the version that made it into Sarge is good enough.

    I had previously shied away from KOffice/Kword because although the earlier versions offered the ability to save/print to pdf file, the pdf file it created sometimes wasn't compatible with Acroread or Windows or even OO.org. So when creating docs with earlier versions of KWord, just to be sure, I'd save the file as ps, then open a shell and use ps2pdf to convert, and everything worked ok. In order to avoid that, as OO.org hit 1.1.x then 1.2.x then 1.3.x, I started using OO.org more and more, especially because its export to pdf button worked flawlessly every time. Still does. But events have conspired to bring me back into the KOffice fold.

    OO.org is just too resource intensive. When I need to create a short document, if kword/kate or vim aren't good enough for lack of features, I found myself trying to think of alternatives rather than fire up OO.org and watch it eat up memory and slow everything down. So I apt-get installed KOffice again after purging it, and installed all the KOffice related recommends/suggests, and found that it had advanced enough to the point of my liking it. That's a change because just a few versions back I was really disappointed in the pdf problem, the limited number of other file formats it was capable of saving to with those formats being compatible with the same formats on other applications, etc.

    Now, the number one reason I'm using KOffice almost exclusively is because I can't print from OO.org, Mozilla/Firefox, or some other applications. I have an HP4+ printer plugged via parallel port into a knoppix desktop running from the CD drive. It's running cupsd, and I'm printing either directly from the knoppix desktop, or printing from other desktops logged into the file server via ssh, using the identities on the file server. Previously, I had an Epson ink jet printer plugged into the knoppix via cupsd, but changed the printer to the HP a while back. Changed the configurations in cupsd and cups in /etc on the knoppix acting as the print server, plus the desktop cups clients. KWord, and all the KDE apps picked up the change, correctly showing the HP and being able to print to the HP after I added the HP via the cups administration interface and checking the config files as needed. But OO.org and Mozilla and Firefox all show the old setup and I'm unable to print from them because they aren't showing/connecting to HP printer via cups. They show the old Epson printer, and the settings that I added for another printer (just testing) when the Epson was still hooked up.

    I went to the OO.org site and followed the how-to for setting up a printer, but I still couldn't get it to work. It was a while ago, but I think I also went to the Firefox site to look for help, and went through the Mozilla/Firefox help menus to try and find help, but I still can't print from OO.org, Firefox, and now that I think about it, Acroread and possibly xpdf as well.

    So I think I'm missing an entry in another config file where OO.org and Firefox and Xpdf and other non-kde apps look for info on what printers are available. Luckily, kde apps are using some other method to list available printers, so if I need to create something in OO.org, I reopen it in Kword or create a pdf and print it through kword or kpdf. If I have a web page opened in Firefox or Mozilla that I need to print, I have to re-open the page in Konqueror before I can print it.

    As long as my situation lasts, I'm hoping that KOffice gets better and better before Etch hits stable, and continues to get better after that. I'm semi-hooked and getting in deeper as time passes.

    1. Re:Why I'm using KOffice by Maltheus · · Score: 2, Informative

      Google "openoffice kprinter". You can print from those apps, using the KDE print manager. I just don't like doing it that way. But I feel your pain.

  22. Try OO.org 2.0 by linuxkrn · · Score: 2, Informative

    That is in OO.org 2.0+, so you'll have to wait until you can use the 2.0 version to get ODF in OO.org

  23. Re:I still don't get it...... by adtifyj · · Score: 3, Insightful

    OpenOffice inherited a lot of this bloat from its predecessor, StarOffice.

    Also, a more appropriate comparison is that the OpenOffice codebase includes a subset of the KDE functionality. This "bloat", written to be cross-platform from the outset, is why OpenOffice works on Microsoft Windows now, and KOffice does not.

  24. Re:I still don't get it...... by m50d · · Score: 2, Interesting
    Also, a more appropriate comparison is that the OpenOffice codebase includes a subset of the KDE functionality. This "bloat", written to be cross-platform from the outset, is why OpenOffice works on Microsoft Windows now, and KOffice does not.

    No, that's coincidental. Look at audacity for something happy to use an existing library and very crossplatform. And look at say xine for something that implements its own widgets and is still linux-only.

    --
    I am trolling
  25. Re:Kcrappy Knaming Kscheme by bipolarpinguino · · Score: 2, Interesting

    Wait... are you trying to say that you changed your whole desktop environment because you did not like its naming scheme. I'm sure there are many valid reasons (I have yet to come across any, mind you) for using gnome over kde, but the preference of 'g' over 'k' is not one of them.

  26. Linux vs Windows naming by mopslik · · Score: 3, Interesting

    To me the K is fine, but some of the Linux application names are just dumb. Take Pico, GIMP, and GAIM. Who would of thought that they are a text editor, image editor, and IM apps, respectively?

    You're right. Applications should have clear and consise names that reflect what they do, like Microsoft Excel...

    Certainly not me, and according to usability studies not by many other users either.

    The GIMP's name affects its usability? I assumed the less-than-stellar UI was what causes issues, not some silly name. I guess that's why the iPod was so unsuccessful too, since you can't tell it's a music player from its name.

    Linux wouldn't be where it is today without its user interface, and that is of course, how Windows became so popular.

    The one "borrowed" from Apple/Xerox?

    For the Linux users that say, well its an "expert" interface

    By "Linux" I assume you mean KDE, or Gnome, or XFCE, or TWM, or any number of window managers or desktop environments that run atop the kernel. Of course, you can choose whichever interface is most appropriate to your tastes/tasks: KDE gives you immense customization ala Windows, GNOME strives to keep things simpler, etc.

    Linux will only become more dominate with a better UI

    I fail to see how KDE or GNOME will ultimately fail in this respect, with my preference going to the former. But YMMV.

  27. Re:Kcrappy Knaming Kscheme by Millenniumman · · Score: 2, Insightful

    K names like KOffice aren't that bad. They make it clear what the software does. It's Ubuntu, GIMP, etc. that seem like bad names to me. Not only do they have no relation to the software, but they aren't words. I sort of like iNames better than k/gNames only because i somehow seems better. The non-i OS X applications have very good names in my opinion.

    --
    Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
  28. Re:MS Word import quality? by Anonymous Coward · · Score: 2, Informative

    Sounds like you're using OpenOffice.org 1 or don't have the MS Core Fonts installed. Try OO.o2 and install the MS Core Fonts (Times New Roman, Verdana, Arial, blahblah).

  29. why kspread sucks by Arthur+B. · · Score: 2, Insightful

    experiment: A0 = 0 An+1 = An + normsinv(rand()) plot A0 to A1000, go get a cup of koffee gnumeric is the only decent excel competitor in that area

    --
    \u262D = \u5350
  30. Re:LyX by gatzke · · Score: 3, Informative

    I have not used gnumeric much, but it looks like it may be able to do tables in latex.

    I also found a csv2latex application, that would be nice as well.

    Thanks!

  31. Re:Kcrappy Knaming Kscheme by TeknoHog · · Score: 2, Funny
    Oh so using Windows makes me part of the Least Common Denominator guys, great. Where's the holy temple I can praise you, oh almighty Linux user?

    Here.

    --
    Escher was the first MC and Giger invented the HR department.
  32. Re:Kcrappy Knaming Kscheme by ablaze · · Score: 2, Insightful

    Actually your comment is very Euro- or American- centric. And it's a shame!

    Ubuntu _is_ a word indeed. It's Swahili for "humanity".

    To quote http://www.learning-org.com/97.05/0042.html:

    "A literal translation of the word 'ubuntu' would be 'humanity'. Old
    dictionaries will show that the word humanity in English had a very rich
    meaning: 1 humans collectively, 2 human nature, 3 human quality, 4
    educated, 5 civilised, 6 humane and dignified. But as the information
    overload increases, the richness of the word has immerged in the ascending
    order. The pollution of information leads to the trivialisation of
    knowledge. Now only meaning 1 probably survives. However, the word
    'ubuntu' still has all six meanings in ascending order of emergent
    importance! The deepest or highest meaning of ubuntu is thus to become
    humane while behaving with dignity. Let us not pollute and thus trivialise
    this word ubuntu!"