Here's the generated backtrace after doing M-x toggle-debug-on-error and then trying to do export on Windows. Debugger entered--Lisp error: (rng-uri-error "Bad escapes in URI ‘file:///c:/Program%20Files/Ema...") signal(rng-uri-error ("Bad escapes in URI ‘file:///c:/Program%20Files/Ema...")) rng-uri-error("Bad escapes in URI `%s'" "file:///c:/Program%20Files/Emacs/x86_64/share/emac...") rng-uri-file-name-1("file:///c:/Program%20Files/Emacs/x86_64/share/emac..." nil) rng-uri-file-name("file:///c:/Program%20Files/Emacs/x86_64/share/emac...") rng-locate-schema-file() rng-auto-set-schema(t) rng-validate-mode(1) rng-nxml-mode-init() xml-mode() set-auto-mode-0(xml-mode nil) set-auto-mode() normal-mode(t) after-find-file(nil nil) find-file-noselect-1(# "c:/Users/donni/AppData/Local/Temp/odt-s6F4yN/style..." t nil "c:/Users/donni/AppData/Local/Temp/odt-s6F4yN/style..." (6755399441121385 3391104951)) find-file-noselect("c:/Users/donni/AppData/Local/Temp/odt-s6F4yN/style..." t) org-odt-template(#("\n\n :input-buffer "belvoire.org" :input-file "c:/Users/donni/OneDrive/Do..." :odt-styles-file nil :description nil :keywords nil :subtitle nil :odt-content-template-file nil :odt-display-outline-level 2 :odt-fontify-srcblocks t ...)) org-export-as(odt nil nil nil nil) org-odt-export-to-odt(nil nil nil nil) org-export-dispatch(nil) funcall-interactively(org-export-dispatch nil) call-interactively(org-export-dispatch nil nil) command-execute(org-export-dispatch) Sent from Mailspring (https://link.getmailspring.com/link/2D4DFACA-A01A-4F4C-9162-46E73035B8BA@getmailspring.com/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=ZW1hY3Mtb3JnbW9kZUBnbnUub3Jn), the best free email app for work On Jun 26 2021, at 11:05 pm, Tim Cross wrote: > > Brandon Taylor 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 > M-x toggle-debug-on-error > 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 > working. > > 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? > > -- > Tim Cross >