Pandoc is a powerful tool but it is not Obsidian-specific. You may have better luck looking for more general resources elsewhere on the web. Edit: Your request may sound simple, but I think there’s a lot of inherent complexity. How do you decide where to start and end? What about recognizing embedded content, especially notes embedded in other notes? What if you have an embed loop? Point is: this is not a trivial task, in my opinion.
Otherwise, Obsidian does not have an “Export all as PDF” feature at the moment. You may want to submit one to #feature-requests.
In order to reduce complexity, you can probably start by supporting a subset of the key features of Obsidain (excluding embedding dynamic content, since it might lead to more complexity). As for where to start, it’s a fair point, I would imagine a dialog asking for the starting point. From there you can build a tree through the links and pull in those specific documents/pages. For embedded content, you can cut support for types of content by choosing file types that are fairly static (pdf/images). That might help mitigate the embedded loop altogether.
Obsidian isn’t open sourced, so I cannot look and make suggestions. Therefore, I am not sure how hard it would be to design an export to PDF function that builds a tree of links/documents based on a “start” page.
Although, I think that carefully crafting a subset of features that is supported and types of content that is supported for pdf export would probably help make the task relatively more possible vs not.
I found a similar request as mines already floating in the #feature-requests section so I will piggyback there.
I’m completly lost with pandoc and I’m searching for this option to print everything since nearly one year now…
I didn’t get it to work and am just sitting here and waiting for someone to write a plugin for it, because I am unable to do it even with tutorials
Yeah I noticed that some of the tutorials use a YAML file to specific some funky options. I looked at their documentation and couldn’t exactly figure out what those options do.
For me, I literally forked and tried to replicate their work with their commands, and somehow the version of Pandoc on Windows is different enough that it doesn’t work. I even tried to do it in Ubuntu VM, still didn’t work.
Even with the API provided, I will probably have to do a deep dive of the Pandoc documentation in order to figure out the basics.
Not currently. Not by default. There could be a Community Plugin you’d install, but I think it has yet to be developed.
You can export single files as PDFs currently, probably with wkhtmltopdf.
Pandoc is a powerful tool, https://pandoc.org , however, you’d have to go into your vault directory, use Pandoc to convert the Markdown files to PDF with LaTeX, then combine them with pdftk, ghostscript, or imagemagick. All of which would require some scripting to make things easier to repeat later on, but for a normal user who doesn’t want to tinker, having a community plugin would be idea. It’s just not a reality yet.
The Pandoc plugin that others are referencing is probably this: Plugins - Obsidian, but it still only does one file at a time.
And it would be great first to make one transitional big md file, to be able to make some modifications before exportation. For example, I use some kind of headers in my notes with tags, creation date and update date. But I wouldn’t like to have that on the exported file, so I would need to delete some lines.
This feature is particularly important for the next decades as we may experience in some countries blackouts due to energy shortage. So it would be valuable to print at least some useful parte of our vaults.