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: on the fragility of export to ODT
Date: Mon, 16 Feb 2015 17:29:07 +0000	[thread overview]
Message-ID: <87r3tp3gv0.fsf@ucl.ac.uk> (raw)

Hello all,

(I hope this is not just noise...)

I use org as my main writing tool, typically for publications that I
submit using LaTeX.  So far, so excellent!

However, I do have to export to ODT (as a means to DOC) and I find the
export to be very fragile.  I keep running into some strange error in
long documents (which make it difficult to track down the source).  The
typical output to *Messages* is:

,----
| Deleting lines with ignore heading tag
| Local Ispell dictionary set to british
| org-babel-exp process latex at line 185...
| executing Latex code block...
| Code block evaluation complete.
| org-babel-exp process latex at line 244...
| executing Latex code block (radarchart)...
| result silenced
| org-babel-exp process latex at line 245...
| executing Latex code block...
| Processing LaTeX file /tmp/babel-7173ozh/latex-7173lhW.tex...
| PDF file produced.
| Code block evaluation complete.
| org-babel-exp process latex at line 460...
|  [...]
| org-babel-exp process bibtex at line 1151...
| org-babel-exp process emacs-lisp at line 1201...
| LaTeX to MathML converter not available.
| Formatting LaTeX using verbatim
| OpenDocument export failed: FIXME: Resolve (paragraph (:begin 54129 :end 54321
`----

At this point, I get very long data structures dumped to
*Messages*...  difficult to figure out what is wrong.  It's often my
mistake but tracking it down is difficult.

However, more importantly, the failure is complete and nothing is
exported which does not help me at all.  It would be great if offending
paragraphs (elements, objects, whatever) would be skipped over and the
rest of the document generated.  Is this possible?

Thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-840-g451c7b

next             reply	other threads:[~2015-02-16 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 17:29 Eric S Fraga [this message]
2015-02-16 20:20 ` on the fragility of export to ODT 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
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=87r3tp3gv0.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).