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@gnu.org
Subject: Re: tricky odt export needs
Date: Thu, 21 Nov 2013 11:34:55 -0500	[thread overview]
Message-ID: <CAGO+QKtBzbjo+6ZA_QZUjVtKXtsuD+SA4gj=LSPUEWqHs+odXQ@mail.gmail.com> (raw)
In-Reply-To: <m2txf6sqpw.fsf@vpn-client193.uio.no>

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

On Wed, Nov 20, 2013 at 4:33 PM, Christian Moe <mail@christianmoe.com>wrote:

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

That sounds pretty neat, Christian. But I get an export failed error, and
it doesn't complete creating the odt file. Any suggestions?

Thanks,

Dan

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

  reply	other threads:[~2013-11-21 16:34 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 [this message]
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

  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+QKtBzbjo+6ZA_QZUjVtKXtsuD+SA4gj=LSPUEWqHs+odXQ@mail.gmail.com' \
    --to=dgriswol@rochester.rr.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.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).