Most Common Use of Pandoc?

[iwelch]

I am mulling about writing a version or extension of pandoc if it is likely to be useful to many other people, too. I am not deeply versed in the subject area, though. Some advice would be appreciated. Here is what I would like to find out.

My own use is pandoc for markdown to either latex or html. I know that there are many other interesting uses of pandoc (and I have very occasionally also used it for markdown to docx conversion, and even epub, ansi-ascii), but I am focused only on markdown to my others. my success on most other conversions (e.g., back to markdown) have been very limited --- often because there are simply big differences in the input and output language markup capabilities, not because this is a flaw of pandoc.

is my use case by far the most common (.markdown -> latex/beamer and .markdown -> html/epub), or is it more like one of many?

---

My rationale is that markdown lacks some facilities I still need in latex and html, which is what I want to remedy. I would probably start with John's CommonMark C code, and supplement it with the kinds of stuff I use often and need too often to abandon most of my latex/html source files. Things like :

tables features, (multicol, rules); clearpage, bigskip, color, relsize, endinput, floats, input, centering, a clearer specification of 'html-only' and 'latex-only', rudimentary macro functions, etc.

I'd have to go through my documents and see what my most important uncovered macro facilities and markup facilities are.)

[tarleb]

There's a project where we needed to support a very extended version of Markdown. I wrote panluna for that, a wrapper of jgm's lunamark, and it's working well. The major downside of that library is the missing support for citation syntax, and I didn't get to implement that yet.

However, combined with some filters and custom writers, we can use stock pandoc while supporting all the features that we needed for the project. (Pandoc's citations syntax would still be nice to have though.)