emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Griswold <dgriswol@rochester.rr.com>
To: Christian Moe <mail@christianmoe.com>
Cc: Emacs-orgmode <Emacs-orgmode@gnu.org>,
	Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: [BUG][ODT] Subtree export fails when link references target on higher level
Date: Fri, 22 Nov 2013 06:19:49 -0500	[thread overview]
Message-ID: <CAGO+QKsqYomjxphSgy3HRD3ATdJHj2Bm1JQeWP29yiN-Sq5iug@mail.gmail.com> (raw)
In-Reply-To: <m2r4a8yf9w.fsf@uio.no>

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

On Fri, Nov 22, 2013 at 4:08 AM, Christian Moe <mail@christianmoe.com>wrote:

> Hi,
> 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

I can say that this describes my typical needs very well. I have a project
with a fair number of targets (at least 26) that all will be referred to by
page number. Like this:

<<this target>


See above, on p. [[this target]].

I don't know if mine would be the odd or typical use. But it is what I am


Dan Griswold
Rochester, NY

[-- Attachment #2: Type: text/html, Size: 1413 bytes --]

  parent reply	other threads:[~2013-11-22 11:19 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
2013-11-22 11:19         ` Dan Griswold [this message]
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=CAGO+QKsqYomjxphSgy3HRD3ATdJHj2Bm1JQeWP29yiN-Sq5iug@mail.gmail.com \
    --to=dgriswol@rochester.rr.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \
    --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).