From: Alan L Tyree <alantyree@gmail.com>
To: "Saša Janiška" <gour@atmarama.com>,
"Emacs Orgmode" <emacs-orgmode@gnu.org>
Subject: Re: org-mode markup vs rst for general content
Date: Fri, 10 Mar 2017 10:27:47 +1100 [thread overview]
Message-ID: <bc565af8-58eb-a833-e1ce-94ae76a8bcff@gmail.com> (raw)
In-Reply-To: <87variglbb.fsf@atmarama.com>
On 10/03/17 09:03, Saša Janiška wrote:
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> Could you be more specific about what kind of richness you are looking
>> for?
> In a general sense…iow, it’s a fact that rst markup is richer than
> e.g. Markdown. Probably, Asciidoc(tor) also provides more semantic
> richness and make it suitable markup for longer docs/books, so I wonder
> where one can put org-mode’s markup on this scale?
>
>
> Sincerely,
> Gour
>
I write legal textbooks (up to 600 printed pages) using org-mode. They
are structurally simple (no sidebars, no illustrations, no computer
code). On the other hand, they have lots of citations and internal cross
references. Org-mode is the best for this kind of work because of the
flexible outline structure, not just collapsing and expanding, but the
"hoisting" facility that allows me to focus on smaller sections. The
org-ref module does its work, and the internal cross referencing is the
best.
I recently assisted a friend to put together a memoir that he wanted to
publish as ePub and print. It had lots of pictures. He had originally
typed it in Word and it was a nightmare. Images would not stay put, even
the typeface would change. The on-line publishers like Lulu rejected it.
We reformatted in in Pandoc Markdown and produced a very nice result. I
would have preferred org-mode, but he had never been near Emacs. We got
good ePub, xhtml and print from a single manuscript.
I have also written in rst: it is a slightly richer language out of the
box with provisions for sidebars, cautions, etc, but unless you really
need those things, I would stick with org-mode. I find the syntax of rst
to be very fiddly. Most of the special effects can be obtained with css
in any case.
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.
I would say Markdown if you are collaborating with someone not familiar
with Emacs. The Pandoc version will do a surprising amount. Org-mode
for nearly everything else, but if you need more, go on to LaTeX.
This may be more than you wanted to know :-).
Regards,
Alan
--
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206 sip:typhoon@iptel.org
next prev parent reply other threads:[~2017-03-09 23:27 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 [this message]
2017-03-10 0:17 ` Samuel Wales
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=bc565af8-58eb-a833-e1ce-94ae76a8bcff@gmail.com \
--to=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).