earlier LaTeX version test
xetex removed from checkengines to save some time, because xetex is no longer recommended for LaTeX
in \@CheckKOMAScriptVersion \ExplSyntaxOff replaced by \csname …\endcsname
Unable to change font of headings and toc after installing TeXlive 2026
Sorry for bothering you. It is in fact a problem with Texlive 2026. I reinstalled Texlive 2025 latest version, got the expected fonts, and the log-file says all KOMA-packages are v3.49.2. The Frakturx-package is a relict from about 2010/11, it was used for a history project in university and I install the package routinely in texmf-local ( I am a Biologist, but I like scanning and reprinting old textbooks).
implementation docu added
\DocumentMetadata usage results in fatal error
Nothing has been changed in KOMA-Script in the font handling since several years. And indeed your example also does not compile without error using TL25 instead of TL26: /usr/local/texlive/2025/texmf-dist/tex/latex/base/fontenc.sty:115: Package font enc Error: Encoding file `lf2enc.def' not found. (fontenc) You might have misspelled the name of the encoding (fontenc) or a required support package (e.g., cyrillic) is (fontenc) missing in your installation. … /usr/local/texlive/2025/texmf-dist/tex/latex/base/fontenc.sty:116:...
Nothing has been changed in KOMA-Script in the font handling since several years. And indeed your example also does not compile without error using TL25 instead of TL26: /usr/local/texlive/2025/texmf-dist/tex/latex/base/fontenc.sty:115: Package font enc Error: Encoding file `lf2enc.def' not found. (fontenc) You might have misspelled the name of the encoding (fontenc) or a required support package (e.g., cyrillic) is (fontenc) missing in your installation. … /usr/local/texlive/2025/texmf-dist/tex/latex/base/fontenc.sty:116:...
Unable to change font of headings and toc after installing TeXlive 2026
scrlttr2 not compatible with tagged PDF
BTW: If you want to know more about tagging with KOMA-Script see https://github.com/TeXhackse/komascript-tagging-lab.
BTW: If you want to know more about tagging with KOMA-Script see https://github.com/TeXhackse/komascript-tagging-lab.
release 3.49.2
Releases
Release 3.49.1
Release 3.49.2
Releases
Releases
Release 3.49.1
Release 3.49.2
Release 3.49.2
prepared for release 2026/02/02 v3.49.2
Yes, it was a bug in the build process. Versions with two dots in the version number automatically have been marked as beta version. This is no longer correct, but I've missed it before the release. It is already changed in [r4260]. Workaround: Ignore the message. I hope, I can make one more release next week.
Warning: "… NOT AN OFFICIAL RELEASE…"
Yes, it was a bug in the build process. Versions with two dots in the version number automatically has been marked as beta version. This is no longer correct, but I've missed it before the release. It is already changed in [r4260]. Workaround: Ignore the message. I hope, I can make one more release next week.
Warning: "… NOT AN OFFICIAL RELEASE…"
beta version automatism changed
Releases
Release 3.49
Release 3.49
Release 3.49
Release 3.49.1
Release 3.50
Release 3.50
Releases
Release 3.49
Release 3.49.1
release 3.49.1
prepared for bugfix release v3.49.1
babel message has changed in babel-german v2.99
babel message has changed in babel-german v2.99
Sorry for forgetting to document the workaround: Load tocbasic and all packages that load tocbasic themselves before caption. Of course, you can also install the current developer version of KOMA-Script instead. How to do this is documented in section "Testing" of CONTRIBUTING.md.
Sorry for forgetting to document the workaround: Load tocbasic and all packages that load tocbasic themselves after caption. Of course, you can also install the current developer version of KOMA-Script instead. How to do this is documented in section "Testing" of CONTRIBUTING.md.
tocbasis generate error if caption was loaded before
Duplicate of [#103].
tocbasis generate error if caption was loaded before
replaced version v3.40 by v3.49.1 because it is a patch level version only
long argument for \caption, \captionabove, \captionbelow etc.
Problem with recent babel package and language "spanish"
Workaround added in [r4254].
Already fixed in [r4250] + [r4251].
tocbasic throws error when nomencl is loaded after caption
Already fixed in [r4251].
tocbasic throws error when nomencl is loaded after caption
babel catcode issue workaround
improved babel catcode issue workaround
new beta already started
\cs_if_exist:NTF \KOMAClassName has to be \cs_if_exist:NT …
patch \caption@documentclass only for KOMA-Script classes and disable package with beamer class
workaround for babel-spanish catcode issue [#102]
The alternative would be to once again redefine \@startsection, which has been removed to avoid several other issues. So this is not really an option.
You get the same error with: \documentclass{book} \AddToHook{cmd/@startsection/before}{\typeout{Hook Test}} \usepackage[spanish]{babel} \begin{document} Test \end{document} So IMHO this is a babel-spanish issue not a KOMA-Script issue. BTW: KOMA-Script does not use \@startsection anymore and the new version does no longer redefine it but only adds a hook to warn that several features are no longer available, when using \@startsection. See also [wiki-en:Release 3.49] resp. [wiki-de:Release 3.49].
In some sense it is a KOMA issue, as KOMA is the one doing the patching. Command hooks are quite nice, but they are no fully safe if catcode changes are involved and personally I try to avoid them for long term code. See e.g. https://github.com/latex3/latex2e/issues/1099
You get the same error with: \documentclass{book} \AddToHook{cmd/@startsection/before}{\typeout{Hook Test}} \usepackage[spanish]{babel} \begin{document} Test \end{document} So IMHO this is a babel-spanish issue not a KOMA-Script issue. BTW: KOMA-Script does not use \@startsection anymore and the new version does no longer redefine it but only adds a hook to warn that several features are no longer available, when using \@startsection.
You get the same error with: \documentclass{book} \AddToHook{cmd/@startsection/before}{\typeout{Hook Test}} \usepackage[spanish]{babel} \begin{document} Test \end{document} So IMHO this is a babel-spanish issue not a KOMA-Script issue. BTW: KOMA-Script does not use \@startsection anymore and the new version does no longer redefine it but only adds a hook to warn, that several features are no longer available, when using \@startsection.
You get the same error with: \documentclass{book} \AddToHook{cmd/@startsection/before}{\typeout{Hook Test}} \usepackage[spanish]{babel} \begin{document} Test \end{document} So IMHO this is a babel-spanish issue not a KOMA-Script issue.
Problem with recent babel package and language "spanish"
\caption indeed accepted arguments with \par (because KOMA-Script did not touch \caption itself), but KOMA-Script wasn't able to process them, i.e., using a paragraph resulted in an error inside \@settodim. A somehow "strange error", because it was hard to understand. Hm, but yes, in combination with package caption paragraphs have been possible. Maybe I can support it, but this would result again in the "less than perfect" error messages at strange places, when not using package caption. But wouldn't...
\caption indeed accepted arguments with \par (because KOMA-Script did not touch \caption itself), but KOMA-Script wasn't able to process them, i.e., using a paragraph resulted in an error inside \@settodim. A somehow "strange error", because it was hard to understand. Hm, but yes, in combination with package caption paragraphs have been possible. Maybe I can support it, but this would result again in the "less than perfect" error messages at strange places, when not using package caption. But wouldn't...
\caption indeed accepted arguments with \par (because KOMA-Script did not touch \caption itself), but KOMA-Script wasn't able to process them, i.e., using a paragraph resulted in an error inside \@settodim. A somehow "strange error", because it was hard to understand. Hm, but yes, in combination with package caption paragraphs have been possible. Maybe I can support it, but this would result again in the "less than perfect" error messages at strange places, when not using package caption. But wouldn't...
\caption indeed accepted arguments with \par (because KOMA-Script did not touch \caption itself), but KOMA-Script wasn't able to process them, i.e., using a paragraph resulted in an error inside \@settodim. A somehow "strange error", because it was hard to understand. Hm, but yes, in combination with package caption paragraphs have been possible. Maybe I can support it, but this would result again in the "less than perfect" error messages at strange places, when not using package caption. But maybe...
long argument for \caption, \captionabove, \captionbelow etc.
Releases
Release 3.49
Release 3.48
Release 3.49
Release 3.50
Releases
Release 3.48
Release 3.49
Release 3.50
Release 3.50
release 3.49
release 3.49
prepared for release 3.49
The code in scrkernel-footnotes.dtx is used only in scrextend. I've changed it in [r4245] to use xpatch if available, try also etoolbox of only this one is available and use hard coded redefinition in other cases.
Patching using etoolbox or xpatch
The code in scrkernel-footnotes.dtx is used only in scrextend. I've changed it in [r4225] to use xpatch if available, try also etoolbox of only this one is available and use hard coded redefinition in other cases.
patching uses xpatch if available → [#61]
replacing eso-pic
Suggesting `tocafterskip` option for `\RedeclareSectionCommand`
Feature Request: Customizable vertical space before \closing in scrlttr2
documentation occasionally misspells “scrreprt” as “scrreport”