Pandoc

“knowing `pandoc` means you can convert any kind of document into any other kind of document”

“I never had issues with Pandoc on any distribution. But I have struggled with Pandoc extensions”

“makes it really easy to have one source document that does different things when outputting to different formats”

“it was always there as a good option. I mostly use it for Markdown->Typst these days and it does this job very well.”

“It's not easy to maintain so many parsers and renderers, and at the same time to keep the qualities of them.”

“Pandoc is awesome. My fav usage is configuring git to use it to normalize binary docs to markdown”

“I have never had any issues with it, and it's the tool I reach for anytime I need to covert documents.”

“which strips out styling, wrapper divs, spans, inline attributes, etc from (for instance) HTML copied from a google or word doc”

“I won't touch Pandoc with a ten foot pole because of the endless Haskell dependencies on Arch Linux.”

“I use it multiple times per day to move content between Outlook emails and a coding harness”

“how things can be extended and snowball in usefulness when things are built correctly, by hand, from basic principles”

“for what it offers (templating, lua filters, built-in templates for all supported markup languages) it is entirely reasonable”

“With Pandoc you have to deal with LaTeX templates and/or heavy installations.”

“Pandoc can't parse them out of html - including its own html - since there is nothing to parse”

“I couldn't figure out even the most basic things, mostly because of the dozens of incompatible flavors”

“one thing that works really well is using pandoc to download and convert a webpage to EPUB”

“Personally I love it, markdown is becoming more and more central to my workflows.”

“Pandoc is an impressive piece of software but I could never quite get PDF generation working nicely with it.”

“My biggest was time — my Makefile process was taking several (like 10+) seconds to render everything”

“being able to split the output into a latex/typst file as well as a docx is very handy”

“Works great on my MD -> DOCX/PDF/HTML workflows but not the inverse, alas.”

“This gives you an easy workflow with all the power you need using Latex as an escape hatch.”

“The Swiss army knife for document conversion, Pandoc, supports compiling to WASM since 3.9”

“anything the tool doesn't do that you want is probably implementable with a simple inline filter”

“still requires a non-zero amount of time to setup and most importantly maintain and keep up to date”

“pandoc is still the hammer when you need serious format coverage and reliability”

“kept having issues with loss of information and sometimes even syntax error”

“I love Pandoc's markdown. Wrote my PhD thesis in it, and most of my subsequent articles.”

“Pandoc is powerful but the CLI and template management can be a massive overhead for simple tasks.”

“This has almost the full power of the command-line app, subject to the limitations imposed by the WASM sandbox.”

“my workflow is already full of little pandoc scripts that do document conversion wherever I need it”

“it has a huge binary and (just tested) is nearly thirty times slower than comrak!”

“pandoc is big (nearly 200MB binary on Debian) and does far more than just Markdown -> HTML”

“I'd rather pandoc translate between my (sane, well documented, fully extensible) org text”

“I love Pandoc for this, it's easily one of the favorite tools in my daily toolkit”

“Something I've started doing in my workflow is using Pandoc to convert between Markdown and DOCX”

“Pandoc is great for resumes too. My static website turns my pandoc resume into pdf and html and they look great”

“I also used pandoc and markdown, and never bothered going back to ascidoc, full HTML, or latex.”

“Pandoc lets me do things like generate libreoffice or microsoft word documents from the markdown”

“pandoc has an internal representation of what a document is. That representation is not as rich as many of the formats it supports.”