From: Samuel Wales <samologist@gmail.com>
To: Alan L Tyree <alantyree@gmail.com>
Cc: "Emacs Orgmode" <emacs-orgmode@gnu.org>,
"Saša Janiška" <gour@atmarama.com>
Subject: Re: org-mode markup vs rst for general content
Date: Thu, 9 Mar 2017 17:17:03 -0700 [thread overview]
Message-ID: <CAJcAo8s-zDcAWm27Z+_2_W=3VrzEWPgdox1knrxqOr3krdNm-A@mail.gmail.com> (raw)
In-Reply-To: <bc565af8-58eb-a833-e1ce-94ae76a8bcff@gmail.com>
On 3/9/17, Alan L Tyree <alantyree@gmail.com> wrote:
> The only problem that I have had is converting org-mode to Word files as
> required by my publisher. The ODT export module is fiddly and often
> chokes on my longer documents. When it does choke, it is hard to trace
> the problems. Markdown + Pandoc seems much better in this regard, but
> the outlining features in Emacs do not seem to be as good for the
> Markdown mode. To get a decent export in my latest manuscript I had to
> export to LaTeX then use ht4tex. Not a pretty workflow.
your answer seems very helpful. not sure what you mean in this par though.
just to clarify:
are you referring to exporting to word from org-mode?
- odt [is that word format?]
- org -> markdown -> pandoc [presumably word]
- org -> latex -> ht4tex [= word?]
i was wondering, too, what format would be good to export to for a
nontechnical reader, from org, and can preserve org's external
hyperlinks and numbered outline structure.
to the original poster: org can also insert literal target format
code. for example, you can put literal html code into your export as
needed. dunno if that fits your needs.
--
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>
The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.
The NIH, FDA, and CDC are not there for you. Not without activism.
"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.
next prev parent reply other threads:[~2017-03-10 0:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 9:14 org-mode markup vs rst for general content Saša Janiška
2017-03-09 18:50 ` John Kitchin
2017-03-09 19:17 ` Uwe Brauer
2017-03-09 20:38 ` John Kitchin
2017-03-09 21:40 ` Uwe Brauer
2017-03-09 22:03 ` Saša Janiška
2017-03-09 23:27 ` Alan L Tyree
2017-03-10 0:17 ` Samuel Wales [this message]
2017-03-10 0:49 ` Alan L Tyree
2017-03-10 1:25 ` Alan L Tyree
2017-03-10 11:15 ` Uwe Brauer
2017-03-10 14:47 ` John Kitchin
2017-03-10 16:14 ` Uwe Brauer
2017-03-10 16:24 ` Uwe Brauer
2017-03-10 17:06 ` John Kitchin
2017-03-10 17:41 ` Uwe Brauer
[not found] ` <fc159a4ac13f4e439d8007f9de98d495@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 17:57 ` Eric S Fraga
2017-03-10 15:21 ` Saša Janiška
[not found] ` <e047c50c99ba4e8ba5ccfb4029b5aabc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-10 9:09 ` Eric S Fraga
2017-03-10 20:32 ` Samuel Wales
2017-03-10 22:28 ` Alan L Tyree
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='CAJcAo8s-zDcAWm27Z+_2_W=3VrzEWPgdox1knrxqOr3krdNm-A@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=alantyree@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gour@atmarama.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).