From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: the role of org-odt-preferred-output-format etc
Date: Sun, 10 Apr 2016 21:22:41 +0800 [thread overview]
Message-ID: <87y48liony.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87mvp139fh.fsf@mat.ucm.es
Uwe Brauer <oub@mat.ucm.es> writes:
> Hello
>
> Maybe I misunderstood the manual
> http://orgmode.org/manual/Extending-ODT-export.html
> and
> http://orgmode.org/manual/Configuring-a-document-converter.html#Configuring-a-document-converter
>
> I can successfully convert a org file to odt, but sometimes I need it to
> be directly in doc format.
>
> So I thought I set org-odt-preferred-output-format
> to «doc».
I set that option to the string "rtf", and everything works as expected.
You don't actually specify the preferred output, you just export to ODT,
and then the secondary conversion happens automtically. Ie, I now just
export to ODT, and automatically end up with an RTF file. I haven't
tried that programmatically, but I'd guess it works the same way: just
don't put the "doc" in there at all. Does that work?
> But then what?
>
> Shall I use
>
> org-odt-convert
>
> For example
> (org-odt-convert "~/tex/Proy-MTM-2016/LaTeX-org/cv-libre.odt" "doc")
>
> That did not work
>
> I also checked the variable
> org-odt-convert-process
>
> which was set to «Libreoffice», I changed that to «unoconv», but that did
> not help.
>
> Any suggestion?
>
> thanks
>
> Uwe Brauer
next prev parent reply other threads:[~2016-04-10 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 13:00 the role of org-odt-preferred-output-format etc Uwe Brauer
2016-04-10 13:22 ` Eric Abrahamsen [this message]
2016-04-10 13:41 ` Uwe Brauer
2016-04-10 15:09 ` Ken Mankoff
2016-04-10 15:52 ` Uwe Brauer
2016-04-10 16:21 ` Ken Mankoff
2016-04-10 16:30 ` Uwe Brauer
2016-04-12 9:30 ` Uwe Brauer
2016-04-11 7:56 ` Rasmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y48liony.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.