From: Matt Price <matt.price@utoronto.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Re: interacting with word processors (opeonffice, word)
Date: Thu, 04 Feb 2010 09:43:31 -0500 [thread overview]
Message-ID: <1265294611.4059.174.camel@gont> (raw)
In-Reply-To: <hka7af$dtd$1@ger.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1762 bytes --]
On Tue, 2010-02-02 at 22:00 +0000, Shelagh Manton wrote:
> On Tue, 02 Feb 2010 21:40:49 +0200, Rainer M Krug wrote:
>
> > On Tue, Feb 2, 2010 at 8:34 PM, Matt Price <matt.price@utoronto.ca>
> > wrote:
> >
> >> Hi,
> >>
> >> I;m getting more and more used to using org for my own writing
> >> purposes, and love it. But I still find it pretty difficult to work
> >> with word-processor users whoexpect to get a doument in .doc or .odt
> >> formats. I've just found odt2org
> >> (http://mantiel.wikidot.com/os:odt2org) which looks great for importing
> >> odt files into org; but my main concern right now is getting things
> >> from org-mode out into odt or doc. May i ask what other people tend to
> >> do in this situation? I I guess I could export to html, then import in
> >> Openoffice, then edit & save as odf, but this seems a little
> >> cumbersome. If someone has a better solution I'd love to hear it.
> >>
> >>
> > Oh - and ther is also:
> >
> > mk4ht oolatex
> >
> > which converts LaTeX to odt.
> >
> > Cheers,
> >
> > Rainer
> >
> Wouldn't the org-docbook package be suitable as there are docbook to odt
> transformers (which makes sense as odt is a type of xml like docbook)
>
> http://open.comsultia.com/docbook2odf/ might be helpful.
>
> Shelagh
> >
thanks to everyone for their advice -- I'm going to try these all out &
if I have any constructive commetns I'll report them back. It's a
little duanting for me, as a non-latex user, to try to figure out how to
get documentsl ooking about how I want them to -- the default output of
the latex export has way too much whitespace for my tastes -- but I
guess I hsould be able to figure those issues out somehow. thanks
again!
matt
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-02-04 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 18:34 interacting with word processors (opeonffice, word) Matt Price
2010-02-02 18:44 ` Rainer M Krug
2010-02-02 18:55 ` Russell Adams
2010-02-02 19:28 ` David Maus
2010-02-03 1:00 ` Matt Lundin
2010-02-02 19:39 ` Rainer M Krug
2010-02-03 7:13 ` Eric S Fraga
2010-02-02 19:40 ` Rainer M Krug
2010-02-02 22:00 ` Shelagh Manton
2010-02-04 14:43 ` Matt Price [this message]
2010-02-04 15:10 ` Eric S Fraga
2010-02-05 1:44 ` Shelagh Manton
2010-02-05 21:25 ` Matt Price
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=1265294611.4059.174.camel@gont \
--to=matt.price@utoronto.ca \
--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).