ConTeXt[1] is monolithic typesetting software that I've integrated into my Markdown editor[2]. I find ConTeXt allows for a complete separation of content and presentation. This makes it possible to write a novel in Markdown and produce various styles: a formatted PDF and a manuscript PDF. See the themes output in the screenshots[3]. Too bad the authors didn't evaluate LuaTeX or ConTeXt.
Typesetting Engines: A Programmer's Perspective
11–20 of 55 posts
Re: Typesetting Engines: A Programmer's Perspective
#12I've written and published over a dozen books. (Two published with big tech publishers, the rest self-published.)
With my most recent book, I've moved my PDF generation to Typst. LaTeX, you served me well, but I'm more than happy to never use you again. Typst is better (or decent enough) in every dimension.
Re: Typesetting Engines: A Programmer's Perspective
#13I've written and published over a dozen books. (Two published with big tech publishers, the rest self-published.) With my most recent book, I've moved my PDF generation to Typst. LaTeX, you served me well, but I'm more than happy to never use you again. Typst is better (or decent enough) in every dimension.
Have you tried TeXmacs or its fork Mogan?
Re: Typesetting Engines: A Programmer's Perspective
#14I've written and published over a dozen books. (Two published with big tech publishers, the rest self-published.) With my most recent book, I've moved my PDF generation to Typst. LaTeX, you served me well, but I'm more than happy to never use you again. Typst is better (or decent enough) in every dimension.
Typst looked promising, but the very first thing I wanted to do with it - generate some slides with code snippets, and use highlights to call out specific features of the code - is not possible. The core layout engine seems to merge `styled(...)` spans in code blocks far too aggressively, making it impossible for codly (the code highlighting package I tried) to pick out precise ranges to highlight.
I went back to beamer.
Re: Typesetting Engines: A Programmer's Perspective
#15I've written and published over a dozen books. (Two published with big tech publishers, the rest self-published.) With my most recent book, I've moved my PDF generation to Typst. LaTeX, you served me well, but I'm more than happy to never use you again. Typst is better (or decent enough) in every dimension.
Typst looked promising, but the very first thing I wanted to do with it - generate some slides with code snippets, and use highlights to call out specific features of the code - is not possible. The core layout engine seems to merge `styled(...)` spans in code blocks far too aggressively, making it impossible for codly (the code highlighting package I tried) to pick out precise ranges to highlight. I went back to bea…
This is pretty hard to believe considering how good the ecosystem in Typst is so far. There are quite a few packages for making slides in Typst including [Polylux](https://github.com/gszauer/polylux),
[Touying](https://github.com/Wyntau/touying],
[minideck](https://typst.app/universe/package/minideck),
[slydst](https://typst.app/universe/package/slydst)
[minimal-presentation](https://typst.app/universe/package/minimal-presentation) and many more.
Re: Typesetting Engines: A Programmer's Perspective
#16Earlier quoted context omitted.
Typst looked promising, but the very first thing I wanted to do with it - generate some slides with code snippets, and use highlights to call out specific features of the code - is not possible. The core layout engine seems to merge `styled(...)` spans in code blocks far too aggressively, making it impossible for codly (the code highlighting package I tried) to pick out precise ranges to highlight. I went back to bea…
This is pretty hard to believe considering how good the ecosystem in Typst is so far. There are quite a few packages for making slides in Typst including [Polylux]( https://github.com/gszauer/polylux ), [Touying]( https://github.com/Wyntau/touying ], [minideck]( https://typst.app/universe/package/minideck ), [slydst]( https://typst.app/universe/package/slydst ) [minimal-presentation]( https://typst.app/universe/packa…
The problem is not with the slides package, it's with the content I want to put on the slides:
https://github.com/Dherse/codly/issues/35 and in particular, this comment from the author of codly where he sounds constrained by Typst: https://github.com/Dherse/codly/issues/35#issuecomment-24667...
Re: Typesetting Engines: A Programmer's Perspective
#17I've written and published over a dozen books. (Two published with big tech publishers, the rest self-published.) With my most recent book, I've moved my PDF generation to Typst. LaTeX, you served me well, but I'm more than happy to never use you again. Typst is better (or decent enough) in every dimension.
Typst looked promising, but the very first thing I wanted to do with it - generate some slides with code snippets, and use highlights to call out specific features of the code - is not possible. The core layout engine seems to merge `styled(...)` spans in code blocks far too aggressively, making it impossible for codly (the code highlighting package I tried) to pick out precise ranges to highlight. I went back to bea…
Look at Quarto. Write in markdown and export to web, print, and presentations (including straight to PowerPoint or reveal.js for interactive web-based slides.
All from the same content using includes, variables, flags, etc. Show interactive plots directly in you presentations, tons of other features.
Almost every project I create now whether it's documentation, presentation, report, website, or anything else project-related can fit within `quarto create project`.
Re: Typesetting Engines: A Programmer's Perspective
#18> Indo-European languages: a language family native to the overwhelming majority of Europe, the Iranian plateau, and the northern Indian subcontinent. Widely spoken indo-european languages includes English, French, Portuguese, Russian, Dutch, and Spanish, etc.
> Indo-European languages typically use the Latin alphabet
After the first sentence, "Indo-European" seems to have transformed to just "European" in the author's mind. Hindi and Bengali, languages more widely spoken than half the language in that list, seem to have been forgotten, along with their Devanagri script.
(Over the course of the article, it's seeming like the author just wanted to say European languages, or languages using Latin script, and for some reason chose to use Indo-European instead, despite clearly stating the definition themself.)
Re: Typesetting Engines: A Programmer's Perspective
#19GNU TeXmacs ( https://youtu.be/H46ON2FB30U ) is missing.
I firmly believe that just its name set TeXmacs back by a lot. It's a pretty great choice, was even more so a decade or two ago (when typst and the ilk weren't available). But every single time I've tried to introduce it to someone, it's always some variant of "Oh, I don't use Emacs, so a plugin for that isn't useful to me". It's a really unintuitive and unfortunate naming choice that I wish they'd at least changed at some point along the way.
Re: Typesetting Engines: A Programmer's Perspective
#20> Indo-European languages: a language family native to the overwhelming majority of Europe, the Iranian plateau, and the northern Indian subcontinent. Widely spoken indo-european languages includes English, French, Portuguese, Russian, Dutch, and Spanish, etc. > Indo-European languages typically use the Latin alphabet After the first sentence, "Indo-European" seems to have transformed to just "European" in the author…
Not just "European", Western European. A whole lot of people read and write with the Cyrillic alphabet.