LaTeXML VS Zundler

Stacks project is available on github, so in theory (if you're bored enough) it should be possible to reverse engineer their design from their make-project file https://github.com/stacks/stacks-project/blob/master/documen...

At a high level they use plastex https://github.com/plastex/plastex to convert latex to html (you seem to be using pandoc?) and so can control the rendering to any fine accuracy they want. I liked this general style as well, so I tried using plastex but couldn't get my head around it and so started using LateXML https://github.com/brucemiller/LaTeXML

My usecase: I wanted to have a "dependency graph" of lemmas to make it easier to see proofs without having to jump back and forth through a pdf, and this was sort of similar to lean formalization blueprint graphs https://teorth.github.io/pfr/blueprint/dep_graph_document.ht... (which also uses plastex) but without the lean parts. There's still a lot of work to be done, but I think I have a pretty okay implementation using latexml which meets 50% of my requirements for now, so I'm happyish https://texviz.arsricharan.in/ghrss24/

LaTeML [1] is presumably the latex to html tool that arXiv is testing right now. What are peoples thoughts about it compared to other such tools?

[1] https://github.com/brucemiller/LaTeXML

They aren't using the rendered PDFs. They are convering from the LaTeX sources, that you upload to arxiv with https://github.com/brucemiller/LaTeXML

I fully agree with the author's "I want to replace PDF" sentiment.

It's true that running code in the document has some downsides, but the vast majority of people does it all the time in their browsers. And it comes with tremendous upsides. Just imagine large amount of data presented in interactive tables which can sort, filter and export or interactive graphs inside the document. We already use HTML+JS so much, why should we stop at documents? Yes, they can't be printed, but in my observation less and less people even own a printer these days, and I see no reason why this trend should not continue. I bet the future will be mostly living, interactive documents.

It's funny that I just mentioned this in the other thread [1], but I also felt that there is a need for a format that is self-contained and widely supported by standard software (by which I mean browsers). A well-specified open format would be great, but until then I tackled the self-containedness problem with JS and wrote a Python script that zips and bundles all assets and embeds them as a SPA into one HTML file [2]. The focus is on Sphinx docs but it should work in general with all distributed HTML docs.

[1] https://news.ycombinator.com/item?id=39138444

[2] https://github.com/AdrianVollmer/Zundler

One of the selling points of PDF is that it is a single self-contained file. I found this lacking in Sphinx and wrote an extension for it to zip and bundle the assets into a single HTML file: https://github.com/AdrianVollmer/Zundler

Also works with HTML documents produced in other ways.

I have used my own format, resume.json and recently restructuredText. I put both resume.json and the restructuredText as a github gist. My biggest thing is that I don't want to mess around with the style of layout and let other people design a theme. I have been using the sphinx plugins docxbuilder, sphinx-design (for a dropdown option that I kinda thought would be cool), and finally Zundler for an all-in-one HTML file.

So I wrote a tool in Python and JavaScript that attempts to solve this by embedding everything in one singular self-contained HTML file: Zundler