emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.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: Mon, 25 Nov 2013 15:19:32 +0530	[thread overview]
Message-ID: <87siukvmj7.fsf@gmail.com> (raw)
In-Reply-To: <m2siuoyi9o.fsf@uio.no> (Christian Moe's message of "Fri, 22 Nov 2013 09:04:19 +0100")

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.

When using page numbers, one may have to use "Update Fields" - an
extraneous step - to have a consistent doc.

With the use of section numbers, the extraneous step and the
inconsistency are altogether avoided.  Remember the "section numbers"
are computed by ODT exporter by hand (i.e., these section numbers are
NOT "auto-magically" plugged in by LibreOffice.)

It is more important to have a consistent document.  So, use of page
numbers can be an configurable option.  It should NOT be the default
option.  When using page numbers, please mention in the docstring/manual
that updating of fields is a user responsibility.


A potential patch will touch `org-odt-label-styles' and
`org-odt-category-map-alist' or steal significantly from these


      parent reply	other threads:[~2013-11-25  9:53 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
2013-11-25  9:49     ` Jambunathan K [this message]

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=87siukvmj7.fsf@gmail.com \
    --to=kjambunathan@gmail.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).