Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Open Source Software Technology

LibreOffice 5.0 Released 236

New submitter ssam writes: The Document Foundation has announced LibreOffice 5.0, the tenth major release since the launch of the project, bringing new features including Windows 10, Android and Ubuntu touch compatibility, superior interoperability features, an updated UI, and lots of under the hood improvements. For people still running OpenOffice it is probably time to move over.
This discussion has been archived. No new comments can be posted.

LibreOffice 5.0 Released

Comments Filter:
  • by Maddog Batty ( 112434 ) on Wednesday August 05, 2015 @10:14AM (#50256017) Homepage

    So what is the story between the two? I know that LibreOffice is a fork of OpenOffice and that some/most/all of the devs moved to LibreOffice.
    Is LibreOffice now far enough ahead to say forget about OpenOffice?

    • by nine-times ( 778537 ) <nine.times@gmail.com> on Wednesday August 05, 2015 @10:35AM (#50256197) Homepage

      Well, LibreOffice just hit version 5.0, while OpenOffice is at 4.1.1. Obviously, LibreOffice is exactly 0.8.9 amount better.

    • by dbIII ( 701233 )
      It was club level politics with people who wanted to be in charge but didn't have the time to run the project in one camp and others that wanted to get stuff done in another. With open source if you take your ball and go home the game still continues.
    • by JImbob0i0 ( 1202835 ) on Thursday August 06, 2015 @09:37AM (#50262729)

      I wrote about this on reddit only recently ... Link to the discussion there [reddit.com]

      Copied in full to here:

      So back when Sun maintained OpenOffice.org and sold StarOffice they had a Contributor License Agreement that required handing over ownership of patches to them so they could sell the closed source supported suite and license out to IBM for Symphony.

      To get around this bureaucracy and to not sign over ownership for patches most distributions used go-oo.org (aka ooo-build) that was the source code of OpenOffice.org with a bunch of patches on top to help compatibility with MS Office and some other things that Sun could or did not want in the upstream oo.org code.

      When Oracle bought Sun they left oo.org languishing with no maintenance for months. This was naturally unacceptable to the various linux distros and they didn't want to be beholden to Oracle's whims (for good reason given the state of the various projects that used to be with Sun). Due to this they got together and formed The Document Foundation [documentfoundation.org] and took the go-oo.org code (which was basically what this group used and collaborated on anyway) and forked it to LibreOffice.

      Fast forward some more time and Oracle decide they don't want anything to do with OpenOffice.org after all and essentially (with IBM's help ... presumably so there would be a sort of maintained base for Symphony) dumped it on the Apache Software Foundation. As per their requirements it went through an incubation process and all the code was relicensed to the Apache Public License. This was months after LibreOffice had been created and worked on and most consider it a pretty petty move rather than giving the brand to TDF to work with.

      From that point on it's pretty much been IBM driving Apache OpenOffice (as they renamed oo.org to) although they appear to have stopped caring about it mid to end last year. The amount of development work on AOO is minimal compared to LO and the number of active committers is in the teens (at best) for AOO compared to the hundreds for LO.

      Due to the way the licensing works out LO can merge in any fixes (there were some in the early days, not many now as can be seen in the CVE issue I mentioned) but AOO cannot merge in work from LO.

      The last release of AOO was August 2014 and if you go look at the changelogs from 3.4 (the first AOO release as opposed to oo.org IIRC... mostly rebranding) up to the 4.1.1 then you'll see there's been minimal work - mostly translations. Anything developed/fixed in AOO is either merged into LO or improved/obsoleted by other work. Compare these to the release notes for each LO release from the forking point of 3.3 and it really is quite significant - the heavy work on clean up and better build systems for LO lower the barrier to entry for LO contribution by the common person too.

      The proposed AOO release of 4.1.2 is going forwards at the moment - driven mostly by only a few people Apache OpenOffice Dev mail archives [apache.org].

      To give an idea how bad this has got the no-interaction code execution as privileges of user bug by a special HWP file was announced publicly last April. It was fixed in LibreOffice the same month and users would have had the update notification and been protected. Anyone using Apache OpenOffice is still vulnerable and although there was a disclosure on the security part of the AOO site at the time, the workaround was to 'delete .dll/.so' ... not a release with a fix and unless anyone actively went to check up on this they would not have known the issue.

      To add to this (if it's not enough already) AOO can still only read and not write docx/xlsx/pptx (OOXML) files produced by MS Office whereas LibreOffice can

  • by LichtSpektren ( 4201985 ) on Wednesday August 05, 2015 @10:20AM (#50256061)
    LibreOffice now supports amd64, which is a huge boon for people that work with very large documents. It purports to have better .docx compatibility, although I myself have found that MSWord is more likely to screw up the formatting in .docx documents than LibreOffice is. All-in-all, a good day for free software, and a bad day for Microsoft.
    • by jkrise ( 535370 )

      According to the summary, the Android version of LibreOffice is available. Does it mean I can now edit my docs, spreadsheets and ppts on my smartphone if I want to?

    • If your documents are large enough that you run into file size limits on 32-bit systems, you're using the wrong tool for the job. Word was painful with 50+ Mb in one document, I shudder to think what a Gb-sized document will do.

  • by Anonymous Coward on Wednesday August 05, 2015 @10:21AM (#50256067)

    Having no release manager and no one contributing code for 9 months seems like more of a "Dead but hasn't stopped twitching" sort of state.

    • Having no release manager and no one contributing code for 9 months seems like more of a "Dead but hasn't stopped twitching" sort of state.

      Dev and user lists are still very active. I would hardly consider AOO to be "dead" by any means.

      • Re: (Score:2, Informative)

        by Anonymous Coward

        If you consider mails on the dev list about buildbots down and how to find a release manager and a resigning project chair to be "very active" ...

    • by Translation Error ( 1176675 ) on Wednesday August 05, 2015 @11:54AM (#50256877)
      Don't worry! I'm sure SourceForge will revive it and add a shiny new installer!
  • I like the old UI. It works well for those of us who are working on desktops and laptops.

    Hope they have the old UI or something similar as the default when it realises you don't have a touch screen.

  • Oracle Happened (Score:5, Informative)

    by BrendaEM ( 871664 ) on Wednesday August 05, 2015 @10:36AM (#50256207) Homepage

    Oracle bought out Sun. When they looked at their IP portfolio, they appeared to have lost their minds, and assert their ownership over several open-source projects. Yes, I believe it was some 26 programmers who left Open-Office and started LibreOffice. Then Oracle was falling out of brainshare, and didn't seem want to appear as an orgre, but it was already out of its cave by then.

    What happened: Oracle's possessiveness made LibrieOffice into the superior office suite it is today!

    • It would be in poor taste to mention that, I hope the wall Oracle is pounding it's head against over this has a coat-hook somewhere on it, so I won't.

    • Yes, I believe it was some 26 programmers who left Open-Office and started LibreOffice.

      Not quite. There were only 3 people that actually founded LibreOffice; everyone else were more or less lemmings in the matter, and those three made decisions "for the community" when they wanted the decision to go a certain way even before the community was finished discussing the matter (f.e CLA's). That's why I dropped out of TDF/LO - it wasn't really a community.

  • Why did apache foundation agree to take on responsibility for openoffice? It was kind of a poisoned chalice.

  • Is there anything out there that straightforwardly automates databinding LibreOffice controls to an XML data structure?

    I'm talking primarily about controls where you can type in text and that text will automatically appear in other content controls that are bound to the same XML data node.

    I've done it in Word via VBA, but it's not something that I would recommend for others to use. Is there something like this for LibreOffice that makes the process easy for the user.

  • LibreOffice 5.0, the tenth major release

    Version 5 = 10th major release? Were they using excel [joelonsoftware.com] to calculate their version number?

    • No, they just count each x.y as a major release, which is not unreasonable since there is quite a lot of new features going in to each of them. They started out at 3.3 since that's where they forked from OpenOffice; so there have been 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.2, 4.3, 4.4, 5.0. That gives 5.0 as the tenth major release.
    • by dbIII ( 701233 )

      LibreOffice 5.0, the tenth major release

      Version 5 = 10th major release? Were they using excel [joelonsoftware.com] to calculate their version number?

      It's almost as bad as going 3.11, 95, 98, ME, 2000, XP, Vista, 7, 8, 10.

  • I don't understand why either of these guys (Open OR Libre) can't get their act together and implement something with the functionality of MS Word's Outline Mode. This has probably been the singe most requested feature in Open/Libre Office for *years* (requests go back to at least 2002), and it has steadily been ignored. It's the *only* reason I continue to use Word...

    • by dbIII ( 701233 )
      While I've been asking MS for a "show codes" feature in MS Word since before 1995.
      Some things that people think will be very useful are just not cared about by the people releasing software.
  • If your distro (e.g. CentOS 6) doesn't carry the latest LibreOffice release, then you have to download it from the official LibreOffice site. Unfortunately, a litany of RPM packaging disasters [richardlloyd.org.uk] still abound with 5.0. I've never seen any Open Source software as badly RPM-packaged as the official LibreOffice RPMs!

  • by ShieldW0lf ( 601553 ) on Wednesday August 05, 2015 @03:01PM (#50258509) Journal

    We've only been doing word processors for decades now.

    Why do word processors need new features at this point? Why is this not a "done" thing?

    So many software projects are destroyed by the inability of developers to say "Well, that tool is finished."

    When are we going to see LibreOfficeOS, I wonder. It kept the browser developers amused, maybe you guys should do that?

    • by steelfood ( 895457 ) on Wednesday August 05, 2015 @04:36PM (#50259111)

      That's because MS Word and L/OO Writer are not word processors anymore. They're WYSIWYG document creation tools, i.e. they attempt to combine text input, text management, and document layout into one tool.

      Besides which, word processors aren't feature complete yet. Even advanced text-only word processors like Textpad and Notepad++ are constantly adding new features, and has a leg up on Word/Writer on things like search and cursor movement.

      And with persistent connectivity, there's a whole new layer of features for everyone to add.

      • by Osgeld ( 1900440 )

        They're WYSIWYG document creation tools

        they have been since the mid 80's and still do the same job as my mac SE, so back to the op...

      • by dbIII ( 701233 )

        That's because MS Word and L/OO Writer are not word processors anymore. They're WYSIWYG document creation tools, i.e. they attempt to combine text input, text management, and document layout into one tool.

        They attempt to do it but still fall short of the desktop publishing stuff of the early 1990s, which is probably just as well because a lot of features to tweak can be a serious time sink. That leaves it neither fish nor fowl, a kitchen sink full of parts that has way more than you need for one task but n

    • > Why do word processors need new features at this point?

      Unicode for multiple languages, and the desire to embed graphics.

  • So LO has a few more features, and hopefully fixed a few bugs.

    But there is still no decent writing tool for our current needs.

    When I need to write something, it usually doesn't need to be printed on A4 (or Letter) paper. It is to be viewed on some digital display. And it doesn't need to be pixel-precise. Just well structured to be understandable. So the natural format would be HTML with CSS, which has become a universal format that can be displayed on anything, and can even be searched as plain text with grep and the like when needed.

    But there is no word processing program that produces sane HTML/CSS. The real word processing programs which have all the features and tools to help for writing produce totally insane HTML. The HTML tools are designed for programmers or "web designers" (whatever that really is these days), not for plain writing of content. In the end, I often just send an HTML email done in Thunderbird, or I use Amaya, and mostly a plain text editor with a browser window to re-read it. But none of this is a comfortable solution. The alternative is to write in MS Word or Libre/OpenOffice, and produce a f*ing PDF.

    I have been longing for a modern "Ami Pro for HTML/CSS" for the last 15 years...

    • by msobkow ( 48369 )

      1. Create .html text file
      2. Open .html text file in browser
      3. Write content in text editor.
      4. Save file.
      5. Refresh browser window
      6. Fix any broken tags
      7. Lather, rinse, repeat.

      If all you're doing is creating content, that's all you need to do. If you want fancy WYSWIG features, you're barking up the wrong tree to expect to do it with "real" HTML support. WYSWIG implies that you have precise control over layouts; HTML presumes you have no precise control over layouts. The goals are incompatible.

  • Button icons were huge at first, but i figured out how to fix that.

    I don't really like the sidebar thing. Minimizing it is easy, but then there's a very dark, very obvious, poorly aligned button on the right side. Preferably i'd like to remove it entirely, but getting the color toned down might be an acceptable alternative.

    They still have the messed up column and row header colors. Back in 2.1 the headers were a nice solid dark grey. Then sometime between then and 3.4 they added shading. The "inner" hal
    • Addendum: there is apparently no longer any local help. Going to Help->LibreOffice Help opens up a browser window to the online documentation. Searching for help on the internet is fine in general, but the search results in this site seem very cluttered and it seems far less convenient than the offline help present in OO 3.4.1. Not to mention the fact that i frequently have to use VPN software at work that disables my regular internet.
      • Did you miss the (large green) LibreOffice Built in help in English (US) download link that is located right below the Main Installer download?

        • by Daetrin ( 576516 )
          Actually i did miss it. The large green button is actually a deterrent in this case. It's such an eye-searing shade that my eyes keep automatically trying to skip over it to save themselves. (I also didn't notice it on the first page because it was below the bottom edge of the window, but it also shows up in all its painful glory on the donation page you get redirected to after hitting download.)

          Thanks for pointing it out though!

Avoid strange women and temporary variables.

Working...