From: Christian Moe <mail@christianmoe.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Emacs-orgmode <Emacs-orgmode@gnu.org>
Subject: Re: [BUG][ODT] Subtree export fails when link references target on higher level
Date: Fri, 22 Nov 2013 09:04:19 +0100 [thread overview]
Message-ID: <m2siuoyi9o.fsf@uio.no> (raw)
In-Reply-To: <87wqk15py1.fsf@gmail.com>
Nicolas Goaziou writes:
> Hello,
>
> Christian Moe <mail@christianmoe.com> writes:
>
>> The two examples below illustrate an odd ODT export failure that occurs in
>> restricted circumstances: only when the target of the link is on a
>> higher level of the tree than the link.
>>
>> * This fails
>>
>> ** A subheader
>>
>> This paragraph is bookmarked. <<target1>>
>>
>> When I try to export this subtree to ODT (`C-c C-e C-s o O' at point), I get
>> : user-error: No such file: /Users/CM/org/OpenDocument export failed: FIXME?
>>
>> *** A sub-subheader
>>
>> Here's a ref to the bookmark at [[target1]].
>
> In this case, <<target1>> doesn't belong to any headline. What is the
> expected output for [[target]]?
Oh... right. But in that case, the output should be "No description for
this link", as happens with HTML export. More helpful and informative
than an export failure.
In ODT, the link can be useful anyway, as the ODT output is a reference
field that can be automatically updated to a different format, e.g. to
refer to a page number instead of the (missing) headline text.
Yours,
Christian
next prev parent reply other threads:[~2013-11-22 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 21:33 [BUG][ODT] Subtree export fails when link references target on higher level Christian Moe
2013-11-21 22:51 ` Nicolas Goaziou
2013-11-22 8:04 ` Christian Moe [this message]
2013-11-22 8:09 ` Nicolas Goaziou
2013-11-22 9:08 ` Christian Moe
2013-11-22 9:42 ` Nicolas Goaziou
2013-11-22 11:19 ` Dan Griswold
2013-11-25 9:49 ` Jambunathan K
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=m2siuoyi9o.fsf@uio.no \
--to=mail@christianmoe.com \
--cc=Emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).