xkevio

Luckily, Typst actually has experimental HTML export which is progressing quite nicely (even with MathML in the next update!), see here: https://typst.app/docs/reference/html/

It makes use of https://github.com/EnzymeAD/enzyme which is an LLVM plugin and since Rust also uses LLVM in its backend, we can enable this plugin in our Rust toolchain when autodiff is enabled. So, it is a bit of compiler black magic rather than a direct implementation in the standard library.

IJIMAI (https://typst.app/blog/2025/typst-at-ijimai) and JUTI (https://forum.typst.app/t/juti-call-for-papers-best-paper-aw...).

Admittedly, not the most renowned or most known journals but you have to start somewhere.

This is a very welcome release with all its features and as an active community member, I've seen the lengths the devs have gone to over the past few months to ensure proper internal reworkings for all of the big upcoming or planned features.

I don't always understand all of it but I trust and know that care has been taken to properly validate all of those changes, partially thanks to all the unit/integration tests we have.

It's a somewhat difficult issue and I understand being hesitant because of this. Converting to SVG is one possible path around it which isn't too bad but having it natively is of course even better.

The thing is, inserting PDF for just the PDF export would be quite easy. The issue is the other export targets Typst supports (SVG and PNG) as that would require some form of rasterization / a full blown PDF engine written in Rust without C-bindings because of the web app and that simply does not exist yet.

And the developers are hesitant to just add features for one specific export target which I get.

Ah, yeah fair enough! I was confused thinking that you were unaware of the existence of the functionality as a whole. Well, as laurmaedje (one of the main devs) said below, it should be easy to add, though it seems difficult to find which size values `big`, `bigg` and so on exactly represent.

Am I misunderstanding what exactly you are looking for? You can change the spacing in math mode of symbols/operators with https://typst.app/docs/reference/math/class/ and delimiter size with https://typst.app/docs/reference/math/lr#functions-lr (or automatically).

HN doesn't support LaTeX in comments sadly, so I am just writing it out as you would before rendering it with LaTeX.

Maybe there are add-ons that detect valid LaTeX math symbols and convert them whenever possible but as-is you can't get it to render within the comments.

I think you might have gotten your symbols mixed up a litte.

From what I understand, just \nabla(f) describes the gradient of a function f -- meaning all the first order partial derivatives (of a certain point) in a vector.

\nabla * f describes the divergence of the function f -- meaning a scalar field of the quantity of the vector field's sources at each point.

\nabla * \nabla(f), divergence of gradient, then describes the Laplace operator. Also written as \nabla^2(f) or \Delta(f) -- note that it's an uppercase delta.

OneLoneCoder has a good introductory video about using SIMD instructions with C++ to speed up a Mandelbrot calculation: https://www.youtube.com/watch?v=x9Scb5Mku1g