emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Emacs-orgmode <Emacs-orgmode@gnu.org>,
	Christian Moe <mail@christianmoe.com>
Subject: Re: [BUG][ODT] Subtree export fails when link references target on higher level
Date: Fri, 22 Nov 2013 10:08:59 +0100	[thread overview]
Message-ID: <m2r4a8yf9w.fsf@uio.no> (raw)
In-Reply-To: <87ob5c6eor.fsf@gmail.com>


What I described already works out of the box, as long as a bookmark and
cross-reference are generated. In LibreOffice, you can then right-click
on the field of the cross-reference to display e.g. the target's chapter
heading number or page number instead of a textual description.

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.


Nicolas Goaziou writes:

> Hello,
> Christian Moe <mail@christianmoe.com> writes:
>> 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.
> I don't know ODT syntax, but if you provide that useful syntax in this
> case, I can add it to ox-odt.el.
> Regards,

  reply	other threads:[~2013-11-22  9:10 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 [this message]
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:

  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=m2r4a8yf9w.fsf@uio.no \
    --to=mail@christianmoe.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \


* 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


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).