emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Christian Moe <mail@christianmoe.com>
To: Dan Griswold <dgriswol@rochester.rr.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: tricky odt export needs
Date: Thu, 21 Nov 2013 22:02:31 +0100	[thread overview]
Message-ID: <m2wqk1xyc8.fsf@uio.no> (raw)
In-Reply-To: <CAGO+QKttVwS4=Ono7Ceb_8i+KXDdx0-_wVy_SjnnQ9+vwu+9yA@mail.gmail.com>

Hi, Dan,

Is this the message you get?

 No such file: /[path]/OpenDocument export failed: FIXME?

Does the error always occur when you have my filter set, and never when
you don't?

Does it matter whether you're restricting export to subtrees?

After some more testing, I'm seeing the above error message myself in a
limited set of circumstances (only during subtree export, and only when
the target/bookmark/label is at a higher heading level than the
reference). But whether I use the filter or not does not seem to matter.

I enclose a working version of the filter again, on the off chance that
there was a typo in my previous message.

#+begin_src emacs-lisp
  (defun my-odt-filter-pagerefs (text backend info)
    "Make page-number references rather than 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)
#+end_src

Yours,
Christian

Dan Griswold writes:

> On Thu, Nov 21, 2013 at 11:38 AM, Suvayu Ali <fatkasuvayu+linux@gmail.com>wrote:
>
>> First I would check the Output buffer.  That should have more
>> information on why the export failed.
>>
>
> Thanks Suvayu. There was no Output buffer, only a few error messages in the
> *Messages* buffer (and these are of dubious relevance.)
>
> But it seems that the problem occurs only when I have
> org-odt-preferred-output-format set to "odt" rather than "doc" or nil.
>
> Dan

next prev parent reply	other threads:[~2013-11-21 21:04 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
2013-11-21 16:38       ` Suvayu Ali
2013-11-21 20:19         ` Dan Griswold
2013-11-21 21:02           ` Christian Moe [this message]
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=m2wqk1xyc8.fsf@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

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