From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode markup vs rst for general content
Date: Fri, 10 Mar 2017 09:47:22 -0500 [thread overview]
Message-ID: <m2efy5429x.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <874lz1e625.fsf@mat.ucm.es>
Over the past few years I have looked at pandoc a few times:
http://kitchingroup.cheme.cmu.edu/blog/2014/07/17/Pandoc-does-org-mode-now/
http://kitchingroup.cheme.cmu.edu/blog/2015/01/29/Export-org-mode-to-docx-with-citations-via-pandoc/
http://kitchingroup.cheme.cmu.edu/blog/2015/06/11/ox-pandoc-org-mode-+-org-ref-to-docx-with-bibliographies/
Of the exports, to Word is still the least well developed (in my opinion
of course).
Sometimes I just use ox-clip to copy org-mode into word with formatting.
It works pretty well for simple things.
I started https://github.com/jkitchin/scimax/blob/master/ox-rtf.el s an
alternative path to word. It works kind of minimally, but it does not do
everything, and I have not worked on it in a while.
You might see the first three entries of
http://kitchingroup.cheme.cmu.edu/blog/2014/08/08/What-we-are-using-org-mode-for/
which talk about the blog, two large "books" I wrote in org-mode, and a
few of the scientific papers we have written in org-mode and converted
to Latex then pdf (there are over 15 now I think).
A long time ago I was enamored by rst, and Sphinx documentation in
Python. These days I vastly prefer the simpler, and more functional
org-mode markup. The functionality (links, executable code, flexible
export, etc) could be made to work in rst too (it is emacs after all),
but I find it easier to do it and extend it in org-mode (but that is
mostly my experience with org-mode speaking). I like keeping it all in
emacs, and not switching over to a browser to get access to
documentation. That is certainly a preference of mine, but one that is
so strong I wrote an emacs pydoc module to show python docstrings in
emacs, and started writing those in org-mode so I could have equations,
figures and links in them ;)
I think about org-documents in a fundamentally different way than I
think about Latex/rst/html. My org-documents are simultaneously
narrative functional text and documents that contain human readable,
machine-addressable information, e.g. contacts, bibtex entries,
meetings, etc. that I can use in other documents or applications, while
retaining the capability to export the documents to other formats that
are considerably more limited, but that a publisher might demand.
Uwe Brauer writes:
> > On 10/03/17 09:03, Saša Janiška 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.
>
> I had good experience with pandoc exporting from org mode to docx, but
> maybe your documents are more complex.
>
> Uwe Brauer
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2017-03-10 14:47 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
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 [this message]
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=m2efy5429x.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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).