Articles, the packages on CTAN, the books, and a record of the conferences
I have been to — with the talks, where there were talks. Entries appear
here once their title, venue and year are recorded: a citation missing any
of those would be a fabricated one, so it is left off rather than guessed
at.
Also published in Dutch:
Documenten in YAML specificeren en invullen met lua-placeholders in LaTeX
— MAPS 54 (2024.1), pages 15–27 (2024) ·
PDF Dit artikel bekijkt de implementatie van het factuursjabloon in GinVoice en onderzoekt hoe het factuursjabloon beter kan aansluiten bij het LaTeX-ecosysteem door de introductie van een extra datalaag in YAML met behulp van lua-placeholders. Met de introductie van lua-placeholders hebben LaTeX-gebruikers volledige vrijheid in het opmaken van factuursjablonen en zijn de factuursjablonen direct integreerbaar met de verbeterde versie van GinVoice.
This article examines the implementation of the invoice template in GinVoice [3] and explores how the invoice template can better align with the LaTeX ecosystem by introducing an additional data layer in YAML using lua-placeholders. With the introduction of lua-placeholders, LaTeX users have complete freedom in formatting invoice templates, and the invoice templates are directly integratable with the enhanced version of GinVoice.
References cited above
J. Collins, E. McLean, D.J. Musliner. The latexmk package. https://www.cantab.net/users/johncollins/latexmk/index.html
S. Dierl. The invoice2 package. https://github.com/no-preserve-root/invoice2
E. Nijenhuis. The GinVoice GTK application. https://gitlab.gnome.org/MacLotsen/ginvoice
E. Nijenhuis. The GinVoice template. https://github.com/Xerdi/ginvoice-template/tree/maps
E. Nijenhuis. The lua-placeholders package. https://ctan.org/pkg/lua-placeholders
This article presents Xerdi's Documentation Project (XDP), a modular framework for scaling and simplifying LaTeX-based document production. XDP separates template logic, content, and configuration into structured components, such as Executable Document Templates (EDTs), Document Portfolios, Data Definition Repositories, and Workspaces. Leveraging LaTeX features like TEXMFHOME and TEXMFDOTDIR, it enables reusable and extensible document workflows across teams or clients. Through practical examples, it demonstrates how intertwined documents can simplify use cases like legal documents, invoices, and academic materials, and how XDP tackles responsive branding, agile development, and user-friendly input for minimal-coding authors. The framework incorporates tools such as bib2gls [9], attachfile2 [5] and zref [6] to automate complex workflows and improve document scalability.
References cited above
M. Hoftich. The make4ht package, 2025-04-14. A build system for tex4ht. https://ctan.org/pkg/make4ht
E. Nijenhuis. The lua-placeholders package, 2024-04-03. Specifying placeholders for demonstration purposes. https://ctan.org/pkg/lua-placeholders
E. Nijenhuis. The regulatory package, 2024-09-05. Flexible drafting of legal documents, especially in Dutch. https://ctan.org/pkg/regulatory
E. Nijenhuis. The gitinfo-lua package, 2024-09-14. Display git project information in your LaTeX projects. https://ctan.org/pkg/gitinfo-lua
H. Oberdiek. The attachfile2 package, 2024-01-20. Attach files into PDF output. https://ctan.org/pkg/attachfile2
H. Oberdiek. The zref package, 2025-06-08. A new reference scheme for LaTeX. https://ctan.org/pkg/zref
J. Peron, The Gregorio Project. The lyluatex package, 2023-04-18. Commands to include Lilypond scores within a (Lua)LaTeX document. https://ctan.org/pkg/lyluatex
V. Starý Novotný. The markdown package, 2025-06-24. Converting and rendering Markdown documents inside TeX. https://ctan.org/pkg/markdown
N. Talbot. The bib2gls package, 2025-05-15. Command line application to convert .bib files to glossaries-extra.sty resource files. https://ctan.org/pkg/bib2gls
N. Talbot, V. Belaïche, E. Nijenhuis. The fmtcount package, 2025-02-09. Display the value of a LaTeX counter in a variety of formats. https://ctan.org/pkg/fmtcount
This article presents the gitinfo-lua package, which integrates Git information into LaTeX documents. It provides macros for document versioning, listing authors and displaying a change log, improving collaboration and traceability in software documentation.
In juli 2025 bezocht ik in India een workshop van het LaTeX-team over Tagged PDF. In dit artikel beschrijf ik wat ik daar leerde: waarom tagging ertoe doet, hoe tagging tegenwoordig in LaTeX werkt (met tagpdf en latex-lab, inclusief sockets en templates), welke standaarden relevant zijn (PDF 2.0, PDF/UA-2, WTPDF) en welke praktische valkuilen je in de dagelijkse praktijk tegenkomt. Tot besluit ga ik in op nuanceringen en actuele uitdagingen in de regulatory context, met name rond enumitem (lijsten) en titlesec (koppen), die de weg naar goed getagde PDF's bemoeilijken.
No publisher and no date — when either exists it will say so here rather
than be implied. Not all of them can be read: an entry marked internal or classified is
listed because it exists, not because it is available. For the rest, write to erik@xerdi.com.
Dans der Planeten— Music and the orbits[in progress]
A book in Dutch about music and the motion of the planets, typeset in LaTeX. The oldest of the three, and the one furthest from the day job.
Xerdi's Documentation Project— The typesetting book[internal]
The book behind XDP: executable document templates, data and layout kept apart, and what it takes to make a document build the same way twice. It tracks a framework that is still moving, so it is never finished and stays in-house for now. The TUGboat article on intertwined documents is a chapter's worth of it.
Germen M. Haijtema worked through the typesetting problems of pharmacy compliance documents with the book alone, and no help from me. That is the test it was written to pass.
Operator's Handbook— The infrastructure book[classified]
Infrastructure as something you can hand to the next operator: the estate documented as a bound volume, with the ansible roles and shell scripts typeset from the sources that actually deploy them. It documents live systems, so it is not for circulation — listed here because it exists, not because it is available.
The method is not secret; only the estate is. Every role and script is typeset from the file that actually deploys it, with the prose living in that file as ordinary comments — so the annotated source still runs, and the book cannot drift from what is running. One chapter is an Ansible role that provisions a TeX Live mirror: the same file Ansible executes, set as prose with numbered listings. That works because a documentation comment is still just a comment. Nothing is extracted and no second copy exists, which is the part that matters — the usual literate workflow in TeX, a .dtx run through docstrip, is built to produce a package, and docstrip remains the right answer for TeX sources. An operator writes no .sty and no .cls. Their file has to run exactly as it stands, and that is the shape comment2tex is cut for. It is on CTAN, and it will annotate your infrastructure as readily as it does mine. comment2tex on CTAN.
conferences attended
Where I have been. Attending is not the same as speaking, so a talk is only
noted where there is something to point at.