emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Jörg Hagmann" <joerg.hagmann@unibas.ch>
To: Scot Becker <scot03@streetgreek.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Footnotes and org-export, revisited
Date: Wed, 17 Dec 2008 15:04:56 +0100	[thread overview]
Message-ID: <49490708.7000406@unibas.ch> (raw)
In-Reply-To: <e0e1fe620812170452w7c4fcc78n5f8fd0db1bf0f278@mail.gmail.com>

>
> 5.  A final solution (which might also gain other advantages) could be
> to begin to facilitate an org-export mode to Pandoc's native
> plain-text syntax (an extension of Markdown).[7] Pandoc is a robust
> Haskell engine to convert between plain text formats.  This would add
> a step to org-mode export, but that one step could potentially allow
> conversion into the wide range of formats that Pandoc supports
> (markdown, reStructuredText, HTML, LaTeX, ConTeXt, RTF, DocBook XML,
> OpenDocument XML, ODT, GNU Texinfo, MediaWiki markup, groff man pages,
> and S5 HTML slide shows). Pandoc's syntax model already has a lot in
> common with org's.  (Both allow LaTeX pass-through, for example).  I
> don't know if such an export would meet the effort vs. value trade
> off, but I suggest it might.
>   
I would welcome an org-export mode to Pandoc's markdown. I'm currently 
using markdown --> Pandoc for generating pdfs via ConTeXt and editable 
documents for people using word processors. An org-export mode to 
markdown would definitely make org the dominating mode for me.

Cheers, Jörg

-- 
Prof. Jörg Hagmann-Zanolari MD
University of Basel
Department of Biomedicine
Institute of Biochemistry and Genetics
Mattenstrasse 28
CH-4058 Basel
Switzerland
Phone +41 (0)61 267 3565

  parent reply	other threads:[~2008-12-17 14:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 12:52 Footnotes and org-export, revisited Scot Becker
2008-12-17 13:28 ` Paul R
2008-12-17 13:31 ` Carsten Dominik
2008-12-17 15:29   ` Paul R
2008-12-17 15:59     ` Scot Becker
2008-12-17 20:54       ` Matthew Lundin
2008-12-17 22:23         ` Scot Becker
2008-12-17 16:08     ` Carsten Dominik
2008-12-17 16:32       ` Paul R
2008-12-17 16:58         ` Carsten Dominik
2008-12-17 17:25           ` Paul R
2008-12-17 17:18     ` Sivaram Neelakantan
2008-12-18  8:08       ` Carsten Dominik
2008-12-18 17:13         ` Sivaram Neelakantan
2008-12-18 10:34       ` Peter Frings
2008-12-18 10:55         ` Peter Frings
2008-12-17 14:04 ` Jörg Hagmann [this message]
2009-01-01  9:07 ` Carsten Dominik
2009-01-01 16:48   ` Matthew Lundin
2009-01-01 17:10     ` Carsten Dominik
2009-01-02 15:10       ` Matthew Lundin
2009-01-03  8:17         ` Carsten Dominik
2009-01-03 22:53           ` Matthew Lundin
2009-01-04  7:39             ` Carsten Dominik
2009-01-12 11:29               ` Scot Becker
2009-01-12 14:21                 ` Paul R

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=49490708.7000406@unibas.ch \
    --to=joerg.hagmann@unibas.ch \
    --cc=emacs-orgmode@gnu.org \
    --cc=scot03@streetgreek.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).