emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan L Tyree <alantyree@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode markup vs rst for general content
Date: Sat, 11 Mar 2017 09:28:19 +1100	[thread overview]
Message-ID: <59c2a062-b939-7e24-063a-7568efe43a2a@gmail.com> (raw)
In-Reply-To: <CAJcAo8srXYoVMXCcd1KXKUQaOv__4CDrdC5tEjyv5es-WGJ6Rg@mail.gmail.com>

On 11/03/17 07:32, Samuel Wales wrote:
> On 3/10/17, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>>> 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.
>> Excellent summary.
> the pandoc version of ...?  org->markdown->pandoc->word?
The opinion is mine (I don't want Eric embarrassed by my opinions!!). 
The pandoc version of Markdown is what I meant. And I definitely prefer 
org-mode, but the context was one of collaboration with someone who has 
never used Emacs. I had no hope of converting him from Word to 
Emacs/org-mode, but he was happy with Markdown. The text was simply 
enough that none of the complexities that you mention below arose.

Also, on export to Word: my export path actually was org -> LaTeX -> 
LibreOffice. The last step uses a special script that is part of the 
tex4ht (I even got the name wrong before) package: oolatex.

For some reason, the Debian Jessie package does not install oolatex on 
the PATH. On my system it is installed at /usr/share/tex4ht/oolatex.

oolatex will pause periodically, at least on a long manuscript. Restart 
by typing 'x'.

Cheers,
Alan

>
> i think a major feature would be working with internal links.  so
> you'd export a subtree, and links to locations in the subtree would be
> supported.  does markdown do that?
>
> also, org-export-with-tasks can't be supported by pandoc, because
> presumably it doesn't go off and inspect your .emacs, but can it
> support the properties drawer equivalent?
>


-- 
Alan L Tyree                    http://www2.austlii.edu.au/~alan
Tel:  04 2748 6206              sip:typhoon@iptel.org

      reply	other threads:[~2017-03-10 22:28 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
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 [this message]

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=59c2a062-b939-7e24-063a-7568efe43a2a@gmail.com \
    --to=alantyree@gmail.com \
    --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 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).