#patoline — Public Fediverse posts

Today's thoughts?
Sometimes I smile seeing posts such as: "Do you use #TeXLaTex, #context, #typst, or #patoline as #digitalTypesetting solution?").

What about just #markdown or #djot to #pdf with _one_ software? It's called the #sile typesetter with just _one_ extra collection installed:
https://github.com/Omikhleia/resilient.sile

(Heh! Don't tell me it counts as 2 if you need Pandoc, LaTeX, _lots_ of CTAN modules to achieve the same, not even that. Book covers,, ISBN, styling... all in just _one_ collection.

@nobodyinperson Any thoughts to suggest for spinning up #speedata, or #patoline in a Nix shell? I think I have almost everything else of note these days running, but Speedata has a messy build with no notion of an installation (which explains why it has never been packaged for any distro) and Patoline only builds against a legacy OCAML toolchain. Since it isn't a very active player in the #typesetter space I can write off the later for now but @speedata Publisher probably deserves a fair shake.

I've recently launched an idea at https://polytype.dev — a sort of Rosetta Stone for #typesetting engines.

The goal is to build up a sample gallery that showcases both differences and similarities between the input and output of #SILE, #TeXLaTeX, #Typst, #speedata, #weasyprint, #pagedjs, #groff, #satysfi, #patoline, and potentially others.

The source code is at https://github.com/alerque/polytype and contributions are very welcome! The UI in particular could use the touch of a front-end developer!