That error would tend to indicate there is a problem with the way the
file uri is being encoded. This could either be a bug or it could be due
to an error in your configuration or possibly the original org file your
trying to encode. Unfortunately, in that backtrace output, I cannot see
the full uri. I would start by looking at the full uri and seeing if you
can spot what is wrong with the encoding and identify where that uri is
coming from (i.e. your config, a link in the org file your trying to
Here is what I would do -
- Create a minimal basic org file which generates the error when you try
to export to odt
- Post that minimal org file, together with details on your Emacs
version, org-mode version to the list. You might be lucky and someone
else on Windows will be able to use your test org file to see if they
get the same error when exporting to odt. Maybe someone not on windows
can also try exporting it to verify it is not a platform independent
bug. See M-x org-submit-bug-report for a straight-forward way to
generate the email.
- Try running emacs -Q and then adding a minimal config to get org odt
export to work and verify you still get the error. This may help
identify bad local config, bad org installation/update or issue with org
version you have.
The objective here is to provide all the information necessary for
someone else to try and reproduce your issue. This will help in
determining whether you have a real org or emacs bug, a local
setup/config error or a problem in your org file.
BTW it probably would be worth running org-lint on the org file your
trying to export, just to verify it has good org syntax etc.
Brandon Taylor <firstname.lastname@example.org> writes:
> 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)
> set-auto-mode-0(xml-mode nil)
> after-find-file(nil nil)
> find-file-noselect-1(#<buffer styles.xml> "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<text:h text:style-name=..." 186 203 (:parent (headline ... ...)) 304 509 (:parent (paragraph ... ...)) 704 714 (:parent
> (headline ... ...)) 815 987 (:parent (paragraph ... ...)) 995 1044 (:parent (paragraph ... ...)) 1052 1083 (:parent (paragraph ... ...)) 1278 1289 (:parent
> (headline ... ...)) 1390 1489 (:parent (paragraph ... ...)) ...) (:export-options nil :back-end #s(org-export-backend :name odt :parent nil :transcoders
> (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :options (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :filters (...) :blocks nil
> :menu (111 "Export to ODT" ...)) :translate-alist ((bold . org-odt-bold) (center-block . org-odt-center-block) (clock . org-odt-clock) (code .
> org-odt-code) (drawer . org-odt-drawer) (dynamic-block . org-odt-dynamic-block) (entity . org-odt-entity) (example-block . org-odt-example-block)
> (export-block . org-odt-export-block) (export-snippet . org-odt-export-snippet) (fixed-width . org-odt-fixed-width) (footnote-definition .
> org-odt-footnote-definition) (footnote-reference . org-odt-footnote-reference) (headline . org-odt-headline) (horizontal-rule . org-odt-horizontal-rule)
> (inline-src-block . org-odt-inline-src-block) (inlinetask . org-odt-inlinetask) (italic . org-odt-italic) (item . org-odt-item) (keyword . org-odt-keyword)
> (latex-environment . org-odt-latex-environment) (latex-fragment . org-odt-latex-fragment) (line-break . org-odt-line-break) (link . org-odt-link)
> (node-property . org-odt-node-property) (paragraph . org-odt-paragraph) ...) :exported-data #<hash-table eq 34/4001 0x26f5845> :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)
> funcall-interactively(org-export-dispatch nil)
> call-interactively(org-export-dispatch nil nil)
> Sent from Mailspring, the best free email app for work
> On Jun 26 2021, at 11:05 pm, Tim Cross <email@example.com> wrote:
> 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
> > 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
> > Windows PATH environment variable, I get the following output:
> > Executing soffice --headless --convert-to odt --outdir "c:/Users/donni/OneDrive/Documents/"
> > 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
> 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