I've posted a test fix that enables LibreOffice Portable to use spaces in paths. You can right-click and save the below file to your local machine:
Then copy it to your LibreOfficePortable\App\AppInfo\Launcher directory in either the 3.3.4 or 3.4.3 release of LibreOffice Portable. This should allow the app to work from paths with spaces (example: X:\Portable Apps\LibreOfficePortable).
This fix was not included in the LibreOffice Portable 3.3.4 and 3.4.3 releases as there wasn't enough time to give it a proper shakedown to ensure it didn't affect any features or functionality. It may impact some less-used features within LibreOffice itself or Java integration on some systems. So, please test this in different configurations to ensure this works properly so we can push it out to everyone. Note that this does not fix the issues with LibreOffice crashing when installed to longer paths.
Once testing is complete, we will likely push this out as a revision. We'll be posting a simple patch file as a small download (couple hundred KB) for existing users to be able to update instead of requiring a full download of the new version.
Thanks for testing!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
At least, this fix work for me regarding get LibreOffice starting. Haven't tested much more, yet.
Nevertheless, the fix tends to slow down starting LibreOffice. This is just an impression and not an exact measurement. In my opinion LibreOffice started in 2-3 seconds before and now (by adding the fix) it needs 4-5 seconds. Am i right?
Nevertheless, this is something i can live with. Thank you so much for the fix.
The changes, for those who care:
[Launch]:NoSpacesInPath=trueremoved[FileWrite2]:Valuechanged fromfile:///%PAL:DataDir:ForwardSlash%/settingsto$ORIGIN/../../../Data/settingsNow, some comments (or rather questions):
I presume that $ORIGIN is a special value; is there any other variable that we could use to achieve a similar result without the icky
..parts?This looks as though it would still work in live mode, but is it possible for LibreOffice to run from a read-only medium? If it was then it would be strongly desirable to set [LiveMode]:CopyApp=false, except that then after this patch that would break (as Data would be on a different drive to App).
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
As all the variables are internal to the LibreOffice path, you need those parent directory dots. With an externally set variable set to a standard Windows path (PORTABLEDATAPATH=%PAL:DataDir%\settings), it fails. With an externally set variable set to a forward-slashed path (PORTABLEDATAPATH=%PAL:DataDir:ForwardSlash%/settings), it fails. With an externally set variable set to the old value (file:///%PAL:DataDir:ForwardSlash%/settings) it starts but it does not properly pass the full path to certain things within LibreOffice and a path like X:\PortableApps\LibreOffice Portable gets shortened to X:\PortableApps\LibreOffice in certain locations which become evident in the registrymodifications.xcu file. That shortened directory gets created by LibreOffice and things get placed in it.
Sometimes, the impossible can become possible, if you're awesome!