From: "Moritz Schäfer" <mail@moritzs.de>
To: emacs-orgmode@gnu.org
Subject: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)]
Date: Sun, 8 May 2022 20:39:20 +0200 [thread overview]
Message-ID: <CA+FVMQCvmpPG2jiO+F+3+Pzkeear3UyjipqNV1JC-ZyJ3to_=A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
Dear mailing list,
When exporting an org-file with org-id based links to odt, I get the
error error "FIXME: Unable to resolve <filename>", where <filename> is the
filename, the org-id-link was pointing to.
Org-id links (example below) are the default for org-roam (v2).
[[id:5222a0dd-5084-41bd-b61d-21dcb3290187][Note title]]
The issue lies within ox-odt.el in the org-odt-link function. There, '
destination' takes the value of the file name of the id-link target.
Therefore, (org-element-type destination) gets evaluated to 'plain-text,
which is not resolvable by 'org-odt-link--infer-description', thus it
raises the error.
I worked around this issue by adding a check for plain-text, but would like
to raise this issue here to find proper ideas on how to fix this.
(cond
;; workaround
((eq (org-element-type destination) 'plain-text)
(format "<text:a xlink:type=\"simple\" xlink:href=\"#%s\">%s</text:a>"
destination
desc
))
;; workaround end
((not label-reference)
(org-odt-link--infer-description destination info))
Thank you,
Moritz
Emacs : GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.30, cairo version 1.16.0)
Package: Org mode version 9.5.2 (9.5.2-gfbff08 @
/home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)
[-- Attachment #2: Type: text/html, Size: 2015 bytes --]
next reply other threads:[~2022-05-09 7:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 18:39 Moritz Schäfer [this message]
2022-10-18 7:47 ` [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)] Ihor Radchenko
2022-10-19 8:00 ` Moritz Schäfer
2022-10-19 10:36 ` Ihor Radchenko
2022-10-20 10:09 ` Max Nikulin
2022-10-21 3:16 ` Ihor Radchenko
2022-10-21 14:46 ` Max Nikulin
2022-10-22 5:03 ` [BUG] ox-odt file: links are not pointing to the real files (was: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)]) Ihor Radchenko
2022-10-22 8:04 ` Max Nikulin
2022-10-23 4:29 ` Ihor Radchenko
2022-10-24 11:40 ` Max Nikulin
2022-10-25 10:20 ` Max Nikulin
2022-10-31 6:13 ` Ihor Radchenko
2022-10-31 14:37 ` Max Nikulin
2022-11-01 5:40 ` Ihor Radchenko
2022-11-01 15:04 ` Max Nikulin
2022-11-02 5:04 ` Ihor Radchenko
2022-11-02 15:39 ` Max Nikulin
2022-11-03 6:25 ` [DISCUSSION] Default description for relative file links in odt export (was: [BUG] ox-odt file: links are not pointing to the real files (was: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)])) Ihor Radchenko
2022-11-01 5:47 ` org-export: How to handle links to the exported file? " Ihor Radchenko
2022-11-01 15:18 ` org-export: How to handle links to the exported file? Max Nikulin
2022-11-01 5:48 ` [BUG] ox-odt file: links are not pointing to the real files (was: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)]) Ihor Radchenko
2022-11-01 15:28 ` export and cross links between files Max Nikulin
2022-11-02 6:38 ` [DISCUSSION] Unified handling of links between Org files on export (was: export and cross links between files) Ihor Radchenko
2022-10-21 12:02 ` [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)] Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+FVMQCvmpPG2jiO+F+3+Pzkeear3UyjipqNV1JC-ZyJ3to_=A@mail.gmail.com' \
--to=mail@moritzs.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).