From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
Subject: Re: problem with ox-pandoc export
Date: Thu, 02 Jul 2015 13:50:20 +0200 [thread overview]
Message-ID: <86fv56vkw3.fsf@example.com> (raw)
In-Reply-To: <87ioa2n68f.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> (Nicolas Goaziou's message of "Thu, 02 Jul 2015 13:34:08 +0200")
Hello,
Nicolas Goaziou writes:
> Sebastien Vauban writes:
>> Nicolas Goaziou writes:
>
>>> So this is not a Pandoc export back-end (i.e. a back-end that
>>> translates Org syntax into Pandoc's extended Markdown syntax).
>
>> If the pandoc back-end is some flavor of Markdown, shouldn't it be
>> better named `ox-md-pandoc'?
>
> Which one are you talking about, the one from ELPA or the one
> I suggest adding to core?
The latter.
> The former doesn't translate to Markdown at all. It simply calls
> pandoc on an Org document to produce something else. It depends on how
> well pandoc's Org importer behaves, i.e, how much Org syntax it does
> support.
>
> Therefore, I suggest to write an Org to native pandoc's syntax. It
> would be derived from "ox-md" but that doesn't mean its name must be
> prefixed with "ox-md",
I'd think it'd make more sense, yes.
> consider, for example "ox-beamer" and "ox-latex".
Even if it's not necessarily like that for all cases.
_My_ point of view is simply to make `ox-pandoc' more visible as an
alternative option when one wants to export to Markdown: simply by
looking at file names, by Googling or by looking at "require" calls used
in other's configs, one would expect that `ox-md' and `ox-md-pandoc'
would both generate "markdown".
For Beamer, it could be similar, except that people don't necessarily
search for "latex" when trying to export to "beamer".
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-07-02 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 12:59 problem with ox-pandoc export Alan Schmitt
2015-06-26 15:36 ` Nicolas Goaziou
2015-06-27 10:07 ` Alan Schmitt
2015-06-27 10:19 ` Alan Schmitt
2015-06-27 10:26 ` Nicolas Goaziou
2015-06-28 16:48 ` Alan Schmitt
2015-06-29 9:52 ` Alan Schmitt
2015-06-29 12:19 ` Nicolas Goaziou
2015-06-29 14:50 ` Alan Schmitt
2015-06-29 18:54 ` Nicolas Goaziou
2015-06-30 7:31 ` Alan Schmitt
2015-07-01 12:57 ` Nicolas Goaziou
2015-07-02 9:23 ` Sebastien Vauban
2015-07-02 11:34 ` Nicolas Goaziou
[not found] ` <87ioa2n68f.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-07-02 11:50 ` Sebastien Vauban [this message]
2015-07-02 12:02 ` Rasmus
2015-07-02 14:26 ` Fabrice Popineau
2015-07-02 14:35 ` Rasmus
2015-07-02 14:38 ` Fabrice Popineau
2015-07-07 15:22 ` Rasmus
2015-07-02 21:31 ` Nicolas Goaziou
2015-07-02 22:31 ` Rasmus
2015-07-03 10:23 ` Nicolas Goaziou
2015-07-03 16:37 ` Richard Lawrence
2015-07-03 16:42 ` Nicolas Goaziou
2015-07-03 16:57 ` Rasmus
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=86fv56vkw3.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org \
--cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.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).