I've been frustrated by Markdown previews not supporting Pandoc features, so I created a Pandoc-based Markdown preview for VS Code [1]. The preview supports all Pandoc extensions to Markdown syntax, because Pandoc itself generates the preview. There is also optional support for code execution with Jupyter kernels. I'm currently in the process of adding support for non-Markdown formats (including scroll sync), plus taking advantage of some of the new Pandoc 3.0 features.<p>[1]: Examples and animations: <a href="https://codebraid.org/presentations/scipy2022/" rel="nofollow">https://codebraid.org/presentations/scipy2022/</a>. Installation for VS Code: <a href="https://marketplace.visualstudio.com/items?itemName=gpoore.codebraid-preview" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=gpoore.c...</a>. Installation for VSCodium: <a href="https://open-vsx.org/extension/gpoore/codebraid-preview" rel="nofollow">https://open-vsx.org/extension/gpoore/codebraid-preview</a>.
Pandoc is a great piece of software. As a university teacher and researcher, I use it in three ways:<p>1. I write markdown for my website and for the websites for my research projects and simply generate standalone html out of it. Done.<p>2. When we create electronic exams, the exam platform takes questions using a html-backed rich text editor. We write down our exam questions using markdown, create html document fragments, that we simply paste into the exam platform.<p>3. When students do electronic exams, we receive xml files from our exam platform. We use python to pass on submissions to different submission checkers (akin to autograders or static analysis) and create yaml files with the student submission and grading suggestions and static analysis annotations. We manually review and grade and comment within the yaml file (that works incredibly well), collect all the data using python and generate markdown reports for each student, including their submission, our comments and scoring. We pass this markdown through pandoc, creating well layouted pdfs which we either print and hand out or send out electronically.<p>Pandoc fits our yaml+markdown-based processes very well. Only for the actual research papers we still write LaTeX and build pdfs without pandoc.
I love Pandoc. I don't often write "documents for office consumption" but when I do, I just write a markdown file and spit out docx or PDF. I was congratulated more than once on how coherent my documents are in their structure.<p>Plus, having a git history is a great boon.
Out of every tool I’ve ever used to make a .docx file from Markdown, Pandoc is the only one that has consistent results with converting Markdown headers to Word styles rather than just a bigger font size. Lots of Markdown tools in my tool belt, and would love to know of any more that can do this, because it’s really useful on the (unfortunate) occasions something needs to live as a Word doc.
Quarto, excellent software for building publications, websites, etc…, is leveraging Pandoc: <a href="https://quarto.org/" rel="nofollow">https://quarto.org/</a>
Pandoc is such a great conversion program, and this new 3.0 release has so many improvements, especially for figures.<p>I write in markdown and export to PDF and using pygments for code syntax coloring, with .tex files to adjust layouts, tables, and the like.<p><a href="https://github.com/SixArm/pandoc-from-markdown-to-pdf">https://github.com/SixArm/pandoc-from-markdown-to-pdf</a>
Love this program. Means I can write in plain text, markdown or zim-wiki syntax, and export to word no hassles.<p>If I'm writing markdown I use pandocs version as it has support for advanced tables.<p>Brilliant software.
That's great news. I've been waiting for years for a dedicated 'Figure' element. The workaround was pretty brittle. It'll make pandoc-plot [0] easier to maintain as well.<p>[0]: <a href="https://github.com/LaurentRDC/pandoc-plot">https://github.com/LaurentRDC/pandoc-plot</a>
Does it still automatically generate "smart" quotes (which are anything but) from traditional ones during conversion?<p>Love the tool, but this is the most awful default setting I've seen in a program in a while, especially if you include any code that depends on quotes not being mangled.
I love pandoc. With it's lua filters, I love using it for generating html and blog posts, one thing which always annoys me about most static website generating tools is they make you use some very limited templating language, when I just want to use a proper programming language.<p>My only irritation -- while I understand why one would want to do it for neatness, it's annoying that the "pandoc" package no longer provides the "pandoc" program! Maybe instead introducing "pandoc-core" and renaming "pandoc-cli" to "pandoc" would be better (it would certainly avoid breaking existing scripts, like mine).
I've been looking for a tech stack to replace latex for decades now. As a very recent development, the combination of pandoc+weasyprint (plus a little bit of homebrewed pandoc filter magic) has now become good enough for my needs, and I have finally been able to take the plunge. Feels great.<p>For those who are a little less adventurous and who happen to be in the social sciences, humanities, journalism, etc., pandoc+msword is also definitely worth looking into. It's a much better tech stack than standalone msword. -- It's really only in the STEM fields that, in my mind, there really is no way around latex.
Pandoc powers my little static site maker:<p>cf. <a href="https://github.com/adityaathalye/shite/blob/master/bin/templating.sh#L112">https://github.com/adityaathalye/shite/blob/master/bin/templ...</a><p><pre><code> __shite_templating_compile_source_to_html() {
# If content has front matter metadata, it is presumed to be in a format
# that the content compiler can safely process and elide or ignore.
local file_type=${1:?"Fail. We expect file type of content like html, org, md etc."}
case ${file_type} in
html )
pandoc -f html -t html
;;
md )
pandoc -f markdown -t html
;;
org )
pandoc -f org -t html
;;
esac
}</code></pre>
I've been using Pandoc to write Latex-lite for a couple years now. Just write .md files with basic Markdown syntax for all the major text content, and add some Latex when I need to do something more particular. Best of both worlds, really.
One day I wish to see the AsciiDoc(tor) Reader. I'd love to be freed from Ruby as AsciiDoc is superior to Markdown and most other lightweight markup syntax options in features and syntax. This lack of features is why we have an incompatible group of Markdown syntax forks (aka "flavors" to mask that forks are incompatible).
fantastic software, never build it from source, or if you have to, make sure you have an OS that bundles all the Haskell dependencies into a single meta package
One new feature that will make Python documentarians happy is the `—-list-tables` flag for rST output: You can now convert any table to the list table syntax of reStructuredText, which is, in many's opinion, superior to classic tables with ASCII borders.
I'm in a job where I pretty much never need to output a PDF, but whenever the occasional thing comes around, pandoc is always there for me. Such a useful tool.
I use pandoc to convert GitHub style markdown to PDF/EPUB ebooks. The default output is good and there are plenty of customization options too. I didn't know LaTeX/CSS but stitched a few things together with help from stackexchange sites to customize the output produced. Later came to know there are third-party templates that I could've used/started with.
Since Pandoc has Lua inbuilt I wonder if it can also run LuaLatex in full? Because then it could support really all features of LaTeX and become a kind of SuperLaTeX.