pandoc

It might not for GPLv3: it tries to sidestep it by explicitly voiding any clauses placing additional restrictions, but Pandoc is using GPLv2 https://opensource.stackexchange.com/questions/9500/is-apple... https://github.com/jgm/pandoc/#license

I'm currently working on my fourth book produced using Typst, and it has been nothing but amazing. LLMs struggle with Typst a bit but other than that it has been an absolute joy to work with. I have a pretty good workflow set up for publishing these books, which are mostly collections of student essays. I use Pandoc to convert the students' Word documents into Typst, then unify the formatting, styles, and headers (mostly via LLMs). From there, I generate both a nice digital PDF and a print-ready PDF using Typst, and then use Pandoc again to convert the Typst into what ultimately becomes an EPUB. It all works quite beautifully. Most of the challenges I've run into are related to Typst features that don't map cleanly to Pandoc, so I end up adding a few funky conditionals so those features aren't hit when converting via Pandoc. sys.inputs ma

> Maybe 5 people and their friends use Pandoc The pandoc repository[1] has nearly 45k stars and 4k forks. It's embedded in Jupyter notebooks, which are used by data scientists the world over. The python wrapper for pandoc has 16 million downloads[2]. [1]: https://github.com/jgm/pandoc [2]: https://pypi.org/project/pandoc/

The Swiss army knife for document conversion, Pandoc, supports compiling to WASM since 3.9 [1]. It supports Markdown, in a wide variety of flavours, and Typst. Their official demo page provides a PDF output via Typst, all done client-side [2]. Furthermore, you get .docx and other output formats as well [1]: https://github.com/jgm/pandoc/releases/tag/3.9 [2]: https://pandoc.org/app/

There's an Obsidian extension for Pandoc so you can convert your Obsidian notes to any other format. https://github.com/jgm/pandoc/pull/11135 There are a number of basic errors in this report, but since it's LLM-written I suppose I shall put as much effort correcting them as the author put into generating them. Sigh.

From the pandoc release announcement: https://github.com/jgm/pandoc/releases/3.9 : > Starting with this release, pandoc can be compiled to WASM, making it possible to use pandoc in the browser. A full-featured GUI interface is provided at https://pandoc.org/app

Have only lightly dabbled in latex but Typst was super easy to pickup. I recently even published a whole book[0] in Typst. The process was straightforward for the most part. It took a little time to work out how to get page numbers alternating between the left and right side and a few other small formatting details but by and large it was very easy to create a beautiful PDF that's ready for printing. Also, pandoc has fairly good support for Typst so I use that to create a docx (which Draft2Digital converts to epub). I even opened a few issues (https://github.com/jgm/pandoc/issues?q=sort%3Aupdated-desc%2...) for pandoc support and they were almost all resolved pretty quickly. [0]: https://thelabofthought.co/shop/p/nbmi3

I've used Typst to produce books (for https://printstack.net) and it's been excellent. I started with this: https://news.ycombinator.com/item?id=42271078 But wouldn't recommend going via Pandoc, for example for this reason: https://github.com/jgm/pandoc/discussions/10438 Some things like #show rules can be a bit confusing. And obviously LLMs can't really help you.

I also recently published a book written with Typst. It was absolutely a joy to work with, especially because the book was a collection of student essays. I converted them from docx to Typst and then getting all the figures and tables setup nicely and uniformly was easy. The PDF generation was perfect but converting to docx/epub I ran into a few bugs in pandoc. I reported them and a few were fixed and a few are still open. Overall, a very positive experience. Book: https://thelabofthought.co/shop/p/nbmi3 Bugs: https://github.com/jgm/pandoc/issues?q=is%3Aissue%20state%3A...

I think TFA is unfair wrt pandoc's dependencies. I'm not sure if the listed "ecosystem" is what you need to build pandoc from source, or just the result of shitty packaging of pandoc from the OS package maintainers. For the record, the .deb download from [1] gives you a 146MB statically linked pandoc executable that depends only on libc6 (>= 2.13), libgmp10, zlib1g (>= 1:1.1.4). [1] https://github.com/jgm/pandoc/releases

I have used it to kickstart a blogging project that I wish to come back to soon. The Lua inter-op for custom readers, writers and filters is great but I wish there was more editor integration and even perhaps an official IDE/editor with built-in debugging features (probably something already do-able with Emacs but I haven't checked). The only blocker for my project is no support for "ChunkedDoc" for Lua filters [1] which forces me to write more code and a complicated Makefile. [1]: https://github.com/jgm/pandoc/issues/9061

This would never happen but in an ideal world, we should be able to click on a citation to jump to the part of the paper that is being referenced and each paper page should have a discussion board so we can easily communicate with the authors and group the discussion in one place instead of us having to google to see if there is relevant discussion on twitter/reddit. We can even put links to talks, tutorials, blogs, github repo, demo, paperswithcode/google scholar/open review, background material, a timeline of citations in tree form on the same page(actually I am seeing more machine learning papers that have a project page that does some of these) or even turn it into a mini wiki. I just think html has so much more potential(especially now with LLM we can do semantic search). I wonder if there would be interest in such a chrom extension

pandoc is a format converter, not a format. You still need to write the document. That said, I would rather choose something pandoc supports as an input format than asciidoc, which is a constantly moving target that still doesn't have a specification, is governed by a working group that seemingly never makes decisions, and in practice asciidoctor may as well be the specification. As an addendum to yesterday's discussion of software estimates, one of the more amusing open source versions is this guy saying in July of 2014 he expected pandoc's asciidoc frontend to be done in a "few months": https://github.com/jgm/pandoc/issues/1456#issuecomment-50805...