The handling of formats can be tweaked by enabling or disabling format extensions. Running

pandoc --list-extensions=my_format

lists available extensions and their default status. Extensions are enabled by prefixing them with `+`, and disable with `-`:

pandoc --from my_format+enabled_extension-disabled_extension

Example: disable the smart handling of quotes, ellipses, etc in #Markdown with

pandoc --from=markdown-smart

#pandoc #formatExtension

Pandoc in the browser, with a friendly interface. This app is a web-assembly version of pandoc, the documents never leave your computer:

https://pandoc.org/wasm-demo/convert.html

#pandoc #wasm

“pandoc for the people”, the pandoc wasm web-app, is now available at https://pandoc.org/app/
It allows to run any kind of document conversion that pandoc supports in the browser. The documents never leave the computer, thus ensuring *full privacy*.
Conversions to pdf are done via Typst.

#pandoc #wasm #typst

The default HTML-output generated by pandoc is polyglot HTML, i.e., it's both valid HTML and XML.
The `tidy` utility is tool that can generate pure HTML; it can also shed a few bytes by omitting optional tags. E.g.

pandoc --to=html -s … | tidy -q -ashtml -omit

#pandoc #html #html5 #xml #tidy

The default HTML-output generated by pandoc is polyglot HTML, i.e., it's both valid HTML and XML.
The `tidy` utility is tool that can generate pure HTML; it can also shed a few bytes by omitting optional tags. E.g.

pandoc --to=html -s … | tidy -q -ashtml -omit

#pandoc #html #html5 #xml #tidy

@jarango Everything true.

However, I disagree with #Markdown: https://www.karl-voit.at/2025/08/17/Markdown-disaster/

It's way more open than, let's say, #OneNote & so forth. Unfortunately, it's far from being a #textformat that can be reused anywhere without problems. At least I need to convert MD all the time from one flavor to a different.

With more and more #Obsidian add-ons introducing their own syntax elements, you will end up with clear text files you still can't convert for a different tool without modifications. Good luck with finding out which elements are going to survive and which not. For a few files, that seems OK. If you have a decent #PKM like you describe in your awesome #DulyNoted book, it requires more effort.

For everything I need to use with #MD, I keep a syntax file with one example element so that I keep an overview & know what to convert how in case I need to reuse information stored in this MD flavor.

With org, I just push it through #pandoc & I'm done. 🤷

#publicvoit #LML #Zettelkasten

There is now an up-to-date pandoc-wasm package available on npm.

The credit for this goes to @gws and @johanneswilm thanks a lot!

https://www.npmjs.com/package/pandoc-wasm

#pandoc #wasm #npm #javascript

🆕 pandoc 3.9 🎉🚀

• Official support for wasm (WebAssembly), allowing to run pandoc in the browser,
• the *alerts* extension is now available in the pandoc Markdown flavor,
• support for defaults files using JSON instead of YAML,
• extension of `${.}` vars in the `defaults` field, making it easier to base defaults files on other defaults,
• method to run Lua code with a modified pandoc state,
• and much more

Many thanks to all who contributed!

https://github.com/jgm/pandoc/releases/tag/3.9

#pandoc #release

There is now an up-to-date pandoc-wasm package available on npm.

The credit for this goes to @gws and @johanneswilm thanks a lot!

https://www.npmjs.com/package/pandoc-wasm

#pandoc #wasm #npm #javascript

Time to #askfedi about #pandoc. No, not the shiny, new browser version, the old-school version. I'm converting a bunch of markdown files into a single ODT file. It works great, but now I need to keep the endnotes collected with each "chapter," and not all piled up at the end of the document. Markdown's understanding of a "section" is a anchor, and doesn't appear to correspond to ODT's sections.