From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: hindiogine@gmail.com
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: How do I convert org to OpenOffice?
Date: Thu, 07 Oct 2010 08:08:37 +0100 [thread overview]
Message-ID: <87ocb6pjii.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <87y6ab81tl.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Wed, 06 Oct 2010 14:10:30 -0700, Henri-Paul Indiogine <hindiogine@gmail.com> wrote:
>
> Hi Eric!
>
> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> > org document
> > -> export as HTML (C-c e h)
> > -> open in OOo
> > -> select and copy all (C-a C-c)
> > -> open new document in OOo (A-f n t [I believe])
> > -> paste selection (C-v)
> > -> save (in my case, often as MS Word)
> > -> go and cry because you have to degrade org mode so much ;-)
>
> 1. export should be "C-c C-e h"
Yes, sorry, typo.
> 2. My BibTeX references are not exported. Am I missing something or is
> it not possible this way?
Not possible this way. If you need bibtex then latex2rtf, as
mentioned by others, is what I have used in the past.
> 3. How could I have some sort of version control? My advisor uses the
> accursed MS Word and that is all he knows.
I am not sure what you are asking. I use version control (git/hg/rcs)
for all of my org files regardless of whether I export them or not.
[-- Attachment #2: Type: text/plain, Size: 75 bytes --]
--
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D
[-- Attachment #3: 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-10-07 7:34 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
2010-10-06 15:21 ` Eric S Fraga
2010-10-06 21:10 ` Henri-Paul Indiogine
2010-10-07 7:08 ` Eric S Fraga [this message]
-- 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=87ocb6pjii.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=hindiogine@gmail.com \
/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).