Re: problem with ox-pandoc export

[Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>]

Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> writes:
> Alan Schmitt <alan.schmitt-o/5/jSaJEHk+NdeTPqioyti2O/JbrIOy@public.gmane.org> writes:
>
>> In short, it exports the org file to another temporary org file (using
>> the pandoc exporter that inherits from the org exporter), then it calls
>> the pandoc binary to convert from org to the target format. The first
>> step (org to temporary org) is used to extract some information from the
>> org file that is used in further steps (like creating a custom CSS or
>> adding arguments to the call to the pandoc binary).
>
> 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'?

BTW, when looking at Markdown formats known by Pandoc, there are:

- Pandoc markdown
- Pandoc markdown_github
- Pandoc markdown_mmd
- Pandoc markdown_phpextra
- Pandoc markdown_strict

Is the Pandoc back-end exporting the flavor known as "Pandoc markdown"?

Best regards,
  Seb

-- 
Sebastien Vauban