From: Bastien <firstname.lastname@example.org>
To: Jambunathan K <email@example.com>
Cc: firstname.lastname@example.org, Rainer Stengele <email@example.com>
Subject: Re: Bug in ODT exporter
Date: Sat, 09 Jul 2011 10:41:26 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Jambunathan K.'s message of "Sat, 09 Jul 2011 02:36:55 +0530")
Jambunathan K <firstname.lastname@example.org> writes:
> Thanks for reporting the bug. I have pushed a fix few moments ago. Could
> you please try again?
I tried and it works -- thanks for the fix!
> The problem was that timestamps were occuring as list item in the
> example you provided which confused the exporter.
> If you encounter corruption issue or issues related to formatting of odt
> file you can identify the root cause as below:
> 1. Switch to *.odt buffer (C-x b 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)
> 4. Note the error message as well as the XML stuff at the point of
> Once the error is identified, you can create a minimal org file for
> reproducing the bug very easily.
Thanks for the detailed recipe.
next prev parent reply other threads:[~2011-07-09 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 12:22 Bug in ODT exporter Rainer Stengele
2011-07-08 13:42 ` Bastien
2011-07-08 13:53 ` Rainer Stengele
2011-07-08 14:17 ` Bastien
2011-07-08 21:06 ` Jambunathan K
2011-07-09 8:41 ` Bastien [this message]
2017-02-07 13:10 Dimitri Minaev
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).