Can you generate your figures in multiple formats and want to always use the format that's suited best for the target? Omit the file extension from the image path and use `--default-image-extension`. E.g., if you export an #image as both #pdf and #svg, then you can write this #Markdown

and run #pandoc with
pandoc --to=html --default-image-extension=svg
or
pandoc --to=latex --default-image-extension=pdf
The freshly baked Docker images for pandoc 3.8.3 are on Docker Hub and in GitHub Container Registry.
Changes: The build-process for those images has been simplified thanks to the new arm64 binaries available for pandoc-crossref. Also, the #Typst images now ship with the latest version, Typst 0.14.0.
🆕 pandoc 3.8.3 🎉
This release adds three new input formats ( #Asciidoc, #PPTX, and #XLSX) and one new output format ( #BBCode + variants).
It also fixes a number of bugs (including some regressions in 3.8). See the changelog for full details.
Thanks to all who contributed!
The freshly baked Docker images for pandoc 3.8.3 are on Docker Hub and in GitHub Container Registry.
Changes: The build-process for those images has been simplified thanks to the new arm64 binaries available for pandoc-crossref. Also, the #Typst images now ship with the latest version, Typst 0.14.0.
🆕 pandoc 3.8.3 🎉
This release adds three new input formats ( #Asciidoc, #PPTX, and #XLSX) and one new output format ( #BBCode + variants).
It also fixes a number of bugs (including some regressions in 3.8). See the changelog for full details.
Thanks to all who contributed!
🆕 pandoc 3.8.3 🎉
This release adds three new input formats ( #Asciidoc, #PPTX, and #XLSX) and one new output format ( #BBCode + variants).
It also fixes a number of bugs (including some regressions in 3.8). See the changelog for full details.
Thanks to all who contributed!
Pandoc allows to access and modify the Haskell runtime system (RTS) that the program runs on.
E.g., to print memory usage:
pandoc +RTS -s -RTS …
Or to limit the maximum heap size available to pandoc to 2 GB:
pandoc +RTS -M2G -RTS …
See all available options by running:
pandoc +RTS -?
This can be helpful when facing performance issues.
Pandoc allows to access and modify the Haskell runtime system (RTS) that the program runs on.
E.g., to print memory usage:
pandoc +RTS -s -RTS …
Or to limit the maximum heap size available to pandoc to 2 GB:
pandoc +RTS -M2G -RTS …
See all available options by running:
pandoc +RTS -?
This can be helpful when facing performance issues.
Querverweis is a Lua filter designed for cross-referencing within documents. It is configurable and usable with languages other than English.
The project is still under development, but is already used in production.
Querverweis is a Lua filter designed for cross-referencing within documents. It is configurable and usable with languages other than English.
The project is still under development, but is already used in production.
A “hidden feature” of pandoc, because it's not mentioned in the manual: Typst properties. E.g., use this Markdown to get very large text:
{typst:text:size=48pt}
Isn't this great?
:::
All text properties can be modified this way, and block properties can be set with `typst:property`.
The full docs are here: https://pandoc.org/typst-property-output.html
A “hidden feature” of pandoc, because it's not mentioned in the manual: Typst properties. E.g., use this Markdown to get very large text:
{typst:text:size=48pt}
Isn't this great?
:::
All text properties can be modified this way, and block properties can be set with `typst:property`.
The full docs are here: https://pandoc.org/typst-property-output.html
Simplify custom LaTeX templates maintenance with "partials" & baked-in internal template snippets: The `common.latex` partial is the most important, as it contains almost all LaTeX definitions and instructions necessary to compile pandoc-generated LaTeX code.
% In LaTeX templates, use
$common.latex()$
Manual template updates become mostly unnecessary this way.
See the contents of the partial with
pandoc --print-default-data-file=templates/common.latex
Simplify custom LaTeX templates maintenance with "partials" & baked-in internal template snippets: The `common.latex` partial is the most important, as it contains almost all LaTeX definitions and instructions necessary to compile pandoc-generated LaTeX code.
% In LaTeX templates, use
$common.latex()$
Manual template updates become mostly unnecessary this way.
See the contents of the partial with
pandoc --print-default-data-file=templates/common.latex
Besides the `common.latex` partial, there are also:
• `passoptions.latex` – options for packages that may be loaded implicitly (should come before `\begin{document}`)
• `fonts.latex` – Fonts setup
• `font-settings.latex` – Fonts configs
• `hypersetup.latex` – Options for the “hypertext” package (hyperlinks and metadata)
• `after-header-includes.latex` – Everything that *must* happen late.
Using all of these partials in custom templates gives maximum robustness.
Simplify custom LaTeX templates maintenance with "partials" & baked-in internal template snippets: The `common.latex` partial is the most important, as it contains almost all LaTeX definitions and instructions necessary to compile pandoc-generated LaTeX code.
% In LaTeX templates, use
$common.latex()$
Manual template updates become mostly unnecessary this way.
See the contents of the partial with
pandoc --print-default-data-file=templates/common.latex
@claireon my usage of Obsidian is so “basic” that I think I’ll try to edit most posts with Helix and keep Obsidian open in the background to sync with my phone.
Worst case I’ll install oxide to make Helix smarter!
@thibaultamartin
I wish there was good #OrgMode support in helix, but i guess alot of good stuff for PKIM lies in #emacs anyway ( #pandoc etc.).
@claireon