From: Christian Moe <mail@christianmoe.com>
To: Dan Griswold <dgriswol@rochester.rr.com>, emacs-orgmode@gnu.org
Subject: Re: tricky odt export needs
Date: Wed, 20 Nov 2013 22:33:47 +0100 [thread overview]
Message-ID: <m2txf6sqpw.fsf@vpn-client193.uio.no> (raw)
In-Reply-To: <m2vbzmsth6.fsf@vpn-client193.uio.no>
I said:
> 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.
Well, here's one way to get those page references, using filters:
(defun my-odt-filter-pagerefs (text backend info)
"Make page references, not textual references in ODT export."
(when (org-export-derived-backend-p backend 'odt)
(replace-regexp-in-string "text:reference-format=\"text\"" "text:reference-format=\"page\"" text)))
(add-to-list 'org-export-filter-link-functions
'my-odt-filter-pagerefs)
(Whee! I just wrote my first export filter.)
Org doesn't know what the page number will be, so when you open the
document in e.g. LibreOffice, you still have to update fields (Tools >
Update) before you see page numbers.
Yours,
Christian
next prev parent reply other threads:[~2013-11-20 21:35 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2txf6sqpw.fsf@vpn-client193.uio.no \
--to=mail@christianmoe.com \
--cc=dgriswol@rochester.rr.com \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.