emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Christian Egli <christian.egli@sbszh.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: How do I convert org to OpenOffice?
Date: Thu, 30 Sep 2010 12:43:33 -0400	[thread overview]
Message-ID: <871v8b5gi2.fsf@fastmail.fm> (raw)
In-Reply-To: <874od7i9yx.fsf@saadawi.sbszh.ch> (Christian Egli's message of "Thu, 30 Sep 2010 16:26:14 +0200")

Christian Egli <christian.egli@sbszh.ch> writes:

> Matt Lundin <mdl@imapmail.org> writes:
>
>> Lennart Borgman <lennart.borgman@gmail.com> writes:
>>
>>> There is a way, isn't there? ;-)
>>
>> I've had great success with LaTeX2rtf (i..e, org->LaTeX->rtf). As long
>> as you are not using too many exotic packages, it works like a charm.
>
> It works fairly well with LaTeX2rtf. Cross references didn't work
> though.

The manual suggests that cross-references work, but that their
functionality depends on the office suite:

http://latex2rtf.sourceforge.net/docu_1_9_14.html#Cross%20References

I've found both section references and page references to work well with
Open Office. 

> A colleague just showed me PyODConverter[1] which seems to be some kind
> of command line remote control for OO.o. So what you do is to export org
> to html and then use PyODConverter to convert html to doc. According to
> him it works well.

Thanks for pointing this out.

Best,
Matt

  reply	other threads:[~2010-09-30 16:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 17:01 How do I convert org to OpenOffice? Lennart Borgman
2010-09-29 17:52 ` Charles Philip Chan
2010-09-29 18:20   ` Lennart Borgman
2010-09-29 18:34     ` Charles Philip Chan
2010-09-29 18:39     ` Charles Philip Chan
2010-09-29 19:43       ` Nick Dokos
2010-09-29 20:12         ` Charles Philip Chan
2010-09-29 20:59           ` Nick Dokos
2010-09-29 21:33             ` Matt Price
2010-09-29 22:40               ` Alan L Tyree
2010-11-02 17:53               ` Lennart Borgman
2010-11-02 19:08                 ` Jambunathan K
2010-11-02 19:31                   ` Matt Price
2010-11-03  5:37                     ` Jambunathan K
2010-11-04 21:32                       ` Matt Price
2010-11-05  6:03                         ` Jambunathan K
2010-11-05 13:32                       ` J. David Boyd
2010-11-05 13:49                         ` Jambunathan K
2010-11-02 20:10                   ` Lennart Borgman
2010-11-03  1:06                     ` Lennart Borgman
2010-11-03  4:58                       ` Jambunathan K
2010-09-30 12:41 ` Matt Lundin
2010-09-30 14:26   ` Christian Egli
2010-09-30 16:43     ` Matt Lundin [this message]
2010-10-06 15:21 ` Eric S Fraga
2010-10-06 21:10   ` Henri-Paul Indiogine
2010-10-07  7:08     ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2010-09-30  3:25 Rustom Mody

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=871v8b5gi2.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=christian.egli@sbszh.ch \
    --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).