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

From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: on the fragility of export to ODT
Date: Wed, 18 Feb 2015 09:56:44 +0000	[thread overview]
Message-ID: <87oaorczkz.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87lhjwuu4y.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 17 Feb 2015 22:04:45 +0100")

On Tuesday, 17 Feb 2015 at 22:04, Nicolas Goaziou wrote:

[...]

> However, there's a simpler solution. In- "ox-odt.el", function
> `org-odt-link--infer-description', line 2655 (but it depends on Org
> version), there is
>
>   (t (error "FIXME: Resolve %s" destination))
>
> Replace it with
>
>   (t (error "FIXME: Resolve %s" (org-element-interpret-data destination))))
>
> reload Org then trigger the error. The backtrace should be more interesting.

Hi Nicolas,

thanks for taking the time to try to help me out on this.

Your suggested change does indeed yield more interesting and, I guess,
potentially more helpful information.  The output is:

,----
| OpenDocument export failed: FIXME: Resolve #("#+NAME: fig:radar-chart-urea
| #+CAPTION: Radar chart for the urea process which does not require a catalyst.
| #+RESULTS[10c1bfffde9a020d138a430992eb2f43c29c9257]: 
| [[file:radar-chart-urea.pdf]]
| 
| " 40 107 (:parent (#("Radar chart for the urea process which does not require a catalyst." 0 67 (:parent #2)))))
`----

but it unfortunately doesn't tell me how to fix the problem.

A paragraph back, I have a link [[fig:radar-chart-urea]] and this
information in *Messages* is the full content of where the link target
is defined. If I remove the link, the export fails with a similar error
to above but now due to the next link.  Obviously, removing all the
links (or any, for that matter) is not a viable solution...

Any advice?

Thanks again,
eric
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-843-ga5f1a3.dirty

next prev parent reply	other threads:[~2015-02-18  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 17:29 on the fragility of export to ODT Eric S Fraga
2015-02-16 20:20 ` Nicolas Goaziou
2015-02-17 18:08   ` Eric S Fraga
2015-02-17 21:04     ` Nicolas Goaziou
2015-02-18  9:56       ` Eric S Fraga [this message]
2015-02-18 13:55         ` Nicolas Goaziou
2015-02-18 15:04           ` Eric S Fraga

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=87oaorczkz.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).