PortableApps.com and The Document Foundation are proud to announce the release of LibreOffice Portable 3.4.3. LibreOffice Portable is a full-featured office suite -- including a word processor, spreadsheet, presentation tool, drawing package and database -- packaged as a portable app, so you can take all your documents and everything you need to work with them wherever you go. This release updates LibreOffice to the latest version and improves performance. LibreOffice Portable is packaged in PortableApps.com Format so it can easily integrate with the PortableApps.com Platform. And it's open source and completely free.
LibreOffice is packaged for portable use with permission and assistance from The Document Foundation
Update automatically or install from the app store in the PortableApps.com Platform Pre-Release.
Features
LibreOffice Portable is a full-featured office suite that's compatible with Microsoft Office, Word Perfect, Lotus and other office applications. It's easy-to-use and feature-rich, performing nearly all of the functions you'd expect in an office suite, but at no cost.
Learn more about LibreOffice...
PortableApps.com Installer / PortableApps.com Format
LibreOffice Portable is packaged in a PortableApps.com Installer so it will automatically detect an existing PortableApps.com installation when your drive is plugged in. It supports upgrades by installing right over an existing copy, preserving all settings. And it's in PortableApps.com Format, so it automatically works with the PortableApps.com Suite including the Menu and Backup Utility.
Download
LibreOffice Portable is available for immediate download from the LibreOffice Portable homepage. Get it today!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Comments
Test Fix To Install To Paths With Spaces
As many people know, LibreOffice has a bug that prevents it from running properly from paths with spaces in them in the way it handles paths to settings. We have a test patch that will enable this functionality, but it hasn't been thoroughly tested to ensure it won't interfere with any other functionality (like addons, Java, etc on all systems). So, we've made it available as a test patch here:
https://portableapps.com/node/29183
Please test it out on different operating systems with Java and without and report your findings in that thread. The more folks we get testing it, the faster we can call this feature addition stable and push it out for everyone.
Why not call it a Beta or 'Unstable' ?
If functionality is not what it should be (compared to the previous release) and more testing is needed, why didn't you give it a Beta status ? Or call it 'Unstable'? Having read this I will not upgrade until I am confident my productivity won't be damaged.
Misreading It
You're completely misreading what I wrote. The released versions of 3.3.4 and 3.4.3 are stable. The fix that I linked to in the comment you replied to enables a new feature not in the current (or previous or previous to that) stable release that many people like. But as this fix hasn't been tested, it would be irresponsible of us to include it in the stable releases and still call them stable.
So, the feature addition is made available as a patch so people can test out this new feature BEFORE we add it to the stable releases of the apps. Essentially, what I posted about was to preserve stability in the main releases AND make available a feature that's not fully tested for users who want to test it.
Misread...
So, this is a fix for an old bug that was existent in LibreOffice versions ever before this one ? In that case I did indeed misread your notice. Thanks for clarifying that !
Years
The issue with OpenOffice.org and LibreOffice being unable to be manually pointed to a settings directory with a space in it has existed for years.
FWIW
This version in the 3.4.x LO series opens without problems on my WinXP system, which was not the case with the previous 3.4.x release. As I recall, at least one other user had a similar issue. Looks like progress is being made with working out the bugs.