Some users are very interested in what the future holds for KOMA-Script. Well, the most important news is that development is continuing—in fact, it’s currently in full swing. At the same time, however, there doesn’t seem to be any visible progress.

As you may know, PDF tagging is currently one of the topics being intensively discussed at KOMA-Script. In this regard, Ulrike Fischer recently demonstrated at the DANTE conference how KOMA-Script classes can already be taught to perform tagging in a few places. Until now, however, this has been more of a piecemeal effort in the form of stopgap solutions. Behind the scenes, however, a great deal has been happening in this direction. Marei and I have discussed this at great length and have come to the conclusion that we cannot currently rely on the still very unstable template interface of latex-lab. We don’t want a KOMA-Script that might suddenly start throwing errors left and right from one day to the next, but rather one that works as reliably as possible. Given the very rapid ongoing development of LaTeX, this isn’t easy anyway.

That’s a good question, and there’s only one—rather poor—answer to it: Because I don’t have any need for it myself.

The fact is that, for decades, I’ve been creating everything from architectural plans to novels using LaTeX, and I almost always use KOMA-Script for that. For years now, however, KOMA-Script has been able to do everything I need. Furthermore, the number of documents I create is steadily decreasing; or rather, I’m creating the same types of documents over and over again, just with different content. As a result, I can no longer test new features in KOMA-Script sufficiently well in my daily work. Even if I use the current beta version of KOMA-Script for all my documents, I’ll therefore hardly find any new bugs.