From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Help confirming odt->doc bug (Was Re: [odt] User-visible improvements)
Date: Mon, 08 Aug 2011 11:42:56 +0530 [thread overview]
Message-ID: <81ty9sxwgn.fsf@gmail.com> (raw)
In-Reply-To: <8162mbugim.fsf@gmail.com> (Jambunathan K.'s message of "Sat, 06 Aug 2011 13:18:49 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
>> I pushed few user-visible improvements to org-lparse/org-odt a few
>> minutes ago. With these changes an exported document could be
>> post-processed to another format (using an external converter) with just
>> a single command (i.e., you no longer have to launch OpenOffice and do
>> "Save As" etc)
>
> This addition seems to be bearing fruit immediately. I just reported a
> problematic behaviour with org->odt->doc conversion in LibreOffice
> mailing list. See
>
> http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/14739
>
> I am using OpenOffice.org-3.2.1 (OOO20m18/Build:9502).
I have pushed an alternative implementation + workaround that doesn't
trigger this bug. Please update your local copies.
> Does anyone else see the reported behaviour with recent LibreOffice
> builds? I am surprised that no one has complained about this problematic
> behaviour yet. Is it that people in this list (and their friends) have
> actually shifted to OpenDocument formats and don't rely on Word
> anymore. Or Is it that users simply "hand fix" the generated document.
>
> Jambunathan K.
>
>
--
next prev parent reply other threads:[~2011-08-08 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 21:05 [odt] User-visible improvements Jambunathan K
2011-08-06 7:48 ` Help confirming odt->doc bug (Was Re: [odt] User-visible improvements) Jambunathan K
2011-08-06 9:50 ` Achim Gratz
2011-08-08 6:10 ` Jambunathan K
2011-08-08 6:12 ` Jambunathan K [this message]
2011-08-21 18:38 ` Jambunathan K
2011-08-18 7:31 ` [odt] User-visible improvements Bastien
2011-08-18 12:31 ` suvayu ali
2011-08-19 8:44 ` Jambunathan K
2011-08-19 7:35 ` 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=81ty9sxwgn.fsf@gmail.com \
--to=kjambunathan@gmail.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
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
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).