Brandon Taylor <firstname.lastname@example.org> writes:
> Okay. Well, I've gone ahead and installed LibreOffice, which took care of the "missing 'soffice'" problem, but like a frustrating game of Whac-A-Mole,
> another problem popped up. Now I'm left high and dry as to what might have happened, because after adding the location of soffice.exe in my
> Windows PATH environment variable, I get the following output:
> Executing soffice --headless --convert-to odt --outdir "c:/Users/donni/OneDrive/Documents/" "c:/Users/donni/OneDrive/Documents/belvoire.odt"
> Export to c:/Users/donni/OneDrive/Documents/belvoire.odt failed
> with absolutely no rhyme or reason as to what went wrong.
You can try turning on debug on error with
which might give you a backtrace that will provide more details.
I would also try executing the command
soffice --headless --convert-to odt --outdir "c:/Users/donni/OneDrive/Documents/" "c:/Users/donni/OneDrive/Documents/belvoire.odt"
at a command prompt and see if you get any additonal information. I've
not done odt exports of org files, but that command line looks odd to me
- it looks like it is trying to convert an odt file to odt?
I suspect you will have a hard time getting all this to work on Windows.
It is possible, but as Windows is not a 'preferred' platform, you have a
significant amount of configuration/customisation to do to get it
I never use Windows, so cannot provide much help of any real substance.
I do wonder if it might be easier if you use WSL?