From: Christian Moe <mail@christianmoe.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Dan Griswold <dgriswol@rochester.rr.com>,
Nicolas Goaziou <n.goaziou@gmail.com>,
emacs-orgmode@gnu.org, Christian Moe <mail@christianmoe.com>
Subject: Re: tricky odt export needs
Date: Fri, 20 Dec 2013 10:25:30 +0100 [thread overview]
Message-ID: <m28uvfdgc5.fsf@uio.no> (raw)
In-Reply-To: <87eh58ghn1.fsf@gmail.com>
Jambunathan K writes:
> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.orgmode as well.
>
>
> Christian Moe <mail@christianmoe.com> writes:
>
>> You can do cross-references with ordinary links. Have a look at the
>> manual section 4.2, "Internal links". However, what you get out of the
>> box is textual references to e.g. section headings, not page
>> references. You can change that for each reference individually by
>> right-clicking on them in LibreOffice. There should be a way to get
>> page references by default, but off the cuff, I'm not sure how.
>
> I am interested in rolling out support for xref by pagenumbers. I would
> like to know what the standard or recommended practice is like.
>
> So, when one says "I want pagenumbers for xref", what xref-es they have
> in mind. Do they mean ONE-or-SOME-or-ALL of a xref to outline headings,
> figure, table, source listings, formula etc.
I don't know what recommended practice is would be.
My own take on this is that all objects you mention are probably
best left as xrefs to the section, figure etc. concerned, exported as
section title, section number, figure number etc. as appropriate.
On a different thread, however, I have suggested that xrefs to
*dedicated link targets* should export as page numbers in ODT. (Or this
should be made an option.)
http://article.gmane.org/gmane.emacs.orgmode/79096
Nicolas Goaziou raised a couple of objections on that thread, as did
you. I forgot to copy my reply to the list, and I think I partly
misunderstood what Nicolas was saying, anyway.
Nicolas raised a use case I'd forgotten about: Dedicated link targets in
list items are currently exported as the item number. Nicolas suggested
that item numbers are more useful than page numbers here, and he's
probably right. But keeping this behavior would make my proposal more
complex to implement and maintain.
Nicolas also raised concerns over backend compatibility. However, I
don't think this is a strong argument against introducing page number
references. A page reference solution makes sense for paged media (ODT,
LaTeX backends) but not for screen (HTML).
Finally, it should also be considered to make page numbers the default
for *non-numbered* headings:
When headings are not numbered in export (#+options: num:nil), current
ODT export outputs a cross-reference with a descriptive text equal to
the heading text of the item the dedicated target is in. However, this
seems to be fragile; as soon as you Update Fields in LibreOffice, the
cross-reference collapses to an empty space. The other backends also
seem to struggle with the case of xrefs to headings without heading
numbering.
Yours,
Christian
next prev parent reply other threads:[~2013-12-20 9:25 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 [this message]
2013-12-21 7:09 ` Jambunathan K
2013-12-22 10:25 ` Christian Moe
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=m28uvfdgc5.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).