From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Christian Moe <mail@christianmoe.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 10:42:03 +0100 [thread overview]
Message-ID: <87a9gw6adw.fsf@gmail.com> (raw)
In-Reply-To: <m2r4a8yf9w.fsf@uio.no> (Christian Moe's message of "Fri, 22 Nov 2013 10:08:59 +0100")
Hello,
Christian Moe <mail@christianmoe.com> writes:
> But on reflection, I think there's a strong case to change the default
> ODT output of links with dedicated targets to page number
> references. Under the new exporter, such <<targets>> are hidden in
> output, i.e. they no longer contain text that will serve as a
> description, and as shown by my example they may not always belong to a
> heading. But in an ODT document they will always belong to a page, and
> page number references would be a customary choice for printed media.
>
> If that sounds reasonable I'll send a mini-patch later today.
You seem to forget a use-case here: when the target belongs to an item,
[[target1]] returns its number. Displaying the page, albeit correct,
would be less interesting in that situation.
Also, that would introduce an incompatibility with every other major
back-end. At the moment, the compatible way to handle it would just be
to ignore [[target1]] altogether (and keep section/list/whatever number
for other calls).
What do you think?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-11-22 9:41 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
2013-11-22 8:09 ` Nicolas Goaziou
2013-11-22 9:08 ` Christian Moe
2013-11-22 9:42 ` Nicolas Goaziou [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9gw6adw.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.