From: Jambunathan K <email@example.com>
Cc: emacs-org <firstname.lastname@example.org>
Subject: Re: export to ODT
Date: Thu, 07 Jul 2011 13:49:29 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Henri-Paul Indiogine's message of "Wed, 06 Jul 2011 16:38:55 -0700")
Info manual has some useful info on odt exporter. See
It's relatively a reliable way to explore the capabilities of the
> I got the following line in my *Messages* buffer:
> Use of MathJax is incompatible with ODT exporter. Using dvipng instead.
> I do know about this MathJax.
(Very roughly) what this message tries to convey is this:
If you have LaTeX fragments in your Org file you are better off using
dvipng instead of MathJax. This message concerns with the following
config line (implicit or explicit)
It is also a cue to the developer that ODT and HTML exporter still needs
If it doesn't trouble you don't bother about it much.
> When the odt file is loading I get a message window from LibreOffice
> with a general error. Then it goes away and the file continues
In my experience this typically happens when the XML is *not*
well-formed. If OpenOffice thinks that it can get around to recover from
the non-well-formedness, then it continues loading the file by repairing
it. In othercases, OpenOffice may not be able to recover from the
malformed XML and in that it case it simply says the file is corrupt and
resigns from the task at hand.
One thing you could do for identifying the root cause of this error is:
1. Switch to *.odt buffer (C-x n whatever.odt)
2. Open the content.xml (Hit RET on content.xml)
3. Do a C-u C-c C-n (M-x rng-first-error)
You will be able to identify the error and surrounding the context which
This will help you with constructing a minimal sample that reproduces
> There are a few issues with merging lines and no space in between
> them, but overall it looks great.
Please add few more lines of description. Send me a minimal sample that
reconstructs these issues.
> Thanks to the developer(s) or org-odt!!!
Thanks for trying out org-odt and feeding back your experiences.
next prev parent reply other threads:[~2011-07-07 8:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 22:26 export to ODT Henri-Paul Indiogine
2011-07-06 22:47 ` Nick Dokos
2011-07-06 23:38 ` Henri-Paul Indiogine
2011-07-07 8:19 ` Jambunathan K [this message]
2013-06-07 14:19 export to odt Manfred Lotz
2013-06-07 20:35 ` Christian Moe
2013-06-10 15:42 ` Manfred Lotz
2013-06-11 10:33 ` Eric S Fraga
2013-06-11 19:52 ` Manfred Lotz
2013-06-12 7:33 ` Eric S Fraga
2013-06-12 17:39 ` Manfred Lotz
2013-06-13 7:37 ` Eric S Fraga
2013-06-13 10:34 ` Manfred Lotz
2013-06-14 7:07 ` Christian Moe
2013-06-14 7:57 ` Manfred Lotz
2013-06-14 14:51 ` Eric S Fraga
2013-06-12 2:58 ` Manfred Lotz
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).