From: Christian Moe <mail@christianmoe.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Dan Griswold <dgriswol@rochester.rr.com>,
emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>,
Christian Moe <mail@christianmoe.com>
Subject: Re: tricky odt export needs
Date: Sun, 22 Dec 2013 11:25:57 +0100 [thread overview]
Message-ID: <m2sitlb2ru.fsf@uio.no> (raw)
In-Reply-To: <87wqiy1y0h.fsf@gmail.com>
Jambunathan K writes:
> When we are typesetting a xref in a backend - I can authoritatively
> speak for the ODT backend - we need not be resticted to "ONE-OF" but can
> have "ANY-COMBINATION-OF" descriptors. What I mean is this:
>
> In the pdf version of Emacs info manuals one typically sees all three of
> a Section number AND a Description AND a Page number, something like:
>
> See Section 3.1 [Tropical Storms], page 24.
>
> In Org context, I am wondering whether there is such a need.
Two thoughts:
1. Assuming my suggestion for dedicated links to be typeset as page number
references, one partly achieve this by multiple links.
e.g.
------------------------------------------------
See Section [[*Tropical Storms]], page [[tropstorms]].
* Tropical Storms
Bla bla bla...
<<tropstorms>> Bla bla bla..
--------------------------------------------------
2. Maybe, instead of trying to make simple cross-reference links do
everything for everyone, it would be better to think in terms of
creating several link types?
e.g. something like
See Section [[*Tropical Storms]], [[textref:*Tropical Storms]],
[[pageref:tropstorms]].
Yours,
Christian Moe
next prev parent reply other threads:[~2013-12-22 10:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 19:13 tricky odt export needs Dan Griswold
2013-11-20 20:24 ` Nicolas Goaziou
2013-11-20 20:37 ` Dan Griswold
2013-11-20 21:10 ` Nicolas Goaziou
2013-11-20 21:34 ` Dan Griswold
2013-11-20 20:34 ` Christian Moe
2013-11-20 20:40 ` Dan Griswold
2013-11-20 21:33 ` Christian Moe
2013-11-21 16:34 ` Dan Griswold
2013-11-21 16:38 ` Suvayu Ali
2013-11-21 20:19 ` Dan Griswold
2013-11-21 21:02 ` Christian Moe
2013-11-21 20:52 ` Dan Griswold
2013-11-21 21:16 ` Christian Moe
2013-12-20 6:29 ` Jambunathan K
2013-12-20 9:25 ` Christian Moe
2013-12-21 7:09 ` Jambunathan K
2013-12-22 10:25 ` Christian Moe [this message]
2014-02-15 6:24 ` 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=m2sitlb2ru.fsf@uio.no \
--to=mail@christianmoe.com \
--cc=dgriswol@rochester.rr.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--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).