CTAN sync 202404110301

59 files changed, 5075 insertions, 2463 deletions

diff --git a/FILES.byname b/FILES.byname
index 98115f6030..04b4692ce0 100644
--- a/FILES.byname
+++ b/FILES.byname
@@ -2081,12 +2081,12 @@
 2024/03/12 |       1837 | biblio/citation-style-language/README.md
 2024/03/12 |      12878 | biblio/citation-style-language/vancouver.csl
 2024/03/12 |    4553440 | biblio/citation-style-language.zip
-2024/04/09 |       1678 | biblio/ctan-bibdata/biblatex-ctan/ctan.bbx
+2024/04/10 |       1678 | biblio/ctan-bibdata/biblatex-ctan/ctan.bbx
 2022/10/08 |        127 | biblio/ctan-bibdata/biblatex-ctan/ctan.cbx
-2024/04/09 |    2860148 | biblio/ctan-bibdata/ctan.bib
-2024/04/09 |    3708800 | biblio/ctan-bibdata/ctan.pdf
+2024/04/10 |    2860154 | biblio/ctan-bibdata/ctan.bib
+2024/04/10 |    3708800 | biblio/ctan-bibdata/ctan.pdf
 2023/01/16 |       1489 | biblio/ctan-bibdata/README
-2024/04/09 |    4120075 | biblio/ctan-bibdata.zip
+2024/04/10 |    4120086 | biblio/ctan-bibdata.zip
 2023/02/23 |       3126 | biblio/pbibtex/pbibtex-base/cpp.awk
 2023/02/23 |       1009 | biblio/pbibtex/pbibtex-base/generate.sh
 2023/02/23 |      22362 | biblio/pbibtex/pbibtex-base/jabbrv.bst
@@ -5448,7 +5448,7 @@
 1990/10/02 |       5440 | dviware/vutex/vaxvms.hlp
 1990/10/02 |        812 | dviware/vutex/vaxvms.ins
 1990/10/02 |     127576 | dviware/vutex/vutex.web
-2024/04/09 |      52570 | FILES.last07days
+2024/04/10 |      56182 | FILES.last07days
 2021/07/24 |    1139410 | fonts/aboensis/Aboensis.glyphs
 2021/07/24 |   18907382 | fonts/aboensis/aboensis.pdf
 2021/07/24 |     137860 | fonts/aboensis/Aboensis-Regular.otf
@@ -230814,19 +230814,19 @@
 2017/04/19 |      25397 | macros/latex/contrib/css-colors/css-colors.xlsx
 2016/12/26 |        794 | macros/latex/contrib/css-colors/README.txt
 2017/04/21 |    2106199 | macros/latex/contrib/css-colors.zip
-2024/03/22 |        495 | macros/latex/contrib/cs-techrep/COPYING
-2024/03/22 |      24314 | macros/latex/contrib/cs-techrep/cs-techrep.dtx
-2024/03/22 |        727 | macros/latex/contrib/cs-techrep/cs-techrep.ins
-2024/03/22 |     187700 | macros/latex/contrib/cs-techrep/cs-techrep.pdf
-2024/03/22 |        364 | macros/latex/contrib/cs-techrep/docstrip.cfg
-2024/03/22 |       1810 | macros/latex/contrib/cs-techrep/README
-2024/03/22 |      29633 | macros/latex/contrib/cs-techrep/template/cpn_all_all.bib
-2024/03/22 |      18588 | macros/latex/contrib/cs-techrep/template/cpn_supervised_all.bib
-2024/03/22 |     144956 | macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.pdf
-2024/03/22 |      11367 | macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.tex
-2024/03/22 |        276 | macros/latex/contrib/cs-techrep/template/selfref.bib
-2024/03/22 |      12954 | macros/latex/contrib/cs-techrep/template/webdev_commons.bib
-2024/03/23 |     329342 | macros/latex/contrib/cs-techrep.zip
+2024/04/10 |        500 | macros/latex/contrib/cs-techrep/COPYING
+2024/04/10 |      24190 | macros/latex/contrib/cs-techrep/cs-techrep.dtx
+2024/04/10 |        846 | macros/latex/contrib/cs-techrep/cs-techrep.ins
+2024/04/10 |     187505 | macros/latex/contrib/cs-techrep/cs-techrep.pdf
+2024/04/10 |        364 | macros/latex/contrib/cs-techrep/docstrip.cfg
+2024/04/10 |       1810 | macros/latex/contrib/cs-techrep/README
+2024/04/10 |      29814 | macros/latex/contrib/cs-techrep/template/cpn_all_all.bib
+2024/04/10 |      18588 | macros/latex/contrib/cs-techrep/template/cpn_supervised_all.bib
+2024/04/10 |     145442 | macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.pdf
+2024/04/10 |      11523 | macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.tex
+2024/04/10 |        330 | macros/latex/contrib/cs-techrep/template/selfref.bib
+2024/04/10 |      12954 | macros/latex/contrib/cs-techrep/template/webdev_commons.bib
+2024/04/10 |     329129 | macros/latex/contrib/cs-techrep.zip
 2019/08/08 |      48847 | macros/latex/contrib/csvmerge/csvmerge.dtx
 2019/08/08 |       1461 | macros/latex/contrib/csvmerge/csvmerge.ins
 2019/08/10 |     218699 | macros/latex/contrib/csvmerge/csvmerge.pdf
@@ -238419,28 +238419,28 @@
 2009/09/02 |     174319 | macros/latex/contrib/hyphenat/hyphenat.pdf
 2009/09/02 |       2042 | macros/latex/contrib/hyphenat/README
 2009/09/02 |     164702 | macros/latex/contrib/hyphenat.zip
-2024/03/20 |        498 | macros/latex/contrib/iaria/COPYING
-2024/03/20 |        344 | macros/latex/contrib/iaria/docstrip.cfg
-2024/03/20 |      12635 | macros/latex/contrib/iaria/iaria.dtx
-2024/03/20 |        710 | macros/latex/contrib/iaria/iaria.ins
-2024/03/20 |     172037 | macros/latex/contrib/iaria/iaria.pdf
-2024/03/20 |        498 | macros/latex/contrib/iaria-lite/COPYING
-2024/03/20 |        364 | macros/latex/contrib/iaria-lite/docstrip.cfg
-2024/03/20 |      10122 | macros/latex/contrib/iaria-lite/iaria-lite.dtx
-2024/03/20 |        730 | macros/latex/contrib/iaria-lite/iaria-lite.ins
-2024/03/20 |     169779 | macros/latex/contrib/iaria-lite/iaria-lite.pdf
-2024/03/20 |       1427 | macros/latex/contrib/iaria-lite/README
-2024/03/20 |      29633 | macros/latex/contrib/iaria-lite/template/cpn_all_all.bib
-2024/03/20 |      18588 | macros/latex/contrib/iaria-lite/template/cpn_supervised_all.bib
-2024/03/20 |     132907 | macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.pdf
-2024/03/20 |       8573 | macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.tex
-2024/03/20 |     293129 | macros/latex/contrib/iaria-lite.zip
-2024/03/20 |       1398 | macros/latex/contrib/iaria/README
-2024/03/20 |      29633 | macros/latex/contrib/iaria/template/cpn_all_all.bib
-2024/03/20 |      18588 | macros/latex/contrib/iaria/template/cpn_supervised_all.bib
-2024/03/20 |     132856 | macros/latex/contrib/iaria/template/iaria-example-neumann.pdf
-2024/03/20 |       7034 | macros/latex/contrib/iaria/template/iaria-example-neumann.tex
-2024/03/20 |     295615 | macros/latex/contrib/iaria.zip
+2024/04/10 |        500 | macros/latex/contrib/iaria/COPYING
+2024/04/10 |        344 | macros/latex/contrib/iaria/docstrip.cfg
+2024/04/10 |      13100 | macros/latex/contrib/iaria/iaria.dtx
+2024/04/10 |        821 | macros/latex/contrib/iaria/iaria.ins
+2024/04/10 |     172223 | macros/latex/contrib/iaria/iaria.pdf
+2024/04/10 |        500 | macros/latex/contrib/iaria-lite/COPYING
+2024/04/10 |        364 | macros/latex/contrib/iaria-lite/docstrip.cfg
+2024/04/10 |      10587 | macros/latex/contrib/iaria-lite/iaria-lite.dtx
+2024/04/10 |        846 | macros/latex/contrib/iaria-lite/iaria-lite.ins
+2024/04/10 |     170730 | macros/latex/contrib/iaria-lite/iaria-lite.pdf
+2024/04/10 |       1820 | macros/latex/contrib/iaria-lite/README
+2024/04/10 |      29814 | macros/latex/contrib/iaria-lite/template/cpn_all_all.bib
+2024/04/10 |      18588 | macros/latex/contrib/iaria-lite/template/cpn_supervised_all.bib
+2024/04/10 |     132913 | macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.pdf
+2024/04/10 |       8741 | macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.tex
+2024/04/10 |     294340 | macros/latex/contrib/iaria-lite.zip
+2024/04/10 |       1786 | macros/latex/contrib/iaria/README
+2024/04/10 |      29814 | macros/latex/contrib/iaria/template/cpn_all_all.bib
+2024/04/10 |      18588 | macros/latex/contrib/iaria/template/cpn_supervised_all.bib
+2024/04/10 |     132891 | macros/latex/contrib/iaria/template/iaria-example-neumann.pdf
+2024/04/10 |       7299 | macros/latex/contrib/iaria/template/iaria-example-neumann.tex
+2024/04/10 |     296151 | macros/latex/contrib/iaria.zip
 2023/07/26 |       8071 | macros/latex/contrib/ibrackets/ibrackets.dtx
 2023/07/26 |       1993 | macros/latex/contrib/ibrackets/ibrackets.ins
 2023/07/26 |      93437 | macros/latex/contrib/ibrackets/ibrackets.pdf
@@ -240299,6 +240299,12 @@
 2024/03/06 |      23652 | macros/latex/contrib/jslectureplanner/jsmembertable.sty
 2024/03/06 |      10156 | macros/latex/contrib/jslectureplanner/README
 2024/03/06 |    1498662 | macros/latex/contrib/jslectureplanner.zip
+2024/04/09 |     380391 | macros/latex/contrib/jsonparse/jsonparse-doc.pdf
+2024/04/09 |      16885 | macros/latex/contrib/jsonparse/jsonparse-doc.tex
+2024/04/09 |      15644 | macros/latex/contrib/jsonparse/jsonparse.sty
+2024/04/05 |      19105 | macros/latex/contrib/jsonparse/LICENCE
+2024/04/09 |       1485 | macros/latex/contrib/jsonparse/README.md
+2024/04/10 |     379536 | macros/latex/contrib/jsonparse.zip
 2015/06/02 |     141342 | macros/latex/contrib/jumplines/jumplines_doc.pdf
 2015/06/02 |      10822 | macros/latex/contrib/jumplines/jumplines_doc.tex
 2015/06/02 |     110248 | macros/latex/contrib/jumplines/jumplines_example.pdf
@@ -297625,10 +297631,10 @@
 2021/10/26 |     246523 | support/latex-make/texdepends.pdf
 2021/10/26 |    1069049 | support/latex-make.zip
 2006/03/12 |       5889 | support/latexmake.zip
-2024/01/30 |      43527 | support/latexmk/CHANGES
+2024/04/10 |      44371 | support/latexmk/CHANGES
 2013/12/03 |      17993 | support/latexmk/COPYING
-2022/01/28 |       2881 | support/latexmk/example_rcfiles/asymptote_latexmkrc
-2017/11/20 |        853 | support/latexmk/example_rcfiles/bib2gls_latexmkrc
+2024/02/29 |       2388 | support/latexmk/example_rcfiles/asymptote_latexmkrc
+2024/02/04 |       1623 | support/latexmk/example_rcfiles/bib2gls_latexmkrc
 2022/01/29 |       2995 | support/latexmk/example_rcfiles/chapterbib-latexmkrc
 2022/01/26 |       1113 | support/latexmk/example_rcfiles/clean_pattern_latexmkrc
 2022/02/03 |       5730 | support/latexmk/example_rcfiles/dot2tex-latexmkrc
@@ -297640,6 +297646,7 @@
 2020/11/15 |       6617 | support/latexmk/example_rcfiles/hyperxmp-latexmkrc
 2020/02/13 |       4092 | support/latexmk/example_rcfiles/knitr-latexmkrc
 2017/01/14 |        272 | support/latexmk/example_rcfiles/lualatex_latexmkrc
+2024/03/29 |      10738 | support/latexmk/example_rcfiles/memoize_latexmkrc
 2022/01/15 |       1986 | support/latexmk/example_rcfiles/minted_latexmkrc
 2014/03/04 |        991 | support/latexmk/example_rcfiles/mpost_latexmkrc
 2016/10/13 |        303 | support/latexmk/example_rcfiles/nomenclature_latexmkrc
@@ -297650,7 +297657,7 @@
 2023/11/06 |       3006 | support/latexmk/example_rcfiles/README-latexmk-rcfiles
 2021/09/11 |       1024 | support/latexmk/example_rcfiles/sagetex_latexmkrc
 2012/08/04 |       3447 | support/latexmk/example_rcfiles/schulz-texshop-latexmkrc
-2019/03/26 |       1378 | support/latexmk/example_rcfiles/splitindex.latexmkrc
+2024/03/06 |       1513 | support/latexmk/example_rcfiles/splitindex_latexmkrc
 2020/02/13 |       2535 | support/latexmk/example_rcfiles/sweave_latexmkrc
 2012/10/02 |       1161 | support/latexmk/example_rcfiles/tex4ht-latexmkrc
 2021/11/20 |       2176 | support/latexmk/example_rcfiles/texinfo-latexmkrc
@@ -297670,14 +297677,14 @@
 2007/09/29 |       1492 | support/latexmk/extra-scripts/pst2pdf_for_latexmk_README.txt
 2016/10/13 |       4828 | support/latexmk/extra-scripts/README-latexmk-scripts
 2006/01/14 |       5588 | support/latexmk/extra-scripts/startacroread
-2024/01/31 |      17975 | support/latexmk/INSTALL
-2024/01/31 |     195651 | support/latexmk/latexmk.1
+2024/04/08 |      17974 | support/latexmk/INSTALL
+2024/04/08 |     206488 | support/latexmk/latexmk.1
 2022/03/15 |       1219 | support/latexmk/latexmk.cmd
-2024/01/31 |     230287 | support/latexmk/latexmk.pdf
-2024/01/31 |     516745 | support/latexmk/latexmk.pl
-2024/01/31 |     242840 | support/latexmk/latexmk.txt
-2024/01/31 |       2523 | support/latexmk/README
-2024/04/02 |     539823 | support/latexmk.zip
+2024/04/08 |     241304 | support/latexmk/latexmk.pdf
+2024/04/10 |     524565 | support/latexmk/latexmk.pl
+2024/04/08 |     256981 | support/latexmk/latexmk.txt
+2024/04/10 |       2521 | support/latexmk/README
+2024/04/10 |     563689 | support/latexmk.zip
 1997/11/24 |       7551 | support/latexn/latexn
 2023/02/27 |      22923 | support/latexpand/latexpand
 2023/02/24 |       1529 | support/latexpand/LICENCE
@@ -301074,9 +301081,9 @@
 1999/09/13 |      17553 | support/texref/texref
 1999/09/14 |      10702 | support/texref/texref.1
 2006/03/12 |      12757 | support/texref.zip
-2024/03/24 |        750 | support/texshop/README.txt
-2024/03/24 |        702 | support/texshop/texshop531.html
-2024/03/24 |   69654494 | support/texshop/texshop531.zip
+2024/04/10 |        750 | support/texshop/README.txt
+2024/04/10 |       1925 | support/texshop/texshop532.html
+2024/04/10 |   69576234 | support/texshop/texshop532.zip
 1994/11/10 |     411107 | support/texspell/texspell.zip
 1994/11/10 |      42315 | support/texspell/texspsrc.zip
 1994/11/10 |     411107 | support/texspell.zip
@@ -307622,9 +307629,9 @@
 2019/02/28 |        768 | systems/texlive/tlnet/archive/dickimaw.r32925.tar.xz
 2024/02/07 |      19788 | systems/texlive/tlnet/archive/dictsym.doc.r69720.tar.xz
 2024/02/07 |      31652 | systems/texlive/tlnet/archive/dictsym.r69720.tar.xz
-2024/04/09 |     264372 | systems/texlive/tlnet/archive/didactic.doc.r70890.tar.xz
-2024/04/09 |       4504 | systems/texlive/tlnet/archive/didactic.r70890.tar.xz
-2024/04/09 |      10996 | systems/texlive/tlnet/archive/didactic.source.r70890.tar.xz
+2024/04/10 |     268488 | systems/texlive/tlnet/archive/didactic.doc.r70901.tar.xz
+2024/04/10 |       4612 | systems/texlive/tlnet/archive/didactic.r70901.tar.xz
+2024/04/10 |      11776 | systems/texlive/tlnet/archive/didactic.source.r70901.tar.xz
 2024/02/29 |     487352 | systems/texlive/tlnet/archive/didec.doc.r70229.tar.xz
 2024/02/29 |       4856 | systems/texlive/tlnet/archive/didec.r70229.tar.xz
 2023/11/15 |    1346876 | systems/texlive/tlnet/archive/diffcoeff.doc.r68838.tar.xz
@@ -307999,22 +308006,22 @@
 2024/03/01 |      81960 | systems/texlive/tlnet/archive/dviout-util.x86_64-solaris.r70276.tar.xz
 2023/03/24 |    2735736 | systems/texlive/tlnet/archive/dviout.windows.r66655.tar.xz
 2024/03/08 |     412872 | systems/texlive/tlnet/archive/dvipdfmx.aarch64-linux.r70489.tar.xz
-2024/03/08 |     398084 | systems/texlive/tlnet/archive/dvipdfmx.amd64-freebsd.r70489.tar.xz
+2024/04/10 |     398032 | systems/texlive/tlnet/archive/dvipdfmx.amd64-freebsd.r70898.tar.xz
 2024/03/09 |     395992 | systems/texlive/tlnet/archive/dvipdfmx.amd64-netbsd.r70499.tar.xz
 2024/03/08 |     349384 | systems/texlive/tlnet/archive/dvipdfmx.armhf-linux.r70489.tar.xz
 2023/12/14 |    3125132 | systems/texlive/tlnet/archive/dvipdfmx.doc.r69127.tar.xz
-2024/03/08 |     399344 | systems/texlive/tlnet/archive/dvipdfmx.i386-freebsd.r70489.tar.xz
-2024/03/08 |     469944 | systems/texlive/tlnet/archive/dvipdfmx.i386-linux.r70489.tar.xz
+2024/04/10 |     398020 | systems/texlive/tlnet/archive/dvipdfmx.i386-freebsd.r70898.tar.xz
+2024/04/10 |     469988 | systems/texlive/tlnet/archive/dvipdfmx.i386-linux.r70898.tar.xz
 2024/03/09 |     368092 | systems/texlive/tlnet/archive/dvipdfmx.i386-netbsd.r70499.tar.xz
-2024/03/08 |     427836 | systems/texlive/tlnet/archive/dvipdfmx.i386-solaris.r70489.tar.xz
+2024/04/10 |     428004 | systems/texlive/tlnet/archive/dvipdfmx.i386-solaris.r70898.tar.xz
 2023/12/14 |      26704 | systems/texlive/tlnet/archive/dvipdfmx.r69127.tar.xz
-2024/03/09 |     805944 | systems/texlive/tlnet/archive/dvipdfmx.universal-darwin.r70520.tar.xz
-2024/03/07 |     353704 | systems/texlive/tlnet/archive/dvipdfmx.windows.r70450.tar.xz
+2024/04/10 |     805532 | systems/texlive/tlnet/archive/dvipdfmx.universal-darwin.r70899.tar.xz
+2024/04/10 |     353640 | systems/texlive/tlnet/archive/dvipdfmx.windows.r70904.tar.xz
 2024/03/11 |     410760 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-cygwin.r70560.tar.xz
 2024/03/08 |     412704 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-darwinlegacy.r70489.tar.xz
-2024/03/08 |     460516 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-linuxmusl.r70489.tar.xz
-2024/03/08 |     438496 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-linux.r70489.tar.xz
-2024/03/08 |     464940 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-solaris.r70489.tar.xz
+2024/04/10 |     460464 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-linuxmusl.r70898.tar.xz
+2024/04/10 |     438856 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-linux.r70898.tar.xz
+2024/04/10 |     465028 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-solaris.r70898.tar.xz
 2024/03/01 |     463612 | systems/texlive/tlnet/archive/dvipng.aarch64-linux.r70276.tar.xz
 2024/03/01 |     440424 | systems/texlive/tlnet/archive/dvipng.amd64-freebsd.r70276.tar.xz
 2024/03/01 |     437212 | systems/texlive/tlnet/archive/dvipng.amd64-netbsd.r70286.tar.xz
@@ -308283,9 +308290,9 @@
 2019/02/28 |       2216 | systems/texlive/tlnet/archive/elocalloc.source.r42712.tar.xz
 2021/08/11 |     388088 | systems/texlive/tlnet/archive/elpres.doc.r60209.tar.xz
 2021/08/11 |      75136 | systems/texlive/tlnet/archive/elpres.r60209.tar.xz
-2020/11/25 |     807964 | systems/texlive/tlnet/archive/elsarticle.doc.r56999.tar.xz
-2020/11/25 |      18868 | systems/texlive/tlnet/archive/elsarticle.r56999.tar.xz
-2020/11/25 |      10880 | systems/texlive/tlnet/archive/elsarticle.source.r56999.tar.xz
+2024/04/10 |     807536 | systems/texlive/tlnet/archive/elsarticle.doc.r70902.tar.xz
+2024/04/10 |      18920 | systems/texlive/tlnet/archive/elsarticle.r70902.tar.xz
+2024/04/10 |      11016 | systems/texlive/tlnet/archive/elsarticle.source.r70902.tar.xz
 2022/04/06 |     349288 | systems/texlive/tlnet/archive/els-cas-templates.doc.r62931.tar.xz
 2022/04/06 |      54856 | systems/texlive/tlnet/archive/els-cas-templates.r62931.tar.xz
 2023/04/11 |    1015496 | systems/texlive/tlnet/archive/elteiktdk.doc.r66821.tar.xz
@@ -314069,8 +314076,8 @@
 2019/12/07 |     594984 | systems/texlive/tlnet/archive/pmboxdraw.doc.r53046.tar.xz
 2019/12/07 |       7216 | systems/texlive/tlnet/archive/pmboxdraw.r53046.tar.xz
 2019/12/07 |      14376 | systems/texlive/tlnet/archive/pmboxdraw.source.r53046.tar.xz
-2024/01/11 |     379560 | systems/texlive/tlnet/archive/pmdraw.doc.r69366.tar.xz
-2024/01/11 |       6352 | systems/texlive/tlnet/archive/pmdraw.r69366.tar.xz
+2024/04/10 |     386828 | systems/texlive/tlnet/archive/pmdraw.doc.r70900.tar.xz
+2024/04/10 |       6420 | systems/texlive/tlnet/archive/pmdraw.r70900.tar.xz
 2019/02/28 |     129312 | systems/texlive/tlnet/archive/pmgraph.doc.r15878.tar.xz
 2019/02/28 |      10064 | systems/texlive/tlnet/archive/pmgraph.r15878.tar.xz
 2023/03/05 |     967940 | systems/texlive/tlnet/archive/pmhanguljamo.doc.r66361.tar.xz
@@ -316464,7 +316471,7 @@
 2022/09/13 |        600 | systems/texlive/tlnet/archive/texlive-scripts.amd64-freebsd.r64356.tar.xz
 2022/09/13 |        596 | systems/texlive/tlnet/archive/texlive-scripts.amd64-netbsd.r64356.tar.xz
 2022/09/13 |        596 | systems/texlive/tlnet/archive/texlive-scripts.armhf-linux.r64356.tar.xz
-2024/04/08 |     434544 | systems/texlive/tlnet/archive/texlive-scripts.doc.r70879.tar.xz
+2024/04/10 |     434424 | systems/texlive/tlnet/archive/texlive-scripts.doc.r70895.tar.xz
 2020/01/27 |        916 | systems/texlive/tlnet/archive/texlive-scripts-extra.aarch64-linux.r53577.tar.xz
 2020/01/27 |        924 | systems/texlive/tlnet/archive/texlive-scripts-extra.amd64-freebsd.r53577.tar.xz
 2020/01/27 |        916 | systems/texlive/tlnet/archive/texlive-scripts-extra.amd64-netbsd.r53577.tar.xz
@@ -316486,7 +316493,7 @@
 2022/09/13 |        592 | systems/texlive/tlnet/archive/texlive-scripts.i386-linux.r64356.tar.xz
 2022/09/13 |        596 | systems/texlive/tlnet/archive/texlive-scripts.i386-netbsd.r64356.tar.xz
 2022/09/13 |        596 | systems/texlive/tlnet/archive/texlive-scripts.i386-solaris.r64356.tar.xz
-2024/04/08 |     114204 | systems/texlive/tlnet/archive/texlive-scripts.r70879.tar.xz
+2024/04/10 |     114136 | systems/texlive/tlnet/archive/texlive-scripts.r70895.tar.xz
 2022/09/13 |        580 | systems/texlive/tlnet/archive/texlive-scripts.universal-darwin.r64356.tar.xz
 2024/03/01 |      60292 | systems/texlive/tlnet/archive/texlive-scripts.windows.r70269.tar.xz
 2022/09/13 |        596 | systems/texlive/tlnet/archive/texlive-scripts.x86_64-cygwin.r64356.tar.xz
@@ -317323,9 +317330,9 @@
 2019/02/28 |      13868 | systems/texlive/tlnet/archive/uaclasses.source.r15878.tar.xz
 2021/01/08 |      30020 | systems/texlive/tlnet/archive/uafthesis.doc.r57349.tar.xz
 2021/01/08 |       7548 | systems/texlive/tlnet/archive/uafthesis.r57349.tar.xz
-2023/04/11 |    4360632 | systems/texlive/tlnet/archive/uantwerpendocs.doc.r66819.tar.xz
-2023/04/11 |    6475944 | systems/texlive/tlnet/archive/uantwerpendocs.r66819.tar.xz
-2023/04/11 |      44216 | systems/texlive/tlnet/archive/uantwerpendocs.source.r66819.tar.xz
+2024/04/10 |    4367680 | systems/texlive/tlnet/archive/uantwerpendocs.doc.r70903.tar.xz
+2024/04/10 |    6475972 | systems/texlive/tlnet/archive/uantwerpendocs.r70903.tar.xz
+2024/04/10 |      45820 | systems/texlive/tlnet/archive/uantwerpendocs.source.r70903.tar.xz
 2019/02/28 |     106832 | systems/texlive/tlnet/archive/uassign.doc.r38459.tar.xz
 2019/02/28 |       1984 | systems/texlive/tlnet/archive/uassign.r38459.tar.xz
 2023/03/21 |     273308 | systems/texlive/tlnet/archive/ucalgmthesis.doc.r66602.tar.xz
@@ -318407,17 +318414,17 @@
 2020/01/24 |       8760 | systems/texlive/tlnet/archive/zxjatype.r53500.tar.xz
 2020/07/18 |      47816 | systems/texlive/tlnet/archive/zztex.doc.r55862.tar.xz
 2020/07/18 |     101724 | systems/texlive/tlnet/archive/zztex.r55862.tar.xz
-2024/02/05 |     125030 | systems/texlive/tlnet/install-tl
-2024/04/09 |    5749104 | systems/texlive/tlnet/install-tl-unx.tar.gz
-2024/04/09 |        152 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512
-2024/04/09 |        488 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512.asc
+2024/04/09 |     125043 | systems/texlive/tlnet/install-tl
+2024/04/10 |    5749137 | systems/texlive/tlnet/install-tl-unx.tar.gz
+2024/04/10 |        152 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512
+2024/04/10 |        488 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512.asc
 2023/05/13 |       5083 | systems/texlive/tlnet/install-tl-windows.bat
-2024/04/09 |   27719584 | systems/texlive/tlnet/install-tl-windows.exe
-2024/04/09 |        153 | systems/texlive/tlnet/install-tl-windows.exe.sha512
-2024/04/09 |        488 | systems/texlive/tlnet/install-tl-windows.exe.sha512.asc
-2024/04/09 |   34425343 | systems/texlive/tlnet/install-tl.zip
-2024/04/09 |        145 | systems/texlive/tlnet/install-tl.zip.sha512
-2024/04/09 |        488 | systems/texlive/tlnet/install-tl.zip.sha512.asc
+2024/04/10 |   27716340 | systems/texlive/tlnet/install-tl-windows.exe
+2024/04/10 |        153 | systems/texlive/tlnet/install-tl-windows.exe.sha512
+2024/04/10 |        488 | systems/texlive/tlnet/install-tl-windows.exe.sha512.asc
+2024/04/10 |   34425285 | systems/texlive/tlnet/install-tl.zip
+2024/04/10 |        145 | systems/texlive/tlnet/install-tl.zip.sha512
+2024/04/10 |        488 | systems/texlive/tlnet/install-tl.zip.sha512.asc
 2024/03/13 |       1229 | systems/texlive/tlnet/README.md
 2024/03/13 |          0 | systems/texlive/tlnet/TEXLIVE_2024
 2024/01/02 |       9011 | systems/texlive/tlnet/tlpkg/gpg/pubring.gpg
@@ -318427,7 +318434,7 @@
 2024/01/02 |       1280 | systems/texlive/tlnet/tlpkg/gpg/trustdb.gpg
 2024/01/16 |      50726 | systems/texlive/tlnet/tlpkg/installer/config.guess
 2010/11/11 |      11651 | systems/texlive/tlnet/tlpkg/installer/COPYING.MinGW-runtime.txt
-2024/04/07 |       7325 | systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl
+2024/04/09 |       7023 | systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl
 2024/03/15 |     229654 | systems/texlive/tlnet/tlpkg/installer/curl/curl-ca-bundle.crt
 2020/04/15 |    2606592 | systems/texlive/tlnet/tlpkg/installer/curl/curl.exe
 2017/04/16 |       2629 | systems/texlive/tlnet/tlpkg/installer/installer-options.txt
@@ -318469,12 +318476,12 @@
 2023/02/21 |      20371 | systems/texlive/tlnet/tlpkg/TeXLive/TLCrypto.pm
 2024/01/31 |       5840 | systems/texlive/tlnet/tlpkg/TeXLive/TLDownload.pm
 2023/04/08 |      28167 | systems/texlive/tlnet/tlpkg/TeXLive/TLPaper.pm
-2024/04/09 |   19415475 | systems/texlive/tlnet/tlpkg/texlive.tlpdb
-2024/04/09 |         48 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5
+2024/04/10 |   19415529 | systems/texlive/tlnet/tlpkg/texlive.tlpdb
+2024/04/10 |         48 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5
 2024/03/10 |      87229 | systems/texlive/tlnet/tlpkg/TeXLive/TLPDB.pm
-2024/04/09 |        144 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512
-2024/04/09 |        488 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc
-2024/04/09 |    2562444 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz
+2024/04/10 |        144 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512
+2024/04/10 |        488 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc
+2024/04/10 |    2564424 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz
 2023/02/20 |      58928 | systems/texlive/tlnet/tlpkg/TeXLive/TLPOBJ.pm
 2023/06/11 |      42749 | systems/texlive/tlnet/tlpkg/TeXLive/TLPSRC.pm
 2023/02/21 |      16138 | systems/texlive/tlnet/tlpkg/TeXLive/TLTREE.pm
@@ -329881,7 +329888,7 @@
 2014/07/05 |        611 | systems/win32/yandy/README
 2014/07/05 |    1004628 | systems/win32/yandy/yandy-src.tar.xz
 2014/07/05 |    1012416 | systems/win32/yandy.zip
-2024/04/10 |        186 | timestamp
+2024/04/11 |        186 | timestamp
 2002/08/26 |      61898 | usergrps/dante/antrag.pdf
 2002/08/26 |     118217 | usergrps/dante/antrag.ps
 2021/11/11 |        917 | usergrps/dante/dtk/doc/beispiel.bib
diff --git a/FILES.byname.gz b/FILES.byname.gz
index 89608037d4..8c49c21c68 100644
--- a/FILES.byname.gz
+++ b/FILES.byname.gz
diff --git a/FILES.last07days b/FILES.last07days
index 26d286b9f5..d983153787 100644
--- a/FILES.last07days
+++ b/FILES.last07days
@@ -1,3 +1,86 @@
+2024/04/10 |       8741 | macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.tex
+2024/04/10 |        846 | macros/latex/contrib/iaria-lite/iaria-lite.ins
+2024/04/10 |        846 | macros/latex/contrib/cs-techrep/cs-techrep.ins
+2024/04/10 |        821 | macros/latex/contrib/iaria/iaria.ins
+2024/04/10 |     807536 | systems/texlive/tlnet/archive/elsarticle.doc.r70902.tar.xz
+2024/04/10 |     805532 | systems/texlive/tlnet/archive/dvipdfmx.universal-darwin.r70899.tar.xz
+2024/04/10 |        750 | support/texshop/README.txt
+2024/04/10 |       7299 | macros/latex/contrib/iaria/template/iaria-example-neumann.tex
+2024/04/10 |   69576234 | support/texshop/texshop532.zip
+2024/04/10 |    6475972 | systems/texlive/tlnet/archive/uantwerpendocs.r70903.tar.xz
+2024/04/10 |       6420 | systems/texlive/tlnet/archive/pmdraw.r70900.tar.xz
+2024/04/10 |    5749137 | systems/texlive/tlnet/install-tl-unx.tar.gz
+2024/04/10 |     563689 | support/latexmk.zip
+2024/04/10 |     524565 | support/latexmk/latexmk.pl
+2024/04/10 |        500 | macros/latex/contrib/iaria-lite/COPYING
+2024/04/10 |        500 | macros/latex/contrib/iaria/COPYING
+2024/04/10 |        500 | macros/latex/contrib/cs-techrep/COPYING
+2024/04/10 |         48 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5
+2024/04/10 |        488 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc
+2024/04/10 |        488 | systems/texlive/tlnet/install-tl.zip.sha512.asc
+2024/04/10 |        488 | systems/texlive/tlnet/install-tl-windows.exe.sha512.asc
+2024/04/10 |        488 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512.asc
+2024/04/10 |     469988 | systems/texlive/tlnet/archive/dvipdfmx.i386-linux.r70898.tar.xz
+2024/04/10 |     465028 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-solaris.r70898.tar.xz
+2024/04/10 |       4612 | systems/texlive/tlnet/archive/didactic.r70901.tar.xz
+2024/04/10 |     460464 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-linuxmusl.r70898.tar.xz
+2024/04/10 |      45820 | systems/texlive/tlnet/archive/uantwerpendocs.source.r70903.tar.xz
+2024/04/10 |      44371 | support/latexmk/CHANGES
+2024/04/10 |     438856 | systems/texlive/tlnet/archive/dvipdfmx.x86_64-linux.r70898.tar.xz
+2024/04/10 |    4367680 | systems/texlive/tlnet/archive/uantwerpendocs.doc.r70903.tar.xz
+2024/04/10 |     434424 | systems/texlive/tlnet/archive/texlive-scripts.doc.r70895.tar.xz
+2024/04/10 |     428004 | systems/texlive/tlnet/archive/dvipdfmx.i386-solaris.r70898.tar.xz
+2024/04/10 |    4120086 | biblio/ctan-bibdata.zip
+2024/04/10 |     398032 | systems/texlive/tlnet/archive/dvipdfmx.amd64-freebsd.r70898.tar.xz
+2024/04/10 |     398020 | systems/texlive/tlnet/archive/dvipdfmx.i386-freebsd.r70898.tar.xz
+2024/04/10 |     386828 | systems/texlive/tlnet/archive/pmdraw.doc.r70900.tar.xz
+2024/04/10 |     379536 | macros/latex/contrib/jsonparse.zip
+2024/04/10 |    3708800 | biblio/ctan-bibdata/ctan.pdf
+2024/04/10 |        364 | macros/latex/contrib/iaria-lite/docstrip.cfg
+2024/04/10 |        364 | macros/latex/contrib/cs-techrep/docstrip.cfg
+2024/04/10 |     353640 | systems/texlive/tlnet/archive/dvipdfmx.windows.r70904.tar.xz
+2024/04/10 |        344 | macros/latex/contrib/iaria/docstrip.cfg
+2024/04/10 |   34425285 | systems/texlive/tlnet/install-tl.zip
+2024/04/10 |        330 | macros/latex/contrib/cs-techrep/template/selfref.bib
+2024/04/10 |     329129 | macros/latex/contrib/cs-techrep.zip
+2024/04/10 |      29814 | macros/latex/contrib/iaria/template/cpn_all_all.bib
+2024/04/10 |      29814 | macros/latex/contrib/iaria-lite/template/cpn_all_all.bib
+2024/04/10 |      29814 | macros/latex/contrib/cs-techrep/template/cpn_all_all.bib
+2024/04/10 |     296151 | macros/latex/contrib/iaria.zip
+2024/04/10 |     294340 | macros/latex/contrib/iaria-lite.zip
+2024/04/10 |    2860154 | biblio/ctan-bibdata/ctan.bib
+2024/04/10 |   27716340 | systems/texlive/tlnet/install-tl-windows.exe
+2024/04/10 |     268488 | systems/texlive/tlnet/archive/didactic.doc.r70901.tar.xz
+2024/04/10 |    2564424 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz
+2024/04/10 |       2521 | support/latexmk/README
+2024/04/10 |      24190 | macros/latex/contrib/cs-techrep/cs-techrep.dtx
+2024/04/10 |   19415529 | systems/texlive/tlnet/tlpkg/texlive.tlpdb
+2024/04/10 |       1925 | support/texshop/texshop532.html
+2024/04/10 |      18920 | systems/texlive/tlnet/archive/elsarticle.r70902.tar.xz
+2024/04/10 |     187505 | macros/latex/contrib/cs-techrep/cs-techrep.pdf
+2024/04/10 |      18588 | macros/latex/contrib/iaria/template/cpn_supervised_all.bib
+2024/04/10 |      18588 | macros/latex/contrib/iaria-lite/template/cpn_supervised_all.bib
+2024/04/10 |      18588 | macros/latex/contrib/cs-techrep/template/cpn_supervised_all.bib
+2024/04/10 |       1820 | macros/latex/contrib/iaria-lite/README
+2024/04/10 |       1810 | macros/latex/contrib/cs-techrep/README
+2024/04/10 |       1786 | macros/latex/contrib/iaria/README
+2024/04/10 |     172223 | macros/latex/contrib/iaria/iaria.pdf
+2024/04/10 |     170730 | macros/latex/contrib/iaria-lite/iaria-lite.pdf
+2024/04/10 |       1678 | biblio/ctan-bibdata/biblatex-ctan/ctan.bbx
+2024/04/10 |        153 | systems/texlive/tlnet/install-tl-windows.exe.sha512
+2024/04/10 |        152 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512
+2024/04/10 |        145 | systems/texlive/tlnet/install-tl.zip.sha512
+2024/04/10 |     145442 | macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.pdf
+2024/04/10 |        144 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512
+2024/04/10 |     132913 | macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.pdf
+2024/04/10 |     132891 | macros/latex/contrib/iaria/template/iaria-example-neumann.pdf
+2024/04/10 |      13100 | macros/latex/contrib/iaria/iaria.dtx
+2024/04/10 |      12954 | macros/latex/contrib/cs-techrep/template/webdev_commons.bib
+2024/04/10 |      11776 | systems/texlive/tlnet/archive/didactic.source.r70901.tar.xz
+2024/04/10 |      11523 | macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.tex
+2024/04/10 |     114136 | systems/texlive/tlnet/archive/texlive-scripts.r70895.tar.xz
+2024/04/10 |      11016 | systems/texlive/tlnet/archive/elsarticle.source.r70902.tar.xz
+2024/04/10 |      10587 | macros/latex/contrib/iaria-lite/iaria-lite.dtx
 2024/04/09 |     988498 | macros/latex/contrib/pdfmanagement-testphase/hyperref-generic.pdf
 2024/04/09 |      88642 | macros/latex/contrib/pdfmanagement-testphase/l3backend-testphase.dtx
 2024/04/09 |      85072 | graphics/pmdraw/pmdraw.tex
@@ -9,6 +92,7 @@
 2024/04/09 |     753165 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield.pdf
 2024/04/09 |       7148 | systems/texlive/tlnet/archive/collection-latexextra.r70890.tar.xz
 2024/04/09 |     710596 | macros/latex/contrib/pdfmanagement-testphase/l3backend-testphase.pdf
+2024/04/09 |       7023 | systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl
 2024/04/09 |     685171 | macros/latex/contrib/pdfmanagement-testphase/l3pdfmanagement.pdf
 2024/04/09 |      67782 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield.dtx
 2024/04/09 |       6585 | macros/luatex/generic/luakeys/README.md
@@ -22,7 +106,6 @@
 2024/04/09 |     586990 | macros/latex/contrib/pdfmanagement-testphase/ltdocinit.pdf
 2024/04/09 |      57741 | macros/latex/contrib/uantwerpendocs/uantwerpenexam-example1.pdf
 2024/04/09 |     575300 | systems/texlive/tlnet/archive/mptrees.doc.r70887.tar.xz
-2024/04/09 |    5749104 | systems/texlive/tlnet/install-tl-unx.tar.gz
 2024/04/09 |       5704 | macros/latex/contrib/uantwerpendocs/uantwerpendocs.ins
 2024/04/09 |     567628 | macros/latex/contrib/pdfmanagement-testphase/l3pdffile.pdf
 2024/04/09 |     558195 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield-action.pdf
@@ -34,46 +117,33 @@
 2024/04/09 |     516025 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield-textfield.pdf
 2024/04/09 |     515190 | macros/latex/contrib/pdfmanagement-testphase/l3pdfdict.pdf
 2024/04/09 |     505252 | macros/latex/contrib/uantwerpendocs/uantwerpendocs.pdf
-2024/04/09 |         48 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5
-2024/04/09 |        488 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc
-2024/04/09 |        488 | systems/texlive/tlnet/install-tl.zip.sha512.asc
-2024/04/09 |        488 | systems/texlive/tlnet/install-tl-windows.exe.sha512.asc
-2024/04/09 |        488 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512.asc
 2024/04/09 |       4761 | macros/latex/contrib/pdfmanagement-testphase/pdfmanagement-testphase.ins
 2024/04/09 |     463888 | macros/latex/contrib/pdfmanagement-testphase/pdfmanagement-testphase.pdf
 2024/04/09 |      46170 | graphics/pmdraw/pmdraw.sty
 2024/04/09 |     453698 | macros/latex/contrib/elsarticle/doc/elsdoc.pdf
 2024/04/09 |     452495 | macros/luatex/generic/luakeys.zip
-2024/04/09 |       4504 | systems/texlive/tlnet/archive/didactic.r70890.tar.xz
 2024/04/09 |     434032 | macros/latex/contrib/pdfmanagement-testphase/pdfmanagement-firstaid.pdf
 2024/04/09 |     427235 | macros/latex/contrib/pdfmanagement-testphase/l3pdfxform.pdf
 2024/04/09 |     426656 | macros/luatex/generic/luakeys/luakeys.pdf
-2024/04/09 |    4120075 | biblio/ctan-bibdata.zip
 2024/04/09 |     404476 | graphics/pmdraw.zip
 2024/04/09 |     384283 | graphics/pmdraw/pmdraw.pdf
 2024/04/09 |       3840 | systems/texlive/tlnet/archive/prociagssymp.source.r70888.tar.xz
 2024/04/09 |     383792 | systems/texlive/tlnet/archive/l3sys-query.doc.r70889.tar.xz
-2024/04/09 |    3708800 | biblio/ctan-bibdata/ctan.pdf
-2024/04/09 |   34425343 | systems/texlive/tlnet/install-tl.zip
+2024/04/09 |     380391 | macros/latex/contrib/jsonparse/jsonparse-doc.pdf
 2024/04/09 |    3225054 | macros/latex/contrib/uantwerpendocs/beamerthemeuantwerpenuserguide.pdf
 2024/04/09 |      31145 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield-radiobutton.dtx
 2024/04/09 |      29934 | macros/latex/contrib/pdfmanagement-testphase/l3pdffile.dtx
 2024/04/09 |      29764 | macros/latex/contrib/elsarticle/doc/elsdoc.tex
 2024/04/09 |       2882 | macros/latex/contrib/pdfmanagement-testphase/colorspace-patches-tmp-ltx.sty
 2024/04/09 |      28685 | macros/latex/contrib/pdfmanagement-testphase/l3pdfannot.dtx
-2024/04/09 |    2860148 | biblio/ctan-bibdata/ctan.bib
 2024/04/09 |       2843 | macros/latex/contrib/pdfmanagement-testphase/xcolor-patches-tmp-ltx.sty
 2024/04/09 |     280597 | macros/latex/contrib/didactic.zip
-2024/04/09 |   27719584 | systems/texlive/tlnet/install-tl-windows.exe
 2024/04/09 |      27558 | macros/latex/contrib/uantwerpendocs/uantwerpenletter-example.pdf
 2024/04/09 |      26550 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield-action.dtx
 2024/04/09 |      26540 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield-pushbutton.dtx
-2024/04/09 |     264372 | systems/texlive/tlnet/archive/didactic.doc.r70890.tar.xz
-2024/04/09 |    2562444 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz
 2024/04/09 |     225580 | macros/latex/contrib/uantwerpendocs/uantwerpendocs.dtx
 2024/04/09 |      21991 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield-textfield.dtx
 2024/04/09 |      20430 | macros/latex/contrib/pdfmanagement-testphase/l3pdffield-choice.dtx
-2024/04/09 |   19415475 | systems/texlive/tlnet/tlpkg/texlive.tlpdb
 2024/04/09 |      19207 | macros/latex/contrib/pdfmanagement-testphase/pdfmanagement-testphase.dtx
 2024/04/09 |     188533 | macros/latex/contrib/uantwerpendocs/uantwerpenphdthesis-example1.pdf
 2024/04/09 |       1857 | graphics/pmdraw/README.md
@@ -83,11 +153,9 @@
 2024/04/09 |     175643 | macros/luatex/latex/luacensor.zip
 2024/04/09 |      17338 | macros/latex/contrib/pdfmanagement-testphase/l3pdfdict.dtx
 2024/04/09 |      17112 | macros/latex/contrib/pdfmanagement-testphase/l3pdftools.dtx
-2024/04/09 |       1678 | biblio/ctan-bibdata/biblatex-ctan/ctan.bbx
-2024/04/09 |        153 | systems/texlive/tlnet/install-tl-windows.exe.sha512
-2024/04/09 |        152 | systems/texlive/tlnet/install-tl-unx.tar.gz.sha512
-2024/04/09 |        145 | systems/texlive/tlnet/install-tl.zip.sha512
-2024/04/09 |        144 | systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512
+2024/04/09 |      16885 | macros/latex/contrib/jsonparse/jsonparse-doc.tex
+2024/04/09 |      15644 | macros/latex/contrib/jsonparse/jsonparse.sty
+2024/04/09 |       1485 | macros/latex/contrib/jsonparse/README.md
 2024/04/09 |    1430199 | macros/latex/contrib/elsarticle.zip
 2024/04/09 |     141996 | systems/texlive/tlnet/archive/prociagssymp.doc.r70888.tar.xz
 2024/04/09 |     137149 | macros/latex/contrib/uantwerpendocs/uantwerpenphdthesis-example2.pdf
@@ -96,6 +164,7 @@
 2024/04/09 |   13098654 | macros/latex/contrib/uantwerpendocs.zip
 2024/04/09 |       1276 | systems/texlive/tlnet/archive/prociagssymp.r70888.tar.xz
 2024/04/09 |     127166 | macros/latex/contrib/uantwerpendocs/uantwerpenbamathesis-example.pdf
+2024/04/09 |     125043 | systems/texlive/tlnet/install-tl
 2024/04/09 |      12362 | macros/latex/contrib/pdfmanagement-testphase/ltdocinit.dtx
 2024/04/09 |       1197 | macros/luatex/generic/luakeys/luakeys-debug.tex
 2024/04/09 |      11965 | macros/latex/contrib/pdfmanagement-testphase/CHANGELOG.md
@@ -103,7 +172,6 @@
 2024/04/09 |      11838 | macros/latex/contrib/pdfmanagement-testphase/pdfmanagement-firstaid.dtx
 2024/04/09 |       1162 | macros/latex/contrib/pdfmanagement-testphase/README.md
 2024/04/09 |   11079556 | macros/latex/contrib/pdfmanagement-testphase.zip
-2024/04/09 |      10996 | systems/texlive/tlnet/archive/didactic.source.r70890.tar.xz
 2024/04/09 |     106135 | macros/latex/contrib/pdfmanagement-testphase/l3pdfmeta.dtx
 2024/04/09 |   10481064 | systems/texlive/tlnet/archive/xetex.windows.r70891.tar.xz
 2024/04/09 |       1044 | macros/luatex/generic/luakeys/luakeys.sty
@@ -121,7 +189,6 @@
 2024/04/08 |      55636 | systems/texlive/tlnet/archive/hulipsum.r70885.tar.xz
 2024/04/08 |     514740 | systems/texlive/tlnet/archive/footmisc.doc.r70885.tar.xz
 2024/04/08 |      48977 | graphics/metapost/contrib/macros/mptrees/mptrees.mp
-2024/04/08 |     434544 | systems/texlive/tlnet/archive/texlive-scripts.doc.r70879.tar.xz
 2024/04/08 |      42932 | macros/latex/contrib/didactic/didactic.dtx
 2024/04/08 |       3988 | systems/texlive/tlnet/archive/moloch.r70885.tar.xz
 2024/04/08 |     380420 | systems/texlive/tlnet/archive/asymptote.r70885.tar.xz
@@ -134,15 +201,19 @@
 2024/04/08 |     273748 | systems/texlive/tlnet/archive/hershey-mp.doc.r70885.tar.xz
 2024/04/08 |     268125 | macros/latex/contrib/didactic/didactic.pdf
 2024/04/08 |      26052 | systems/texlive/tlnet/archive/minim-hatching.doc.r70885.tar.xz
+2024/04/08 |     256981 | support/latexmk/latexmk.txt
 2024/04/08 |       2536 | systems/texlive/tlnet/archive/rectopma.source.r70885.tar.xz
 2024/04/08 |      25344 | systems/texlive/tlnet/archive/minim.r70885.tar.xz
+2024/04/08 |     241304 | support/latexmk/latexmk.pdf
 2024/04/08 |    2345040 | systems/texlive/tlnet/archive/asymptote.doc.r70885.tar.xz
 2024/04/08 |     230780 | systems/texlive/tlnet/archive/rectopma.doc.r70885.tar.xz
 2024/04/08 |      22564 | systems/texlive/tlnet/archive/minim-mp.r70885.tar.xz
 2024/04/08 |      22408 | systems/texlive/tlnet/archive/footmisc.source.r70885.tar.xz
 2024/04/08 |       2232 | systems/texlive/tlnet/archive/minim-hatching.r70885.tar.xz
+2024/04/08 |     206488 | support/latexmk/latexmk.1
 2024/04/08 |     203956 | systems/texlive/tlnet/archive/abntexto.doc.r70885.tar.xz
 2024/04/08 |      17987 | CTAN.sites
+2024/04/08 |      17974 | support/latexmk/INSTALL
 2024/04/08 |      17496 | systems/texlive/tlnet/archive/minim-pdf.r70885.tar.xz
 2024/04/08 |       1684 | systems/texlive/tlnet/archive/hershey-mp.r70885.tar.xz
 2024/04/08 |     159364 | macros/luatex/latex/luacensor/luacensor-documentation.pdf
@@ -158,7 +229,6 @@
 2024/04/08 |       1286 | macros/latex/contrib/prociagssymp/README.txt
 2024/04/08 |       1196 | support/l3sys-query/README.md
 2024/04/08 |      11733 | support/l3sys-query/l3sys-query-tool.tex
-2024/04/08 |     114204 | systems/texlive/tlnet/archive/texlive-scripts.r70879.tar.xz
 2024/04/08 |      11288 | macros/latex/contrib/prociagssymp/procIAGssymp.dtx
 2024/04/08 |       1025 | support/l3sys-query/CHANGELOG.md
 2024/04/08 |     100228 | systems/texlive/tlnet/archive/minim-math.doc.r70885.tar.xz
@@ -168,7 +238,6 @@
 2024/04/07 |        859 | macros/luatex/latex/luacensor/README.txt
 2024/04/07 |      76228 | systems/texlive/tlnet/archive/latexindent.r70874.tar.xz
 2024/04/07 |     737020 | systems/texlive/tlnet/archive/bithesis.doc.r70873.tar.xz
-2024/04/07 |       7325 | systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl
 2024/04/07 |       6580 | systems/texlive/tlnet/archive/bookcover.r70872.tar.xz
 2024/04/07 |        576 | systems/texlive/tlnet/archive/collection-formatsextra.r70875.tar.xz
 2024/04/07 |      51330 | macros/latex/contrib/fontscale/fontscale.sty
@@ -364,6 +433,7 @@
 2024/04/05 |      20802 | macros/latex/contrib/sjtutex/sjtu-vi-name-red.pdf
 2024/04/05 |      20101 | macros/latex/contrib/sjtutex/sjtu-vi-badge-red.pdf
 2024/04/05 |      20011 | macros/latex/contrib/sjtutex/sjtu-vi-badge-small-red.pdf
+2024/04/05 |      19105 | macros/latex/contrib/jsonparse/LICENCE
 2024/04/05 |       1904 | macros/latex/contrib/sjtutex/README.md
 2024/04/05 |       1813 | fonts/simpleicons/doc/simpleicons.tex
 2024/04/05 |      18108 | systems/texlive/tlnet/archive/csquotes.r70858.tar.xz
@@ -670,33 +740,3 @@
 2024/04/04 |     101201 | macros/luatex/generic/luamplib/luamplib.dtx
 2024/04/04 |      10096 | macros/latex/contrib/glossaries/samples/samplexdy.tex
 2024/04/04 |      10078 | macros/latex/contrib/glossaries/glossaries-user-examples/glossaries-user-example025.pdf
-2024/04/03 |       9981 | macros/latex/contrib/msu-thesis/samples/MSU-thesis-testfile.tex
-2024/04/03 |       8139 | graphics/pgf/contrib/pgf-periodictable/translations/pgfPT.lang.undefined.tex
-2024/04/03 |    7654649 | graphics/pgf/contrib/pgf-periodictable.zip
-2024/04/03 |    7457011 | graphics/pgf/contrib/pgf-periodictable/pgf-PeriodicTableManual.pdf
-2024/04/03 |       7248 | graphics/pgf/contrib/pgf-periodictable/myGroupColors.tex
-2024/04/03 |      70914 | macros/latex/contrib/msu-thesis/samples/MSU-thesis-template.pdf
-2024/04/03 |       6771 | macros/latex/contrib/msu-thesis/samples/MSU-thesis-template.tex
-2024/04/03 |      56681 | macros/luatex/generic/minim-mp/minim-mp.lua
-2024/04/03 |     563829 | macros/latex/contrib/msu-thesis.zip
-2024/04/03 |      43644 | macros/latex/contrib/msu-thesis/msu-thesis.cls
-2024/04/03 |      42365 | macros/latex/contrib/msu-thesis/docs/msu-thesis.tex
-2024/04/03 |     411282 | macros/luatex/generic/minim.zip
-2024/04/03 |     397133 | macros/luatex/generic/minim/minim.pdf
-2024/04/03 |        393 | macros/latex/contrib/msu-thesis/samples/chap2bib.tex
-2024/04/03 |     343643 | macros/luatex/latex/lua-placeholders.zip
-2024/04/03 |        327 | macros/latex/contrib/msu-thesis/samples/chap4bib.tex
-2024/04/03 |        319 | macros/latex/contrib/msu-thesis/samples/chap3bib.tex
-2024/04/03 |       3005 | graphics/pgf/contrib/pgf-periodictable/README
-2024/04/03 |       2935 | macros/latex/contrib/msu-thesis/README.md
-2024/04/03 |        277 | macros/latex/contrib/msu-thesis/samples/chap1bib.tex
-2024/04/03 |      25847 | graphics/pgf/contrib/pgf-periodictable/manualfiles/pgfPTmanual.macros.tex
-2024/04/03 |     214979 | macros/latex/contrib/msu-thesis/samples/MSU-thesis-testfile.pdf
-2024/04/03 |     208078 | graphics/pgf/contrib/pgf-periodictable/pgf-PeriodicTable.sty
-2024/04/03 |     164656 | macros/luatex/generic/minim-mp.zip
-2024/04/03 |     139419 | macros/latex/contrib/msu-thesis/samples/MSU-thesis-chapterbib-testfile.pdf
-2024/04/03 |     134407 | macros/luatex/generic/minim-mp/minim-mp.pdf
-2024/04/03 |       1276 | macros/latex/contrib/msu-thesis/samples/MSU-thesis-chapterbib-testfile.tex
-2024/04/03 |     114013 | macros/latex/contrib/msu-thesis/msu-thesis.pdf
-2024/04/03 |       1088 | macros/latex/contrib/msu-thesis/samples/MSU-thesis-testfile.bib
-2024/04/03 |      10430 | graphics/pgf/contrib/pgf-periodictable/translations/pgfPT.lang.nl.tex
diff --git a/biblio/ctan-bibdata/ctan.bib b/biblio/ctan-bibdata/ctan.bib
index 1a229afa74..23277511f6 100644
--- a/biblio/ctan-bibdata/ctan.bib
+++ b/biblio/ctan-bibdata/ctan.bib
@@ -1,7 +1,7 @@
 %% bib file of all CTAN packages
 %% (C) Herbert Voß
 %% 
-%% created at 10-04-2024, 02:00:03
+%% created at 11-04-2024, 02:00:03
 %% 
 
 %% This file is provided under the terms of the LPPL v1.3 or
@@ -16434,8 +16434,8 @@
   title      = {The \texttt{cs-techrep} package},
   subtitle   = {Technical Reports in Computer Science and Software Engineering},
   author     = {Christoph P. Neumann},
-  date       = {2024-03-27},
-  version    = {0.1},
+  date       = {2024-04-10},
+  version    = {0.2},
   license    = {lppl1.3c},
   mirror     = {https://mirror.ctan.org/macros/latex/contrib/cs-techrep},
   url        = {https://ctan.org/pkg/cs-techrep},
@@ -33336,8 +33336,8 @@
   title      = {The \texttt{iaria-lite} package},
   subtitle   = {Write documents for the IARIA publications},
   author     = {Christoph P. Neumann},
-  date       = {2024-03-27},
-  version    = {0.1},
+  date       = {2024-04-10},
+  version    = {0.2},
   license    = {lppl1.3c},
   mirror     = {https://mirror.ctan.org/macros/latex/contrib/iaria-lite},
   url        = {https://ctan.org/pkg/iaria-lite},
@@ -33347,8 +33347,8 @@
   title      = {The \texttt{iaria} package},
   subtitle   = {Write documents for the IARIA publications},
   author     = {Christoph P. Neumann},
-  date       = {2024-03-27},
-  version    = {0.1},
+  date       = {2024-04-10},
+  version    = {0.2},
   license    = {lppl1.3c},
   mirror     = {https://mirror.ctan.org/macros/latex/contrib/iaria},
   url        = {https://ctan.org/pkg/iaria},
@@ -36108,6 +36108,17 @@
   url        = {https://ctan.org/pkg/jslectureplanner},
 }
 
+@manual{ctan-jsonparse,
+  title      = {The \texttt{jsonparse} package},
+  subtitle   = {Parse, store and access JSON data in \LaTeX{} documents},
+  author     = {Jasper Habicht},
+  date       = {2024-04-10},
+  version    = {0.5.5},
+  license    = {lppl1.3c},
+  mirror     = {https://mirror.ctan.org/macros/latex/contrib/jsonparse},
+  url        = {https://ctan.org/pkg/jsonparse},
+}
+
 @manual{ctan-jspell,
   title      = {The \texttt{jspell} package},
   subtitle   = {An ASCII file spelling checker},
@@ -38915,8 +38926,8 @@
   title      = {The \texttt{latexmk} package},
   subtitle   = {Fully automated \LaTeX{} document generation},
   author     = {John Collins and Evan McLean and David J. Musliner},
-  date       = {2024-04-02},
-  version    = {4.83},
+  date       = {2024-04-10},
+  version    = {4.85},
   license    = {gpl2},
   mirror     = {https://mirror.ctan.org/support/latexmk},
   url        = {https://ctan.org/pkg/latexmk},
@@ -69627,8 +69638,8 @@
   title      = {The \texttt{texshop} package},
   subtitle   = {TeX front end for use on MacOS X},
   author     = {Dick Koch},
-  date       = {2024-03-24},
-  version    = {5.31},
+  date       = {2024-04-10},
+  version    = {5.32},
   license    = {gpl},
   mirror     = {https://mirror.ctan.org/support/texshop},
   url        = {https://ctan.org/pkg/texshop},
diff --git a/macros/latex/contrib/cs-techrep/COPYING b/macros/latex/contrib/cs-techrep/COPYING
index 241acd1c5d..cfe1772eff 100644
--- a/macros/latex/contrib/cs-techrep/COPYING
+++ b/macros/latex/contrib/cs-techrep/COPYING
@@ -1,4 +1,4 @@
-Copyright 2024 Christoph P. Neumann 
+Copyright 2023-2024 Christoph P. Neumann 
  
 This work may be distributed and/or modified under the 
 conditions of the LaTeX Project Public License, either version 1.3c 
diff --git a/macros/latex/contrib/cs-techrep/README b/macros/latex/contrib/cs-techrep/README
index d133b67a2d..bb3aefdd37 100644
--- a/macros/latex/contrib/cs-techrep/README
+++ b/macros/latex/contrib/cs-techrep/README
@@ -1,5 +1,5 @@
               -----------------------------
-              Version 0.1 of the cs-techrep class
+              Version 0.2 of the cs-techrep class
                   Christoph P. Neumann
               -----------------------------
 
diff --git a/macros/latex/contrib/cs-techrep/cs-techrep.dtx b/macros/latex/contrib/cs-techrep/cs-techrep.dtx
index 8f9dccfa51..35775ca107 100644
--- a/macros/latex/contrib/cs-techrep/cs-techrep.dtx
+++ b/macros/latex/contrib/cs-techrep/cs-techrep.dtx
@@ -1,16 +1,16 @@
 %\iffalse
 % cs-techrep.dtx generated using makedtx version 1.2 (c) Nicola Talbot
 % Command line args:
-%   -src "(cs-techrep.cls)=>\1"
+%   -preamble "Copyright 2023-2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. "
+%   -setambles ".*=>\nopreamble"
+%   -author "Christoph P. Neumann "
 %   -dir "src"
-%   -date "0.1"
+%   -src "(_cpn_copyIntoExamplesFolder_cls.cmd|cs-techrep.cls)=>\1"
 %   -doc "doc/cs-techrep.tex"
-%   -author "Christoph P. Neumann "
+%   -date "2023-2024"
 %   -macrocode ".*"
-%   -preamble "Copyright 2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. "
-%   -setambles ".*=>\nopreamble"
 %   cs-techrep
-% Created on 2024/3/22 20:18
+% Created on 2024/4/10 18:14
 %\fi
 %\iffalse
 %<*package>
@@ -33,27 +33,10 @@
 %\fi
 % \iffalse
 % Doc-Source file to use with LaTeX2e
-% Copyright (C) 0.1 Christoph P. Neumann , all rights reserved.
+% Copyright (C) 2023-2024 Christoph P. Neumann , all rights reserved.
 % \fi
 % \iffalse
 %<*driver>
-%%
-%% Copyright 2023 Christoph P. Neumann
-%%
-%% This LaTeX class provides a simple interface for creating
-%% a verfy fancy Curriculum Vitae. At the moment only CVs in
-%% the german language are supported.
-%%
-%% This file is free property; as a special exception the author
-%% gives unlimited permission to copy and/or distribute it, with
-%% or without modifications, as long as this notice is
-%% preserved.
-%%
-%% This file is distributed in the hope that it will be useful,
-%% but WITHOUT ANY WARRANTY, to the extent permitted by law;
-%% without even the implied warranty of MERCHANTABILITY or
-%% FITNESS FOR A PARTICULAR PURPOSE.
-
 \documentclass{ltxdoc}
 
 \CodelineNumbered
@@ -73,6 +56,7 @@
 %\title{\textsf{cs-techrep}\\
 %Technical Reports in Computer Science and Software Engineering}
 %\author{Christoph P.\ Neumann \texttt{$<$cyberpetaneuron@gmail.com$>$}}
+%\date{Version 0.2}
 %\maketitle
 %\PrintChanges
 %
@@ -195,6 +179,31 @@
 %\section{The Code}
 %\iffalse
 %    \begin{macrocode}
+%<*_cpn_copyIntoExamplesFolder_cls.cmd>
+%    \end{macrocode}
+%\fi
+%    \begin{macrocode}
+@echo off
+
+rem ***************************************************************************
+rem * author: Christoph P. Neumann
+rem ***************************************************************************
+cd /d "%~dp0"
+
+echo == ..\examples\* ==
+for /D %%D in (..\examples\*) do (
+	echo == %%D ==
+	xcopy /Y ".\*.cls" "%%~D"
+)
+
+pause%    \end{macrocode}
+%\iffalse
+%    \begin{macrocode}
+%</_cpn_copyIntoExamplesFolder_cls.cmd>
+%    \end{macrocode}
+%\fi
+%\iffalse
+%    \begin{macrocode}
 %<*cs-techrep.cls>
 %    \end{macrocode}
 %\fi
@@ -213,7 +222,7 @@
 \NeedsTeXFormat{LaTeX2e}
 
 % Provide the name of your document class, the date it was last updated, and a comment about what it's used for
-\ProvidesClass{cs-techrep}[2024/03/20 Technical Reports in Computer Science and Software Engineering v0.1]
+\ProvidesClass{cs-techrep}[2024/04/10 Technical Reports in Computer Science and Software Engineering v0.2]
 
 % Define marker counter for options (counter are global in latex):
 \newcounter{cstechrep@pbalancetracker}
@@ -553,8 +562,6 @@
 
 \RequirePackage{orcidlink}
 
-\RequirePackage[caption=false,font=footnotesize]{subfig}
-
 % For easy quotations: \enquote{text}
 % This package is very smart when nesting is applied, otherwise textcmds (see below) provides a shorter command
 \RequirePackage[autostyle=true]{csquotes}
@@ -613,9 +620,6 @@
 % Does not work on MiKTeX, therefore disabled - issue reported at https://github.com/MiKTeX/miktex-packaging/issues/271
 % \input{ushyphex}
 
-% correct bad hyphenation here
-\hyphenation{op-tical net-works semi-conduc-tor}
-
 % Enable copy and paste of text from the PDF
 % Only required for pdflatex. It "just works" in the case of lualatex.
 % Alternative: cmap or mmap package
diff --git a/macros/latex/contrib/cs-techrep/cs-techrep.ins b/macros/latex/contrib/cs-techrep/cs-techrep.ins
index 28d177822b..0fc5868464 100644
--- a/macros/latex/contrib/cs-techrep/cs-techrep.ins
+++ b/macros/latex/contrib/cs-techrep/cs-techrep.ins
@@ -1,13 +1,14 @@
-% cs-techrep.ins generated using makedtx version 1.2 2024/3/22 20:18
+% cs-techrep.ins generated using makedtx version 1.2 2024/4/10 18:14
 \input docstrip
 
 \preamble
-Copyright 2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. 
+Copyright 2023-2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. 
 \endpreamble
 
 \askforoverwritefalse
 
-\generate{\file{cs-techrep.cls}{\nopreamble\from{cs-techrep.dtx}{cs-techrep.cls}}
+\generate{\file{_cpn_copyIntoExamplesFolder_cls.cmd}{\nopreamble\from{cs-techrep.dtx}{_cpn_copyIntoExamplesFolder_cls.cmd}}
+\file{cs-techrep.cls}{\nopreamble\from{cs-techrep.dtx}{cs-techrep.cls}}
 }
 
 \endbatchfile
diff --git a/macros/latex/contrib/cs-techrep/cs-techrep.pdf b/macros/latex/contrib/cs-techrep/cs-techrep.pdf
index 543f528806..766e80d57b 100644
--- a/macros/latex/contrib/cs-techrep/cs-techrep.pdf
+++ b/macros/latex/contrib/cs-techrep/cs-techrep.pdf
diff --git a/macros/latex/contrib/cs-techrep/template/cpn_all_all.bib b/macros/latex/contrib/cs-techrep/template/cpn_all_all.bib
index d7796e6272..cc7abaec4a 100644
--- a/macros/latex/contrib/cs-techrep/template/cpn_all_all.bib
+++ b/macros/latex/contrib/cs-techrep/template/cpn_all_all.bib
@@ -281,7 +281,7 @@
   publisher = {Gesellschaft f{\"u}r Informatik e.V.\ (GI), K{\"o}ln, Germany},
   doi = {10.1145/1620432.1620442},
   url  = {https://dl.gi.de/20.500.12116/20447},
-  _isbn = {978\-/3\-/88579\-/238\-/3},
+  _isbn = {978-3-88579-238-3},
   _issn = {1617\-/5468},
 }
 
@@ -347,9 +347,10 @@
   address = {Nice, France},
   month=jun,
   year={2023},
-  doi = {10.48550/ARXIV.2310.19459},
+  doi = {10.48550/arXiv.2310.19459},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2023_2_10_28004},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2310.19459},
+  _issn = {2308-4294},
   pages = {21--29},
 }
 
@@ -361,9 +362,10 @@
   address = {Venice, Italy},
   month=apr,
   year={2024},
-  _doi = {TODO},
+  doi = {10.48550/arXiv.2404.02637},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2024_X_YY_ZZZZZ},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2404.02637},
+  _issn = {2308\-/4294},
   _pages = {AA--OO},
   note = {accepted for publication}
 }
@@ -402,9 +404,10 @@
   address = {Nice, France},
   month=jun,
   year={2023},
-  doi = {10.48550/ARXIV.2310.19461},
+  doi = {10.48550/arXiv.2310.19461},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2023_2_30_28006},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2310.19461},
+  _issn = {2308\-/4294},
   pages = {41--46},
 }
 
diff --git a/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.pdf b/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.pdf
index ab3603dce7..ca478d3d61 100644
--- a/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.pdf
+++ b/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.pdf
diff --git a/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.tex b/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.tex
index 9122c3ddf4..1ae583aed0 100644
--- a/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.tex
+++ b/macros/latex/contrib/cs-techrep/template/cs-techrep-example-neumann.tex
@@ -16,6 +16,7 @@
 % Team example:
 %\cstechrepAuthorListBib{Vorname1 Nachname1 and Vorname2 Nachname2 and Vorname3 Nachname3 and Vorname4 Nachname4 and Vorname5 Nachname5 and Vorname6 Nachname6 and Christoph P. Neumann}
 
+% Capitalization: https://capitalizemytitle.com/style/Chicago/
 \cstechrepTitleTex{The cs-techrep Example of a Technical Report in Computer Science and Software Engineering}
  % IF you need manual linebreaks in the titel, then clone the title without linebreaks for BibTeX:
 \cstechrepTitleBib{{\cstechrepTitleTex}}
@@ -42,57 +43,57 @@
 % DO NOT DELETE THIS:
 \filecontentsForceExpansion|[] % force command expansion inside a filecontents* environment
 \begin{filecontents*}[overwrite]{selfref.bib}
-	@TECHREPORT{selfref,
-		author = {|cstechrepAuthorListBib},
-		title  = {\cstechrepTitleBib},
-		institution = {\cstechrepInstitution, \cstechrepDepartment},
-		series = {\cstechrepSeries},
-		number = {\cstechrepNumber},
-		year   = {|cstechrepYear},
-		month  = {|cstechrepMonth},
-		langid  = {|cstechrepLang},
-	}
+    @TECHREPORT{selfref,
+        author = {|cstechrepAuthorListBib},
+        title  = {\cstechrepTitleBib},
+        institution = {\cstechrepInstitution, \cstechrepDepartment},
+        series = {\cstechrepSeries},
+        number = {\cstechrepNumber},
+        year   = {|cstechrepYear},
+        month  = {|cstechrepMonth},
+        langid  = {|cstechrepLang},
+    }
 \end{filecontents*}
 
 % ======================================================================
 % EDIT THIS:
 
 \begin{filecontents}[overwrite]{embedded.bib}
-	@online{ieee2015howto,
-		author = {Michael Shell},
-		title = {How to Use the {IEEEtran} \LaTeX\ Class},
-		url = {http://mirrors.ctan.org/macros/latex/contrib/IEEEtran/IEEEtran_HOWTO.pdf},
-		year = {2015}
-	}
-	@online{ieee2018formattingrules,
-		author = {{IEEE}},
-		title = {Conference Template and Formatting Specifications},
-		url = {https://www.ieee.org/content/dam/ieee-org/ieee/web/org/conferences/Conference-template-A4.doc},
-		year = {2018}
-	}
-	@online{iaria2014formattingrules,
-		author = {{IARIA}},
-		title = {Formatting Rules},
-		url = {http://www.iaria.org/formatting.doc},
-		year = {2014}
-	}
-	@online{iaria2009editorialrules,
-		_author = {Cosmin Dini},
-		author = {{IARIA}},
-		title = {Editorial Rules},
-		url = {https://www.iaria.org/editorialrules.html},
-		year = {2009}
-	}
-	@online{languagetool,
-		author = {{LanguageTooler GmbH}},
-		title  = {{LangueTool}},
-		url    = {https://languagetool.org/overleaf}
-	}
-	@online{overleaf,
-		author = {{Digital Science UK Limited}},
-		title  = {{Overleaf}},
-		url    = {https://www.overleaf.com}
-	}
+@online{ieee2015howto,
+    author = {Michael Shell},
+    title = {How to Use the {IEEEtran} \LaTeX\ Class},
+    url = {http://mirrors.ctan.org/macros/latex/contrib/IEEEtran/IEEEtran_HOWTO.pdf},
+    year = {2015}
+}
+@online{ieee2018formattingrules,
+    author = {{IEEE}},
+    title = {Conference Template and Formatting Specifications},
+    url = {https://www.ieee.org/content/dam/ieee-org/ieee/web/org/conferences/Conference-template-A4.doc},
+    year = {2018}
+}
+@online{iaria2014formattingrules,
+    author = {{IARIA}},
+    title = {Formatting Rules},
+    url = {http://www.iaria.org/formatting.doc},
+    year = {2014}
+}
+@online{iaria2009editorialrules,
+    _author = {Cosmin Dini},
+    author = {{IARIA}},
+    title = {Editorial Rules},
+    url = {https://www.iaria.org/editorialrules.html},
+    year = {2009}
+}
+@online{languagetool,
+    author = {{LanguageTooler GmbH}},
+    title  = {{LangueTool}},
+    url    = {https://languagetool.org/overleaf}
+}
+@online{overleaf,
+    author = {{Digital Science UK Limited}},
+    title  = {{Overleaf}},
+    url    = {https://www.overleaf.com}
+}
 \end{filecontents}
 
 \usepackage{fontawesome} % i.a., \faWarning{}
@@ -108,8 +109,8 @@
 % plural, within sentence       = \acp{gui}
 % plural, beginning of sentence = \Acp{gui}
 \begin{acronym}
-	\acro{gui}[GUI]{Graphical User Interface}
-	\acro{ide}[IDE]{Integrated Development Environment}
+    \acro{gui}[GUI]{Graphical User Interface}
+    \acro{ide}[IDE]{Integrated Development Environment}
 \end{acronym}
 
 % https://www.silbentrennung24.de/
@@ -122,15 +123,15 @@
 \maketitle
 
 \begin{abstract}
-	\lipsum[1][3-10]
-	\{\,\faWarning{}The abstract does neither mention a teaching module nor a team/project,
-	it is a summary of the content of the technical report, thus, the objectives and architecture.\}
+\lipsum[1][3-10]
+\{\,\faWarning{}The abstract does neither mention a teaching module nor a team/project,
+it is a summary of the content of the technical report, thus, the objectives and architecture.\}
 \end{abstract}
 
 % A list of IEEE Computer Society appoved keywords can be obtained at
 % http://www.computer.org/mc/keywords/keywords.htm
 \begin{IEEEkeywords}
-	template; lorem ipsum.
+template; lorem ipsum.
 \end{IEEEkeywords}
 
 \section{Introduction and Objectives \textbar{} Functional Requirements \textbar{} Problem Statement}
@@ -255,5 +256,5 @@ Could include (3) a software bill of materials (SBOM), at least for the major li
 \sloppy
 \printbibliography[notcategory=selfref]
 \endgroup 
-	
+    
 \end{document}
diff --git a/macros/latex/contrib/cs-techrep/template/selfref.bib b/macros/latex/contrib/cs-techrep/template/selfref.bib
index ecd901e557..f498920efc 100644
--- a/macros/latex/contrib/cs-techrep/template/selfref.bib
+++ b/macros/latex/contrib/cs-techrep/template/selfref.bib
@@ -1,10 +1,10 @@
- @TECHREPORT{selfref,
-  author = {Christoph P. Neumann},
-  title  = {\cstechrepTitleBib},
-  institution = {\cstechrepInstitution, \cstechrepDepartment},
-  series = {\cstechrepSeries},
-  number = {\cstechrepNumber},
-  year   = {2024},
-  month  = {3},
-  langid  = {english},
- }
+    @TECHREPORT{selfref,
+        author = {Christoph P. Neumann},
+        title  = {\cstechrepTitleBib},
+        institution = {\cstechrepInstitution, \cstechrepDepartment},
+        series = {\cstechrepSeries},
+        number = {\cstechrepNumber},
+        year   = {2024},
+        month  = {3},
+        langid  = {english},
+    }
diff --git a/macros/latex/contrib/iaria-lite/COPYING b/macros/latex/contrib/iaria-lite/COPYING
index 778959f22c..cfe1772eff 100644
--- a/macros/latex/contrib/iaria-lite/COPYING
+++ b/macros/latex/contrib/iaria-lite/COPYING
@@ -1,13 +1,13 @@
-Copyright 2024 Christoph P. Neumann 
+Copyright 2023-2024 Christoph P. Neumann 
  
 This work may be distributed and/or modified under the 
-conditions of the LaTeX Project Public License, either version 1.3 
+conditions of the LaTeX Project Public License, either version 1.3c 
 of this license or any later version. 
 The latest version of this license is in 
 https://www.latex-project.org/lppl.txt 
 and version 1.3c or later is part of all distributions of LaTeX 
 version 2008 or later. 
  
-This work has the LPPL maintenance status «maintained». 
+This work has the LPPL maintenance status maintained. 
  
 The Current Maintainer of this work is Christoph P. Neumann. 
diff --git a/macros/latex/contrib/iaria-lite/README b/macros/latex/contrib/iaria-lite/README
index 3211e97595..018e09ba46 100644
--- a/macros/latex/contrib/iaria-lite/README
+++ b/macros/latex/contrib/iaria-lite/README
@@ -1,5 +1,5 @@
               -----------------------------
-              Version 0.1 of the iaria-lite class
+              Version 0.2 of the iaria-lite class
                   Christoph P. Neumann
               -----------------------------
 
@@ -40,11 +40,28 @@ Call:
 
   mktexlsr
 
+
 Templates
 ---------
 
-In template.zip document templates for a german and an english CV can be 
-found. Just unzip the template.zip, cd to template and run make to get the
-pdf.
+In the template directory you can find an example document.
+
+
+Source Code
+-----------
+
+The source code of this latex package can be found at:
+https://github.com/cyberlytics/iaria-lite
+
+The build that creates the CTAN-conforming upload ZIP archive
+can be achieved with the Docker image at Dockerhub:
+cyberlytics/ctan-prep:latest
+
+An examplery 'make dist' call is:
+docker run --rm -it -v ${PWD}/:/app cyberlytics/ctan-prep:latest make dist
+
+The source code of this supportive Docker image can be found at:
+https://github.com/cyberlytics/ctan-prep
+
 
 /Christoph P. Neumann, <cyberpetaneuron+iarialite@gmail.com>
diff --git a/macros/latex/contrib/iaria-lite/iaria-lite.dtx b/macros/latex/contrib/iaria-lite/iaria-lite.dtx
index 4b0a3b1c27..3bc6f34d28 100644
--- a/macros/latex/contrib/iaria-lite/iaria-lite.dtx
+++ b/macros/latex/contrib/iaria-lite/iaria-lite.dtx
@@ -1,16 +1,16 @@
 %\iffalse
 % iaria-lite.dtx generated using makedtx version 1.2 (c) Nicola Talbot
 % Command line args:
-%   -preamble "Copyright 2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status «maintained».    The Current Maintainer of this work is Christoph P. Neumann. "
-%   -date "2023-2024"
-%   -author "Christoph P. Neumann "
+%   -dir "src"
+%   -preamble "Copyright 2023-2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. "
+%   -macrocode ".*"
 %   -setambles ".*=>\nopreamble"
 %   -doc "doc/iaria-lite.tex"
-%   -src "(iaria-lite.cls)=>\1"
-%   -macrocode ".*"
-%   -dir "src"
+%   -src "(_cpn_copyIntoExamplesFolder_cls.cmd|iaria-lite.cls)=>\1"
+%   -author "Christoph P. Neumann "
+%   -date "2024-2024"
 %   iaria-lite
-% Created on 2024/3/20 15:52
+% Created on 2024/4/10 18:20
 %\fi
 %\iffalse
 %<*package>
@@ -33,27 +33,10 @@
 %\fi
 % \iffalse
 % Doc-Source file to use with LaTeX2e
-% Copyright (C) 2023-2024 Christoph P. Neumann , all rights reserved.
+% Copyright (C) 2024-2024 Christoph P. Neumann , all rights reserved.
 % \fi
 % \iffalse
 %<*driver>
-%%
-%% Copyright 2023 Christoph P. Neumann
-%%
-%% This LaTeX class provides a simple interface for creating
-%% a verfy fancy Curriculum Vitae. At the moment only CVs in
-%% the german language are supported.
-%%
-%% This file is free property; as a special exception the author
-%% gives unlimited permission to copy and/or distribute it, with
-%% or without modifications, as long as this notice is
-%% preserved.
-%%
-%% This file is distributed in the hope that it will be useful,
-%% but WITHOUT ANY WARRANTY, to the extent permitted by law;
-%% without even the implied warranty of MERCHANTABILITY or
-%% FITNESS FOR A PARTICULAR PURPOSE.
-
 \documentclass{ltxdoc}
 
 \CodelineNumbered
@@ -73,6 +56,7 @@
 %\title{\textsf{iaria-lite}\\
 % An Unofficial IARIA LaTeX Class (Lite Version)}
 %\author{Christoph P.\ Neumann \texttt{$<$cyberpetaneuron@gmail.com$>$}}
+%\date{Version 0.2}
 %\maketitle
 %\PrintChanges
 %
@@ -171,6 +155,31 @@
 %\section{The Code}
 %\iffalse
 %    \begin{macrocode}
+%<*_cpn_copyIntoExamplesFolder_cls.cmd>
+%    \end{macrocode}
+%\fi
+%    \begin{macrocode}
+@echo off
+
+rem ***************************************************************************
+rem * author: Christoph P. Neumann
+rem ***************************************************************************
+cd /d "%~dp0"
+
+echo == ..\examples\* ==
+for /D %%D in (..\examples\*) do (
+	echo == %%D ==
+	xcopy /Y ".\*.cls" "%%~D"
+)
+
+pause%    \end{macrocode}
+%\iffalse
+%    \begin{macrocode}
+%</_cpn_copyIntoExamplesFolder_cls.cmd>
+%    \end{macrocode}
+%\fi
+%\iffalse
+%    \begin{macrocode}
 %<*iaria-lite.cls>
 %    \end{macrocode}
 %\fi
@@ -189,7 +198,7 @@
 \NeedsTeXFormat{LaTeX2e}
 
 % Provide the name of your document class, the date it was last updated, and a comment about what it's used for
-\ProvidesClass{iaria-lite}[2023/01/01 unofficial IARIA-lite conference template]
+\ProvidesClass{iaria-lite}[2024/04/10 unofficial IARIA-lite conference template v0.2]
 
 % Define marker counter for options (counter are global in latex):
 \newcounter{iaria@pbalancetracker}
@@ -242,6 +251,10 @@
 % Diferring from IEEE, IARIA requires a hyphen after "Keywords" instead of an  emdash:
 \xpatchcmd\IEEEkeywords{---}{-}{}{}
 
+% Diferring from IEEE, IARIA requires also the keywords in Italic (and Bold)(and lower case!):
+\let\oldIEEEkeywords\IEEEkeywords
+\def\IEEEkeywords{\oldIEEEkeywords\itshape\ignorespaces}
+
 \makeatletter
 \renewcommand{\IEEEauthorblockN}[1]{%
 % copied from IEEEtran.cls:
@@ -261,6 +274,19 @@
     \crcr}
 \makeatother
 
+% IARIA subfigure captions require this:
+\RequirePackage[caption=false,font=footnotesize]{subfig}
+
+% IARIA requires to bring the table caption in the same line of "Table I"
+\usepackage{etoolbox}
+\makeatletter
+\patchcmd{\@makecaption}
+  {\\}
+  {.\ }
+  {}
+  {}
+\makeatother
+
 % Balance/level columns at the last page / in bibliography
 % DISCLAIMER: No solution is a 100%/perfect one!
 % Mainstream option: pbalance (see https://ctan.org/pkg/pbalance)
diff --git a/macros/latex/contrib/iaria-lite/iaria-lite.ins b/macros/latex/contrib/iaria-lite/iaria-lite.ins
index c24fad9888..5f61f6cac0 100644
--- a/macros/latex/contrib/iaria-lite/iaria-lite.ins
+++ b/macros/latex/contrib/iaria-lite/iaria-lite.ins
@@ -1,13 +1,14 @@
-% iaria-lite.ins generated using makedtx version 1.2 2024/3/20 15:52
+% iaria-lite.ins generated using makedtx version 1.2 2024/4/10 18:20
 \input docstrip
 
 \preamble
-Copyright 2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status «maintained».    The Current Maintainer of this work is Christoph P. Neumann. 
+Copyright 2023-2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. 
 \endpreamble
 
 \askforoverwritefalse
 
-\generate{\file{iaria-lite.cls}{\nopreamble\from{iaria-lite.dtx}{iaria-lite.cls}}
+\generate{\file{_cpn_copyIntoExamplesFolder_cls.cmd}{\nopreamble\from{iaria-lite.dtx}{_cpn_copyIntoExamplesFolder_cls.cmd}}
+\file{iaria-lite.cls}{\nopreamble\from{iaria-lite.dtx}{iaria-lite.cls}}
 }
 
 \endbatchfile
diff --git a/macros/latex/contrib/iaria-lite/iaria-lite.pdf b/macros/latex/contrib/iaria-lite/iaria-lite.pdf
index b976032ec0..a004deb1be 100644
--- a/macros/latex/contrib/iaria-lite/iaria-lite.pdf
+++ b/macros/latex/contrib/iaria-lite/iaria-lite.pdf
diff --git a/macros/latex/contrib/iaria-lite/template/cpn_all_all.bib b/macros/latex/contrib/iaria-lite/template/cpn_all_all.bib
index d7796e6272..cc7abaec4a 100644
--- a/macros/latex/contrib/iaria-lite/template/cpn_all_all.bib
+++ b/macros/latex/contrib/iaria-lite/template/cpn_all_all.bib
@@ -281,7 +281,7 @@
   publisher = {Gesellschaft f{\"u}r Informatik e.V.\ (GI), K{\"o}ln, Germany},
   doi = {10.1145/1620432.1620442},
   url  = {https://dl.gi.de/20.500.12116/20447},
-  _isbn = {978\-/3\-/88579\-/238\-/3},
+  _isbn = {978-3-88579-238-3},
   _issn = {1617\-/5468},
 }
 
@@ -347,9 +347,10 @@
   address = {Nice, France},
   month=jun,
   year={2023},
-  doi = {10.48550/ARXIV.2310.19459},
+  doi = {10.48550/arXiv.2310.19459},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2023_2_10_28004},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2310.19459},
+  _issn = {2308-4294},
   pages = {21--29},
 }
 
@@ -361,9 +362,10 @@
   address = {Venice, Italy},
   month=apr,
   year={2024},
-  _doi = {TODO},
+  doi = {10.48550/arXiv.2404.02637},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2024_X_YY_ZZZZZ},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2404.02637},
+  _issn = {2308\-/4294},
   _pages = {AA--OO},
   note = {accepted for publication}
 }
@@ -402,9 +404,10 @@
   address = {Nice, France},
   month=jun,
   year={2023},
-  doi = {10.48550/ARXIV.2310.19461},
+  doi = {10.48550/arXiv.2310.19461},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2023_2_30_28006},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2310.19461},
+  _issn = {2308\-/4294},
   pages = {41--46},
 }
 
diff --git a/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.pdf b/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.pdf
index a577cadf32..a7d0a9b52f 100644
--- a/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.pdf
+++ b/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.pdf
diff --git a/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.tex b/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.tex
index defc029c2e..e4a4a45462 100644
--- a/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.tex
+++ b/macros/latex/contrib/iaria-lite/template/iaria-lite-example-neumann.tex
@@ -11,12 +11,16 @@
 \usepackage[utf8]{inputenc}
 \usepackage[T1]{fontenc}
 
-% en-US  = [english]/[american]/[usenglish] (+ [canadian])   <DEFAULT>
+% en-US  = [english]/[american]/[USenglish] <DEFAULT>
 \usepackage[babel=true,english=american]{csquotes}
-\usepackage[usenglish]{babel}
-% en-UK  =           [british] /[ukenglish] (+ [australian]) <OXFORD>
+\usepackage[english]{babel} % en-US
+% IARIA requires uppercase TABLE, and babel intervenes in the tablename
+\addto\captionsenglish{\renewcommand\tablename{TABLE}}
+% en-UK  =           [british] /[UKenglish] <OXFORD>
 %\usepackage[babel=true,english=british]{csquotes}
-%\usepackage[ukenglish]{babel}
+%\usepackage[british]{babel} % en-UK
+%% IARIA requires uppercase TABLE, and babel intervenes in the tablename
+%\addto\captionsbritish{\renewcommand\tablename{TABLE}}
 
 % Diferring from IEEE, IARIA requires 
 % in bibliography: 6+ authors as first author et al.
@@ -80,41 +84,41 @@
 ]{microtype}
 
 \begin{filecontents}[overwrite]{embedded.bib}
-	@online{ieee2015howto,
-		author = {Michael Shell},
-		title = {How to Use the {IEEEtran} \LaTeX\ Class},
-		url = {http://mirrors.ctan.org/macros/latex/contrib/IEEEtran/IEEEtran_HOWTO.pdf},
-		year = {2015}
-	}
-	@online{ieee2018formattingrules,
-		author = {{IEEE}},
-		title = {Conference Template and Formatting Specifications},
-		url = {https://www.ieee.org/content/dam/ieee-org/ieee/web/org/conferences/Conference-template-A4.doc},
-		year = {2018}
-	}
-	@online{iaria2014formattingrules,
-		author = {{IARIA}},
-		title = {Formatting Rules},
-		url = {http://www.iaria.org/formatting.doc},
-		year = {2014}
-	}
-	@online{iaria2009editorialrules,
-		_author = {Cosmin Dini},
-		author = {{IARIA}},
-		title = {Editorial Rules},
-		url = {https://www.iaria.org/editorialrules.html},
-		year = {2009}
-	}
-	@online{languagetool,
-		author = {{LanguageTooler GmbH}},
-		title  = {{LangueTool}},
-		url    = {https://languagetool.org/overleaf}
-	}
-	@online{overleaf,
-		author = {{Digital Science UK Limited}},
-		title  = {{Overleaf}},
-		url    = {https://www.overleaf.com}
-	}
+@online{ieee2015howto,
+    author = {Michael Shell},
+    title = {How to Use the {IEEEtran} \LaTeX\ Class},
+    url = {http://mirrors.ctan.org/macros/latex/contrib/IEEEtran/IEEEtran_HOWTO.pdf},
+    year = {2015}
+}
+@online{ieee2018formattingrules,
+    author = {{IEEE}},
+    title = {Conference Template and Formatting Specifications},
+    url = {https://www.ieee.org/content/dam/ieee-org/ieee/web/org/conferences/Conference-template-A4.doc},
+    year = {2018}
+}
+@online{iaria2014formattingrules,
+    author = {{IARIA}},
+    title = {Formatting Rules},
+    url = {http://www.iaria.org/formatting.doc},
+    year = {2014}
+}
+@online{iaria2009editorialrules,
+    _author = {Cosmin Dini},
+    author = {{IARIA}},
+    title = {Editorial Rules},
+    url = {https://www.iaria.org/editorialrules.html},
+    year = {2009}
+}
+@online{languagetool,
+    author = {{LanguageTooler GmbH}},
+    title  = {{LangueTool}},
+    url    = {https://languagetool.org/overleaf}
+}
+@online{overleaf,
+    author = {{Digital Science UK Limited}},
+    title  = {{Overleaf}},
+    url    = {https://www.overleaf.com}
+}
 \end{filecontents}
 
 \usepackage{fontawesome} % i.a., \faWarning{}
@@ -127,128 +131,128 @@
 % https://www.hyphenation24.com/
 \hyphenation{block-chain block-chains Ethe-re-um}
 
+% Capitalization: https://capitalizemytitle.com/style/Chicago/
 \title{The Unofficial \textsmaller{IARIA}-lite \LaTeX{} Class Paper Example (v2024-03)}
 
 \author{
-	\IEEEauthorblockN{Christoph P.\ Neumann\,\orcidlink{0000-0002-5936-631X}}
-	\IEEEauthorblockA{%
-		Department of Electrical Engineering, Media, and Computer Science\\
-		Ostbayerische Technische Hochschule Amberg-Weiden\\
-		Amberg, Germany\\
-		% Diferring from IEEE ("Email"), IARIA requires "e-mail":
-		e-mail: \texttt{c.neumann@oth-aw.de}
-		% Multiple authors and their e-mail addresses:
-		%e-mail: {\tt$\lbrace$j.smith\,|\,c.neumann$\rbrace$@oth-aw.de}
-	}
+    \IEEEauthorblockN{Christoph P.\ Neumann\,\orcidlink{0000-0002-5936-631X}}
+    \IEEEauthorblockA{%
+        Department of Electrical Engineering, Media, and Computer Science\\
+        Ostbayerische Technische Hochschule Amberg-Weiden\\
+        Amberg, Germany\\
+        % Diferring from IEEE ("Email"), IARIA requires "e-mail":
+        e-mail: \texttt{c.neumann@oth-aw.de}
+        % Multiple authors and their e-mail addresses:
+        %e-mail: {\tt$\lbrace$j.smith\,|\,c.neumann$\rbrace$@oth-aw.de}
+    }
 }
 
 \begin{document}
-	
-	\maketitle
-	
-	\begin{abstract}
-		\lipsum[1][3-12]
-	\end{abstract}
-	
-	% A list of IEEE Computer Society appoved keywords can be obtained at
-	% http://www.computer.org/mc/keywords/keywords.htm
-	\begin{IEEEkeywords}
-		% Diferring from IEEE, IARIA requires also the keywords in Bold and Italic (and lower case):
-		\textbf{\textit{template; lorem ipsum.}}
-	\end{IEEEkeywords}
-	
-	\section{Introduction}
-	
-	The \textsmaller{IARIA} formatting is based on \textsmaller{IEEE} style.
-	The unofficial \textsmaller{IARIA}-lite \LaTeX\ class is based on \textsmaller{IEEE}tran class \cite{ieee2015howto}.
-	The \textsmaller{IARIA} formatting rules \cite{iaria2014formattingrules} are adopted from the \textsmaller{IEEE} template and formatting specifications \cite{ieee2018formattingrules}.
-	In addition, be aware of the supplementary \textsmaller{IARIA} editorial rules \cite{iaria2009editorialrules} \faWarning{} that provide a beginner-friendly set of further advices.
-	It is recommended to use a grammar tool, e.\,g., the LanguageTool \cite{languagetool} browser plugin in combination with Overleaf \cite{overleaf}.
-	
-	\lipsum[2]
-	
-	\{\faWarning{} \textsmaller{IARIA} editorial rules: Introduction must end with a paragraph describing the structure of the paper!\}
-	The remainder of the paper is organized as follows: In Section~II, …
-	
-	\section{Related work \textbar{} Methods}
-	\lipsum[3]
-	
-	\section{Results}
-	\lipsum[4]
-	
-	\section{Discussion \textbar{} Evalution}
-	\lipsum[5]
-	
-	\section{Conclusion and Future Work}
-	\{\faWarning{} \textsmaller{IARIA} editorial rules: Last section must be \textquote{Conclusion and Future Work}!\}
-	\lipsum[6]
-	
-	
-	
-	%%% Advisor
-	\nocite{StNe23foodfresh}
-	
-	%%% First-Author
-	\nocite{NeLe13adhocCoop}
-	\nocite{Neumann2012lni}
-	\nocite{NeLe12alphaFlow}
-	\nocite{NeHL12hydra}
-	\nocite{NeWL12offsync}
-	\nocite{NSWL11alphaadaptive}
-	\nocite{NeFL10oxdbs}
-	\nocite{NeLe10alphaUC}
-	\nocite{NeLe09alphaflow}
-	\nocite{NeLe09dmps}
-	\nocite{NHSL09oxdbs} % DE
-	\nocite{NeWL09xdsrig} % DE
-	\nocite{NRDL09deus}
-	
-	%%% Co-Authorship
-	\nocite{LeNe24vocattllm}
-	\nocite{PANP23seccloudfogai}
-	\nocite{WaNe12alphaoffsync}
-	\nocite{ToNe11alphaprops}
-	\nocite{FDI+10esmmog}
-	\nocite{JBN+10fcmdb}
-	\nocite{ILN+09semrttx}
-	\nocite{IND+09lzatav} % DE
-	\nocite{MeNe04testejb}
-	
-	%%% Monographic Work
-	\nocite{Neumann2013dissBook}
-	\nocite{Neumann2012dissPreprint}
-	\nocite{neumann2005da}
-	\nocite{neumann2004sa}
-	
-	%%% TechRep / Non-Peer-Reviewed
-	
-	\nocite{SaNe24othfb}
-	
-	\nocite{ModA-TR-2023SS-WAE-TeamWeiss-Neunerln}
-	\nocite{ModA-TR-2023SS-BDCC-TeamRot-CompVisPipeline}
-	\nocite{ModA-TR-2023SS-BDCC-TeamBlau-NauticalNonsense}
-	\nocite{ModA-TR-2023SS-BCN-TeamGruen-TorpedoTactics}
-	\nocite{ModA-TR-2023SS-BCN-TeamCyan-Stockbird}
-	\nocite{ModA-TR-2023SS-BCN-TeamBlau-FancyChess}
-	\nocite{ModA-TR-2023WS-SWT-TeamRot-SGDb}
-	\nocite{ModA-TR-2023WS-SWT-TeamGruen-OPCUANetzwerk}
-	\nocite{ModA-TR-2022SS-WAE-TeamWeiss-WoIstMeinGeld}
-	\nocite{ModA-TR-2022SS-BDCC-TeamWeiss-TwitterDash}
-	\nocite{ModA-TR-2022SS-BDCC-TeamRot-Reddiment}
-	\nocite{ModA-TR-2022SS-BDCC-TeamGruen-ExplosionGuy}
-	\nocite{ModA-TR-2022SS-BDCC-TeamCyan-OTHWiki}
-	\nocite{ModA-TR-2022WS-SWT-TeamGruen-Graphvio}
-	\nocite{ModA-TR-2021SS-WAE-TeamWeiss-CovidDashboard}
-	\nocite{ModA-TR-2021SS-WAE-TeamRot-FireForceDefense}
-	\nocite{ModA-TR-2021SS-WAE-TeamGruen-MedPlanner}
-	
-	\nocite{NeRL12deus}
-	\nocite{LNR+11egr}
-	
-	% ======== References =========
-	\begingroup
-	\sloppy
-	\printbibliography
-	\endgroup 
-	
+
+\maketitle
+
+\begin{abstract}
+    \lipsum[1][3-12]
+\end{abstract}
+
+% A list of IEEE Computer Society appoved keywords can be obtained at
+% http://www.computer.org/mc/keywords/keywords.htm
+\begin{IEEEkeywords}
+    template; lorem ipsum.
+\end{IEEEkeywords}
+
+\section{Introduction}
+
+The \textsmaller{IARIA} formatting is based on \textsmaller{IEEE} style.
+The unofficial \textsmaller{IARIA}-lite \LaTeX\ class is based on \textsmaller{IEEE}tran class \cite{ieee2015howto}.
+The \textsmaller{IARIA} formatting rules \cite{iaria2014formattingrules} are adopted from the \textsmaller{IEEE} template and formatting specifications \cite{ieee2018formattingrules}.
+In addition, be aware of the supplementary \textsmaller{IARIA} editorial rules \cite{iaria2009editorialrules} \faWarning{} that provide a beginner-friendly set of further advices.
+It is recommended to use a grammar tool, e.\,g., the LanguageTool \cite{languagetool} browser plugin in combination with Overleaf \cite{overleaf}.
+
+\lipsum[2]
+
+\{\faWarning{} \textsmaller{IARIA} editorial rules: Introduction must end with a paragraph describing the structure of the paper!\}
+The remainder of the paper is organized as follows: In Section~II, …
+
+\section{Related work \textbar{} Methods}
+\lipsum[3]
+
+\section{Results}
+\lipsum[4]
+
+\section{Discussion \textbar{} Evalution}
+\lipsum[5]
+
+\section{Conclusion and Future Work}
+\{\faWarning{} \textsmaller{IARIA} editorial rules: Last section must be \textquote{Conclusion and Future Work}!\}
+\lipsum[6]
+
+
+
+%%% Advisor
+\nocite{StNe23foodfresh}
+
+%%% First-Author
+\nocite{NeLe13adhocCoop}
+\nocite{Neumann2012lni}
+\nocite{NeLe12alphaFlow}
+\nocite{NeHL12hydra}
+\nocite{NeWL12offsync}
+\nocite{NSWL11alphaadaptive}
+\nocite{NeFL10oxdbs}
+\nocite{NeLe10alphaUC}
+\nocite{NeLe09alphaflow}
+\nocite{NeLe09dmps}
+\nocite{NHSL09oxdbs} % DE
+\nocite{NeWL09xdsrig} % DE
+\nocite{NRDL09deus}
+
+%%% Co-Authorship
+\nocite{LeNe24vocattllm}
+\nocite{PANP23seccloudfogai}
+\nocite{WaNe12alphaoffsync}
+\nocite{ToNe11alphaprops}
+\nocite{FDI+10esmmog}
+\nocite{JBN+10fcmdb}
+\nocite{ILN+09semrttx}
+\nocite{IND+09lzatav} % DE
+\nocite{MeNe04testejb}
+
+%%% Monographic Work
+\nocite{Neumann2013dissBook}
+\nocite{Neumann2012dissPreprint}
+\nocite{neumann2005da}
+\nocite{neumann2004sa}
+
+%%% TechRep / Non-Peer-Reviewed
+
+\nocite{SaNe24othfb}
+
+\nocite{ModA-TR-2023SS-WAE-TeamWeiss-Neunerln}
+\nocite{ModA-TR-2023SS-BDCC-TeamRot-CompVisPipeline}
+\nocite{ModA-TR-2023SS-BDCC-TeamBlau-NauticalNonsense}
+\nocite{ModA-TR-2023SS-BCN-TeamGruen-TorpedoTactics}
+\nocite{ModA-TR-2023SS-BCN-TeamCyan-Stockbird}
+\nocite{ModA-TR-2023SS-BCN-TeamBlau-FancyChess}
+\nocite{ModA-TR-2023WS-SWT-TeamRot-SGDb}
+\nocite{ModA-TR-2023WS-SWT-TeamGruen-OPCUANetzwerk}
+\nocite{ModA-TR-2022SS-WAE-TeamWeiss-WoIstMeinGeld}
+\nocite{ModA-TR-2022SS-BDCC-TeamWeiss-TwitterDash}
+\nocite{ModA-TR-2022SS-BDCC-TeamRot-Reddiment}
+\nocite{ModA-TR-2022SS-BDCC-TeamGruen-ExplosionGuy}
+\nocite{ModA-TR-2022SS-BDCC-TeamCyan-OTHWiki}
+\nocite{ModA-TR-2022WS-SWT-TeamGruen-Graphvio}
+\nocite{ModA-TR-2021SS-WAE-TeamWeiss-CovidDashboard}
+\nocite{ModA-TR-2021SS-WAE-TeamRot-FireForceDefense}
+\nocite{ModA-TR-2021SS-WAE-TeamGruen-MedPlanner}
+
+\nocite{NeRL12deus}
+\nocite{LNR+11egr}
+
+% ======== References =========
+\begingroup
+\sloppy
+\printbibliography
+\endgroup 
+
 \end{document}
diff --git a/macros/latex/contrib/iaria/COPYING b/macros/latex/contrib/iaria/COPYING
index 778959f22c..cfe1772eff 100644
--- a/macros/latex/contrib/iaria/COPYING
+++ b/macros/latex/contrib/iaria/COPYING
@@ -1,13 +1,13 @@
-Copyright 2024 Christoph P. Neumann 
+Copyright 2023-2024 Christoph P. Neumann 
  
 This work may be distributed and/or modified under the 
-conditions of the LaTeX Project Public License, either version 1.3 
+conditions of the LaTeX Project Public License, either version 1.3c 
 of this license or any later version. 
 The latest version of this license is in 
 https://www.latex-project.org/lppl.txt 
 and version 1.3c or later is part of all distributions of LaTeX 
 version 2008 or later. 
  
-This work has the LPPL maintenance status «maintained». 
+This work has the LPPL maintenance status maintained. 
  
 The Current Maintainer of this work is Christoph P. Neumann. 
diff --git a/macros/latex/contrib/iaria/README b/macros/latex/contrib/iaria/README
index 7f8ea18dcf..73edb8b502 100644
--- a/macros/latex/contrib/iaria/README
+++ b/macros/latex/contrib/iaria/README
@@ -1,5 +1,5 @@
               -----------------------------
-              Version 0.1 of the iaria class
+              Version 0.2 of the iaria class
                   Christoph P. Neumann
               -----------------------------
 
@@ -40,11 +40,28 @@ Call:
 
   mktexlsr
 
+
 Templates
 ---------
 
-In template.zip document templates for a german and an english CV can be 
-found. Just unzip the template.zip, cd to template and run make to get the
-pdf.
+In the template directory you can find an example document.
+
+
+Source Code
+-----------
+
+The source code of this latex package can be found at:
+https://github.com/cyberlytics/iaria
+
+The build that creates the CTAN-conforming upload ZIP archive
+can be achieved with the Docker image at Dockerhub:
+cyberlytics/ctan-prep:latest
+
+An examplery 'make dist' call is:
+docker run --rm -it -v ${PWD}/:/app cyberlytics/ctan-prep:latest make dist
+
+The source code of this supportive Docker image can be found at:
+https://github.com/cyberlytics/ctan-prep
+
 
 /Christoph P. Neumann, <cyberpetaneuron+iaria@gmail.com>
diff --git a/macros/latex/contrib/iaria/iaria.dtx b/macros/latex/contrib/iaria/iaria.dtx
index 8d8d394d09..bc091c3b83 100644
--- a/macros/latex/contrib/iaria/iaria.dtx
+++ b/macros/latex/contrib/iaria/iaria.dtx
@@ -1,16 +1,16 @@
 %\iffalse
 % iaria.dtx generated using makedtx version 1.2 (c) Nicola Talbot
 % Command line args:
-%   -setambles ".*=>\nopreamble"
+%   -author "Christoph P. Neumann "
 %   -dir "src"
-%   -src "(iaria.cls)=>\1"
+%   -src "(_cpn_copyIntoExamplesFolder_cls.cmd|iaria.cls)=>\1"
+%   -preamble "Copyright 2023-2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. "
 %   -date "2023-2024"
-%   -author "Christoph P. Neumann "
-%   -macrocode ".*"
-%   -preamble "Copyright 2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status «maintained».    The Current Maintainer of this work is Christoph P. Neumann. "
 %   -doc "doc/iaria.tex"
+%   -macrocode ".*"
+%   -setambles ".*=>\nopreamble"
 %   iaria
-% Created on 2024/3/20 15:50
+% Created on 2024/4/10 18:20
 %\fi
 %\iffalse
 %<*package>
@@ -37,23 +37,6 @@
 % \fi
 % \iffalse
 %<*driver>
-%%
-%% Copyright 2023 Christoph P. Neumann
-%%
-%% This LaTeX class provides a simple interface for creating
-%% a verfy fancy Curriculum Vitae. At the moment only CVs in
-%% the german language are supported.
-%%
-%% This file is free property; as a special exception the author
-%% gives unlimited permission to copy and/or distribute it, with
-%% or without modifications, as long as this notice is
-%% preserved.
-%%
-%% This file is distributed in the hope that it will be useful,
-%% but WITHOUT ANY WARRANTY, to the extent permitted by law;
-%% without even the implied warranty of MERCHANTABILITY or
-%% FITNESS FOR A PARTICULAR PURPOSE.
-
 \documentclass{ltxdoc}
 
 \CodelineNumbered
@@ -73,6 +56,7 @@
 %\title{\textsf{iaria}\\
 %An Unofficial IARIA LaTeX Class}
 %\author{Christoph P.\ Neumann \texttt{$<$cyberpetaneuron@gmail.com$>$}}
+%\date{Version 0.2}
 %\maketitle
 %\PrintChanges
 %
@@ -165,6 +149,31 @@
 %\section{The Code}
 %\iffalse
 %    \begin{macrocode}
+%<*_cpn_copyIntoExamplesFolder_cls.cmd>
+%    \end{macrocode}
+%\fi
+%    \begin{macrocode}
+@echo off
+
+rem ***************************************************************************
+rem * author: Christoph P. Neumann
+rem ***************************************************************************
+cd /d "%~dp0"
+
+echo == ..\examples\* ==
+for /D %%D in (..\examples\*) do (
+	echo == %%D ==
+	xcopy /Y ".\*.cls" "%%~D"
+)
+
+pause%    \end{macrocode}
+%\iffalse
+%    \begin{macrocode}
+%</_cpn_copyIntoExamplesFolder_cls.cmd>
+%    \end{macrocode}
+%\fi
+%\iffalse
+%    \begin{macrocode}
 %<*iaria.cls>
 %    \end{macrocode}
 %\fi
@@ -197,7 +206,7 @@
 \NeedsTeXFormat{LaTeX2e}
 
 % Provide the name of your document class, the date it was last updated, and a comment about what it's used for
-\ProvidesClass{iaria}[2023/01/01 unofficial IARIA conference template]
+\ProvidesClass{iaria}[2024/04/10 unofficial IARIA conference template v0.2]
 
 % Define marker counter for options (counter are global in latex):
 \newcounter{iaria@pbalancetracker}
@@ -300,6 +309,10 @@
 % Diferring from IEEE, IARIA requires a hyphen after "Keywords" instead of an  emdash:
 \xpatchcmd\IEEEkeywords{---}{-}{}{}
 
+% Diferring from IEEE, IARIA requires also the keywords in Italic (and Bold)(and lower case!):
+\let\oldIEEEkeywords\IEEEkeywords
+\def\IEEEkeywords{\oldIEEEkeywords\itshape\ignorespaces}
+
 \makeatletter
 \renewcommand{\IEEEauthorblockN}[1]{%
 % copied from IEEEtran.cls:
@@ -319,6 +332,19 @@
     \crcr}
 \makeatother
 
+% IARIA subfigure captions require this:
+\RequirePackage[caption=false,font=footnotesize]{subfig}
+
+% IARIA requires to bring the table caption in the same line of "Table I"
+\usepackage{etoolbox}
+\makeatletter
+\patchcmd{\@makecaption}
+  {\\}
+  {.\ }
+  {}
+  {}
+\makeatother
+
 % Allows to hyphenate a word that contains a dash:
 % https://stackoverflow.com/questions/2193307/how-do-i-get-latex-to-hyphenate-a-word-that-contains-a-dash
 \RequirePackage[shortcuts]{extdash} % Use \-/ for a breakable dash that does not prevent the remainer of the word to be hyphenated
diff --git a/macros/latex/contrib/iaria/iaria.ins b/macros/latex/contrib/iaria/iaria.ins
index 187a236425..846e42400d 100644
--- a/macros/latex/contrib/iaria/iaria.ins
+++ b/macros/latex/contrib/iaria/iaria.ins
@@ -1,13 +1,14 @@
-% iaria.ins generated using makedtx version 1.2 2024/3/20 15:50
+% iaria.ins generated using makedtx version 1.2 2024/4/10 18:20
 \input docstrip
 
 \preamble
-Copyright 2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status «maintained».    The Current Maintainer of this work is Christoph P. Neumann. 
+Copyright 2023-2024 Christoph P. Neumann    This work may be distributed and/or modified under the  conditions of the LaTeX Project Public License, either version 1.3c  of this license or any later version.  The latest version of this license is in  https://www.latex-project.org/lppl.txt  and version 1.3c or later is part of all distributions of LaTeX  version 2008 or later.    This work has the LPPL maintenance status maintained.    The Current Maintainer of this work is Christoph P. Neumann. 
 \endpreamble
 
 \askforoverwritefalse
 
-\generate{\file{iaria.cls}{\nopreamble\from{iaria.dtx}{iaria.cls}}
+\generate{\file{_cpn_copyIntoExamplesFolder_cls.cmd}{\nopreamble\from{iaria.dtx}{_cpn_copyIntoExamplesFolder_cls.cmd}}
+\file{iaria.cls}{\nopreamble\from{iaria.dtx}{iaria.cls}}
 }
 
 \endbatchfile
diff --git a/macros/latex/contrib/iaria/iaria.pdf b/macros/latex/contrib/iaria/iaria.pdf
index 9696d69f44..f7665d3d4b 100644
--- a/macros/latex/contrib/iaria/iaria.pdf
+++ b/macros/latex/contrib/iaria/iaria.pdf
diff --git a/macros/latex/contrib/iaria/template/cpn_all_all.bib b/macros/latex/contrib/iaria/template/cpn_all_all.bib
index d7796e6272..cc7abaec4a 100644
--- a/macros/latex/contrib/iaria/template/cpn_all_all.bib
+++ b/macros/latex/contrib/iaria/template/cpn_all_all.bib
@@ -281,7 +281,7 @@
   publisher = {Gesellschaft f{\"u}r Informatik e.V.\ (GI), K{\"o}ln, Germany},
   doi = {10.1145/1620432.1620442},
   url  = {https://dl.gi.de/20.500.12116/20447},
-  _isbn = {978\-/3\-/88579\-/238\-/3},
+  _isbn = {978-3-88579-238-3},
   _issn = {1617\-/5468},
 }
 
@@ -347,9 +347,10 @@
   address = {Nice, France},
   month=jun,
   year={2023},
-  doi = {10.48550/ARXIV.2310.19459},
+  doi = {10.48550/arXiv.2310.19459},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2023_2_10_28004},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2310.19459},
+  _issn = {2308-4294},
   pages = {21--29},
 }
 
@@ -361,9 +362,10 @@
   address = {Venice, Italy},
   month=apr,
   year={2024},
-  _doi = {TODO},
+  doi = {10.48550/arXiv.2404.02637},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2024_X_YY_ZZZZZ},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2404.02637},
+  _issn = {2308\-/4294},
   _pages = {AA--OO},
   note = {accepted for publication}
 }
@@ -402,9 +404,10 @@
   address = {Nice, France},
   month=jun,
   year={2023},
-  doi = {10.48550/ARXIV.2310.19461},
+  doi = {10.48550/arXiv.2310.19461},
   _url = {https://www.thinkmind.org/index.php?view=article&articleid=cloud_computing_2023_2_30_28006},
-  issn = {2308-4294},
+  _url = {https://doi.org/10.48550/arXiv.2310.19461},
+  _issn = {2308\-/4294},
   pages = {41--46},
 }
 
diff --git a/macros/latex/contrib/iaria/template/iaria-example-neumann.pdf b/macros/latex/contrib/iaria/template/iaria-example-neumann.pdf
index 8277068b7b..7c5d190398 100644
--- a/macros/latex/contrib/iaria/template/iaria-example-neumann.pdf
+++ b/macros/latex/contrib/iaria/template/iaria-example-neumann.pdf
diff --git a/macros/latex/contrib/iaria/template/iaria-example-neumann.tex b/macros/latex/contrib/iaria/template/iaria-example-neumann.tex
index eb9514ad8f..eda28b0f0c 100644
--- a/macros/latex/contrib/iaria/template/iaria-example-neumann.tex
+++ b/macros/latex/contrib/iaria/template/iaria-example-neumann.tex
@@ -2,12 +2,16 @@
 \documentclass[conference,flushend]{iaria}
 \pdfoutput=1 % pdflatex hint for arxiv.org (within first 5 lines)
 
-% en-US  = [english]/[american]/[USenglish] (+ [canadian])   <DEFAULT>
+% en-US  = [english]/[american]/[USenglish] <DEFAULT>
 \usepackage[babel=true,english=american]{csquotes}
-\usepackage[USenglish]{babel}
-% en-UK  =           [british] /[UKenglish] (+ [australian]) <OXFORD>
+\usepackage[english]{babel} % en-US
+% IARIA requires uppercase TABLE, and babel intervenes in the tablename
+\addto\captionsenglish{\renewcommand\tablename{TABLE}}
+% en-UK  =           [british] /[UKenglish] <OXFORD>
 %\usepackage[babel=true,english=british]{csquotes}
-%\usepackage[UKenglish]{babel}
+%\usepackage[british]{babel} % en-UK
+%% IARIA requires uppercase TABLE, and babel intervenes in the tablename
+%\addto\captionsbritish{\renewcommand\tablename{TABLE}}
 
 % Allows to hyphenate a word that contains a dash:
 % https://stackoverflow.com/questions/2193307/how-do-i-get-latex-to-hyphenate-a-word-that-contains-a-dash
@@ -31,41 +35,41 @@ final % Always enable microtype, even if in draft mode. This helps finding bad b
 
 
 \begin{filecontents}[overwrite]{embedded.bib}
-	@online{ieee2015howto,
-		author = {Michael Shell},
-		title = {How to Use the {IEEEtran} \LaTeX\ Class},
-		url = {http://mirrors.ctan.org/macros/latex/contrib/IEEEtran/IEEEtran_HOWTO.pdf},
-		year = {2015}
-	}
-	@online{ieee2018formattingrules,
-		author = {{IEEE}},
-		title = {Conference Template and Formatting Specifications},
-		url = {https://www.ieee.org/content/dam/ieee-org/ieee/web/org/conferences/Conference-template-A4.doc},
-		year = {2018}
-	}
-	@online{iaria2014formattingrules,
-		author = {{IARIA}},
-		title = {Formatting Rules},
-		url = {http://www.iaria.org/formatting.doc},
-		year = {2014}
-	}
-	@online{iaria2009editorialrules,
-		_author = {Cosmin Dini},
-		author = {{IARIA}},
-		title = {Editorial Rules},
-		url = {https://www.iaria.org/editorialrules.html},
-		year = {2009}
-	}
-	@online{languagetool,
-		author = {{LanguageTooler GmbH}},
-		title  = {{LangueTool}},
-		url    = {https://languagetool.org/overleaf}
-	}
-	@online{overleaf,
-		author = {{Digital Science UK Limited}},
-		title  = {{Overleaf}},
-		url    = {https://www.overleaf.com}
-	}
+@online{ieee2015howto,
+    author = {Michael Shell},
+    title = {How to Use the {IEEEtran} \LaTeX\ Class},
+    url = {http://mirrors.ctan.org/macros/latex/contrib/IEEEtran/IEEEtran_HOWTO.pdf},
+    year = {2015}
+}
+@online{ieee2018formattingrules,
+    author = {{IEEE}},
+    title = {Conference Template and Formatting Specifications},
+    url = {https://www.ieee.org/content/dam/ieee-org/ieee/web/org/conferences/Conference-template-A4.doc},
+    year = {2018}
+}
+@online{iaria2014formattingrules,
+    author = {{IARIA}},
+    title = {Formatting Rules},
+    url = {http://www.iaria.org/formatting.doc},
+    year = {2014}
+}
+@online{iaria2009editorialrules,
+    _author = {Cosmin Dini},
+    author = {{IARIA}},
+    title = {Editorial Rules},
+    url = {https://www.iaria.org/editorialrules.html},
+    year = {2009}
+}
+@online{languagetool,
+    author = {{LanguageTooler GmbH}},
+    title  = {{LangueTool}},
+    url    = {https://languagetool.org/overleaf}
+}
+@online{overleaf,
+    author = {{Digital Science UK Limited}},
+    title  = {{Overleaf}},
+    url    = {https://www.overleaf.com}
+}
 \end{filecontents}
 
 \usepackage{fontawesome} % i.a., \faWarning{}
@@ -78,128 +82,129 @@ final % Always enable microtype, even if in draft mode. This helps finding bad b
 % https://www.hyphenation24.com/
 \hyphenation{block-chain block-chains Ethe-re-um}
 
+% Capitalization: https://capitalizemytitle.com/style/Chicago/
 \title{The Unofficial \textsmaller{IARIA} \LaTeX{} Class Paper Example (v2024-03)}
 
 \author{
-	\IEEEauthorblockN{Christoph P.\ Neumann\,\orcidlink{0000-0002-5936-631X}}
-	\IEEEauthorblockA{%
-		Department of Electrical Engineering, Media, and Computer Science\\
-		Ostbayerische Technische Hochschule Amberg-Weiden\\
-		Amberg, Germany\\
-		% Diferring from IEEE ("Email"), IARIA requires "e-mail":
-		e-mail: \texttt{c.neumann@oth-aw.de}
-		% Multiple authors and their e-mail addresses:
-		%e-mail: {\tt$\lbrace$j.smith\,|\,c.neumann$\rbrace$@oth-aw.de}
-	}
+    \IEEEauthorblockN{Christoph P.\ Neumann\,\orcidlink{0000-0002-5936-631X}}
+    \IEEEauthorblockA{%
+        Department of Electrical Engineering, Media, and Computer Science\\
+        Ostbayerische Technische Hochschule Amberg-Weiden\\
+        Amberg, Germany\\
+        % Diferring from IEEE ("Email"), IARIA requires "e-mail":
+        e-mail: \texttt{c.neumann@oth-aw.de}
+        % Multiple authors and their e-mail addresses:
+        %e-mail: {\tt$\lbrace$j.smith\,|\,c.neumann$\rbrace$@oth-aw.de}
+    }
 }
 
 \begin{document}
-	
-	\maketitle
-	
-	\begin{abstract}
-		\lipsum[1][3-12]
-	\end{abstract}
-	
-	% A list of IEEE Computer Society appoved keywords can be obtained at
-	% http://www.computer.org/mc/keywords/keywords.htm
-	\begin{IEEEkeywords}
-		% Diferring from IEEE, IARIA requires also the keywords in Bold and Italic (and lower case):
-		\textbf{\textit{template; lorem ipsum.}}
-	\end{IEEEkeywords}
-	
-	\section{Introduction}
-	
-	The \textsmaller{IARIA} formatting is based on \textsmaller{IEEE} style.
-	The unofficial \textsmaller{IARIA} \LaTeX\ class is based on \textsmaller{IEEE}tran class \cite{ieee2015howto}.
-	The \textsmaller{IARIA} formatting rules \cite{iaria2014formattingrules} are adopted from the \textsmaller{IEEE} template and formatting specifications \cite{ieee2018formattingrules}.
-	In addition, be aware of the supplementary \textsmaller{IARIA} editorial rules \cite{iaria2009editorialrules} \faWarning{} that provide a beginner-friendly set of further advices.
-	It is recommended to use a grammar tool, e.\,g., the LanguageTool \cite{languagetool} browser plugin in combination with Overleaf \cite{overleaf}.
-	
-	\lipsum[2]
-	
-	\{\faWarning{} \textsmaller{IARIA} editorial rules: Introduction must end with a paragraph describing the structure of the paper!\}
-	The remainder of the paper is organized as follows: In Section~II, …
-	
-	\section{Related work \textbar{} Methods}
-	\lipsum[3]
-	
-	\section{Results}
-	\lipsum[4]
-	
-	\section{Discussion \textbar{} Evalution}
-	\lipsum[5]
-	
-	\section{Conclusion and Future Work}
-	\{\faWarning{} \textsmaller{IARIA} editorial rules: Last section must be \textquote{Conclusion and Future Work}!\}
-	\lipsum[6]
-	
-	
-	
-	%%% Advisor
-	\nocite{StNe23foodfresh}
-	
-	%%% First-Author
-	\nocite{NeLe13adhocCoop}
-	\nocite{Neumann2012lni}
-	\nocite{NeLe12alphaFlow}
-	\nocite{NeHL12hydra}
-	\nocite{NeWL12offsync}
-	\nocite{NSWL11alphaadaptive}
-	\nocite{NeFL10oxdbs}
-	\nocite{NeLe10alphaUC}
-	\nocite{NeLe09alphaflow}
-	\nocite{NeLe09dmps}
-	\nocite{NHSL09oxdbs} % DE
-	\nocite{NeWL09xdsrig} % DE
-	\nocite{NRDL09deus}
-	
-	%%% Co-Authorship
-	\nocite{LeNe24vocattllm}
-	\nocite{PANP23seccloudfogai}
-	\nocite{WaNe12alphaoffsync}
-	\nocite{ToNe11alphaprops}
-	\nocite{FDI+10esmmog}
-	\nocite{JBN+10fcmdb}
-	\nocite{ILN+09semrttx}
-	\nocite{IND+09lzatav} % DE
-	\nocite{MeNe04testejb}
-	
-	%%% Monographic Work
-	\nocite{Neumann2013dissBook}
-	\nocite{Neumann2012dissPreprint}
-	\nocite{neumann2005da}
-	\nocite{neumann2004sa}
-	
-	%%% TechRep / Non-Peer-Reviewed
-	
-	\nocite{SaNe24othfb}
-	
-	\nocite{ModA-TR-2023SS-WAE-TeamWeiss-Neunerln}
-	\nocite{ModA-TR-2023SS-BDCC-TeamRot-CompVisPipeline}
-	\nocite{ModA-TR-2023SS-BDCC-TeamBlau-NauticalNonsense}
-	\nocite{ModA-TR-2023SS-BCN-TeamGruen-TorpedoTactics}
-	\nocite{ModA-TR-2023SS-BCN-TeamCyan-Stockbird}
-	\nocite{ModA-TR-2023SS-BCN-TeamBlau-FancyChess}
-	\nocite{ModA-TR-2023WS-SWT-TeamRot-SGDb}
-	\nocite{ModA-TR-2023WS-SWT-TeamGruen-OPCUANetzwerk}
-	\nocite{ModA-TR-2022SS-WAE-TeamWeiss-WoIstMeinGeld}
-	\nocite{ModA-TR-2022SS-BDCC-TeamWeiss-TwitterDash}
-	\nocite{ModA-TR-2022SS-BDCC-TeamRot-Reddiment}
-	\nocite{ModA-TR-2022SS-BDCC-TeamGruen-ExplosionGuy}
-	\nocite{ModA-TR-2022SS-BDCC-TeamCyan-OTHWiki}
-	\nocite{ModA-TR-2022WS-SWT-TeamGruen-Graphvio}
-	\nocite{ModA-TR-2021SS-WAE-TeamWeiss-CovidDashboard}
-	\nocite{ModA-TR-2021SS-WAE-TeamRot-FireForceDefense}
-	\nocite{ModA-TR-2021SS-WAE-TeamGruen-MedPlanner}
-	
-	\nocite{NeRL12deus}
-	\nocite{LNR+11egr}
-	
-	% ======== References =========
-	\begingroup
-	\sloppy
-	\printbibliography
-	\endgroup 
-	
+
+\maketitle
+
+\begin{abstract}
+    \lipsum[1][3-12]
+\end{abstract}
+
+% A list of IEEE Computer Society appoved keywords can be obtained at
+% http://www.computer.org/mc/keywords/keywords.htm
+\begin{IEEEkeywords}
+    % Diferring from IEEE, IARIA requires also the keywords in Bold and Italic (and lower case):
+    template; lorem ipsum.
+\end{IEEEkeywords}
+
+\section{Introduction}
+
+The \textsmaller{IARIA} formatting is based on \textsmaller{IEEE} style.
+The unofficial \textsmaller{IARIA} \LaTeX\ class is based on \textsmaller{IEEE}tran class \cite{ieee2015howto}.
+The \textsmaller{IARIA} formatting rules \cite{iaria2014formattingrules} are adopted from the \textsmaller{IEEE} template and formatting specifications \cite{ieee2018formattingrules}.
+In addition, be aware of the supplementary \textsmaller{IARIA} editorial rules \cite{iaria2009editorialrules} \faWarning{} that provide a beginner-friendly set of further advices.
+It is recommended to use a grammar tool, e.\,g., the LanguageTool \cite{languagetool} browser plugin in combination with Overleaf \cite{overleaf}.
+
+\lipsum[2]
+
+\{\faWarning{} \textsmaller{IARIA} editorial rules: Introduction must end with a paragraph describing the structure of the paper!\}
+The remainder of the paper is organized as follows: In Section~II, …
+
+\section{Related work \textbar{} Methods}
+\lipsum[3]
+
+\section{Results}
+\lipsum[4]
+
+\section{Discussion \textbar{} Evalution}
+\lipsum[5]
+
+\section{Conclusion and Future Work}
+\{\faWarning{} \textsmaller{IARIA} editorial rules: Last section must be \textquote{Conclusion and Future Work}!\}
+\lipsum[6]
+
+
+
+%%% Advisor
+\nocite{StNe23foodfresh}
+
+%%% First-Author
+\nocite{NeLe13adhocCoop}
+\nocite{Neumann2012lni}
+\nocite{NeLe12alphaFlow}
+\nocite{NeHL12hydra}
+\nocite{NeWL12offsync}
+\nocite{NSWL11alphaadaptive}
+\nocite{NeFL10oxdbs}
+\nocite{NeLe10alphaUC}
+\nocite{NeLe09alphaflow}
+\nocite{NeLe09dmps}
+\nocite{NHSL09oxdbs} % DE
+\nocite{NeWL09xdsrig} % DE
+\nocite{NRDL09deus}
+
+%%% Co-Authorship
+\nocite{LeNe24vocattllm}
+\nocite{PANP23seccloudfogai}
+\nocite{WaNe12alphaoffsync}
+\nocite{ToNe11alphaprops}
+\nocite{FDI+10esmmog}
+\nocite{JBN+10fcmdb}
+\nocite{ILN+09semrttx}
+\nocite{IND+09lzatav} % DE
+\nocite{MeNe04testejb}
+
+%%% Monographic Work
+\nocite{Neumann2013dissBook}
+\nocite{Neumann2012dissPreprint}
+\nocite{neumann2005da}
+\nocite{neumann2004sa}
+
+%%% TechRep / Non-Peer-Reviewed
+
+\nocite{SaNe24othfb}
+
+\nocite{ModA-TR-2023SS-WAE-TeamWeiss-Neunerln}
+\nocite{ModA-TR-2023SS-BDCC-TeamRot-CompVisPipeline}
+\nocite{ModA-TR-2023SS-BDCC-TeamBlau-NauticalNonsense}
+\nocite{ModA-TR-2023SS-BCN-TeamGruen-TorpedoTactics}
+\nocite{ModA-TR-2023SS-BCN-TeamCyan-Stockbird}
+\nocite{ModA-TR-2023SS-BCN-TeamBlau-FancyChess}
+\nocite{ModA-TR-2023WS-SWT-TeamRot-SGDb}
+\nocite{ModA-TR-2023WS-SWT-TeamGruen-OPCUANetzwerk}
+\nocite{ModA-TR-2022SS-WAE-TeamWeiss-WoIstMeinGeld}
+\nocite{ModA-TR-2022SS-BDCC-TeamWeiss-TwitterDash}
+\nocite{ModA-TR-2022SS-BDCC-TeamRot-Reddiment}
+\nocite{ModA-TR-2022SS-BDCC-TeamGruen-ExplosionGuy}
+\nocite{ModA-TR-2022SS-BDCC-TeamCyan-OTHWiki}
+\nocite{ModA-TR-2022WS-SWT-TeamGruen-Graphvio}
+\nocite{ModA-TR-2021SS-WAE-TeamWeiss-CovidDashboard}
+\nocite{ModA-TR-2021SS-WAE-TeamRot-FireForceDefense}
+\nocite{ModA-TR-2021SS-WAE-TeamGruen-MedPlanner}
+
+\nocite{NeRL12deus}
+\nocite{LNR+11egr}
+
+% ======== References =========
+\begingroup
+\sloppy
+\printbibliography
+\endgroup 
+
 \end{document}
diff --git a/macros/latex/contrib/jsonparse/LICENCE b/macros/latex/contrib/jsonparse/LICENCE
new file mode 100644
index 0000000000..4db9b5af29
--- /dev/null
+++ b/macros/latex/contrib/jsonparse/LICENCE
@@ -0,0 +1,415 @@
+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c  2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+    Everyone is allowed to distribute verbatim copies of this
+    license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute.  This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but 
+it is written in such a way that you can use it even if your work is 
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work.  If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+   `Work'
+    Any work being distributed under this License.
+    
+   `Derived Work'
+    Any work that under any applicable law is derived from the Work.
+
+   `Modification' 
+    Any procedure that produces a Derived Work under any applicable
+    law -- for example, the production of a file containing an
+    original file associated with the Work or a significant portion of
+    such a file, either verbatim or with modifications and/or
+    translated into another language.
+
+   `Modify'
+    To apply any procedure that produces a Derived Work under any
+    applicable law.
+    
+   `Distribution'
+    Making copies of the Work available from one person to another, in
+    whole or in part.  Distribution includes (but is not limited to)
+    making any electronic components of the Work accessible by
+    file transfer protocols such as FTP or HTTP or by shared file
+    systems such as Sun's Network File System (NFS).
+
+   `Compiled Work'
+    A version of the Work that has been processed into a form where it
+    is directly usable on a computer system.  This processing may
+    include using installation facilities provided by the Work,
+    transformations of the Work, copying of components of the Work, or
+    other activities.  Note that modification of any installation
+    facilities provided by the Work constitutes modification of the Work.
+
+   `Current Maintainer'
+    A person or persons nominated as such within the Work.  If there is
+    no such explicit nomination then it is the `Copyright Holder' under
+    any applicable law.
+
+   `Base Interpreter' 
+    A program or process that is normally needed for running or
+    interpreting a part or the whole of the Work.    
+
+    A Base Interpreter may depend on external components but these
+    are not considered part of the Base Interpreter provided that each
+    external component clearly identifies itself whenever it is used
+    interactively.  Unless explicitly specified when applying the
+    license to the Work, the only applicable Base Interpreter is a
+    `LaTeX-Format' or in the case of files belonging to the 
+    `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1.  Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope.  In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2.  You may distribute a complete, unmodified copy of the Work as you
+received it.  Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3.  You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4.  If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work.  You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work.  Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5.  If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6.  If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition.  Only
+the Current Maintainer is allowed to add such statements of exemption 
+to a component of the Work. 
+
+  a. If a component of this Derived Work can be a direct replacement
+     for a component of the Work when that component is used with the
+     Base Interpreter, then, wherever this component of the Work
+     identifies itself to the user when used interactively with that
+     Base Interpreter, the replacement component of this Derived Work
+     clearly and unambiguously identifies itself as a modified version
+     of this component to the user when used interactively with that
+     Base Interpreter.
+     
+  b. Every component of the Derived Work contains prominent notices
+     detailing the nature of the changes to that component, or a
+     prominent reference to another file that is distributed as part
+     of the Derived Work and that contains a complete and accurate log
+     of the changes.
+  
+  c. No information in the Derived Work implies that any persons,
+     including (but not limited to) the authors of the original version
+     of the Work, provide any support, including (but not limited to)
+     the reporting and handling of errors, to recipients of the
+     Derived Work unless those persons have stated explicitly that
+     they do provide such support for the Derived Work.
+
+  d. You distribute at least one of the following with the Derived Work:
+
+       1. A complete, unmodified copy of the Work; 
+          if your distribution of a modified component is made by
+          offering access to copy the modified component from a
+          designated place, then offering equivalent access to copy
+          the Work from the same or some similar place meets this
+          condition, even though third parties are not compelled to
+          copy the Work along with the modified component;
+
+       2. Information that is sufficient to obtain a complete,
+          unmodified copy of the Work.
+
+7.  If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8.  The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9.  Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+     
+10. a. A Derived Work may be distributed under a different license
+       provided that license itself honors the conditions listed in
+       Clause 6 above, in regard to the Work, though it does not have
+       to honor the rest of the conditions in this license.
+      
+    b. If a Derived Work is distributed under a different license, that
+       Derived Work must provide sufficient documentation as part of
+       itself to allow each recipient of that Derived Work to honor the 
+       restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12.  Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work.  Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose.  The entire risk as to the quality and performance
+of the Work is with you.  Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1.  Make a reasonable attempt to trace the Current Maintainer (and
+     the Copyright Holder, if the two differ) through the means of
+     an Internet or similar search.
+
+ 2.  If this search is successful, then enquire whether the Work
+     is still maintained.
+
+  a. If it is being maintained, then ask the Current Maintainer
+     to update their communication data within one month.
+     
+  b. If the search is unsuccessful or no action to resume active
+     maintenance is taken by the Current Maintainer, then announce
+     within the pertinent community your intention to take over
+     maintenance.  (If the Work is a LaTeX work, this could be
+     done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+     maintenance of the Work to you, then this takes effect
+     immediately upon announcement.
+     
+  b. If the Current Maintainer is not reachable and the Copyright
+     Holder agrees that maintenance of the Work be passed to you,
+     then this takes effect immediately upon announcement.  
+    
+ 4.  If you make an `intention announcement' as described in 2b. above
+     and after three months your intention is challenged neither by
+     the Current Maintainer nor by the Copyright Holder nor by other
+     people, then you may arrange for the Work to be changed so as
+     to name you as the (new) Current Maintainer.
+     
+ 5.  If the previously unreachable Current Maintainer becomes
+     reachable once more within three months of a change completed
+     under the terms of 3b) or 4), then that Current Maintainer must
+     become or remain the Current Maintainer upon request provided
+     they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer.  You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license.  These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license.  You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license.  It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate.  Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component.  While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community.  It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one.  Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified.  Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+  %% pig.dtx
+  %% Copyright 2005 M. Y. Name
+  %
+  % This work may be distributed and/or modified under the
+  % conditions of the LaTeX Project Public License, either version 1.3
+  % of this license or (at your option) any later version.
+  % The latest version of this license is in
+  %   http://www.latex-project.org/lppl.txt
+  % and version 1.3 or later is part of all distributions of LaTeX
+  % version 2005/12/01 or later.
+  %
+  % This work has the LPPL maintenance status `maintained'.
+  % 
+  % The Current Maintainer of this work is M. Y. Name.
+  %
+  % This work consists of the files pig.dtx and pig.ins
+  % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.  
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+   The LPPL requires that distributions of the Work contain all the
+   files of the Work.  It is therefore important that you provide a
+   way for the licensee to determine which files constitute the Work.
+   This could, for example, be achieved by explicitly listing all the
+   files of the Work near the copyright notice of each file or by
+   using a line such as:
+
+    % This work consists of all files listed in manifest.txt.
+   
+   in that place.  In the absence of an unequivocal list it might be
+   impossible for the licensee to determine what is considered by you
+   to comprise the Work and, in such a case, the licensee would be
+   entitled to make reasonable conjectures as to which files comprise
+   the Work.
diff --git a/macros/latex/contrib/jsonparse/README.md b/macros/latex/contrib/jsonparse/README.md
new file mode 100644
index 0000000000..9576069ea3
--- /dev/null
+++ b/macros/latex/contrib/jsonparse/README.md
@@ -0,0 +1,46 @@
+![Version 0.5.5](https://img.shields.io/badge/version-0.5.5-blue)
+
+# The `jsonparse` package
+
+The `jsonparse` package provides an easy way to read in JSON data from files or strings in LaTeX documents, parse the data and store it in a user-defined token variable. The package allows accessing the stored data via a JavaScript-flavored syntax.
+
+Using the commands `\JSONParseFromFile` or `\JSONParse`, JSON data can be stored in a token variable. Using the command `\JSONParseGetValue`, certain entried can be extracted from the stored data.
+
+---
+
+Let's assume a file with the name `example.json` is stored in the working directory with the following contents:
+
+```
+{
+  "first_name": "John",
+  "last_name": "Smith",
+  "is_alive": true,
+  "age": 27,
+  "address": {
+    "street_address": "21 2nd Street",
+    "city": "New York",
+    "state": "NY",
+    "postal_code": "10021-3100"
+  },
+  "phone_numbers": [
+    {
+      "type": "home",
+      "number": "212 555-1234"
+    },
+    {
+      "type": "office",
+      "number": "646 555-4567"
+    }
+  ],
+  "children": [
+    "Catherine",
+    "Thomas",
+    "Trevor"
+  ],
+  "spouse": null
+}
+```
+
+We can store it in the token variable `\myJSONdata` using the command `\JSONParseFromFile{\myJSONdata}{example.json}`. Calling the command `\JSONParseGetValue{\myJSONdata}{phone_numbers[0].number}` would then result in the output `212 555-1234` (indices are zero-based per default). 
+
+This package including all files is subject to the LPPL 1.3c license.
diff --git a/macros/latex/contrib/jsonparse/jsonparse-doc.pdf b/macros/latex/contrib/jsonparse/jsonparse-doc.pdf
new file mode 100644
index 0000000000..127c25d2a5
--- /dev/null
+++ b/macros/latex/contrib/jsonparse/jsonparse-doc.pdf
diff --git a/macros/latex/contrib/jsonparse/jsonparse-doc.tex b/macros/latex/contrib/jsonparse/jsonparse-doc.tex
new file mode 100644
index 0000000000..3fe058a3ea
--- /dev/null
+++ b/macros/latex/contrib/jsonparse/jsonparse-doc.tex
@@ -0,0 +1,360 @@
+% File: jsonparse-doc.tex 
+% Copyright 2024 Jasper Habicht (mail@jasperhabicht.de).
+% 
+% This work may be distributed and/or modified under the
+% conditions of the LaTeX Project Public License version 1.3c,
+% available at http://www.latex-project.org/lppl/.
+% 
+% This file is part of the `jsonparse'  package (The Work in LPPL)
+% and all files in that bundle must be distributed together.
+% 
+% This work has the LPPL maintenance status `author-maintained'.
+% 
+\documentclass[a4paper]{article}
+\def\jsonparsefileversion{0.5.5}
+\def\jsonparsefiledate{9 April 2024}
+
+\usepackage[T1]{fontenc}
+\usepackage{Alegreya}
+\usepackage{AlegreyaSans}
+\usepackage{FiraMono}
+
+\usepackage{geometry, longtable, booktabs, tcolorbox, hyperref}
+\geometry{margin=25mm, left=45mm}
+
+\usepackage{fancyhdr}
+\pagestyle{fancy}
+\fancyhf{}
+\renewcommand{\headrulewidth}{0pt}
+\fancyfoot[R]{\thepage}
+
+\linespread{1.1}\selectfont
+\addtolength{\skip\footins}{1em plus 5pt}
+\makeatletter
+\renewcommand*{\thefootnote}{\fnsymbol{footnote}}
+\renewcommand{\@makefntext}[1]{%
+    \noindent\hbox to 0.75em{\normalfont\@thefnmark\hss}~#1%
+}
+\makeatother
+
+\tcbuselibrary{listings}
+\lstdefinestyle{jsonparsedocmacro}{
+    basicstyle=\small\ttfamily,
+    literate=*{<}{{{\color{black!50}\guilsinglleft}}}1 
+        {>}{{{\color{black!50}\guilsinglright}}}1,
+    keywords={},
+    moredelim=[is][\bfseries]{|}{|},
+    moredelim=[is][\color{black!50}]{!}{!},
+}
+\lstdefinestyle{jsonparsedoccodeexample}{
+    basicstyle=\small\ttfamily,
+    keywords={},
+}
+
+\hypersetup{colorlinks}
+
+\ExplSyntaxOn
+\int_new:N \l_jsonparse_doc_change_int
+\NewDocumentCommand{\changes}{ m m m }{
+    \int_incr:N \l_jsonparse_doc_change_int
+    \prop_new:c { l_jsonparse_doc_change_ 
+        \int_to_roman:n { \l_jsonparse_doc_change_int } _prop }
+    \prop_put:cnn { l_jsonparse_doc_change_ 
+        \int_to_roman:n { \l_jsonparse_doc_change_int } _prop } { version } {#1}
+    \prop_put:cnn { l_jsonparse_doc_change_ 
+        \int_to_roman:n { \l_jsonparse_doc_change_int } _prop } { date } {#2}
+    \prop_put:cnn { l_jsonparse_doc_change_ 
+        \int_to_roman:n { \l_jsonparse_doc_change_int } _prop } { changes } {#3}
+}
+\NewDocumentCommand{\printchanges}{ }{
+    \section{Changes}
+    \begin{description}
+    \int_step_inline:nn { \l_jsonparse_doc_change_int } {
+        \item[ 
+            \prop_item:cn { l_jsonparse_doc_change_ 
+            \int_to_roman:n { ##1 } _prop } { version } ] 
+            ( \prop_item:cn { l_jsonparse_doc_change_ 
+            \int_to_roman:n { ##1 } _prop } { date } ) \\
+            \prop_item:cn { l_jsonparse_doc_change_ 
+            \int_to_roman:n { ##1 } _prop } { changes }
+    }
+    \end{description}
+}
+
+\tl_new:N \l_jsonparse_doc_doctitle_tl
+\NewExpandableDocumentCommand{\makedoctitle}{ o m o m m o m }{
+    \hypersetup{
+        pdfauthor={#5},
+        pdftitle={\IfValueTF{#1}{#1}{#2}},
+        pdfsubject={\IfValueTF{#3}{#3}{#4}}
+    }
+    \tl_set:Nn \l_jsonparse_doc_doctitle_tl {
+        \group_begin:
+            \tcbset{
+                title ~ style ~ hook/.style={
+                    boxrule=2pt,
+                    fontupper=\huge\ttfamily
+                }
+            }
+            \setlength{\parindent}{0pt}\sffamily
+            \Huge{\bfseries #2}\par\bigskip
+            \Large #4\par\bigskip
+            \large #5
+            \IfValueT{#6}{
+                \,\footnote{#6}\par\bigskip
+            }
+            #7\par\bigskip
+            \rule{\textwidth}{.08em}
+        \group_end:
+    }
+}
+
+\NewExpandableDocumentCommand{\printdoctitle}{ }{
+    \tl_use:N \l_jsonparse_doc_doctitle_tl
+}
+\ExplSyntaxOff
+
+\tcbset{
+    size=small,
+    arc=2.5pt,
+    outer arc=2.5pt,
+    colframe=black!10,
+    colback=black!10,
+    title style hook/.style={}
+}
+
+\NewTCBListing{macrodef}{ }{ 
+    listing only,
+    listing style={jsonparsedocmacro},
+    grow to left by=2cm,
+    boxrule=0pt,
+    after={\par\smallskip\noindent}
+}
+
+\NewTCBListing{codeexample}{ }{
+    listing only,
+    listing style={jsonparsedoccodeexample},
+    after={\par\smallskip\noindent}
+}
+
+\NewTCBListing{codeexamplecolumns}{ }{
+    text side listing,
+    lefthand width=4.5cm,
+    listing style={jsonparsedoccodeexample},
+    after={\par\smallskip\noindent}
+}
+
+\NewTotalTCBox{\macro}{ O{} v }{
+    verbatim,
+    size=tight,
+    arc=1pt,
+    outer arc=1pt,
+    top=0.5pt, 
+    bottom=0.5pt,
+    left=2pt, 
+    right=2pt,
+    boxrule=0pt,
+    colframe=black!10,
+    colback=black!10,
+    fontupper=\small\ttfamily,
+    #1
+}{\vphantom{/g}\lstinline^#2^}
+
+\NewTotalTCBox{\titlemacro}{ s O{} m }{
+    verbatim,
+    size=tight,
+    arc=1pt,
+    outer arc=1pt,
+    top=0.5pt, 
+    bottom=0.5pt,
+    left=2pt, 
+    right=2pt,
+    boxrule=0pt,
+    colframe=black!10,
+    colback=black!10,
+    fontupper=\small\ttfamily,
+    title style hook,
+    #2
+}{\vphantom{/g}\IfBooleanT{#1}{\textbackslash}#3}
+
+\usepackage{jsonparse}
+
+\makedoctitle
+    [The jsonparse package]
+    {The \titlemacro{jsonparse} package}
+    {An easy way to parse, store and access JSON data from files or strings in LaTeX documents}
+    {Jasper Habicht}[E-mail: \href{mailto:mail@jasperhabicht.de}{mail@jasperhabicht.de}]
+    {Version \jsonparsefileversion, released on \jsonparsefiledate}
+
+\changes{v0.3.0}{2024/04/08}{First public beta release.}
+\changes{v0.5.0}{2024/04/09}{Changed from string token variables to token lists to support Unicode.}
+\changes{v0.5.5}{2024/04/09}{Bug fixes, introduction and enhancement of user functions.}
+
+\begin{document}
+
+\printdoctitle
+
+\bigskip
+
+\section{Introduction}
+
+The \macro{jsonparse} package provides an easy way to read in JSON data from files or strings in LaTeX documents, parse the data and store it in a user-defined token variable. The package allows accessing the stored data via a JavaScript-flavored syntax.
+
+\section{Loading the package}
+
+To install the package, copy the package file \macro{jsonparse.sty} into the working directory or into the \macro{texmf} directory. After the package has been installted, the \macro{jsonparse} package is loaded by calling \macro{\usepackage{jsonparse}} in the preamble of the document. 
+
+The package does not load any dependencies.
+
+\begin{macrodef}debug\end{macrodef}
+The package can be loaded with the option \macro{debug}. It will then output to the log file every instance of a string, a boolean (true or false) value, a null value, a number as well as the start and end of every object and the start and end of every array that is found while parsing the JSON string or JSON file.
+
+\section{Main user commands}
+
+\begin{macrodef}
+|\JSONParse|{<token variable>}{<JSON string>}
+\end{macrodef}
+The command \macro{\JSONParse} is used to parse a JSON string and store the parsed result in a token variable (a property list). The first argument takes the name of the token variable that is created by the command. The second argument takes the JSON string to be parsed. 
+
+For example, using \macro{\JSONParse{\myJSONdata}{ { "key" : "value" } }}, the relevant JSON string will be parsed and the result stored in the token variable \macro{\myJSONdata} as property list. In this case, the property list only consists of one entry with the key \macro{key} and the value \macro{value}. The command \macro{\JSONParseGetValue{\myJSONdata}{key}}, for example, can then be used to extract the relevant value from this property list (see the description below). 
+
+\begin{macrodef}
+|\JSONParseFromFile|{<token variable>}{<JSON file>}
+\end{macrodef}
+The command \macro{\JSONParseFromFile} is used to parse a JSON file and store the parsed result in a token variable (a property list). It works the same way as \macro{\JSONParse}, but instead of a JSON string, it takes as second argument the path to the JSON file relative to the working directory.
+
+\begin{macrodef}
+|\JSONParseGetValue|{<token variable>}{<key>}
+\end{macrodef}
+The command \macro{\JSONParseGetValue} is used to select values from the token variable (property list) that has been created using the commands \macro{\JSONParse} or \macro{\JSONParseFromFile}. The first argument takes the token variable that holds the parsed JSON data. The second argument takes the key to select the relevant entry from the parsed JSON data using JavaScript syntax.
+
+If the JSON string \macro{{ "key" : "value" }} is parsed into the token variable \macro{\myJSONdata}, using \macro{\JSONParseGetValue{\myJSONdata}{key}} would extract the value associated with the key \macro{key}, which in this case is \macro{value}, and typeset it to the document.
+
+Nested objects and arrays are assigned keys that adhere to JavaScript syntax. For example, if the JSON string \macro{{ "outer_key" : { "inner_key" : "value" } }} is parsed into the token variable \macro{\myJSONdata}, to select the value associated with the key \macro{inner_key}, the command \macro{\JSONParseGetValue{\myJSONdata}{outer_key.inner_key}} can be used. The command \macro{\JSONParseGetValue{\myJSONdata}{key[0]}} selects the first value of the array associated with the key \macro{key} in the parsed JSON string \macro{{ "key" : [ "one" , "two" ] }}.
+
+When a key is associated with an object or array, the whole object or array is output as JSON string. This string can again be parsed using \macro{\JSONParse}. The special key \macro{.} (or the string defined using \macro{\JSONParseSetChildSeparator}) return the whole JSON object.
+
+\begin{macrodef}
+|\JSONParseGetArrayValues|{<token variable>}{<key>}[<subkey>]{<string>}
+\end{macrodef}
+The command \macro{\JSONParseGetArrayValues} is used to select all values from an array from a parsed JSON string or JSON file. The first argument takes the token variable that holds the parsed JSON data. The second argument takes the key to select the relevant entry from the parsed JSON data using JavaScript syntax. The third argument is optional an can be used to pass a subkey, i.\,e. a key that is used to select a value for every item. The last argument takes a string that is inserted between all values when they are typeset.
+
+For example, let us assume the following JSON data structure is parsed into the token variable \macro{\myJSONdata}:
+
+\begin{codeexample}
+{
+  "array" : [
+    {
+      "key_a" : "one" ,
+      "key_b" : "two"
+    } ,
+    {
+      "key_a" : "three" ,
+      "key_b" : "four"
+    }
+  ]
+}
+\end{codeexample}
+
+Then using \macro{\JSONParseGetArrayValues{\myJSONdata}{array}[key_a]{, }}, the text \macro{one, three} is typeset to the document. 
+
+\begin{macrodef}
+|\JSONParseUseArrayValues|{<token variable>}{<key>}[<subkey>]{<command name>}
+\end{macrodef}
+The command \macro{\JSONParseUseArrayValues} takes the same first three arguments as the command \macro{\JSONParseGetArrayValues} and works in a similar way. However, instead of a string that is added between the array items, it takes a command name as fourth argument. This command can be defined beforehand and will be called for every array item. Inside its defintion, the commands \macro{\JSONParseArrayIndex}, \macro{\JSONParseArrayKey} and \macro{\JSONParseArrayValue} can be used which are updated for each item and output the index, the key and the value of the current item respectively. 
+
+For example, let us assume the same JSON data structure as defined above parsed into the token variable \macro{\myJSONdata}. Then, the following can be done:
+
+\JSONParse{\myJSONdata}{ { "array" : [ { "key_a" : "one" , "key_b" : "two" } , { "key_a" : "three" , "key_b" : "four" } ] } }
+
+\begin{codeexamplecolumns}
+\newcommand{\myJSONitem}{
+  \item \emph{\JSONParseArrayValue}
+}
+
+\begin{itemize}
+  \JSONParseUseArrayValues{\myJSONdata}
+    {array}[key_a]{myJSONitem}
+\end{itemize}
+\end{codeexamplecolumns}
+
+\begin{macrodef}
+|\JSONParseGetArrayCount|{<token variable>}{<key>}
+\end{macrodef}
+The command \macro{\JSONParseGetArrayCount} takes as frist argument a token variable that holds a parsed JSON string or JSON file and as second argument a key. It returns an integer representing the number of items contained in the selected array.
+
+\subsection{Commands to alter separators and output}
+
+The package provides a set of commands that can be used to change the separators used to select the relevant value in the JSON structure as well as the output that is generated from the JSON data.
+
+\begin{macrodef}
+|\JSONParseSetChildSeparator|{<string>}
+|\JSONParseSetArraySeparator|{<string>}{<string>}
+\end{macrodef}
+The two commands \macro{\JSONParseSetChildSeparator} and \macro{\JSONParseSetArraySeparator} can be used to change the separators for child objects or array items in the syntax used to select a specific value in the JSON data structure. Per default, the child separator is a dot (\macro{.}) while the array separators are sqare brackets (\macro{[} and \macro{]}). The command \macro{\JSONParseSetArraySeparator} takes two arguments of which the first is the character used before the array separator and the second is used after. Changing the separators can be useful if keys in the JSON structure already use these characters.
+
+\begin{macrodef}
+|\JSONParseSetTrueString|{<string>}
+|\JSONParseSetFalseString|{<string>}
+|\JSONParseSetNullString|{<string>}
+\end{macrodef}
+The commands \macro{\JSONParseSetTrueString} and \macro{\JSONParseSetFalseString} as well as the command \macro{\JSONParseSetNullString} can be used to change the output that is typeset if the JSON value is \macro{true}, \macro{false} or \macro{null}. The default strings that are typeset are \macro{true}, \macro{false} or \macro{null} resepctively.
+
+\begin{macrodef}
+|\JSONParseSetArrayIndexZeroBased|
+|\JSONParseSetArrayIndexOneBased|
+\end{macrodef}
+The command \macro{\JSONParseSetArrayIndexZeroBased} sets the numbering of the index of array items to zero-based. With the command \macro{\JSONParseSetArrayIndexOneBased}, the indexing starts with one instead. Per default, the package uses zero-based indexing to resemble JavaScript notation.
+
+\subsection{Internal variables and commands}
+
+\begin{macrodef}
+|\l_jsonparse_debug_mode_bool|
+\end{macrodef}
+The token variable \macro{\l_jsonparse_debug_mode_bool} holds the boolean value true if the package is loaded with the \macro{debug} option and false otherwise. If set to true, the debug mode will be used for the following use of \macro{\jsonparse_parse:n}. 
+
+\begin{macrodef}
+|\l_jsonparse_child_sep_str|
+|\l_jsonparse_array_sep_left_str|
+|\l_jsonparse_array_sep_right_str|
+|\l_jsonparse_true_str|
+|\l_jsonparse_false_str|
+|\l_jsonparse_null_str|
+|\l_jsonparse_array_index_zero_based_bool|
+\end{macrodef}
+The token variable \macro{\l_jsonparse_child_sep_str} holds the string \macro{.} per default or the string set by the user command \macro{\JSONParseSetChildSeparator}.
+
+The token variable \macro{\l_jsonparse_array_sep_left_str} holds the string \macro{[} per default or the string given as first argument to the user command \macro{\JSONParseSetArraySeparator}. 
+
+The token variable \macro{\l_jsonparse_array_sep_right_str} holds the string \macro{]} per default or the string given as second argument to the user command \macro{\JSONParseSetArraySeparator}.
+
+The token variable \macro{\l_jsonparse_true_str} holds the string \macro{true} per default or the string set by the user command \macro{\JSONParseSetTrueString}.
+
+{\sloppy The token variable \macro{\l_jsonparse_false_str} holds the string \macro{false} per default or the string set by the user command \macro{\JSONParseSetFalseString}. \par}
+
+The token variable \macro{\l_jsonparse_null_str} holds the string \macro{null} per default or the string set by the user command \macro{\JSONParseSetNullString}.
+
+The token variable \macro{\l_jsonparse_array_index_zero_based_bool} holds a boolean value which is \macro{true} per default or if the user command \macro{\JSONParseSetArrayIndexZeroBased} was called. The boolean value is \macro{false} if the user command \macro{\JSONParseSetArrayIndexOneBased} was called.
+
+\begin{macrodef}
+|\g_jsonparse_entries_prop|
+\end{macrodef}
+The token variable (property list) \macro{\g_jsonparse_entries_prop} holds key-value pairs representing all elements of a JSON data structure generated by a previous run of \macro{\jsonparse_parse:n}. 
+
+\begin{macrodef}
+|\jsonparse_parse:n| {<JSON string>}
+\end{macrodef}
+The command \macro{\jsonparse_parse:n} takes as argument a JSON string and populates the token variable (property list) \macro{\g_jsonparse_entries_prop} with key-value pairs representing all elements of the JSON data structure represented by this string.
+  
+\begin{macrodef}
+|\jsonparse_parse_to_prop:Nn| <token variable> {<JSON string>}
+\end{macrodef}
+The command \macro{\jsonparse_parse_to_prop:Nn} creates the token variable given as the first arguments as property list and, after having called \macro{\jsonparse_parse:n} using the second argument, sets this newly created property list equal to \macro{\g_jsonparse_entries_prop}.
+
+% =====
+
+\printchanges
+
+\end{document}
+
+%% End of file `jsonparse-doc.tex`.
diff --git a/macros/latex/contrib/jsonparse/jsonparse.sty b/macros/latex/contrib/jsonparse/jsonparse.sty
new file mode 100644
index 0000000000..64ce2e2193
--- /dev/null
+++ b/macros/latex/contrib/jsonparse/jsonparse.sty
@@ -0,0 +1,485 @@
+% File: jsonparse.sty 
+% Copyright 2024 Jasper Habicht (mail@jasperhabicht.de).
+% 
+% This work may be distributed and/or modified under the
+% conditions of the LaTeX Project Public License version 1.3c,
+% available at http://www.latex-project.org/lppl/.
+% 
+% This file is part of the `jsonparse'  package (The Work in LPPL)
+% and all files in that bundle must be distributed together.
+% 
+% This work has the LPPL maintenance status `author-maintained'.
+% 
+\ProvidesExplPackage {jsonparse} {2024-04-09} {0.5.5} 
+  {JSON Parse}
+
+\bool_new:N \l_jsonparse_debug_mode_bool
+\keys_define:nn { jsonparse } { 
+    debug .bool_set:N = \l_jsonparse_debug_mode_bool ,
+    debug .default:n  = { true } ,
+}
+\ProcessKeyOptions [ jsonparse ]
+
+\msg_new:nnn { jsonparse } { parsing-error } {
+  \msg_warning_text:n { jsonparse } \iow_newline:
+  Could ~ not ~ parse ~ JSON. \iow_newline:
+  Parsing ~ error ~ at ~ key ~ `#1` ~ with ~ value ~ `#2`. 
+}
+
+\msg_new:nnn { jsonparse } { debug-info } {
+  #1
+}
+
+% ===
+	
+\str_new:N \l_jsonparse_child_sep_str
+\str_set:Nn \l_jsonparse_child_sep_str { . }
+\str_new:N \l_jsonparse_array_sep_left_str
+\str_set:Nn \l_jsonparse_array_sep_left_str { [ }
+\str_new:N \l_jsonparse_array_sep_right_str
+\str_set:Nn \l_jsonparse_array_sep_right_str { ] }
+\str_new:N \l_jsonparse_true_str
+\str_set:Nn \l_jsonparse_true_str { true }
+\str_new:N \l_jsonparse_false_str
+\str_set:Nn \l_jsonparse_false_str { false }
+\str_new:N \l_jsonparse_null_str
+\str_set:Nn \l_jsonparse_null_str { null }
+
+\bool_new:N \l_jsonparse_array_index_zero_based_bool
+\bool_set_true:N \l_jsonparse_array_index_zero_based_bool
+
+\NewDocumentCommand { \JSONParseSetChildSeparator } { m } {
+  \str_set:Nn \l_jsonparse_child_sep_str { #1 }
+}
+
+\NewDocumentCommand { \JSONParseSetArraySeparator } { m m } {
+  \str_set:Nn \l_jsonparse_array_sep_left_str { #1 }
+  \str_set:Nn \l_jsonparse_array_sep_right_str { #2 }
+}
+
+\NewDocumentCommand { \JSONParseSetTrueString } { m } {
+  \str_set:Nn \l_jsonparse_true_str { #1 }
+}
+
+\NewDocumentCommand { \JSONParseSetFalseString } { m } {
+  \str_set:Nn \l_jsonparse_false_str { #1 }
+}
+
+\NewDocumentCommand { \JSONParseSetNullString } { m } {
+  \str_set:Nn \l_jsonparse_null_str { #1 }
+}
+
+\NewDocumentCommand { \JSONParseSetArrayIndexZeroBased } { } {
+  \bool_set_true:N \l_jsonparse_array_index_zero_based_bool
+}
+
+\NewDocumentCommand { \JSONParseSetArrayIndexOneBased } { } {
+  \bool_set_false:N \l_jsonparse_array_index_zero_based_bool
+}
+
+% ===
+
+\cs_generate_variant:Nn \tl_range:nnn { nne , nen }
+\cs_generate_variant:Nn \tl_range:Nnn { Nne , Nen }
+\cs_generate_variant:Nn \tl_remove_once:Nn { Ne }
+\cs_generate_variant:Nn \tl_set:Nn { Ne }
+\cs_generate_variant:Nn \str_count:n { e }
+\cs_generate_variant:Nn \str_head_ignore_spaces:n { e }
+\cs_generate_variant:Nn \str_set:Nn { Ne }
+\cs_generate_variant:Nn \prop_gput:Nnn { Nee }
+\cs_generate_variant:Nn \seq_use:Nn { Ne }
+\cs_generate_variant:Nn \msg_log:nnn { nno }
+
+\prg_generate_conditional_variant:Nnn \tl_if_head_is_group:n { e } { TF }
+\prg_generate_conditional_variant:Nnn \str_case:nn { en } { F }
+\prg_generate_conditional_variant:Nnn \str_case_e:nn { en } { F }
+\prg_generate_conditional_variant:Nnn \str_if_eq:nn { ee } { T }
+\prg_generate_conditional_variant:Nnn \str_if_eq:nn { en } { T , TF }
+
+\prop_new:N \g_jsonparse_entries_prop
+\prop_new:N \l__jsonparse_temp_prop
+
+\tl_new:N \l__jsonparse_json_tl
+\tl_new:N \l__jsonparse_input_tl
+\tl_new:N \l__jsonparse_temp_tl
+\tl_new:N \l__jsonparse_prefix_tl
+\tl_new:N \l__jsonparse_key_tl
+\tl_new:N \l__jsonparse_val_tl
+\tl_new:N \l__jsonparse_object_array_key_tl
+\tl_new:N \l__jsonparse_object_array_val_tl
+\tl_new:N \l__jsonparse_array_prefix_tl
+\tl_new:N \l__jsonparse_remainder_tl
+
+\int_new:N \l__jsonparse_array_index_int
+\int_new:N \l__jsonparse_array_count_int
+\int_new:N \l__jsonparse_array_count_last_int
+
+\bool_new:N \l__prop_map_first_bool
+
+\ior_new:N \l__jsonparse_json_ior
+	
+% ===
+
+\cs_new:Npn \jsonparse_parse_to_prop:Nn #1#2 {
+  \bool_if:NT \l_jsonparse_debug_mode_bool {
+    \msg_log:nne { jsonparse } { debug-info } {
+      \iow_newline: 
+      Parsing ~ JSON ~ ... 
+    } 
+  }
+  \prop_gclear:N \g_jsonparse_entries_prop
+  \group_begin:
+    \tl_set_eq:NN \par \c_space_tl
+    \jsonparse_parse:n {#2}
+  \group_end:
+  \prop_set_eq:NN #1 \g_jsonparse_entries_prop 
+  \bool_if:NT \l_jsonparse_debug_mode_bool {
+    \msg_log:nne { jsonparse } { debug-info } {
+      JSON ~ parsing ~ done. \iow_newline: 
+    } 
+  }
+}
+
+\cs_new:Npn \jsonparse_parse:n #1 {
+  \tl_set:Ne \l__jsonparse_input_tl { \tl_trim_spaces:n {#1} }
+  \tl_if_head_is_group:eTF { \l__jsonparse_input_tl } {
+    \exp_last_unbraced:Ne 
+      \__jsonparse_parse_object:w \l__jsonparse_input_tl \q_stop 
+  } {
+    \str_case_e:enF { \str_head_ignore_spaces:e { \l__jsonparse_input_tl } } {
+      { [ } { 
+        \exp_last_unbraced:Ne 
+          \__jsonparse_parse_array_begin:w \l__jsonparse_input_tl \q_stop 
+      }
+      { ] } { 
+        \exp_last_unbraced:Ne 
+          \__jsonparse_parse_array_end:w \l__jsonparse_input_tl \q_stop 
+      }
+      { " } { 
+        \exp_last_unbraced:Ne 
+          \__jsonparse_parse_string_key:w \l__jsonparse_input_tl \q_stop 
+      }
+    } {
+      % other
+      \exp_last_unbraced:Ne 
+        \__jsonparse_parse_other:w \l__jsonparse_input_tl \q_stop 
+    }
+  }
+}
+
+% ===
+
+\cs_new:Npn \__jsonparse_parse_object:w #1#2 \q_stop {
+  \__jsonparse_array_key_set:
+  \tl_set:Ne \l__jsonparse_remainder_tl {#2}
+  \group_begin:
+    % object begin
+    \bool_if:NT \l_jsonparse_debug_mode_bool {
+      \msg_log:nne { jsonparse } { debug-info } {
+        (obj ~ begin) 
+      } 
+    }
+    \tl_if_empty:NTF \l__jsonparse_key_tl {
+      \tl_set:Ne \l__jsonparse_object_array_key_tl { \l_jsonparse_child_sep_str }
+    } {
+      \tl_set:Ne \l__jsonparse_object_array_key_tl { \l__jsonparse_key_tl }
+      \tl_set:Ne \l__jsonparse_prefix_tl { \l__jsonparse_key_tl \l_jsonparse_child_sep_str }
+      \tl_set:Ne \l__jsonparse_val_tl {#1}
+    }
+    \tl_set:Ne \l__jsonparse_object_array_val_tl { { #1 } }
+    \exp_args:Ne \jsonparse_parse:n {#1}
+    \prop_gput:Nee \g_jsonparse_entries_prop 
+      { \l__jsonparse_object_array_key_tl } { \l__jsonparse_object_array_val_tl }
+    \bool_if:NT \l_jsonparse_debug_mode_bool {
+      \msg_log:nne { jsonparse } { debug-info } {
+        (key) ~ \str_use:N \l__jsonparse_object_array_key_tl : \iow_newline:
+        \iow_char:N \  \iow_char:N \  (obj) ~ \str_use:N \l__jsonparse_object_array_val_tl 
+      } 
+    } 
+    % object end
+    \bool_if:NT \l_jsonparse_debug_mode_bool {
+      \msg_log:nne { jsonparse } { debug-info } {
+        (obj ~ end) 
+      } 
+    }
+  \group_end:
+  \__jsonparse_parse_remainder:
+}
+
+\cs_new:Npn \__jsonparse_parse_array_begin:w [ #1 \q_stop {
+  \__jsonparse_array_key_set:
+  \group_begin:
+    \tl_set:Ne \l__jsonparse_remainder_tl {#1}
+    % array begin
+    \bool_if:NT \l_jsonparse_debug_mode_bool {
+      \msg_log:nne { jsonparse } { debug-info } {
+        (arr ~ begin) 
+      }   
+    }
+    \int_zero:N \l__jsonparse_array_index_int
+    \bool_if:NT \l_jsonparse_array_index_zero_based_bool {
+      \int_decr:N \l__jsonparse_array_index_int
+    }
+    \tl_set:Ne \l__jsonparse_object_array_key_tl { \l__jsonparse_key_tl }
+    \tl_set:Nn \l__jsonparse_object_array_val_tl { [ #1 }
+    \tl_set:Ne \l__jsonparse_prefix_tl { \l__jsonparse_key_tl \l_jsonparse_array_sep_left_str }
+    \__jsonparse_parse_remainder:
+}
+
+\cs_new:Npn \__jsonparse_parse_array_end:w ] #1 \q_stop {
+    \tl_set:Ne \l__jsonparse_object_array_val_tl { 
+      \tl_range:Nne \l__jsonparse_object_array_val_tl { 1 } {
+        \int_eval:n {
+          -1 * \tl_count:e {#1} - 1
+        }
+      }
+    }
+    \prop_gput:Nee \g_jsonparse_entries_prop 
+      { \l__jsonparse_object_array_key_tl } { \l__jsonparse_object_array_val_tl }
+    \bool_if:NT \l_jsonparse_debug_mode_bool {
+      \msg_log:nne { jsonparse } { debug-info } {
+        (key) ~ \str_use:N \l__jsonparse_object_array_key_tl : \iow_newline:
+        \iow_char:N \  \iow_char:N \  (arr) ~ \str_use:N \l__jsonparse_object_array_val_tl
+      } 
+    } 
+  \group_end:
+  \tl_set:Ne \l__jsonparse_remainder_tl {#1}
+  % array end
+  \bool_if:NT \l_jsonparse_debug_mode_bool {
+    \msg_log:nne { jsonparse } { debug-info } {
+      (arr ~ end) 
+    } 
+  }
+  \__jsonparse_parse_remainder:
+}
+
+\cs_new:Npn \__jsonparse_array_key_set: {
+  \str_if_eq:eeT { \tl_item:Nn \l__jsonparse_prefix_tl { -1 } } 
+    { \l_jsonparse_array_sep_left_str } {
+    \int_incr:N \l__jsonparse_array_index_int
+    \tl_set:Ne \l__jsonparse_key_tl { 
+      \l__jsonparse_prefix_tl \int_use:N \l__jsonparse_array_index_int \l_jsonparse_array_sep_right_str 
+    }
+  }
+}
+
+\cs_new:Npn \__jsonparse_parse_string_key:w " #1 " #2 \q_stop {
+  \__jsonparse_array_key_set:
+  \tl_set:Ne \l__jsonparse_remainder_tl {#2}
+  % key or string?
+  \str_if_eq:enTF { \tl_head:n { #2 } } { : } {
+    \tl_remove_once:Ne \l__jsonparse_remainder_tl { \c_colon_str }
+    \tl_set:Ne \l__jsonparse_key_tl { \l__jsonparse_prefix_tl #1 }
+  } { 
+    \tl_set:Ne \l__jsonparse_val_tl {#1}
+    \prop_gput:Nee \g_jsonparse_entries_prop 
+      { \l__jsonparse_key_tl } { \l__jsonparse_val_tl }
+    % string
+    \bool_if:NT \l_jsonparse_debug_mode_bool {
+      \msg_log:nne { jsonparse } { debug-info } {
+        (key) ~ \str_use:N \l__jsonparse_key_tl : \iow_newline:
+        \iow_char:N \  \iow_char:N \  (str) ~ \str_use:N \l__jsonparse_val_tl
+      } 
+    }  
+  }
+  \__jsonparse_parse_remainder:
+}
+
+\cs_new:Npn \__jsonparse_parse_other:w #1 \q_stop {
+  \__jsonparse_array_key_set:
+  \tl_set:Ne \l__jsonparse_remainder_tl {#1}
+  \tl_set:Ne \l__jsonparse_temp_tl { #1 , }
+  \tl_replace_once:Nnn \l__jsonparse_temp_tl { ] } { , }
+  \exp_last_unbraced:Ne
+    \__jsonparse_parse_other_aux:w \l__jsonparse_temp_tl \q_stop
+}
+
+\cs_new:Npn \__jsonparse_parse_other_aux:w #1 , #2 \q_stop {
+  \tl_set:Ne \l__jsonparse_temp_tl {#1}
+  \str_case:enF { 
+    \str_lowercase:f { \l__jsonparse_temp_tl } 
+  } {
+    { true } {
+      \tl_set:Ne \l__jsonparse_val_tl { 
+        \l_jsonparse_true_str 
+      }
+      \prop_gput:Nee \g_jsonparse_entries_prop 
+        { \l__jsonparse_key_tl } { \l__jsonparse_val_tl }
+      % true
+      \bool_if:NT \l_jsonparse_debug_mode_bool {
+        \msg_log:nne { jsonparse } { debug-info } {
+          (key) ~ \str_use:N \l__jsonparse_key_tl : \iow_newline:
+          \iow_char:N \  \iow_char:N \  (tru) ~ \str_use:N \l__jsonparse_val_tl
+        } 
+      }  
+    }
+    { false } {
+      \tl_set:Ne \l__jsonparse_val_tl { 
+        \l_jsonparse_false_str 
+      }
+      \prop_gput:Nee \g_jsonparse_entries_prop 
+        { \l__jsonparse_key_tl } { \l__jsonparse_val_tl }
+      % false
+      \bool_if:NT \l_jsonparse_debug_mode_bool {
+        \msg_log:nne { jsonparse } { debug-info } {
+          (key) ~ \str_use:N \l__jsonparse_key_tl : \iow_newline:
+          \iow_char:N \  \iow_char:N \  (fal) ~ \str_use:N \l__jsonparse_val_tl
+        } 
+      }
+    }
+    { null } {
+      \tl_set:Ne \l__jsonparse_val_tl { 
+        \l_jsonparse_null_str 
+      }
+      \prop_gput:Nee \g_jsonparse_entries_prop 
+        { \l__jsonparse_key_tl } { \l__jsonparse_val_tl }
+      % null
+      \bool_if:NT \l_jsonparse_debug_mode_bool {
+        \msg_log:nne { jsonparse } { debug-info } {
+          (key) ~ \str_use:N \l__jsonparse_key_tl : \iow_newline:
+          \iow_char:N \  \iow_char:N \  (nul) ~ \str_use:N \l__jsonparse_val_tl
+        } 
+      }
+    }
+  } {
+    \fp_compare:nNnTF {#1} ? { 0 } { 
+      % nan
+      \msg_error:nnee { jsonparse } { parsing-error }
+        { \l__jsonparse_key_tl } {#1}
+    } { 
+      \tl_set:Ne \l__jsonparse_val_tl {#1}
+      \prop_gput:Nee \g_jsonparse_entries_prop 
+        { \l__jsonparse_key_tl } { \l__jsonparse_val_tl }
+      % number
+      \bool_if:NT \l_jsonparse_debug_mode_bool {
+        \msg_log:nne { jsonparse } { debug-info } {
+          (key) ~ \str_use:N \l__jsonparse_key_tl : \iow_newline:
+          \iow_char:N \  \iow_char:N \  (num) ~ \str_use:N \l__jsonparse_val_tl
+        } 
+      }
+    }
+  }
+  \tl_set:Ne \l__jsonparse_remainder_tl { \tl_trim_spaces:V \l__jsonparse_remainder_tl }
+  \tl_set:Ne \l__jsonparse_remainder_tl { 
+    \tl_range:Nen \l__jsonparse_remainder_tl { 
+      \int_eval:n {
+        \tl_count:e { #1 } + 1 
+      }
+    } { -1 }
+  }
+  \__jsonparse_parse_remainder:
+}
+
+\cs_new:Npn \__jsonparse_parse_remainder: {
+  \tl_set:Ne \l__jsonparse_remainder_tl { \tl_trim_spaces:V \l__jsonparse_remainder_tl }
+  \str_if_eq:enT { \tl_head:N \l__jsonparse_remainder_tl } { , } {
+    \tl_remove_once:Nn \l__jsonparse_remainder_tl { , }
+  }
+  \tl_if_empty:NF \l__jsonparse_remainder_tl {
+    \exp_args:Ne \jsonparse_parse:n { \l__jsonparse_remainder_tl }
+  }
+}	
+
+\cs_new:Npn \jsonparse_filter:Nn #1#2 {
+  \prop_map_inline:Nn #1 {
+    \str_case_e:en { 
+      \tl_range:nne {##1} { 1 } { \int_eval:n { \tl_count:e {#2} + 1 } } 
+    } {
+      { #2 \l_jsonparse_child_sep_str } {
+        \prop_put:Nee \l__jsonparse_temp_prop 
+          { \tl_range:nen {##1} { \int_eval:n { \tl_count:e {#2} + 2 } } { -1 } } {##2} 
+      }
+      { #2 \l_jsonparse_array_sep_left_str } {
+        \prop_put:Nee \l__jsonparse_temp_prop 
+          { \tl_range:nen {##1} { \int_eval:n { \tl_count:e {#2} + 1 } } { -1 } } {##2} 
+      }
+    }
+  }
+  \prop_set_eq:NN #1 \l__jsonparse_temp_prop
+}
+
+% ===
+
+\NewExpandableDocumentCommand { \JSONParse } { m +m } {
+  \prop_new:N #1
+  \jsonparse_parse_to_prop:Nn #1 {#2} 
+}
+
+\NewExpandableDocumentCommand { \JSONParseFromFile } { m m } {
+  \ior_open:Nn \l__jsonparse_json_ior {#2}
+  
+  \tl_clear:N \l__jsonparse_json_tl
+  \ior_map_inline:Nn \l__jsonparse_json_ior {
+    \tl_put_right:Nn \l__jsonparse_json_tl {##1}
+  }
+  
+  \ior_close:N \l__jsonparse_json_ior
+
+  \prop_new:N #1
+  \jsonparse_parse_to_prop:Nn #1 { \l__jsonparse_json_tl } 
+}
+
+\NewExpandableDocumentCommand { \JSONParseGetValue } { m m } {
+  \prop_item:Nn #1 {#2} 
+}
+
+\NewExpandableDocumentCommand { \JSONParseGetArrayValues } { m m O{} m } {
+  \group_begin:
+    \jsonparse_filter:Nn #1 {#2}
+    \bool_set_true:N \l__prop_map_first_bool
+    \prop_map_inline:Nn #1 {
+      \str_if_eq:enT { 
+        \tl_range:nen {##1} { \int_eval:n { -1 * \tl_count:n {#3} } } { -1 } 
+      } {#3} {
+        \bool_if:NTF \l__prop_map_first_bool { 
+          \bool_set_false:N \l__prop_map_first_bool
+        } {        
+          #4 
+        }
+        ##2
+      } 
+    }
+  \group_end:
+}
+
+\cs_new:Npn \__jsonparse_get_array_index_aux:w [ #1 ] #2 \q_stop {
+  #1
+}
+
+\NewExpandableDocumentCommand { \JSONParseGetArrayCount } { m m } {
+  \group_begin:
+    \jsonparse_filter:Nn #1 {#2}
+    \int_zero:N \l__jsonparse_array_count_int
+    \int_set:Nn \l__jsonparse_array_count_last_int { -1 }
+    \prop_map_inline:Nn #1 {
+      \int_compare:nNnF { 
+        \__jsonparse_get_array_index_aux:w ##1 \q_stop 
+      } = { \l__jsonparse_array_count_last_int } {
+        \int_incr:N \l__jsonparse_array_count_int
+      }
+      \int_set:Nn \l__jsonparse_array_count_last_int {
+        \__jsonparse_get_array_index_aux:w ##1 \q_stop
+      }
+    } 
+    \int_use:N \l__jsonparse_array_count_int
+  \group_end:
+}
+
+\NewExpandableDocumentCommand { \JSONParseUseArrayValues } { m m O{} m } {
+  \group_begin:
+    \jsonparse_filter:Nn #1 {#2}
+    \prop_map_inline:Nn #1 {
+      \str_if_eq:enT { 
+        \tl_range:nen {##1} { \int_eval:n { -1 * \tl_count:n {#3} } } { -1 } 
+      } {#3} {
+        \int_incr:N \l__jsonparse_array_index_int
+        \tl_set:Ne \JSONParseArrayIndex { \__jsonparse_get_array_index_aux:w ##1 \q_stop }
+        \tl_set:Ne \JSONParseArrayKey { ##1 }
+        \tl_set:Ne \JSONParseArrayValue { \prop_item:Nn #1 {##1} }
+        \use:c {#4} 
+      }
+    } 
+  \group_end:
+}
+
+% EOF
diff --git a/support/TeX4ht/source/ChangeLog b/support/TeX4ht/source/ChangeLog
index 9a2451b6f1..6f2d034f23 100644
--- a/support/TeX4ht/source/ChangeLog
+++ b/support/TeX4ht/source/ChangeLog
@@ -1,3 +1,19 @@
+2024-04-09  Michal Hoftich  <michal.h21@gmail.com>
+
+	* tex4ht-html5.tex (html5.4ht): set backround and foreground colors
+	in the dark mode.
+	https://puszcza.gnu.org.ua/bugs/index.php?623
+
+2024-04-07  Karl Berry  <karl@freefriends.org>
+
+	* tex4ht-4ht.tex (index.4ht): |<TeX4ht copywrite|> to get version.
+
+2024-04-04  Michal Hoftich  <michal.h21@gmail.com>
+
+	* tex4ht-fonts-minionpro.tex: added support for MinionPro fonts.
+	Thanks to David Gleich.
+	https://github.com/michal-h21/htfgen/issues/2
+
 2024-03-31  Michal Hoftich  <michal.h21@gmail.com>
 
 	* tex4ht-4ht.tex (index.4ht): fixed clash between Imakeidx and Index
diff --git a/support/TeX4ht/source/Makefile b/support/TeX4ht/source/Makefile
index 29c8c7da46..3d2d16b365 100644
--- a/support/TeX4ht/source/Makefile
+++ b/support/TeX4ht/source/Makefile
@@ -1,4 +1,4 @@
-# $Id: Makefile 1429 2024-01-03 14:56:01Z michal_h21 $
+# $Id: Makefile 1498 2024-04-04 15:27:36Z michal_h21 $
 # This file is public domain.  Originally written 2010, Karl Berry.
 # Assumes GNU make.
 
@@ -227,6 +227,10 @@ derived += $(tex4ht_fonts_mnsymbol_derived)
 tex4ht_fonts_mnsymbol_derived = \
 	$(ht_fonts_devdir)/unicode/MnSymbol/MnSymbolA-Bold10.htf
 
+derived += $(tex4ht_fonts_minionpro_derived)
+tex4ht_fonts_minionpro_derived = \
+	$(ht_fonts_devdir)/unicode/Minion_Pro/MinionPro-It-lf-l1-ot1.htf
+
 derived += $(tex4ht_fonts_stix_derived)
 tex4ht_fonts_stix_derived = \
 	$(ht_fonts_devdir)/unicode/STIX/stix-mathbb.htf
@@ -462,6 +466,9 @@ $(tex4ht_fonts_opensans_derived): tex4ht-fonts-opensans.tex
 $(tex4ht_fonts_mnsymbol_derived): tex4ht-fonts-mnsymbol.tex
 	$(HTTEX) $< ""
 
+$(tex4ht_fonts_minionpro_derived): tex4ht-fonts-minionpro.tex
+	$(HTTEX) $< ""
+
 $(tex4ht_fonts_stix_derived): tex4ht-fonts-stix.tex
 	$(HTTEX) $< ""
 
diff --git a/support/TeX4ht/source/tex4ht-4ht.tex b/support/TeX4ht/source/tex4ht-4ht.tex
index 6f4a6b5cbf..1de9704646 100644
--- a/support/TeX4ht/source/tex4ht-4ht.tex
+++ b/support/TeX4ht/source/tex4ht-4ht.tex
@@ -1,4 +1,4 @@
-% $Id: tex4ht-4ht.tex 1497 2024-03-31 14:24:29Z michal_h21 $
+% $Id: tex4ht-4ht.tex 1499 2024-04-07 14:55:22Z karl $
 % tex tex4ht-4ht   or   ht tex tex4ht-4ht
 %
 % Copyright 2009-2024 TeX Users Group    
@@ -32297,11 +32297,9 @@ not necessary in MathML anyway.
 \SubSection{index.sty}
 
 \<index.4ht\><<<
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  
-% index.4ht                             |version %
-% Copyright (C) |CopyYear.1999.       Eitan M. Gurari         %
-% Copyright 2024 TeX Users Group 
-|<TeX4ht copyright|>
+% index.4ht (|version), generated from |jobname.tex
+% Copyright |CopyYear.1999. Eitan M. Gurari
+|<TeX4ht copywrite|>
 |<index shared|>
 \expandafter\ifx \csname @vwritefile\endcsname\relax
   |<index 4.01beta|>
diff --git a/support/TeX4ht/source/tex4ht-html5.tex b/support/TeX4ht/source/tex4ht-html5.tex
index c49bd632d3..64e41d7578 100644
--- a/support/TeX4ht/source/tex4ht-html5.tex
+++ b/support/TeX4ht/source/tex4ht-html5.tex
@@ -1,8 +1,8 @@
-% $Id: tex4ht-html5.tex 1379 2023-10-09 11:56:53Z michal_h21 $
+% $Id: tex4ht-html5.tex 1500 2024-04-09 11:26:35Z michal_h21 $
 % compile 3 times: latex tex4ht-moz
 %           or   xhlatex tex4ht-moz "html,3,sections+"
 %
-% Copyright 2009-2023 TeX Users Group
+% Copyright 2009-2024 TeX Users Group
 % Copyright 2000-2009 Eitan M. Gurari
 % Released under LPPL 1.3c+.
 % See tex4ht-cpright.tex for license text.
@@ -26,7 +26,7 @@
 
 \<html5\><<<
 % html5.4ht (|version), generated from |jobname.tex
-% Copyright 2016-2023 TeX Users Group
+% Copyright 2016-2024 TeX Users Group
 |<TeX4ht copywrite|>
 >>>
 
@@ -104,6 +104,14 @@ background of generated images in the dark mode, or line lenght.
     img[src^="\jobname"]{filter: invert(1); }
   }
 }
+
+\Css{
+  body {
+    background-color: Canvas;
+    color: CanvasText;
+    color-scheme: light dark;
+  }
+} 
 \fi
 >>>
 
diff --git a/support/latexmk/CHANGES b/support/latexmk/CHANGES
index 1a2cc620fd..cd531f1416 100644
--- a/support/latexmk/CHANGES
+++ b/support/latexmk/CHANGES
@@ -906,3 +906,23 @@ From v. 4.82a to 4.83
   Restrict warning diagnostics about ^^ constructs in aux file to those
     involving non-trivial Unicode characters, as against things like ^^M.
 
+From v. 4.83 to 4.84
+  Update example_rcfiles/bib2gls_latexmkrc to deal with situation where
+    .glstex file has basename of .bib file rather than that of main .tex
+   file.
+  Update example_rcfiles/asymptote_latexmkrc.
+  Update example_rcfiles/splitindex_latexmkrc.
+  Add example_rcfiles/memoize_latexmkrc.
+  Improve detection of need to run makeindex (solves non-detection when
+    imakeidx package is used with splitindex option).
+  Implement final-output directory, with option -out2dir, variables
+    $out2_dir, @out2_exts.
+  Document hook mechanism.
+  Document $allow_subdir_creation variable.
+
+From v. 4.84 to 4.85
+  Correct bug that if $out_dir and $out2_dir referred to the same
+    directory, but latexmk didn't detect that, then the subroutine copy
+    reported an error, and latexmk treated that incorrectly as a fatal
+    error.
+
diff --git a/support/latexmk/INSTALL b/support/latexmk/INSTALL
index 1eca0ad101..a0cecb7b13 100644
--- a/support/latexmk/INSTALL
+++ b/support/latexmk/INSTALL
@@ -1,6 +1,6 @@
             INSTALLING latexmk
             ==================
-      (Version 4.83, 31 Jan. 2024)
+      (Version 4.85, 7 Apr. 2024)
 
             John Collins
             Physics Department
diff --git a/support/latexmk/README b/support/latexmk/README
index 466ea9e3d1..1992469167 100644
--- a/support/latexmk/README
+++ b/support/latexmk/README
@@ -1,5 +1,5 @@
-Latexmk, version 4.83, 31 Jan 2024
-----------------------------------
+Latexmk, version 4.85, 7 Apr 2024
+---------------------------------
 
 Latexmk completely automates the process of generating a LaTeX
 document.  Essentially, it is a highly specialized cousin of the
diff --git a/support/latexmk/example_rcfiles/asymptote_latexmkrc b/support/latexmk/example_rcfiles/asymptote_latexmkrc
index 7a7425ff47..a936b4127f 100644
--- a/support/latexmk/example_rcfiles/asymptote_latexmkrc
+++ b/support/latexmk/example_rcfiles/asymptote_latexmkrc
@@ -2,32 +2,13 @@
 # or http://www.ctan.org/pkg/asymptote/)
 # with latexmk.  Asymptote is a vector graphics language with a
 # processing program that generates graphics files that can be used in
-# a LaTex file.  
+# a LaTex file.
 #
-# A standard method of using it is with the asymptote LaTeX style file
-# (http://mirror.ctan.org/graphics/asymptote/doc/asymptote.sty)
-# The graphics drawing code is in the tex file, and applying pdflatex to
-# the tex file produces one or more files with a base name the same as
-# or related to the main tex file, but with the extension 'asy'.  The
-# .asy is processed by the program asy (part of the asymptote
-# software) to produce graphics files (which may be eps, tex, or pdf
-# files) that are used the next time pdflatex is run on the main tex
-# file.    
-#
-# Latexmk can be arranged to run asymptote (i.e., the program asy)
-# when needed, by defining the following custom dependency.  (The code
-# is to be put in one of latexmk's rc files, e.g., ~/.latexmkrc.)
-#
-
-## OLD simple method (taken from the documentation for V. 2.03 of
-## asymptote).  These definitions are simple, but they may not always
-## give the desired type of output file, and they do not ensure that
-## latexmk has dependency information about files imported from the
-## asy file.
-#OLD sub asy {return system("asy \"$_[0]\"");}
-#OLD add_cus_dep("asy","eps",0,"asy");
-#OLD add_cus_dep("asy","pdf",0,"asy");
-#OLD add_cus_dep("asy","tex",0,"asy");
+# The definitions in this file enable automatic compilation of .asy files
+# containing asymptote code to be compiled to graphics files.  The .asy files
+# may be created as stand-alone files or may be created during a *latex
+# run by the use of the asymptote package with a document that contains
+# sections of asymptote code.  
 
 
 # The following definitions arrange to run asy with the correct output
@@ -47,17 +28,28 @@ sub asy2pdf { return asy2x( $_[0], 'pdf' ); }
 sub asy2tex { return asy2x( $_[0], 'tex' ); }
 
 sub asy2x   {
-   my $ret = system("asy -vv -f '$_[1]' '$_[0]' >& '$_[0].log'");
-   open( my $FH, "<", "$_[0].log" );
-   %imp = ();
-
+   my ($base, $fmt ) = @_;
+   my $log_file = "$base.log";
+   my $cmd = "asy -vv -noV -f \"$fmt\" -o \"$base.$fmt\" \"$base\" > '$log_file' 2>&1";
+   print "asy2x: Running '$cmd'\n";
+   my $ret = system($cmd);
+   my $FH = undef;
+   if (! open(  $FH, "<", $log_file ) ) {
+      warn "asy2x: Couldn't read log file '$log_file':\n $!";
+      return $ret;
+   }
+   
+   my %imports = ("$base.asy" => 1);
    while (<$FH>) {
-       if (/^(Including|Loading) .* from (.*)\s*$/) {
+       s/\s*$//;
+       if (/^(Including|Loading) .* from (.*)$/) {
           my $import = $2;
-	  $imp{$import} = 1;
+          # Convert MSWin directory separator to /
+          $import =~ s(\\)(/)g;
+	  $imports{$import} = 1;
        }
        elsif ( /^error/ || /^.*\.asy: \d/ ) {
-           warn "==Message from asy: $_";
+           warn "==Message from asy: $_\n";
 	   $ret = 1;
        }
        elsif ( /^kpsewhich / || /^Processing / || /^Using /
@@ -65,11 +57,11 @@ sub asy2x   {
 	     ) {
        }
        else {
-           warn "==Message from asy: $_";
+#           warn "==Message from asy: $_\n";
        }
    }
    close $FH;
-# For latexmk 4.48
-   rdb_set_source( $rule, keys %imp );
+   show_hash( '', \%imports );
+   rdb_set_source( $rule, keys %imports );
    return $ret;
 }
diff --git a/support/latexmk/example_rcfiles/bib2gls_latexmkrc b/support/latexmk/example_rcfiles/bib2gls_latexmkrc
index 53f13ff30a..fccca2109f 100644
--- a/support/latexmk/example_rcfiles/bib2gls_latexmkrc
+++ b/support/latexmk/example_rcfiles/bib2gls_latexmkrc
@@ -1,35 +1,56 @@
-# Implementing glossary with bib2gls and glossaries-extra, with the
-#  log file (.glg) analyzed to get dependence on a .bib file.
+# Implements use of bib2gls with glossaries-extra.
+# Version of 4 Feb 2024.
+# Thanks to Marcel Ilg for a suggestion.
 
 # !!! ONLY WORKS WITH VERSION 4.54 or higher of latexmk
 
 push @generated_exts, 'glstex', 'glg';
 
+# For case that \GlsXtrLoadResources is used and so glstex file (first one)
+# has same name as .aux file.
 add_cus_dep('aux', 'glstex', 0, 'run_bib2gls');
 
+# For case that \glsxtrresourcefile is used and so glstex file (first one)
+# has same name as .bib file.
+add_cus_dep('bib', 'glstex', 0, 'run_bib2gls_alt');
+
 sub run_bib2gls {
+    my $ret = 0;
     if ( $silent ) {
-        my $ret = system "bib2gls --silent --group '$_[0]'";
+        $ret = system "bib2gls --silent --group '$_[0]'";
     } else {
-        my $ret = system "bib2gls --group '$_[0]'";
+        $ret = system "bib2gls --group '$_[0]'";
     };
-    
+
+    # bib2gls puts output files in current directory.
+    # At least put main glstex in same directory as aux file to satisfy
+    # definition of custom dependency.
     my ($base, $path) = fileparse( $_[0] );
     if ($path && -e "$base.glstex") {
         rename "$base.glstex", "$path$base.glstex";
     }
 
+    if ($ret) {
+        warn "Run_bib2gls: Error, so I won't analyze .glg file\n";
+        return $ret;
+    }
     # Analyze log file.
-    local *LOG;
-    $LOG = "$_[0].glg";
-    if (!$ret && -e $LOG) {
-        open LOG, "<$LOG";
-	while (<LOG>) {
-            if (/^Reading (.*\.bib)\s$/) {
-		rdb_ensure_file( $rule, $1 );
-	    }
-	}
-	close LOG;
+    my $log = "$_[0].glg";
+    if ( open( my $log_fh, '<', $log) ) {
+        while (<$log_fh>) {
+            s/\s*$//;
+            if (/^Reading\s+(.+)$/) { rdb_ensure_file( $rule, $1 ); }
+            if (/^Writing\s+(.+)$/) { rdb_add_generated( $1 ); }
+        }
+        close $log_fh;
+    }
+    else {
+        warn "Run_bib2gls: Cannot read log file '$log': $!\n";
     }
     return $ret;
 }
+
+sub run_bib2gls_alt {
+    return Run_subst( 'internal run_bib2gls %Y%R' );
+}
+
diff --git a/support/latexmk/example_rcfiles/memoize_latexmkrc b/support/latexmk/example_rcfiles/memoize_latexmkrc
new file mode 100644
index 0000000000..6a3b61c208
--- /dev/null
+++ b/support/latexmk/example_rcfiles/memoize_latexmkrc
@@ -0,0 +1,258 @@
+print "============= I am memoize's latexmkrc.  John Collins 2024-03-29\n";
+
+# This rc file shows how to use latexmk with the memoize package.
+#
+# The memoize package (https://www.ctan.org/pkg/memoize) implements
+# externalization and memoization of sections of code in a TeX document.
+# It allows the compilation of the document to reuse results of
+# compilation-intensive code, with a consequent speeding up of runs of
+# *latex.  Such compilation intensive code is commonly encountered, for
+# example, in making pictures by TikZ.
+#
+# When a section of code to be memoized is encountered, an extra page is
+# inserted in the document's pdf file containing the results of the
+# compilation of the section of code. Then a script, memoize-extract.pl or
+# memoize-extract.py, is run to extract the extra parts of the the
+# document's pdf file to individual pdf files (called externs).  On the
+# next compilation by *latex, those generated pdf files are used in place
+# of actually compiling the corresponding code (unless the section of code
+# has changed).
+#
+# This latexmkrc file supports this process by configuring latexmk so that
+# when a compilation by *latex is done, a memoize-extract script is run
+# immediately afterwards.  If any new externs are generated, latexmk
+# notices that and triggers a new compilation, as part of its normal mode
+# of operation.
+#
+# The memoize package itself also runs memoize-extract at the start of each
+# compilation. If latexmk has already run memoize-extract, that extra run
+# of memoize-extract finds that it has nothing to do.  The solution here is
+# more general: (a) It handles the case where the memoize package is
+# invoked in the .tex file with the external=no option.  (b) It handles the
+# situation where the aux and out directories are different, which is not
+# the case for the built-in invocation.  (c) It nicely matches with
+# latexmk's general methods of determining how many runs of *latex are
+# needed.
+#
+#  Needs latexmk v. >= 4.84, memoize >= 1.2.0 (2024/03/15).
+#  TeX Live 2024 (or later, presumably).
+#  Tested on TeX Live 2024 on macOS, Ubuntu, Windows,
+#      with pdflatex, lualatex, and xelatex.
+#  Needs perl module PDF::API2 to be installed.
+#  On TeXLive on Windows, also put
+#      TEXLIVE_WINDOWS_TRY_EXTERNAL_PERL = 1
+#  in the texmf.cnf file in the root directory of the TeX Live installation.
+
+# ==> However, there are some anomalies on Windows, which haven't been sorted out
+#     yet.  These notably concern memoize-clean
+#
+# ==> Fails on MiKTeX on Windows: memoize-extract refuses to create pdf file????
+#            I haven't yet figured out the problem.
+# ==> Also trouble on MiKTeX on macOS: the memoize-extract.pl.exe won't run.
+
+# You can have separate build and output directories, e.g., by
+    #$out_dir = 'output';
+    #$aux_dir = 'build';
+# or they can be the same, e.g., by
+     # $out_dir = $aux_dir = 'output';
+
+
+# Which program and extra options to use for memoize-extract and memoize-clean.
+# Note that these are arrays, not simple strings.
+our @memoize_extract = ( 'memoize-extract.pl' );
+our @memoize_clean = ( 'memoize-clean.pl' );
+
+# Specification of the basic memoize files to delete in a clean-up
+# operation. The generated .memo and .pdf files have more specifications,
+# and we use memoize-clean to delete those, invoked by a cleanup hook.
+push @generated_exts, 'mmz', 'mmz.log';
+
+# Subroutine mmz_analyzes analyzes .mmz file, if it exists **and** was
+# generated in current compilation, to determine whether there are new
+# extern pdfs to be generated from memo files and pdf file.  Communicate
+# to subtroutine mmz_extract_new a need to make new externs by setting the
+# variable to a non-zero value for $mmz_has_new.  Let the value be the
+# name of the mmz file; this is perhaps being too elaborate, since the
+# standard name of the mmz file can be determined
+
+add_hook( 'after_xlatex_analysis', \&mmz_analyze );
+add_hook( 'after_main_pdf', \&mmz_extract_new );
+
+# !!!!!!!!!!!!!!!!!!!! Uncomment the following line **only** if you really
+# want latexmk's cleanup operations to delete Memoize's memoization
+# files. In a document where these files are time-consuming to make, i.e.,
+# in the main use case for the memoize package, the files are precious and
+# should only need deleted when that is really needed. 
+#
+# add_hook( 'cleanup', \&mmz_cleanup );
+
+# Whether there are new externs to be made:
+my $mmz_has_new = '';
+#     Scope of this variable: private, from here to end of file.
+
+
+#-----------------------------------------------------
+
+sub mmz_analyze {
+    use strict;
+    print "============= I am mmz_analyze \n";
+    print "  Still to deal with provoking of rerun if directory made\n";
+
+    # Analyzes mmz file if generated on this run.
+    # Then 1. Arranges to trigger making of missing extern pdfs, if needed.
+    #      2. Sets dependencies on the extern pdfs. This ensures that, in
+    #         the case that one or more extern pdfs does not currently
+    #         exist, a rerun of *latex will triggered after it/they get
+    #         made. 
+    # Return zero on success (or nothing to do), and non-zero otherwise.
+
+    # N.B. Current (2024-03-11) hook implementation doesn't use return
+    #      values from hook subroutines. Future implementation might.
+    #      So I'll provide a return value.
+
+    my $base = $$Pbase;
+    my $mmz_file = "$aux_dir1$base.mmz";
+
+    # Communicate to subroutine mmz_extract_new about whether new extern
+    #   pdf(s) are to be made.  Default to assuming no externs are to be
+    #   made:
+    $mmz_has_new = '';
+    
+    if (! -e $mmz_file) {
+        print "mmz_analyze: No mmz file '$mmz_file', so memoize is not being used.\n";
+        return 0;
+    }
+
+    # Use (not-currently-documented) latexmk subroutine to detemine 
+    #   whether mmz file was generated in current run: 
+    if ( ! test_gen_file_time( $mmz_file) ) {
+        warn "mmz_analyze: Mmz file '$mmz_file' exists, but wasn't generated\n",
+             "  on this run so memoize is not **currently** being used.\n";
+        return 0;
+    }
+
+    # Get dependency information.
+    # We need to cause not-yet-made extern pdfs to be trated as source
+    # files for *latex.
+    my $mmz_fh = undef;
+    if (! open( $mmz_fh, '<', $mmz_file ) ) {
+        warn "mmz_analyze: Mmz file '$mmz_file' exists, but I can't read it:\n",
+        "  $!\n";
+        return 1;
+    }
+    my @externs = ();
+    my @dirs = ();
+    while ( <$mmz_fh> ) {
+         s/\s*$//;           # Remove trailing space, including new lines
+         if ( /^\\mmzNewExtern\s+{([^}]+)}/ ) {
+             # We have a new memo item without a corresponding pdf file.
+             # It will be put in the aux directory. 
+             my $file = "$aux_dir1$1";
+             print "mmz_analyze: new extern for memoize: '$file'\n";
+             push @externs, $file;
+         }
+         elsif ( /^\\mmzPrefix\s+{([^}]+)}/ ) {
+             # Prefix.
+             my $prefix = $1;
+             if ( $prefix =~ m{^(.*)/[^/]*} ) {
+                 my $dir = $1;
+                 push @dirs, "$aux_dir1$1";
+
+             }
+         }
+    }
+    close $mmz_fh;
+    foreach (@dirs) {
+        if ( ! -e ) {
+            my @cmd = ( @memoize_extract, '--mkdir', $_ ); 
+            print "mmz_analyze: Making directory '$_' safely by running\n",
+                  " @cmd\n";
+            mkdir $_;
+        }        
+    }
+
+    rdb_ensure_files_here( @externs );
+    
+    # .mmz.log is read by Memoize package after it does an internal
+    # extract, so it appears as an INPUT file in .fls.  But it was created
+    # earlier in the same run by memoize-extract, so it's not a true
+    # dependency, and should be removed from the list of source files:
+    rdb_remove_files( $rule, "$mmz_file.log" );
+
+    if (@externs ) {
+        $mmz_has_new = $mmz_file;
+    }
+    return 0; 
+}
+
+#-----------------------------------------------------
+
+sub mmz_extract_new {
+    use strict;
+    print "============= I am mmz_extract_new \n";
+
+    # If there are new extern pdf files to be made, run memoize-extract to
+    #    make them.
+    # Situation on entry:
+    #   1. I'm in the context of a rule for making the document's pdf file.
+    #      When new extern pdf files are to be made, the document's pdf
+    #      file contains the pages to be extracted by memoize-extract.
+    #      Given the rule context, the name of the document's pdf file is
+    #      $$Pdest.
+    #   2. $mmz_has_new was earlier set to the name of the mmz file with
+    #      the information on the files used for memoization, but only if
+    #      there are new extern pdf(s) to be made.
+    #   3. If it is empty, then no extern pdfs are to be made.  This covers
+    #      the case that the memoize package isn't being used.
+    # Return zero on success (or nothing to do), and non-zero otherwise.
+    
+    if ( $mmz_has_new eq '' ) { return 0; }
+
+    my $mmz_file = $mmz_has_new;
+    my ($mmz_file_no_path, $path) = fileparse( $mmz_file );
+    my $pdf_file = $$Pdest;
+
+    # The directory used by memoize-extract for putting the generated
+    #   extern pdfs is passed in the TEXMF_OUTPUT_DIRECTORY environment
+    #   variable.  (The need for this way of passing information is
+    #   associated with some security restrictions that apply when
+    #   memoize-extract is called directly from the memoize package in a
+    #   *latex compilation.)  
+    local $ENV{TEXMF_OUTPUT_DIRECTORY} = $aux_dir;
+    for ('TEXMF_OUTPUT_DIRECTORY') {
+        print "mmz_extract_new : ENV{$_} = '$ENV{$_}'\n";
+    }
+    # So we should give the name of the mmz_file to memoize-extract without
+    #   the directory part.    
+    my @cmd = (@memoize_extract, '--format', 'latex',
+                    '--pdf', $pdf_file, $mmz_file_no_path ); 
+
+    if ( ! -e $pdf_file ) {
+        warn "mmz_extract_new: Cannot generate externs here, since no pdf file generated\n";
+        return 1;
+    }
+    elsif ( ! test_gen_file($pdf_file) ) {
+        warn "mmz_extract_new: Pdf file '$pdf_file' exists, but wasn't\n",
+             "  generated on this run.  I'll run memoize-extract.  Pdf file may contain\n",
+             "  extra pages generated by the memoize package.\n";
+        return 1;
+    }
+    print "make_extract_new: Running\n @cmd\n";
+    return system @cmd;
+}
+
+#-----------------------------------------------------
+
+sub mmz_cleanup {
+    use strict;
+    print "============= I am mmz_cleanup \n";
+    my @cmd = ( @memoize_clean, '--all', '--yes',
+                      '--prefix', $aux_dir, 
+                      "$aux_dir1$$Pbase.mmz" );
+    print "mmz_cleanup: Running\n @cmd\n";
+    my $ret = system @cmd;
+    say "Return code $ret";
+    return $ret;
+}
+
+#-----------------------------------------------------
diff --git a/support/latexmk/example_rcfiles/splitindex.latexmkrc b/support/latexmk/example_rcfiles/splitindex_latexmkrc
index 4509538dd7..5ee2273062 100644
--- a/support/latexmk/example_rcfiles/splitindex.latexmkrc
+++ b/support/latexmk/example_rcfiles/splitindex_latexmkrc
@@ -1,8 +1,7 @@
+$makeindex = 'internal splitindex2 %S %D %R %B %O';
 $clean_ext .= " %R-*.ind %R-*.idx %R-*.ilg %R-*.ind";
 
-$makeindex = 'internal splitindex';
-
-sub splitindex {
+sub splitindex2 {
    # Use splitindex instead of makeindex.
    # The splitindex programe starts from an .idx file, makes a set of
    #   other .idx files for separate indexes, and then runs makeindex to
@@ -14,7 +13,7 @@ sub splitindex {
    #   Then we need to invoke makeindex.
    # In addition, latexmk assumes that makeindex or its replacement makes
    #   an .ind file from an .idx file, and latexmk gives an error if it
-   #   doesn't exist, we need to make an .ind file.
+   #   doesn't exist, so we need to make an .ind file.
    # Both problems are solved by running makeindex and then splitindex.
    # Note: errors are returned by makeindex and splitindex for things
    #   like a missing input file.  No error is returned for lines in an
@@ -22,8 +21,12 @@ sub splitindex {
    #   ignored.  So no problem is caused by lines in the .idx file
    #   that are generated by splitindex in a format incompatible with
    #   makeindex.
-   my $ret1 = system( "makeindex", $$Psource );
-   my $ret2 = system( "splitindex", $$Psource );
+   my ($source, $dest, $root, $base, @opts) = @_;
+
+   my $ret1 = system( "makeindex", $source );
+   my $ret2 = system( "splitindex", $source );
    return $ret1 || $ret2;
 }
 
+
+print "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n";
\ No newline at end of file
diff --git a/support/latexmk/latexmk.1 b/support/latexmk/latexmk.1
index 85fc6ed20e..1f041da752 100644
--- a/support/latexmk/latexmk.1
+++ b/support/latexmk/latexmk.1
@@ -1,4 +1,4 @@
-.TH LATEXMK 1 "31 January 2024" ""
+.TH LATEXMK 1 "7 April 2024" ""
 .SH NAME
 latexmk \- generate LaTeX document
 .SH SYNOPSIS
@@ -175,8 +175,8 @@ Windows, and is accepted by \fIlatex\fR etc.
 Sets the directory for auxiliary output files of *latex (.aux, .log etc).
 These are all the generated files, with the exception of final output files
 (.dvi, .ps, .pdf, .synctex.gz, .synctex).  See the
-\fB-outdir\fR/\fB-output-directory\fR option for directories for the final
-output files. 
+\fB-outdir\fR/\fB-output-directory\fR option for directories for the main
+output files, and the \fB-out2dir\fR option for the final output files.
 
 If the directory specified for the \fB-aux\fR/\fB-aux-directory\fR option
 is blank, then the default is used, which is to be the same as the output
@@ -845,13 +845,37 @@ If the aux directory is not set or is the same as the output directory,
 then all output files of *latex are sent to the output directory.
 
 If the aux directory is set, e.g., by the option \fB-auxdir\fR, and is not
-equal to the output directory, then only final output files
+equal to the output directory, then only the primary output files
 (.dvi, .ps, .pdf, .synctex, .synctex.gz) are sent to the output
 directory. Other generated files are sent to the aux directory.
 
 See the section AUXILIARY AND OUTPUT DIRECTORIES for more details.
 
 .TP
+.B -out2dir=FOO
+
+(\fIExperimental new feature.\fR)
+
+Sets the directory for the final output files of a whole round of
+compilations.
+
+The use of this directory solves, among other things, the problem that when
+multiple runs of *latex and other programs are needed, files like the main
+pdf file from pdflatex, etc will be changed multiple times. A viewer like
+SumatraPDF that reloads the file whenever it detects changes will show a
+distracting sequence of intermediate states of the pdf file, rather than
+just the final version after all the repeated runs of *latex etc have been
+done.  Instead, when a distinct final-output directory is set, by the
+\fB-out2dir\fR option or the equivalent \fI$out2_dir\fR variable is set,
+the viewer will only see a changed pdf (etc) file after full sequence of
+repeated runs of *latex etc has finished.
+
+By default the final output directory is the same as the output directory
+(as specified by the \fB-outdir\fR option or the setting of the variable
+\fI$out_dir\fR configuration variable).
+
+
+.TP
 .B -output-format=FORMAT
 This option is one that is allowed for \fIlatex\fR, \fIlualatex\fR, and
 \fIpdflatex\fR. But it is not passed to these programs.  Instead
@@ -1907,11 +1931,13 @@ If the variable \fI$pre_tex_code\fR is the empty string, then %P is
 equivalent to %S.
 .TP
 .B %R
-root filename.  This is the base name for the main tex file.
+root filename.
 
 By default this is the basename of the main tex file.  However the
 value can be changed by the use of the \fI-jobname\fR option or the
-\fI$jobname\fR configuration variable.
+\fI$jobname\fR configuration variable.  This is then the basename for files
+like the .aux and .log files produced by running *latex, as well for the
+main .dvi, .pdf, .ps and/or .xdvi files.
 .TP
 .B %S
 source file (e.g., the name of the dvi file when converting a .dvi file
@@ -2106,6 +2132,21 @@ indicates true, i.e., the behavior occurs, while a zero value
 indicates a false value, i.e., the behavior does not occur.
 
 .TP
+.B $allow_subdir_creation [1]
+
+Specify action to take when message(s) in the .log file indicate a failure
+of an attempt by a *latex compilation to write a file to a subdirectory of
+the output directory because the subdirectory didn't exist.
+
+If the value if \fI$allow_subdir_creation\fR is 0, no action is taken.  If
+it is 1, then the appropriate subdirectory is created and a rerun of *latex
+is triggered, but only if the file being written is an .aux file.  (This
+happens, for example, if the document includes a file from a subdirectory
+of the document directory, by the \\include command.  If the value of
+\fI$allow_subdir_creation\fR is 2, then the subdirectory creation is done
+independently of which type of file is in question.
+
+.TP
 .B $allow_switch [1]
 
 This controls what happens when the output extension of latex,
@@ -2170,7 +2211,7 @@ $analyze_input_log_always to 1.
 Whether to automatically read the standard initialization (rc) files,
 which are the system RC file, the user's RC file, and the RC file in
 the current directory.  The command line option \fB-norc\fR can be
-used to turn this setting off.  Each RC file co2uld also turn this
+used to turn this setting off.  Each RC file could also turn this
 setting off, i.e., it could set \fI$auto_rc_use\fR to zero to prevent
 automatic reading of the later RC files.
 
@@ -2738,7 +2779,7 @@ updated by sending a signal -- see the information on the variable
 \fI$dvi_update_method\fR.  The default value is the one appropriate
 for \fIxdvi\fR on a UNIX system.
 .TP
-.B $emulate_aux [0]
+.B $emulate_aux [1]
 Whether to emulate the use of aux directory when $aux_dir and $out_dir are
 different, rather than using the \fB-aux-directory\fR option for the *latex
 programs.  (MiKTeX supports \fB-aux-directory\fR, but TeXLive doesn't.)
@@ -3196,11 +3237,12 @@ continuous-preview mode.  If \fI$new_viewer_always\fR is 0,
 same file, and if one is running will not start a new one.  If
 \fI$new_viewer_always\fR is non-zero, this check will be skipped, and
 \fIlatexmk\fR will behave as if no viewer is running.
+
 .TP
 .B $out_dir [""]
 If non-blank, this variable specifies the output directory.
 
-This is the directory in which final output files are written (dvi, ps,
+This is the directory in which the main output files are written (dvi, ps,
 pdf, synctex, synctex.gz).  In addition, if the aux directory equals the
 output directory, as is the case by default, then other generated files are
 in effect written to the output directory.
@@ -3213,6 +3255,37 @@ See the section AUXILIARY AND OUTPUT DIRECTORIES for more details.
 
 
 .TP
+.B $out2_dir [""]
+(\fIExperimental new feature.\fR)
+
+If non-blank, this variable specifies the final-output directory, i.e., the
+directory for the final output files.  If this variable is blank (its
+default value), the final-output directory is the same as the output
+directory.
+
+See the description of the option \fB-out2dir\fR for an explanation of the
+rationale for the idea of separate output and final-output directories.
+
+If the final-output directory is different from the output directory, then
+after a full round of compilations of the document, the relevant set of
+files is copied here from the output directory.  The files copied are
+specified by the \fI@out2_exts\fR variable, and by default are those with
+extensions 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz', and a basename the
+same as for the main *latex compilation.
+
+.TP
+.B @out2_exts [( 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz' )]
+
+This variable lists the extensions of the files to be copied to the
+final-output directory. The basename of the files is that for the main
+*latex compilation (corresponding to the value specified by the placeholder
+%R).  More general names may be specified in the same way as for the
+\fI@generated_exts\fR variable, by inclusion of %R in a pattern, e.g.,
+
+    push @out2_exts, '%R-2up.pdf';
+
+
+.TP
 .B $pdf_mode [0]
 If zero, do NOT generate a pdf version of the document.
 If equal to 1, generate a pdf version of the document using \fIpdflatex\fR,
@@ -4041,45 +4114,26 @@ method doesn't delete any previous custom-dependency for the same
 conversion.  So the new method is preferable.
 
 
-.SH Advanced configuration: Some extra resources and advanced tricks
+.SH ADVANCED CONFIGURATION: SOME EXTRA RESOURCES AND ADVANCED TRICKS
+
+For most purposes, simple configuration for \fIlatexmk\fR along the lines
+of the examples given is sufficient.  But sometimes you need something
+harder.  In this section, I indicate some extra possibilities.  Generally
+to use these, you need to be fluent in the Perl language, since this is
+what is used in the rc files.
 
-For most purposes, simple configuration for \fIlatexmk\fR along the
-lines of the examples given is sufficient.  But sometimes you need
-something harder.  In this section, I indicate some extra
-possibilities.  Generally to use these, you need to be fluent in the
-Perl language, since this is what is used in the rc files.
+In this section, I include first, a description of a number of variables
+and subroutines that provide, among other things, access to latexmk's
+internal data structures for handling dependencies.  Then I describe the
+hook mechanism whereby at certain points in the processing, latexmk can
+call user-defined subroutines.
 
 See also the section DEALING WITH ERRORS, PROBLEMS, ETC.  See
 also the examples in the directory \fIexample_rcfiles\fR in the
 \fIlatexmk\fR distributions.  Even if none of the examples apply to
 your case, they may give you useful ideas
 
-.SS Utility subroutines
-
-.TP
-.B ensure_path( var, values ...)
-
-The first parameter is the name of one of the system's environment
-variables for search paths.  The remaining parameters are values that
-should be in the variable.  For each of the value parameters, if it
-isn't already in the variable, then it is prepended to the variable;
-in that case the environment variable is created if it doesn't already
-exist. For separating values, the character appropriate the the
-operating system is used -- see the configuration variable
-\fI$search_path_separator\fR. 
-
-Example:
 
-  ensure_path( 'TEXINPUTS', './custom_cls_sty_files//' );
-
-(In this example, the trailing '//' is documented by TeX systems to
-mean that \fI*latex\fR search for files in the specified
-directory and in all subdirectories.)
-
-Technically \fIensure_path\fR works by setting Perl's variable
-\fI$ENV{var}\fR, where \fIvar\fR is the name of the target variable.
-The changed value is then passed as an environment variable to any
-invoked programs.
 
 .SS Variables and subroutines for processing a rule
 
@@ -4103,15 +4157,97 @@ This variable has the name of the rule, as known to
 \fIlatexmk\fR. Note that the exact contents of this variable for a
 given rule may be dependent on the version of \fIlatexmk\fR
 .TP
-.B $$Psource
-This gives the name of the primary source file.  Note the double
-dollar signs.
+.B $$Pbase
+This gives the basename for the rule.  Generally, it determines the names
+of generated files.  E.g., for a run of *latex, the name of the .log file
+is the aux directory concatenated with the basename and then `.log'.
+
+For a *latex rule, the basename is without a directory component.  For
+other rules, it includes the directory component (if any is used).
+
+This (annoying) difference is associated with the different ways in which
+the commands invoked by latexmk work when the command line includes a name
+for a source file that includes a directory component.  For the *latex
+commands, the directory of the source file is irrelevant to the directory
+component the generated files, which instead is determined by the values in
+the -aux-directory and/or -output-directory options.
+
+In contrast, many other programs (e.g., biber, bibtex) put their generated
+files in the same directory as the source file, merely with a changed extension.
+
+Note the double dollar signs: In Perl terms, the variable \fI$Pbase\fR is a
+\fIreference\fR to a variable that contains the basename.  The second
+dollar sign derefences the reference to give the actual value.  (A
+reference is is used rather like a pointer, and the `P' (for `pointer') at
+the start of the variable name is a convention used in latexmk to indicate
+that the variable is a reference variable.)
+
 .TP
 .B $$Pdest
 This gives the name of the main output file if any.  Note the double
 dollar signs.
 
 .TP
+.B $$Psource
+This gives the name of the primary source file.  Note the double
+dollar signs.
+
+.TP
+.B add_hook( <stack_name>, <subroutine> )
+See the section `Hooks' for more details.
+
+This adds the subroutine specified in the second argument to latexmk's
+stack of hooks specified by the stack name.  It returns 1 on sucess, and
+zero otherwise (e.g., if the specified hook stack doesn't exist).
+
+The subroutine can be specified by a reference to the subroutine, as in
+
+    add_hook( 'after_xlatex_analysis', \&mmz_analyze )
+
+Given that the subroutine mmz_analyze has been defined in the rc file.
+
+The subroutine can be specified by a string whose value is the name of the
+subroutine, e.g., 
+
+    add_hook( 'after_xlatex_analysis', 'mmz_analyze' )
+
+In simple cases, the subroutine can be an anonymous subroutine defined in
+the call to add_hooks, 
+
+    add_hook( 'after_main_pdf', sub{ print \"TEST\\n\"; return 0; } );
+
+Observe that on success, the subroutine should return 0 (like a call to
+Perl's system subroutine), so normally this should be coded explicitly.  If
+a hook subroutine returns a non-zero value, latexmk treats that as an error
+condition. 
+
+
+.TP
+.B ensure_path( var, values ...)
+
+The first parameter is the name of one of the system's environment
+variables for search paths.  The remaining parameters are values that
+should be in the variable.  For each of the value parameters, if it
+isn't already in the variable, then it is prepended to the variable;
+in that case the environment variable is created if it doesn't already
+exist. For separating values, the character appropriate the the
+operating system is used -- see the configuration variable
+\fI$search_path_separator\fR. 
+
+Example:
+
+  ensure_path( 'TEXINPUTS', './custom_cls_sty_files//' );
+
+(In this example, the trailing '//' is documented by TeX systems to
+mean that \fI*latex\fR search for files in the specified
+directory and in all subdirectories.)
+
+Technically \fIensure_path\fR works by setting Perl's variable
+\fI$ENV{var}\fR, where \fIvar\fR is the name of the target variable.
+The changed value is then passed as an environment variable to any
+invoked programs.
+
+.TP
 .B pushd( path ), popd()
 These subroutines are used when it is needed to temporarily change the
 working directory, as in
@@ -4173,6 +4309,12 @@ multiple files, you will need one call to \fRrdb_ensure_file\fI for each
 file.\fR
 
 .TP
+.B rdb_ensure_files_here( file, ... )
+Like subroutine \fIrdb_ensure_files\fR, except that (a) it assumes the
+context is of a rule, and the files are to be added to the source list for
+that rule; (b) multiple files are allowed.
+
+.TP
 .B rdb_remove_files( $rule, file, ... )
 This subroutine removes one or more files from the dependency list for
 the given rule. 
@@ -4211,8 +4353,28 @@ of Command Specifications".  An important action of the
 command is run.  In addition, the command after substitution is
 printed to the screen unless \fIlatexmk\fR is running in silent mode.
 
-.PP
+.TP
+.B test_gen_file_time ( <file> )
+This subroutine is used in the context of a rule.  It returns true or
+false according to whether or not a file of the given name both exists
+and was generated in the latest run of the rule.  If the subroutine returns
+false, but the file exists, then the file is a leftover from a previous
+run.
+
+The test for a file being generated on the current run is whether the
+modification time of the file is at least as recent as the time that the
+run of the rule was started.  An allowance for the granularity of the
+values of modification time on file systems is made.  See the description
+of the variable \fB$filetime_causality_threshold\fR for details.
 
+In addition, latexmk makes allowance for the possiblity that files are
+hosted on a different computer than that running latexmk and that the
+system clock times on the two computers are mismatched.  Latexmk
+automatically detects (and reports) any significant mismatch and corrects
+for it.  
+
+
+.PP
 
 .SS Coordinated Setting of Commands for *latex
 
@@ -4276,6 +4438,93 @@ MiKTeX.)
 
 .PP
 
+.SS Hooks
+
+Latexmk provides a way to arrange for user-defined subroutines to be called
+at certain points in the processing.  These can be used to configure
+appropriate behavior and actions beyond latexmk's normal behavior.  For a
+good example of how they can be used to accommodate latexmk's behavior to
+particular packages, see the file memoize_latexmkrc in the example_rcfiles
+subdirectory of the latexmk distribution.  (In a standard TeXLive
+installation, that subdirectory is to be found in
+texmf-dist/doc/support/latexmk/)
+
+The hook mechanism is complementary to the method of redefining command
+strings like \fB$pdflatex\fR etc.  The two methods have overlapping domains
+of usefulness.
+
+Note that the hook mechanism is newly made public in v. 4.84 of latexmk.
+It is subject to change and improvement as experience is gained.
+
+The hooks are arranged in named hook stacks, and a hook subroutine is added
+to a given stack by latexmk's add_hook subroutine (documented above).  The
+currently available stacks are as follows, listed in the approximate order
+in which they are encountered in processing a document:
+
+.TP 2
+  before_xlatex
+  The subroutines in this hook stack are called just before a
+  *latex programs is run.  
+
+.TP 2
+  after_xlatex
+  The subroutines in this hook stack are called after a *latex programs is
+  run.  Before the subroutines are called, latexmk has done some immediate
+  postprocessing, e.g., to move the generated pdf file from the aux
+  directory to the output directory when \fB$emulate_aux\fR is set to 1.
+
+.TP 2
+  after_xlatex_analysis
+  The subroutines in this hook stack are called after latexmk has done its
+  dependency analysis after a *latex programs is run.  Subroutines in this
+  stack provide a useful way of adding items to the dependency information
+  associated with particular packages and that latexmk doesn't
+  automatically deal with.
+
+.TP 2
+  after_main_pdf
+  The subroutines in this hook stack are called after one of the rules that
+  creates the document's pdf file. (This covers any of pdflatex, lualatex,
+  dvipdf, ps2pdf, xdvipdfmx.)
+
+.TP 2
+  cleanup
+  The subroutines in this hook stack are called whenever latexmk is about
+  to do a cleanup operation.  They can be used, for example, to tailor the
+  deleted files to the pecularities of particular packages when latexmk's
+  general mechanisms for specifying files to be deleted are too inflexible. 
+
+  These subroutines are called before latexmk does any of its own file
+  deletion; thus the hook subroutines have access to all the generated
+  files that give package-specific information.
+
+.TP 2
+  cleanup_extra_full
+  The subroutines in this hook stack are called in addition to the ones in
+  the cleanup stack, whenever a full cleanup operation is to be done (i.e.,
+  one that includes the pdf, ps etc files).  They are called immediately
+  after those in the cleanup stack, but still before latexmk does any of
+  its own file deletion.
+
+.PP
+
+(Any other stacks defined in latexmk.pl but not listed above are to be
+regarded as experimental and subject to change.)
+
+Each subroutine should return 0 on success and a non-zero value on failure.
+This matches the convention used for running programs, e.g., by Perl's
+system subroutine, and the matching convention used for subroutines for
+custom dependencies in latexmk. 
+
+For most of the hook stacks, the subroutines are called in the context of a
+rule, with variables like \fB$rule\fR defined.  However, some hook stacks,
+like the cleanup ones, are called from outside any rule; and latexmk
+adjusts the relevant variables to refer to the overall task (i.e., of
+processing a particular main .tex file). 
+
+
+.PP
+
 .SS Advanced configuration: Using \fIlatexmk\fB with \fImake\fR
 
 This section is targeted only at advanced users who use the \fImake\fR
@@ -4469,7 +4718,7 @@ e-mail addresses are not written in their standard form to avoid being
 harvested too easily.)
 .SH AUTHOR
 Current version, by John Collins 
-(Version 4.83).
+(Version 4.85).
 Report bugs etc to his e-mail (jcc8 at psu.edu).
 
 Released version can be obtained from CTAN:
diff --git a/support/latexmk/latexmk.pdf b/support/latexmk/latexmk.pdf
index 19f863e8c7..593652f209 100644
--- a/support/latexmk/latexmk.pdf
+++ b/support/latexmk/latexmk.pdf
diff --git a/support/latexmk/latexmk.pl b/support/latexmk/latexmk.pl
index 44ee6a05a7..4e7b8a9d55 100755
--- a/support/latexmk/latexmk.pl
+++ b/support/latexmk/latexmk.pl
@@ -47,8 +47,8 @@ BEGIN {
     # blocks.
     $my_name = 'latexmk';
     $My_name = 'Latexmk';
-    $version_num = '4.83';
-    $version_details = "$My_name, John Collins, 31 Jan. 2024. Version $version_num";
+    $version_num = '4.85';
+    $version_details = "$My_name, John Collins, 7 Apr. 2024. Version $version_num";
 }
 
 use Config;
@@ -365,7 +365,8 @@ our @latex_file_hooks = ();
 #
 # Single hash for various stacks of hooks:
 our %hooks = ();
-for ( 'before_xlatex', 'after_xlatex', 'after_xlatex_analysis' ) {
+for ( 'before_xlatex', 'after_xlatex', 'after_xlatex_analysis', 'after_main_pdf',
+      'cleanup', 'cleanup_extra_full' ) {
     $hooks{$_} = [];
 }
 $hooks{aux_hooks} = \@aux_hooks;
@@ -415,7 +416,11 @@ our $lualatex_silent_switch  = '-interaction=batchmode';
 our $xelatex_silent_switch  = '-interaction=batchmode';
 
 # Whether to emulate -aux-directory, so we can use it on system(s) (TeXLive)
-# that don't support it:
+# that don't support it.
+# Possible values: 0: I don't do any emulation, and use -aux-directory &
+#                       -out-directory options to *latex.
+#                  1: Emulate MiKTeX behavior: Use -output-directory=<aux dir>
+#                       in call to *latex.  Then move pdf (etc) files after run.
 our $emulate_aux = 1;
 # Whether emulate_aux had to be switched on during a run:
 our $emulate_aux_switched = 0;
@@ -740,10 +745,6 @@ our ( $pdf_previewer, $ps_previewer, $ps_previewer_landscape, $dvi_previewer,
       $dvi_previewer_landscape, $hnt_previewer );
 $pdf_previewer = $ps_previewer  = $ps_previewer_landscape  = $dvi_previewer  = $dvi_previewer_landscape = $hnt_previewer = "NONE";
 
-# The following variables are assigned once and then used in symbolic 
-#     references, so we need to avoid warnings 'name used only once':
-our ( $aux_dir_requested, $out_dir_requested );
-
 our $dvi_update_signal = undef;
 our $ps_update_signal = undef;
 our $pdf_update_signal = undef;
@@ -767,6 +768,11 @@ our $hnt_update_method = 1;
 our $ps_update_method = 1;
 our $pdf_update_method = 1;
 
+# Whether to allow latexmk to create subdirectories of aux_dir when there's
+#  a report in the log file that *latex "can't write on file ...".
+#  Values: 0: no subdir creation,
+#          1: only for aux files (occurs with \include{chapters/chap} etc
+#          2: generally
 our $allow_subdir_creation = 1;
 
 our $new_viewer_always = 0;     # If 1, always open a new viewer in pvc mode.
@@ -1259,7 +1265,7 @@ our $texfile_search = "";   # Specification for extra files to search for
                         # This variable is obsolete, and only in here for
                         # backward compatibility.
 
-our $jobname = '';          # Jobname: as with current tex, etc indicates
+our $jobname = '';      # Jobname: as with current tex, etc indicates
                         # basename of generated files.  Defined so
                         # that --jobname=STRING on latexmk's command
                         # line has same effect as with current tex,
@@ -1272,6 +1278,7 @@ our $jobname = '';          # Jobname: as with current tex, etc indicates
                         # dependent on name of main TeX file; this is
                         # useful when a jobname is used and latexmk is
                         # invoked on multiple files.
+our $out2_dir = '';     # Directory for final output files.  
 our $out_dir = '';      # Directory for output files.  
                         # Cf. --output-directory of current *latex
                         # Blank means default, i.e., cwd.
@@ -1283,6 +1290,17 @@ our $aux_dir = '';      # Directory for aux files (log, aux, etc).
 # Corresponding forms that can be concatenated (e.g., when $aux_dir is '.', $aux_dir1 is './').
 our $aux_dir1 = '';
 our $out_dir1 = '';
+our $out2_dir1 = '';
+
+# Use the following for saving original values, before directories are normalized.
+our ( $aux_dir_requested, $out_dir_requested, $out2_dir_requested );
+
+
+
+# Extensions for files to be copied to $out2_dir.
+# Specify as for @generated_exts: I.e., extension w/o period
+#  or string including %R to be substituted by basename.
+our @out2_exts = ( 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz' );
 
 ## default flag settings.
 our $recorder = 1;          # Whether to use recorder option on latex/pdflatex
@@ -1641,6 +1659,7 @@ our %rule_db = ();  # Database of all rules:
                     #       %R for base of primary tex file, %T for
                     #       texfile name, %O for options,
                     #       %V=$aux_dir, %W=$out_dir,
+                    #       %X for $out2_dir1
                     #       %Y for $aux_dir1, and %Z for $out_dir1
                     #     int_cmd specifies any internal command to be
                     #       used to implement the application of the
@@ -1865,7 +1884,7 @@ our ($rule, $PA_extra_gen, $PAint_cmd, $PArule_data, $Pbase, $Pchanged,
      $Plast_message, $Plast_result, $Plast_result_info, 
      $Pno_history, $Pout_of_date, $Pout_of_date_user, $Prun_time, $Psource,
      $file, $PAfile_data, $Ptime, $Psize, $Pmd5, $DUMMY, $Pcorrect_after_primary
-);
+    );
            
 # User's home directory
 our $HOME = '';
@@ -1970,8 +1989,6 @@ if ( $auto_rc_use ) {
     read_first_rc_file_in_list( ".latexmkrc", "latexmkrc" );
 }
 
-
-
 ## Process command line args.
 our @command_line_file_list = ();
 our $bad_options = 0;
@@ -2108,6 +2125,9 @@ while (defined(local $_ = $ARGV[0])) {
   elsif ( /^-output-directory=(.*)$/ ||/^-outdir=(.*)$/ ) {
       $out_dir = $1;
   }
+  elsif ( /^-out2dir=(.*)$/ ) {
+      $out2_dir = $1;
+  }
   elsif ( /^-output-format=(.*)$/ ) {
       my $format = $1;
       if ($format eq 'dvi' ) {
@@ -2330,20 +2350,25 @@ print "$My_name: This is $version_details.\n",
 
 &config_to_mine;
 
+# Save original values for use in diagnositics.
+# We may change $aux_dir and $out_dir after a detection
+#  of results of misconfiguration.
+$aux_dir_requested = $aux_dir;
+$out_dir_requested = $out_dir;
+$out2_dir_requested = $out2_dir;
+
 if ($out_dir eq '' ){
     # Default to cwd
     $out_dir = '.';
 }
+if ($out2_dir eq '' ){
+    # Default to cwd
+    $out2_dir = $out_dir;
+}
 if ( $aux_dir eq '' ){
     # Default to out_dir
-    #  ?? This is different than MiKTeX
     $aux_dir = $out_dir;
 }
-# Save original values for use in diagnositics.
-# We may change $aux_dir and $out_dir after a detection
-#  of results of misconfiguration.
-$aux_dir_requested = $aux_dir;
-$out_dir_requested = $out_dir;
 
 if ($bibtex_use > 1) {
     push @generated_exts, 'bbl';
@@ -2742,10 +2767,18 @@ our ( @default_includes, $texfile_name, $root_filename, $log_name,
       $dvi_name, $dviF_name, $hnt_name, $ps_name, $psF_name, $pdf_name,
       $xdv_name, 
       $dvi_final, $hnt_final, $ps_final, $pdf_final, $xdv_final,
+      $dvi_final2, $hnt_final2, $ps_final2, $pdf_final2,
       $view_file,
       %rule_list,
       $missing_dvi_pdf, $switched_primary_output
-);
+    );
+# Defaults for when rule-using subroutines are used outside a rule:
+$rule = '';
+$Pbase = \$root_filename;
+$Psource = \$texfile_name;
+my $start_time = time();
+$Prun_time = \$start_time;
+
 FILE:
 foreach $filename ( @file_list )
 {
@@ -2776,6 +2809,7 @@ foreach $filename ( @file_list )
     #   Use of $do_cd, which can affect how $aux_dir and $out_dir get normalized.
     local $aux_dir = $aux_dir;
     local $out_dir = $out_dir;
+    local $out2_dir = $out2_dir;
 
     local $dvilualatex = $dvilualatex;
     local $hilatex = $hilatex;
@@ -3249,25 +3283,32 @@ sub normalize_aux_out_ETC {
     # Ensure the output/auxiliary directories exist, if need be, **with error checking**.
     my $ret1 = 0;
     my $ret2 = 0;
+    my $ret3 = 0;
     eval {
         if ( $out_dir ) {
             $ret1 = make_path_mod( $out_dir,  'output' );
         }
+        if ( $out2_dir ) {
+            $ret2 = make_path_mod( $out2_dir,  'final output' );
+        }
         if ( $aux_dir && ($aux_dir ne $out_dir) ) {
-            $ret2 = make_path_mod( $aux_dir,  'auxiliary' );
+            $ret3 = make_path_mod( $aux_dir,  'auxiliary' );
         }
     };
-    if ($ret1 || $ret2 || $@ ) {
+    if ($ret1 || $ret2 || $ret3 || $@ ) {
         if ($@) { print "Error message:\n  $@"; }
         die "$My_name: Since there was trouble making the output (and aux) dirs, I'll stop\n"
     }
 
     if ($normalize_names) {
-        foreach ( $aux_dir, $out_dir ) { $_ = normalize_filename_abs($_); }
+        foreach ( $aux_dir, $out_dir, $out2_dir ) {
+            $_ = normalize_filename_abs($_);
+        }
     }
     $aux_dir1 = $aux_dir;
     $out_dir1 = $out_dir;
-    foreach ( $aux_dir1, $out_dir1 ) {
+    $out2_dir1 = $out2_dir;
+    foreach ( $aux_dir1, $out_dir1, $out2_dir1 ) {
         if ($_ eq '.') {$_ = '';}
         if ( ($_ ne '')  && ! m([\\/\:]$) ) {
             # Add a trailing '/' if necessary to give a string that can be
@@ -3317,8 +3358,9 @@ sub normalize_aux_out_ETC {
     
     if ($diagnostics || $aux_out_dir_report ) {
         print "$My_name: Cwd: '", good_cwd(), "'\n";
-        print "$My_name: Normalized aux dir and out dir: '$aux_dir', '$out_dir'\n";
-        print "$My_name: and combining forms: '$aux_dir1', '$out_dir1'\n";
+        print "$My_name: Normalized aux dir and out dirs:\n",
+              " '$aux_dir', '$out_dir', '$out2_dir'\n";
+        print "$My_name: and combining forms:\n '$aux_dir1', '$out_dir1', '$out2_dir1'\n";
         if ($aux_out_dir_report == 2) {
             exit 0;
         }
@@ -3449,6 +3491,7 @@ sub rdb_initialize_rules {
         # until run time, in case of changes.
         foreach ($base, $source, $dest, @$PA_extra_gen, @$PA_extra_source ) {
             s/%R/$root_filename/g;
+            s/%X/$out2_dir1/;
             s/%Y/$aux_dir1/;
             s/%Z/$out_dir1/;
         }
@@ -3504,21 +3547,22 @@ sub rdb_set_rule_templates {
 # Set up specifications for standard rules, adjusted to current conditions
 # Substitutions: %S = source, %D = dest, %B = this rule's base
 #                %T = texfile, %R = root = base for latex.
+#                %X for $out2_dir1, 
 #                %Y for $aux_dir1, %Z for $out_dir1
 
 
     my $print_file = '';
     my $print_cmd = 'NONE';
     if ( $print_type eq 'dvi' ) {
-        $print_file = $dvi_final;
+        $print_file = $dvi_final2;
         $print_cmd = $lpr_dvi;
     }
     elsif ( $print_type eq 'pdf' ) {
-        $print_file = $pdf_final;
+        $print_file = $pdf_final2;
         $print_cmd = $lpr_pdf;
     }
     elsif ( $print_type eq 'ps' ) {
-        $print_file = $ps_final;
+        $print_file = $ps_final2;
         $print_cmd = $lpr;
     }
     elsif ( $print_type eq 'none' ) {
@@ -3533,7 +3577,7 @@ sub rdb_set_rule_templates {
 
     if ( ($view eq 'dvi') || ($view eq 'hnt') || ($view eq 'pdf') || ($view eq 'ps') ) {
         no strict "refs";
-        $view_file = ${$view.'_final'};
+        $view_file = ${$view.'_final2'};
         $viewer = ${$view.'_previewer'};
         $viewer_update_method = ${$view.'_update_method'};
         $viewer_update_signal = ${$view.'_update_signal'};
@@ -3544,6 +3588,8 @@ sub rdb_set_rule_templates {
     # Specification of internal command for viewer update:
     my $PA_update = ['do_update_view', $viewer_update_method, $viewer_update_signal, 0, 1];
 
+    # Base name is to be without path for *latex-type rules
+    # With path for others.
     %rule_list = (
         'dvilualatex'  => [ 'primary',  "$dvilualatex",  '',      "%T",        $dvi_name,  "%R",   1, [$aux_main, $log_name], [$aux_main] ],
         'hilatex'   => [ 'primary',  "$hilatex",     '',          "%T",        $hnt_name,  "%R",   1, [$aux_main, $log_name], [$aux_main] ],
@@ -3551,12 +3597,14 @@ sub rdb_set_rule_templates {
         'lualatex'  => [ 'primary',  "$lualatex",  '',            "%T",        $pdf_name,  "%R",   1, [$aux_main, $log_name], [$aux_main] ],
         'pdflatex'  => [ 'primary',  "$pdflatex",  '',            "%T",        $pdf_name,  "%R",   1, [$aux_main, $log_name], [$aux_main] ],
         'xelatex'   => [ 'primary',  "$xelatex",   '',            "%T",        $xdv_name,  "%R",   1, [$aux_main, $log_name], [$aux_main] ],
+
         'dvipdf'    => [ 'external', "$dvipdf",    'do_viewfile', $dvi_final,  $pdf_name,  "%Z%R", 1 ],
         'xdvipdfmx' => [ 'external', "$xdvipdfmx", 'do_viewfile', $xdv_final,  $pdf_name,  "%Z%R", 1 ],
         'dvips'     => [ 'external', "$dvips",     'do_viewfile', $dvi_final,  $ps_name,   "%Z%R", 1 ],
         'dvifilter' => [ 'external', $dvi_filter,  'do_viewfile', $dvi_name,   $dviF_name, "%Z%R", 1 ],
         'ps2pdf'    => [ 'external', "$ps2pdf",    'do_viewfile', $ps_final,   $pdf_name,  "%Z%R", 1 ],
         'psfilter'  => [ 'external', $ps_filter,   'do_viewfile', $ps_name,    $psF_name,  "%Z%R", 1 ],
+
         'print'     => [ 'external', "$print_cmd", 'if_source',   $print_file, "",         "",     1 ],
         'update_view' => [ 'external', $viewer_update_command, $PA_update,
                                $view_file,  "",        "",   2 ],
@@ -3763,7 +3811,12 @@ sub set_trivial_aux_fdb {
     # 2. Write a corresponding fdb file
     # 3. Provoke a run of *latex (actually of all primaries). 
 
-    open( my $aux_file, '>', $aux_main )
+    # Use raw mode for writing aux file, so that line endings are \n.
+    # Otherwise on Windows, the aux file file will have \r\n line endings.
+    # Since both TeXLive and MiKTeX write \n rather than \r\n, latexmk will
+    # unnecessarily detect a change in the aux file because of the changed
+    # line endings, and thereby provoke a superfluous extra *latex run.
+    open( my $aux_file, '> :raw', $aux_main )
         or die "Cannot write file '$aux_main'\n";
     fprint8( $aux_file, "\\relax \n" );
     # The following is added by recent versions of latex for a
@@ -3788,8 +3841,9 @@ sub do_cleanup {
     my $kind = $_[0];
     if (! $kind ) { return; }
     my @files_to_delete = ();
-    my @dirs = ($aux_dir1);
-    if ($out_dir1 ne $aux_dir1) { push @dirs, $out_dir1; }
+    my %dirs = ();
+    foreach ($aux_dir1, $out_dir1, $out2_dir1) { $dirs{$_} = 1; }
+    my @dirs = keys %dirs;
 
     push @files_to_delete, &get_small_cleanup;
     if ($kind == 1) {
@@ -3797,19 +3851,25 @@ sub do_cleanup {
             push @files_to_delete, cleanup_get1( $dir1, @final_output_exts );
         }
     }
-    # show_array( "Files to delete", sort @files_to_delete );
 
-    # Names of contents of directory are longer than the name of the directory,
-    # but contain the directory name as an initial segment.
-    # Therefore deleting files and directories in the order given by reverse
-    # sort deletes contents of directory before attempting to delete the
-    # directory:
+    # Run the hooks first, since to determine what custom deletions they
+    #   are to make, the hook subroutines may need access to files that
+    #   cleanup later deletes (log, aux, ...). 
+    run_hooks( 'cleanup' );
+    if ($kind == 1) { run_hooks( 'cleanup_extra_full' ); }
+    
+    # Names of contents of directory are longer than the name of the
+    #   directory, but contain the directory name as an initial segment.
+    #   Therefore deleting files and directories in the order given by
+    #   reverse sort deletes contents of directory before attempting to
+    #   delete the directory:
     unlink_or_move( reverse sort @files_to_delete );
     
-    # If the fdb file (or log, fls and/or aux files) exist, it/they will have
-    #   been used to make a changed rule database.  But a cleanup implies
-    #   that we need a virgin rule database, corresponding to current state
-    #    of files (after cleanup) so we reset the rule database and rule net:
+    # If the fdb file (or log, fls and/or aux files) exist, it/they will
+    #   have been used to make a changed rule database.  But a cleanup
+    #   implies that we need a virgin rule database, corresponding to
+    #   current state of files (after cleanup) so we reset the rule
+    #   database and rule net: 
     &rdb_initialize_rules;
 }
 
@@ -4760,6 +4820,8 @@ sub print_help
   "   -norc          - omit automatic reading of system, user and project rc files\n",
   "   -output-directory=dir or -outdir=dir\n",
   "                  - set name of directory for output files\n",
+  "   -out2dir=dir\n",
+  "                  - set name of directory for final output files\n",
   "   -output-format=FORMAT\n",
   "                  - if FORMAT is dvi, turn on dvi output, turn off others\n",
   "                  - if FORMAT is pdf, turn on pdf output, turn off others\n",
@@ -5423,6 +5485,10 @@ sub set_names {
     $ps_name   = "%Z%R.ps";
     $psF_name  = "%Z%R.psF";
     $pdf_name  = "%Z%R.pdf";
+    $dvi_final2 = "%X%R.pdf";
+    $hnt_final2 = "%X%R.pdf";
+    $pdf_final2 = "%X%R.pdf";
+    $ps_final2 = "%X%R.pdf";
     ## It would be logical for a .xdv file to be put in the out_dir,
     ## just like a .dvi file.  But the only program, MiKTeX, that
     ## currently implements aux_dir, and hence allows aux_dir ne out_dir,
@@ -5430,8 +5496,12 @@ sub set_names {
     $xdv_name   = "%Y%R.xdv";
 
     foreach ( $aux_main, $log_name, $fdb_name, $fls_name, $fls_name_alt,
-              $dvi_name, $hnt_name, $ps_name, $pdf_name, $xdv_name, $dviF_name, $psF_name ) {
+              $dvi_name, $hnt_name, $ps_name, $pdf_name, $xdv_name,
+              $dviF_name, $psF_name,
+              $dvi_final2, $hnt_final2, $pdf_final2, $ps_final2,
+        ) {
         s/%R/$root_filename/g;
+        s/%X/$out2_dir1/;
         s/%Y/$aux_dir1/;
         s/%Z/$out_dir1/;
     }
@@ -5452,6 +5522,95 @@ sub set_names {
 
 #**************************************************
 
+sub do_moves_aux_to_out {
+    # do_moves_aux_to_out( source, dest )
+    # Moves appropriate output files from source dir (e.g., $aux_dir1) to
+    # dest dir (e.g., $out_dir1).
+    # Veto move of file if it wasn't generated on current compilation.
+    # Special treatment of .fls file
+    # Assume rule context, which may be global context.
+    # Directory names should end in /, so that concatenation OK.
+    my ($source1, $dest1) = @_;
+    foreach my $ext ( 'fls', 'dvi', 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz' ) {
+        if ( ($ext eq 'fls') && ! $fls_uses_out_dir ) {next;}
+        my $from =  "$source1$$Pbase.$ext";
+        my $to = "$dest1$$Pbase.$ext" ;
+        if ( test_gen_file_time( $from ) ) {
+            if (! $silent) { print "$My_name: Moving '$from' to '$to'\n"; }
+            my $ret = move( $from, $to );
+            if ( ! $ret ) { die "  That failed, with message '$!'\n";}
+        }
+    }
+} #END do_moves_aux_to_out
+
+#*************************************************************************
+
+sub do_copies_out_to_out2 {
+    # do_copies_out_to_out2( source, dest )
+    # Copies final output files from source dir (e.g., $out_dir1) to
+    # dest dir (e.g., $out2_dir1).
+    # Note copy, not move, otherwise rules complain about non-existent
+    #   destination pdf file (etc). 
+    # Assume rule context, which is normally global context.
+    # Directory names should end in /, so that concatenation OK.
+    my ($source1, $dest1) = @_;
+
+    # Ideally, guard against source and destination being same.
+    # Easy case:
+    my $absSource = abs_path($source1);
+    my $absDest = abs_path($dest1);
+    if ( defined($absSource) && defined($absDest) && ($absSource eq $absDest) ) {
+        # Directories are same.  Nothing to do.
+        # Note that abs_path can return undef under certain error conditions.
+        # I'll leave the diagnosis to the copy subroutine.
+        return;
+    }
+    # !!! HOWEVER: !!
+    # There can be multiple ways of referring to the same directories
+    # without that being detectable by the use of abs_path
+    # on the names: E.g., on Windows one directory is referred to via a
+    # drive letter that is used for files on a server, and the second
+    # uses the '\\...' (or '//...'construction to refer to the server directly.
+    # Also, on a OS/FS combination that is insensitive to case, the
+    # abs_paths can differ in case while referring to the same entity
+    # On UNIX, I can use a dev and inode test for equality, from the
+    # results of stat.
+    # But that doesn't work on Windows (where the inode numbers
+    # returned by stat are always zero).
+    # Easiest is to let the copy subroutine do the work, and just
+    # diagnose the situation when it fails 
+    
+    say "$My_name: Copying final output files from '$source1' to '$dest1'";
+
+    foreach ( @out2_exts ) {
+        my $name = ( /%R/ ? $_ : "%R.$_" );
+        $name =~ s/%R/$$Pbase/;
+        my $from =  "$source1$name";
+        my $to = "$dest1$name";
+        if ( test_gen_file_time( $from ) ) {
+            if (! $silent) { print "$My_name: Copying '$from' to '$to'\n"; }
+            # Work around problem that if $from and $to refer to the same
+            # file, then copy returns zero, for error, but does **not** set
+            # $!.  (This is surely a bug, since copy (i.e.,
+            # File::Copy::copy) is documented to set $! when it encounters
+            # an error.) So in this situation $! contains whatever error
+            # code was set by something else earlier.
+            # I'll reset $! to 0 here, which corresponds to no error.
+            # If after running copy, it's still zero, but copy reports
+            # failure, then that indicates that $from and $to are the same
+            # file, and we didn't actually need a copy; for latexmk it's a
+            # non-error.
+            local $! = 0;
+            my $ret = copy( $from, $to );
+            if ( $ret ) { } # Success
+            elsif ($!) { warn "$My_name: Failure of copy from '$from' to '$to', error =\n $!\n"; }
+            else { }  # Non-error.
+        }
+    }
+} #END do_copies_out_to_out2
+
+#*************************************************************************
+
 sub correct_locations {
     # Deal with situations after a *latex run where files are in different
     # directories than expected (specifically aux v. output directory).
@@ -5467,26 +5626,15 @@ sub correct_locations {
     # Assumes rule context.
     
     my $where_log = &find_set_log;
-    if ( $emulate_aux && ($aux_dir ne $out_dir) ) {
-        # Move output files from aux_dir to out_dir
-        # Move fls file also, if the configuration is for fls in out_dir.
-        # Omit 'xdv', that goes to aux_dir (as with MiKTeX). It's not final output.
-        foreach my $ext ( 'fls', 'dvi', 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz' ) {
-            if ( ($ext eq 'fls') && ! $fls_uses_out_dir ) {next;}
-            my $from =  "$aux_dir1$$Pbase.$ext";
-            my $to = "$out_dir1$$Pbase.$ext" ;
-            if ( test_gen_file_time( $from ) ) {
-                if (! $silent) { print "$My_name: Moving '$from' to '$to'\n"; }
-                my $ret = move( $from, $to );
-                if ( ! $ret ) { die "  That failed, with message '$!'\n";}
-            }
-        }
+
+    if ( ($aux_dir_requested ne '') && $emulate_aux && ($aux_dir ne $out_dir) ) {
+        do_moves_aux_to_out( $aux_dir1, $out_dir1 );
     }
 
     # Fix ups on fls file:
     if ($recorder) {
         # Deal with following special cases:
-        #   1. Some implemenations of *latex give fls files of name latex.fls
+        #   1. Some implementations of *latex give fls files of name latex.fls
         #      or pdflatex.fls instead of $$Pbase.fls.
         #   2. In some implementations, the writing of the fls file (memory
         #      of old implementations) may not respect the -output-directory
@@ -6018,8 +6166,9 @@ LINE:
                 $idx_file = $1;                
             }
             else {
-                warn "$My_name: Message indicates index file was written\n",
-                     "  ==> but I do not know how to understand it: <==\n",
+                warn "$My_name: A message suggests an index file may have been written\n",
+                    "  but it is not of a form I understand. This is probably innocuous.\n",
+                    "  The message is\n",
                      "  '$_'\n";
                 next LINE;
             }
@@ -6117,7 +6266,9 @@ LINE:
             my $dir = $1;
             my $file = $2;
             my $full_dir = $aux_dir1.$dir;
-            if ( ($aux_dir ne '') && (! -e $full_dir) && ( $file =~ /\.aux$/) ) {
+            if ( ($aux_dir ne '') && (! -e $full_dir)
+                 && ( ($file =~ /\.aux$/) || ($allow_subdir_creation == 2) )
+               ) {
                 warn "$My_name: === There were problems writing to '$file' in '$full_dir'\n",
                      "    I'll try to make the subdirectory later.\n"
                   if $diagnostics;
@@ -6126,9 +6277,9 @@ LINE:
             else {
                 warn "$My_name: ====== There were problems writing to",
                      "----- '$file' in '$full_dir'.\n",
-                     "----- But this is not the standard situation of\n",
-                     "----- aux file to subdir of output directory, with\n",
-                     "----- non-existent subdir\n",
+                     "----- But this is not the standard situation of file to subdir of output\n",
+                     "----- directory, with non-existent subdir, and either file is aux file or\n",
+                     "----- or \$allow_subdir_creation is set to 2.\n";
             }
         }
 
@@ -7631,6 +7782,7 @@ LINE:
     }
     close $in_handle;
     # Get state of dependencies, including creating cus deps if needed
+    # !!!??? This doesn't match definition of rdb_set_dependents
     &rdb_set_dependents( keys %rule_db );
     &rdb_set_rule_net;
 
@@ -8088,6 +8240,12 @@ sub rdb_set_latex_deps {
         }
     }
 
+    foreach my $file ( keys %generated_fls ) {
+        if ( $file =~ /^(.*)\.idx$/ ) {
+            $idx_files{$file} = [ "$1.ind", $1 ];
+            print "Have index file '$file', @{$idx_files{$file}}\n";
+        }
+    }
   IDX_FILE:
     foreach my $idx_file ( keys %idx_files ) {
         my ($ind_file, $ind_base) = @{$idx_files{$idx_file}};
@@ -8310,7 +8468,7 @@ NEW_SOURCE:
 
     my @more_sources = &rdb_set_dependents( $rule );
     my $num_new = $#more_sources + 1;
-    foreach (@more_sources) { 
+    foreach (@more_sources) {
         $dependents{$_} = 4;
         if ( ! -e $_ ) { 
             # Failure was non-existence of makable file
@@ -8572,7 +8730,8 @@ sub rdb_find_source_file {
     }
     if ( exists $ENV{TEXINPUTS} ) {
         foreach my $searchpath (split $search_path_separator, $ENV{TEXINPUTS}) {
-            my $file = catfile($searchpath,$_[0]);
+            my $file = catfileA($searchpath,$_[0]);
+            if ( $file =~ /\\/ ) { print "====== '$file'\n"; die; }
             my $test = "$file.$_[1]";
             if ( -e $test ) {
                 return $file;
@@ -8589,7 +8748,7 @@ sub rdb_one_dep {
     # Assume file (and rule) context for DESTINATION file.
 
     # Only look for dependency if $rule is primary rule (i.e., latex
-    # or pdflatex) or is a custom dependency:
+    # or pdflatex) or is a custom dependency:  ???WHY???!!!
     if ( (! exists $possible_primaries{$rule}) && ($rule !~ /^cusdep/) ) {
         return;
     }
@@ -8660,7 +8819,7 @@ DEP:
                 && (! -e $file ) 
                 && (! -e "$base_name.$proptoext" ) 
                 && exists $$Pinput_extensions{$proptoext}
-              ) {
+            ) {
             # Empty extension and non-existent destination
             #   This normally results from  \includegraphics{A}
             #    without graphics extension for file, when file does
@@ -9236,8 +9395,11 @@ sub rdb_make {
                       }
                     ); 
     }
-
     rdb_for_some( [@unusual_one_time], \&rdb_make1 );
+    if ( ($out2_dir_requested ne '') && ($out_dir ne $out2_dir) ) {
+        do_copies_out_to_out2( $out_dir1, $out2_dir1 );
+    }
+    
 
     #---------------------------------------
     # All of make done. Finish book-keeping:
@@ -9632,7 +9794,13 @@ sub rdb_run1 {
     else {
         # No special analysis for other rules
     }
-
+    if ($$Pdest eq $pdf_final) {
+        if ( run_hooks( 'after_main_pdf' ) ) {
+            warn "$My_name: ======Some hook failed.\n";
+            $return = -1;
+        }
+    }
+    
     # General
     $updated = 1;
     if ( ($$Plast_result == 0) && ($return != 0) && ($return != -2) ) {
@@ -10572,6 +10740,7 @@ sub rdb_create_rule {
     foreach ( $PAextra_gen, $PAextra_source ) {
         if (! defined $_) { $_ = []; }
     }
+    
     my $last_result = -1;
     my $last_result_info = '';
     my $no_history = ($run_time <= 0);
@@ -11505,6 +11674,7 @@ sub add_hook {
         warn "In add_hook, request to add hook to non-existent stack '$stack'.\n";
         return 0;
     }
+    print "============== ADDING HOOK to $stack\n";
 
     my $ref;
     if ( ref $routine ) {
@@ -11530,22 +11700,35 @@ sub run_hooks {
     #   a. If arguments follow the stackname in the call to run_hooks, these
     #      are given to the called subroutines.
     #   b. Otherwise a hash of information is given to the called subroutines.
-    # Return 1 for success, 0 for failure.        
+    # Each has a return value, which like from system, is 0 for success. 
+    # Return 0 for success, non-zero for failure.   
     my $name = shift;
     my $Pstack = $hooks{$name};
     my @args = @_;
     if (!@args) { @args = &info_make; }
     else { print "Have args\n"; }
-    if (defined $Pstack) {
+
+    if ( ! defined $Pstack ) {
+        warn "run_hooks: No stack named '$name'\n";
+        # But I'll not treat this as an error.  Is that appropriate?
+        return 0;
+    }
+    elsif (! @$Pstack) {
+            # Nothing to do
+            return 0;
+    }
+    else {
+        print "$My_name: Running hooks in stack $name\n";
+        my $fail = 0;
         # Do NOT use default $_, as in "for (...) {...}":
         # The called subroutine may change $_, which is a global variable
         # (although localized to the for loop and called subroutines).
-        for my $Psub ( @$Pstack) { &$Psub(@args); }
-        return 1;
-    }
-    else {
-        warn "run_hooks: No stack named '$name'\n";
-        return 0;
+        for my $Psub ( @$Pstack) {
+            if ( &$Psub(@args) ) {
+                $fail = 1;
+            }
+        }
+        return $fail;
     }
 }
 
@@ -11723,6 +11906,15 @@ sub ext_no_period {
 
 #************************************************************
 
+sub catfileA {
+    # Like catfile, but change \ to / in result.
+    my $file = catfile(@_);
+    $file =~ s[\\][/]g;
+    return $file;
+}
+
+#************************************************************
+
 sub fileparseA {
     # Like fileparse but replace $path for current dir ('./' or '.\') by ''
     # Also default second argument to get normal extension.
@@ -12300,7 +12492,7 @@ sub config_to_mine {
     # -outdir=... option, are already in the system CS, because that is
     # how strings are passed on  the command line.
     # So we just need to do a conversion for strings with utf8 flag on:
-    foreach ( $out_dir, $aux_dir, @default_files, @default_excluded_files ) {
+    foreach ( $out_dir, $out2_dir, $aux_dir, @default_files, @default_excluded_files ) {
         if (utf8::is_utf8($_)) { $_ = encode( $CS_system, $_ ); }
     }
 } #END config_to_mine
diff --git a/support/latexmk/latexmk.txt b/support/latexmk/latexmk.txt
index 462e9a80da..7360edad9b 100644
--- a/support/latexmk/latexmk.txt
+++ b/support/latexmk/latexmk.txt
@@ -61,7 +61,7 @@ DESCRIPTION
 
 
 
-                                31 January 2024                              1
+                                 7 April 2024                                1
 
 
 
@@ -127,7 +127,7 @@ LATEXMK OPTIONS AND ARGUMENTS ON COMMAND LINE
 
 
 
-                                31 January 2024                              2
+                                 7 April 2024                                2
 
 
 
@@ -193,7 +193,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                              3
+                                 7 April 2024                                3
 
 
 
@@ -207,7 +207,8 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               .log  etc).   These are all the generated files, with the excep-
               tion of final output files (.dvi, .ps, .pdf, .synctex.gz, .sync-
               tex).  See the -outdir/-output-directory option for  directories
-              for the final output files.
+              for the main output files, and the -out2dir option for the final
+              output files.
 
               If the directory specified for the -aux/-aux-directory option is
               blank,  then the default is used, which is to be the same as the
@@ -258,8 +259,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-
-                                31 January 2024                              4
+                                 7 April 2024                                4
 
 
 
@@ -325,7 +325,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                              5
+                                 7 April 2024                                5
 
 
 
@@ -391,7 +391,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                              6
+                                 7 April 2024                                6
 
 
 
@@ -457,7 +457,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                              7
+                                 7 April 2024                                7
 
 
 
@@ -523,7 +523,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                              8
+                                 7 April 2024                                8
 
 
 
@@ -589,7 +589,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                              9
+                                 7 April 2024                                9
 
 
 
@@ -655,7 +655,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                             10
+                                 7 April 2024                               10
 
 
 
@@ -721,7 +721,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                             11
+                                 7 April 2024                               11
 
 
 
@@ -787,7 +787,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                             12
+                                 7 April 2024                               12
 
 
 
@@ -853,7 +853,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                             13
+                                 7 April 2024                               13
 
 
 
@@ -919,7 +919,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                             14
+                                 7 April 2024                               14
 
 
 
@@ -985,7 +985,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                             15
+                                 7 April 2024                               15
 
 
 
@@ -1001,44 +1001,81 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               directory.
 
               If the aux directory is set, e.g., by the option -auxdir, and is
-              not  equal to the output directory, then only final output files
-              (.dvi, .ps, .pdf, .synctex, .synctex.gz) are sent to the  output
-              directory. Other generated files are sent to the aux directory.
+              not  equal to the output directory, then only the primary output
+              files (.dvi, .ps, .pdf, .synctex, .synctex.gz) are sent  to  the
+              output  directory. Other generated files are sent to the aux di-
+              rectory.
 
-              See  the  section  AUXILIARY AND OUTPUT DIRECTORIES for more de-
+              See the section AUXILIARY AND OUTPUT DIRECTORIES  for  more  de-
               tails.
 
 
+       -out2dir=FOO
+
+              (Experimental new feature.)
+
+              Sets  the  directory for the final output files of a whole round
+              of compilations.
+
+              The use of this directory solves, among other things, the  prob-
+              lem  that  when  multiple  runs of *latex and other programs are
+              needed, files like the main pdf file from pdflatex, etc will  be
+              changed  multiple  times.  A viewer like SumatraPDF that reloads
+              the file whenever it detects changes will show a distracting se-
+              quence of intermediate states of the pdf file, rather than  just
+              the final version after all the repeated runs of *latex etc have
+              been  done.   Instead, when a distinct final-output directory is
+              set, by the -out2dir option or the equivalent $out2_dir variable
+              is set, the viewer will only see a changed pdf (etc) file  after
+              full sequence of repeated runs of *latex etc has finished.
+
+              By  default the final output directory is the same as the output
+              directory (as specified by the -outdir option or the setting  of
+              the variable $out_dir configuration variable).
+
+
+
        -output-format=FORMAT
-              This option is one that is  allowed  for  latex,  lualatex,  and
-              pdflatex.  But  it is not passed to these programs.  Instead la-
-              texmk emulates it in a way suitable for the context  of  latexmk
+              This  option  is  one  that  is allowed for latex, lualatex, and
+              pdflatex. But it is not passed to these programs.   Instead  la-
+              texmk  emulates  it in a way suitable for the context of latexmk
               and its workflows.
 
-              If  FORMAT  is dvi, then dvi output is turned on, and postscript
-              and pdf output are turned off. This is equivalent to  using  the
+              If FORMAT is dvi, then dvi output is turned on,  and  postscript
+              and  pdf  output are turned off. This is equivalent to using the
               options -dvi -ps- -pdf-.
 
-              If  FORMAT  is  pdf,  then  pdf output is turned on, and dvi and
-              postscript output are turned off. This is  equivalent  to  using
+              If FORMAT is pdf, then pdf output is  turned  on,  and  dvi  and
+              postscript  output  are  turned off. This is equivalent to using
               the options -pdf -ps- -dvi-.
 
+
+
+                                 7 April 2024                               16
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
               If FORMAT is anything else, latexmk gives an error.
 
 
-       -p     Print  out  the  document.  By default the file to be printed is
-              the first in the list postscript, pdf, dvi that is  being  made.
+       -p     Print out the document.  By default the file to  be  printed  is
+              the  first  in the list postscript, pdf, dvi that is being made.
               But you can use the -print=... option to change the type of file
               to be printed, and you can configure this in a start up file (by
               setting the $print_type variable).
 
-              However,  printing  is  enabled by default only under UNIX/Linux
+              However, printing is enabled by default  only  under  UNIX/Linux
               systems, where the default is to use the lpr command and only on
               postscript files.  In general, the correct behavior for printing
               very much depends on your system's software.  In particular, un-
-              der MS-Windows you must have suitable program(s) available,  and
-              you  must  have  configured  the print commands used by latexmk.
-              This can be non-trivial.  See the  documentation  on  the  $lpr,
+              der  MS-Windows you must have suitable program(s) available, and
+              you must have configured the print  commands  used  by  latexmk.
+              This  can  be  non-trivial.   See the documentation on the $lpr,
               $lpr_dvi, and $lpr_pdf configuration variables to see how to set
               the commands for printing.
 
@@ -1046,31 +1083,19 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               turns them off.
 
 
-       -pdf   Generate  pdf  version of document using pdflatex.  (If you wish
+       -pdf   Generate pdf version of document using pdflatex.  (If  you  wish
               to use lualatex or xelatex, you can use whichever of the options
-
-
-
-                                31 January 2024                             16
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
-              -pdflua, -pdfxe, -lualatex or -xelatex applies.)   To  configure
-              latexmk  to  have  such  behavior by default, see the section on
+              -pdflua,  -pdfxe,  -lualatex or -xelatex applies.)  To configure
+              latexmk to have such behavior by default,  see  the  section  on
               "Configuration/initialization (rc) files".
 
 
        -pdfdvi
-              Generate dvi file and then pdf version of document from the  dvi
+              Generate  dvi file and then pdf version of document from the dvi
               file, by default using dvipdf.
 
-              The  program used to compile the document to dvi is latex by de-
-              fault, but this can be changed to dvilulatex by the use  of  the
+              The program used to compile the document to dvi is latex by  de-
+              fault,  but  this can be changed to dvilulatex by the use of the
               -dvilua option or by setting $dvi_mode to 2.
 
 
@@ -1081,56 +1106,56 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        -pdfps Generate dvi file, ps file from the dvi file,  and then pdf file
               from the ps file.
 
-              The  program used to compile the document to dvi is latex by de-
-              fault, but this can be changed to dvilulatex by the use  of  the
+              The program used to compile the document to dvi is latex by  de-
+              fault,  but  this can be changed to dvilulatex by the use of the
               -dvilua option or by setting $dvi_mode to 2.
 
 
-       -pdfxe Generate  pdf  version  of document using xelatex.  Note that to
-              optimize processing time, latexmk uses xelatex  to  generate  an
-              .xdv  file rather than a pdf file directly.  Only after possibly
-              multiple runs to generate a fully up-to-date .xdv file does  la-
-              texmk then call xdvipdfmx to generate the final .pdf file.
+       -pdfxe Generate pdf version of document using xelatex.   Note  that  to
+              optimize  processing  time,  latexmk uses xelatex to generate an
+              .xdv file rather than a pdf file directly.  Only after  possibly
 
-              (Note:  The  reason  why latexmk arranges for xelatex to make an
-              .xdv file instead of the xelatex's default of a .pdf file is  as
-              follows:  When the document includes large graphics files, espe-
-              cially .png files, the production of a .pdf file  can  be  quite
-              time consuming, even when the creation of the .xdv file by xela-
-              tex  is  fast.  So the use of the intermediate .xdv file can re-
-              sult in substantial gains in procesing time, since the .pdf file
-              is produced once rather than on every run of xelatex.)
 
 
-       -pdf-  Turn off generation of pdf version of document.   (This  can  be
-              used  to override a setting in a configuration file.  It may get
-              overridden if some other option requires the generation of a pdf
-              file.)
+                                 7 April 2024                               17
 
-              If after all options have  been  processed,  pdf  generation  is
-              still  turned  off, then generation of a dvi file will be turned
-              on, and then the program used to compiled a document will be la-
-              tex (or, more precisely, whatever program is  configured  to  be
-              used in the $latex configuration variable).
 
 
 
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-                                31 January 2024                             17
 
+              multiple  runs to generate a fully up-to-date .xdv file does la-
+              texmk then call xdvipdfmx to generate the final .pdf file.
 
+              (Note: The reason why latexmk arranges for xelatex  to  make  an
+              .xdv  file instead of the xelatex's default of a .pdf file is as
+              follows: When the document includes large graphics files,  espe-
+              cially  .png  files,  the production of a .pdf file can be quite
+              time consuming, even when the creation of the .xdv file by xela-
+              tex is fast.  So the use of the intermediate .xdv file  can  re-
+              sult in substantial gains in procesing time, since the .pdf file
+              is produced once rather than on every run of xelatex.)
 
 
+       -pdf-  Turn  off  generation  of pdf version of document.  (This can be
+              used to override a setting in a configuration file.  It may  get
+              overridden if some other option requires the generation of a pdf
+              file.)
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+              If  after  all  options  have  been processed, pdf generation is
+              still turned off, then generation of a dvi file will  be  turned
+              on, and then the program used to compiled a document will be la-
+              tex  (or,  more  precisely, whatever program is configured to be
+              used in the $latex configuration variable).
 
 
        -pdflatex
               This sets the generation of pdf files by pdflatex, and turns off
               the generation of dvi and ps files.
 
-              Note:  to  set  the command used when pdflatex is specified, see
+              Note: to set the command used when pdflatex  is  specified,  see
               the -pdflatex="COMMAND" option.
 
 
@@ -1142,19 +1167,31 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
                    latexmk  -pdf  -pdflatex="pdflatex  --shell-escape  %O  %S"
               foo.tex
 
-              The  specification of the contents of the string are the same as
+              The specification of the contents of the string are the same  as
               for the $pdflatex configuration variable.  (The option -pdflatex
               in fact sets the variable $pdflatex.)  Depending on your operat-
-              ing system and the command-line shell you  are  using,  you  may
-              need  to change the single quotes to double quotes (or something
+              ing  system  and  the  command-line shell you are using, you may
+              need to change the single quotes to double quotes (or  something
               else).
 
-              Note: This option when provided with the COMMAND  argument  only
-              sets  the command for invoking pdflatex; it does not turn on the
+              Note:  This  option when provided with the COMMAND argument only
+              sets the command for invoking pdflatex; it does not turn on  the
               use of pdflatex. That is done by other options or in an initial-
               ization file.
 
-              To set the command for running latex (rather  than  the  command
+              To  set  the  command for running latex (rather than the command
+
+
+
+                                 7 April 2024                               18
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
               for pdflatex) see the -latex option.
 
 
@@ -1169,10 +1206,10 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        -pretex=CODE
 
               Given that CODE is some TeX code, this options sets that code to
-              be  executed  before  inputting source file.  This only works if
+              be executed before inputting source file.  This  only  works  if
               the command for invoking the relevant *latex is suitably config-
-              ured.  See the documentation of the variable $pre_tex_code,  and
-              the  substitution  strings %P and %U for more details.  This op-
+              ured.   See the documentation of the variable $pre_tex_code, and
+              the substitution strings %P and %U for more details.   This  op-
               tion works by setting the variable $pre_tex_code.
 
               See also the -usepretex option.
@@ -1180,18 +1217,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               An example:
 
                   latexmk  -pretex='\AtBeginDocument{Message\par}'  -usepretex
-
-
-
-                                31 January 2024                             18
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
               foo.tex
 
               But this is better written
@@ -1204,12 +1229,12 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        -print=dvi, -print=ps, -print=pdf, -print=auto,
-              Define  which kind of file is printed.  This option also ensures
+              Define which kind of file is printed.  This option also  ensures
               that the requisite file is made, and turns on printing.
 
               The (default) case -print=auto determines the kind of print file
-              automatically from the set of files that  is  being  made.   The
-              first  in  the list postscript, pdf, dvi that is among the files
+              automatically  from  the  set  of files that is being made.  The
+              first in the list postscript, pdf, dvi that is among  the  files
               to be made is the one used for print out.
 
 
@@ -1217,13 +1242,24 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        -ps-   Turn off generation of postscript version of document.  This can
-              be used to override a setting in a configuration file.  (It  may
-              get  overridden  by some other option that requires a postscript
+              be  used to override a setting in a configuration file.  (It may
+              get overridden by some other option that requires  a  postscript
               file, for example a request for printing.)
 
 
-       -pF    Postscript file filtering.  The argument to  this  option  is  a
-              filter  which  will generate a filtered postscript file with the
+
+
+                                 7 April 2024                               19
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+       -pF    Postscript  file  filtering.   The  argument to this option is a
+              filter which will generate a filtered postscript file  with  the
               extension ".psF".  All extra processing (e.g. preview, printing)
               will then be performed on this filtered postscript file.
 
@@ -1236,92 +1272,81 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
                    latexmk -ps -pF "psnup -2" foo.tex
 
               Whether to use single or double quotes round the "psnup -2" will
-              depend on your command interpreter, as used  by  the  particular
+              depend  on  your  command interpreter, as used by the particular
               version of perl and the operating system on your computer.
 
 
-       -pv    Run  file previewer.  If the -view option is used, that will se-
+       -pv    Run file previewer.  If the -view option is used, that will  se-
               lect the kind of file to be previewed (.pdf, .ps or .dvi).  Oth-
-              erwise the viewer views the "highest" kind of output  file  that
-              is  made, with the ordering being .pdf, .ps, .dvi (high to low).
-              This option is incompatible with the -p and -pvc options, so  it
+              erwise  the  viewer views the "highest" kind of output file that
+              is made, with the ordering being .pdf, .ps, .dvi (high to  low).
+              This  option is incompatible with the -p and -pvc options, so it
               turns them off.
 
 
-
-                                31 January 2024                             19
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        -pv-   Turn off -pv.
 
 
-       -pvc   Run  a  file  previewer  and  continually  update the .dvi, .ps,
+       -pvc   Run a file previewer  and  continually  update  the  .dvi,  .ps,
               and/or .pdf files whenever changes are made to source files (see
-              the Description above).  Which of these files is  generated  and
-              which  is  viewed  is  governed by the other options, and is the
-              same as for the -pv option.  The preview-continuous option  -pvc
-              can  only work with one file.  So in this case you will normally
-              only specify one filename on the command line.  It is  also  in-
-              compatible  with  the  -p and -pv options, so it turns these op-
+              the  Description  above).  Which of these files is generated and
+              which is viewed is governed by the other  options,  and  is  the
+              same  as for the -pv option.  The preview-continuous option -pvc
+              can only work with one file.  So in this case you will  normally
+              only  specify  one filename on the command line.  It is also in-
+              compatible with the -p and -pv options, so it  turns  these  op-
               tions off.
 
-              The -pvc option also turns off force mode (-f), as  is  normally
-              best  for  continuous  preview  mode.   If you really want force
+              The  -pvc  option also turns off force mode (-f), as is normally
+              best for continuous preview mode.   If  you  really  want  force
               mode, use the options in the order -pvc -f.
 
               With a good previewer the display will be automatically updated.
-              (Under some but not all versions of UNIX/Linux "gv -watch"  does
-              this  for  postscript  files; this can be set by a configuration
-              variable.  This would also work for pdf files except for an  ap-
+              (Under  some but not all versions of UNIX/Linux "gv -watch" does
+              this for postscript files; this can be set  by  a  configuration
+              variable.   This would also work for pdf files except for an ap-
               parent bug in gv that causes an error when the newly updated pdf
               file is read.)  Many other previewers will need a manual update.
 
               Important note: the acroread program on MS-Windows locks the pdf
-              file,  and  prevents  new versions being written, so it is a bad
-              idea to use acroread to view  pdf  files  in  preview-continuous
-              mode.   It  is  better to use a different viewer: SumatraPDF and
-              gsview are good possibilities.
-
-              There are some other methods for arranging  an  update,  notably
-              useful  for  many versions of xdvi and xpdf.  These are best set
-              in latexmk's configuration; see below.
+              file, and prevents new versions being written, so it  is  a  bad
+              idea  to  use  acroread  to view pdf files in preview-continuous
+              mode.  It is better to use a different  viewer:  SumatraPDF  and
 
-              Note that if latexmk  dies  or  is  stopped  by  the  user,  the
-              "forked" previewer will continue to run.  Successive invocations
-              with  the  -pvc option will not fork new previewers, but latexmk
-              will normally use the existing previewer.  (At least  this  will
-              happen  when  latexmk is running under an operating system where
-              it knows how to determine whether an existing previewer is  run-
-              ning.)
 
 
-       -pvc-  Turn off -pvc.
+                                 7 April 2024                               20
 
 
-       -pvctimeout
-              Do  timeout  in pvc mode after period of inactivity, which is 30
-              min. by default.  Inactivity means a period when latexmk has de-
-              tected no file changes and hence has not taken any actions  like
-              compiling the document.
 
 
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+              gsview are good possibilities.
 
-                                31 January 2024                             20
+              There  are  some  other methods for arranging an update, notably
+              useful for many versions of xdvi and xpdf.  These are  best  set
+              in latexmk's configuration; see below.
 
+              Note  that  if  latexmk  dies  or  is  stopped  by the user, the
+              "forked" previewer will continue to run.  Successive invocations
+              with the -pvc option will not fork new previewers,  but  latexmk
+              will  normally  use the existing previewer.  (At least this will
+              happen when latexmk is running under an operating  system  where
+              it  knows how to determine whether an existing previewer is run-
+              ning.)
 
 
+       -pvc-  Turn off -pvc.
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+       -pvctimeout
+              Do timeout in pvc mode after period of inactivity, which  is  30
+              min. by default.  Inactivity means a period when latexmk has de-
+              tected  no file changes and hence has not taken any actions like
+              compiling the document.
 
 
        -pvctimeout-
@@ -1336,31 +1361,43 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        -r <rcfile>
-              Read  the  specified initialization file ("RC file") before pro-
+              Read the specified initialization file ("RC file")  before  pro-
               cessing.
 
               Be careful about the ordering: (1) Standard initialization files
-              -- see the section below on  "Configuration/initialization  (RC)
-              files"  --  are read first.  (2) Then the options on the command
-              line are acted on in the order they are given.  Therefore if  an
-              initialization  file  is  specified by the -r option, it is read
-              during this second step.  Thus an initialization file  specified
+              --  see  the section below on "Configuration/initialization (RC)
+              files" -- are read first.  (2) Then the options on  the  command
+              line  are acted on in the order they are given.  Therefore if an
+              initialization file is specified by the -r option,  it  is  read
+              during  this second step.  Thus an initialization file specified
               with the -r option can override both the standard initialization
               files and previously specified options.  But all of these can be
               overridden by later options.
 
               The contents of the RC file just comprise a piece of code in the
-              Perl  programming  language  (typically a sequence of assignment
+              Perl programming language (typically a  sequence  of  assignment
               statements); they are executed when the -r option is encountered
               during latexmk's parsing of its command line.  See the -e option
-              for a way of giving initialization code  directly  on  latexmk's
-              command  line.   An error results in latexmk stopping.  Multiple
+
+
+
+                                 7 April 2024                               21
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+              for  a  way  of giving initialization code directly on latexmk's
+              command line.  An error results in latexmk  stopping.   Multiple
               instances of the -r and -e options can be used, and they are ex-
               ecuted in the order they appear on the command line.
 
 
        -rc-report
-              After initialization, give a list of the  RC  files  read.  (De-
+              After  initialization,  give  a  list of the RC files read. (De-
               fault)
 
 
@@ -1369,168 +1406,155 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        -recorder
-              Give  the  -recorder  option with *latex.  In (most) modern ver-
-              sions of these programs, this results in  a  file  of  extension
-              .fls  containing  a  list  of the files that these programs have
-              read and written.  Latexmk will then use this  file  to  improve
+              Give the -recorder option with *latex.  In  (most)  modern  ver-
+              sions  of  these  programs,  this results in a file of extension
+              .fls containing a list of the files  that  these  programs  have
+              read  and  written.   Latexmk will then use this file to improve
               its detection of source files and generated files after a run of
               *latex.  This is the default setting of latexmk, unless overrid-
               den in an initialization file.
 
               For further information, see the documentation for the $recorder
+              configuration variable.
 
 
+       -recorder-
+              Do not supply the -recorder option with *latex.
 
-                                31 January 2024                             21
 
+       -rules Show a list of latemk's rules and dependencies after processing.
 
 
+       -rules-
+              Do not show a list of latexmk's  rules  and  dependencies  after
+              processing.  (This is the default.)
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+       -showextraoptions
+              Show  the  list of extra *latex options that latexmk recognizes,
+              but that it simply passes through to the programs  *latex   when
+              they  are  run.   These options are (currently) a combination of
+              those allowed by the TeXLive and MiKTeX implementations.  (If  a
+              particular  option is given to latexmk but is not handled by the
+              particular implementation of *latex that  is  being  used,  that
+              program  will  probably  give a warning or an error.)  These op-
+              tions are very numerous, but are not listed in  this  documenta-
+              tion because they have no effect on latexmk's actions.
 
+              There  are a few options (e.g., -includedirectory=dir, -initial-
+              ize, -ini) that are not recognized, either  because  they  don't
+              fit  with  latexmk's  intended  operations, or because they need
 
-              configuration variable.
 
 
-       -recorder-
-              Do not supply the -recorder option with *latex.
+                                 7 April 2024                               22
 
 
-       -rules Show a list of latemk's rules and dependencies after processing.
 
 
-       -rules-
-              Do  not  show  a  list of latexmk's rules and dependencies after
-              processing.  (This is the default.)
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-       -showextraoptions
-              Show the list of extra *latex options that  latexmk  recognizes,
-              but  that  it simply passes through to the programs *latex  when
-              they are run.  These options are (currently)  a  combination  of
-              those  allowed by the TeXLive and MiKTeX implementations.  (If a
-              particular option is given to latexmk but is not handled by  the
-              particular  implementation  of  *latex  that is being used, that
-              program will probably give a warning or an  error.)   These  op-
-              tions  are  very numerous, but are not listed in this documenta-
-              tion because they have no effect on latexmk's actions.
 
-              There are a few options (e.g., -includedirectory=dir,  -initial-
-              ize,  -ini)  that  are not recognized, either because they don't
-              fit with latexmk's intended operations,  or  because  they  need
-              special  processing by latexmk that isn't implemented (at least,
+              special processing by latexmk that isn't implemented (at  least,
               not yet).
 
-              There are certain options  for  *latex  (e.g.,  -recorder)  that
+              There  are  certain  options  for  *latex (e.g., -recorder) that
               trigger special actions or behavior by latexmk itself. Depending
-              on  the  action,  they  may  also  be passed in some form to the
+              on the action, they may also be  passed  in  some  form  to  the
               called *latex program, and/or may affect other programs as well.
-              These options do have  entries  in  this  documentation.   Among
+              These  options  do  have  entries  in this documentation.  Among
               these options are: -jobname=STRING, -aux-directory=dir, -output-
               directory=DIR, -quiet, and -recorder.
 
-              There  are also options that are accepted by *latex, but instead
+              There are also options that are accepted by *latex, but  instead
               trigger actions purely by latexmk: -help, -version.
 
 
        -silent
               Run commands silently, i.e., with options that reduce the amount
-              of diagnostics generated.  For example, with  the  default  set-
-              tings,  the  command  "latex -interaction=batchmode" is used for
+              of  diagnostics  generated.   For example, with the default set-
+              tings, the command "latex -interaction=batchmode"  is  used  for
               latex, and similarly for its friends.
 
-              See also the -logfilewarninglist  and  -logfilewarninglist-  op-
+              See  also  the  -logfilewarninglist and -logfilewarninglist- op-
               tions.
 
-              Also  reduce  the  number of informational messages that latexmk
-
-
-
-                                31 January 2024                             22
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
+              Also reduce the number of informational  messages  that  latexmk
               itself generates.
 
-              To change the options used to make the  commands  run  silently,
+              To  change  the  options used to make the commands run silently,
               you need to configure latexmk with changed values of its config-
-              uration    variables,    the    relevant    ones   being   $bib-
-              tex_silent_switch, $biber_silent_switch,  $dvipdf_silent_switch,
+              uration   variables,   the    relevant    ones    being    $bib-
+              tex_silent_switch,  $biber_silent_switch, $dvipdf_silent_switch,
               $dvips_silent_switch,      $dvilualatex_silent_switch,      $la-
-              tex_silent_switch,       $lualatex_silent_switch        $makein-
-              dex_silent_switch,     $pdflatex_silent_switch,    and    $xela-
+              tex_silent_switch,        $lualatex_silent_switch       $makein-
+              dex_silent_switch,    $pdflatex_silent_switch,    and     $xela-
               tex_silent_switch
 
 
        -stdtexcmds
-              Sets the commands for latex, etc, so that they are the  standard
+              Sets  the commands for latex, etc, so that they are the standard
               ones. This is useful to override special configurations.
 
-              The  result  is  that  $latex = 'latex %O %S', and similarly for
-              $pdflatex, $lualatex, and $xelatex.  (The option -no-pdf  needed
+              The result is that $latex = 'latex %O  %S',  and  similarly  for
+              $pdflatex,  $lualatex, and $xelatex.  (The option -no-pdf needed
               for $xelatex is provided automatically, given that %O appears in
               the definition.)
 
 
        -time  Show time used.  (On MS Windows, what is shown is clock time; on
-              other  systems  CPU  time.)  See also the configuration variable
+              other systems CPU time.)  See also  the  configuration  variable
               $show_time.
 
 
-       -time- Do not show time used.   See  also  the  configuration  variable
+       -time- Do  not  show  time  used.   See also the configuration variable
               $show_time.
 
 
-       -use-make
-              When  after  a  run  of *latex, there are warnings about missing
-              files (e.g., as requested by the  LaTeX  \input,  \include,  and
-              \includgraphics  commands), latexmk tries to make them by a cus-
-              tom dependency. If no relevant custom dependency with an  appro-
-              priate source file is found, and if the -use-make option is set,
-              then  as  a last resort latexmk will try to use the make program
-              to try to make the missing files.
-
-              Note that the filename may be specified  without  an  extension,
-              e.g.,  by  \includegraphics{drawing}  in  a LaTeX file.  In that
-              case, latexmk will try making drawing.ext with ext set  in  turn
-              to  the  possible  extensions that are relevant for latex (or as
-              appropriate pdflatex, lualatex, xelatex).
 
-              See also the documentation for  the  $use_make_for_missing_files
-              configuration variable.
+                                 7 April 2024                               23
 
 
-       -use-make-
-              Do  not use the make program to try to make missing files.  (De-
-              fault.)
 
 
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-                                31 January 2024                             23
 
+       -use-make
+              When after a run of *latex, there  are  warnings  about  missing
+              files  (e.g.,  as  requested  by the LaTeX \input, \include, and
+              \includgraphics commands), latexmk tries to make them by a  cus-
+              tom  dependency. If no relevant custom dependency with an appro-
+              priate source file is found, and if the -use-make option is set,
+              then as a last resort latexmk will try to use the  make  program
+              to try to make the missing files.
 
+              Note  that  the  filename may be specified without an extension,
+              e.g., by \includegraphics{drawing} in a  LaTeX  file.   In  that
+              case,  latexmk  will try making drawing.ext with ext set in turn
+              to the possible extensions that are relevant for  latex  (or  as
+              appropriate pdflatex, lualatex, xelatex).
 
+              See  also  the documentation for the $use_make_for_missing_files
+              configuration variable.
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+       -use-make-
+              Do not use the make program to try to make missing files.   (De-
+              fault.)
 
 
        -usepretex
               Sets the command lines for latex, etc, so that they use the code
-              that is defined by the variable $pre_tex_code or that is set  by
+              that  is defined by the variable $pre_tex_code or that is set by
               the option -pretex=CODE to execute the specified TeX code before
               the source file is read.  This option overrides any previous de-
               finition of the command lines.
 
-              The  result  is  that  $latex = 'latex %O %P', and similarly for
-              $pdflatex, $lualatex, and $xelatex.  (The option -no-pdf  needed
+              The result is that $latex = 'latex %O  %P',  and  similarly  for
+              $pdflatex,  $lualatex, and $xelatex.  (The option -no-pdf needed
               for $xelatex is provided automatically, given that %O appears in
               the definition.)
 
@@ -1552,107 +1576,108 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        -view=default, -view=dvi, -view=ps, -view=pdf, -view=none
               Set the kind of file used when previewing is requested (e.g., by
               the -pv or -pvc switches).  The default is to view the "highest"
-              kind  of  requested  file  (in  the low-to-high order .dvi, .ps,
-              .pdf).
 
-              Note the possibility -view=none where no  viewer  is  opened  at
-              all.   One example of is use is in conjunction with the -pvc op-
-              tion, when you want latexmk to do  a  compilation  automatically
-              whenever  source  file(s) change, but do not want a previewer to
-              be opened.
 
 
-       -Werror
-              This causes latexmk to return a non-zero status code if  any  of
-              the  files  processed  gives a warning about problems with cita-
-              tions or references (i.e., undefined citations or references  or
-              about  multiply  defined references).  This is after latexmk has
-              completed all the runs it needs to try  and  resolve  references
-              and  citations.  Thus -Werror causes latexmk to treat such warn-
-              ings as errors, but only when they occur on the last run of *la-
-              tex and only after processing is complete.  Also can be  set  by
-              the configuration variable $warnings_as_errors.
+                                 7 April 2024                               24
 
 
-       -xdv   Generate xdv version of document using xelatex.
 
 
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-                                31 January 2024                             24
 
+              kind of requested file (in  the  low-to-high  order  .dvi,  .ps,
+              .pdf).
 
+              Note  the  possibility  -view=none  where no viewer is opened at
+              all.  One example of is use is in conjunction with the -pvc  op-
+              tion,  when  you  want latexmk to do a compilation automatically
+              whenever source file(s) change, but do not want a  previewer  to
+              be opened.
 
 
+       -Werror
+              This  causes  latexmk to return a non-zero status code if any of
+              the files processed gives a warning about  problems  with  cita-
+              tions  or references (i.e., undefined citations or references or
+              about multiply defined references).  This is after  latexmk  has
+              completed  all  the  runs it needs to try and resolve references
+              and citations.  Thus -Werror causes latexmk to treat such  warn-
+              ings as errors, but only when they occur on the last run of *la-
+              tex  and  only after processing is complete.  Also can be set by
+              the configuration variable $warnings_as_errors.
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+       -xdv   Generate xdv version of document using xelatex.
 
 
        -xelatex
               Use xelatex.  That is, use xelatex to process the source file(s)
-              to  pdf.   The  generation of dvi and postscript files is turned
+              to pdf.  The generation of dvi and postscript  files  is  turned
               off.
 
               This option is equivalent to using the following set of options
 
                    -pdfxe -dvi- -ps-
 
-              [Note: Note that the method of implementation  of  this  option,
-              but  not  its  intended primary effect, differ from some earlier
-              versions of latexmk. Latexmk first uses xelatex to make an  .xdv
-              file,  and  does  all  the extra runs needed (including those of
-              bibtex, etc).  Only after that does it make the  pdf  file  from
-              the  .xdv  file, using xdvipdfmx.  See the documentation for the
+              [Note:  Note  that  the method of implementation of this option,
+              but not its intended primary effect, differ  from  some  earlier
+              versions  of latexmk. Latexmk first uses xelatex to make an .xdv
+              file, and does all the extra runs  needed  (including  those  of
+              bibtex,  etc).   Only  after that does it make the pdf file from
+              the .xdv file, using xdvipdfmx.  See the documentation  for  the
               -pdfxe for why this is done.]
 
 
        -xelatex="COMMAND"
-              This sets the string specifying the command to run xelatex.   It
+              This  sets the string specifying the command to run xelatex.  It
               sets the variable $xelatex.
 
               Warning: It is important to ensure that the -no-pdf is used when
-              xelatex  is invoked, since latexmk expects xelatex to produce an
-              .xdv file, not a .pdf file. If you provide  %O  in  the  command
-              specification,  this  will be done automatically.  See the docu-
-              mentation for the -pdfxe option for why  latexmk  makes  a  .xdv
+              xelatex is invoked, since latexmk expects xelatex to produce  an
+              .xdv  file,  not  a  .pdf file. If you provide %O in the command
+              specification, this will be done automatically.  See  the  docu-
+              mentation  for  the  -pdfxe  option for why latexmk makes a .xdv
               file rather than a .pdf file when xelatex is used.
 
-              An example of the use of the -pdfxelatex option:
 
-                   latexmk  -pdfxe  -pdfxelatex="xelatex --shell-escape %O %S"
-              foo.tex
 
-              Note: This option when provided with the COMMAND  argument  only
-              sets  the command for invoking lualatex; it does not turn on the
-              use of lualatex. That is done by other options or in an initial-
-              ization file.
 
+                                 7 April 2024                               25
 
-       Compatibility between options
 
-       The preview-continuous option -pvc can only work with one file.  So  in
-       this  case  you  will normally only specify one filename on the command
-       line.
 
-       Options -p, -pv and -pvc are mutually exclusive.  So each of these  op-
-       tions turns the others off.
 
 
-EXAMPLES
-       % latexmk thesis    # run latex enough times to resolve
-                           cross-references
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+              An example of the use of the -pdfxelatex option:
 
+                   latexmk -pdfxe -pdfxelatex="xelatex --shell-escape  %O  %S"
+              foo.tex
 
-                                31 January 2024                             25
+              Note:  This  option when provided with the COMMAND argument only
+              sets the command for invoking lualatex; it does not turn on  the
+              use of lualatex. That is done by other options or in an initial-
+              ization file.
 
 
+       Compatibility between options
 
+       The  preview-continuous option -pvc can only work with one file.  So in
+       this case you will normally only specify one filename  on  the  command
+       line.
 
+       Options  -p, -pv and -pvc are mutually exclusive.  So each of these op-
+       tions turns the others off.
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
+EXAMPLES
+       % latexmk thesis    # run latex enough times to resolve
+                           cross-references
 
        % latexmk -pvc -ps thesis# run latex enough times to resolve
                            cross-references, make a postscript
@@ -1674,20 +1699,32 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 DEALING WITH ERRORS, PROBLEMS, ETC
        Some possibilities:
 
-       a.  If you get a strange error, do look carefully at the output that is
-       on the screen and in log files.  While there is much  that  is  notori-
+       a. If you get a strange error, do look carefully at the output that  is
+       on  the  screen  and in log files.  While there is much that is notori-
        ously verbose in the output of latex (and that is added to by latexmk),
-       the  verbosity  is  there  for a reason: to enable the user to diagnose
-       problems.  Latexmk does repeat some messages at the end of a  run  that
-       it  thinks  would otherwise be easy to miss in the middle of other out-
+       the verbosity is there for a reason: to enable  the  user  to  diagnose
+       problems.   Latexmk  does repeat some messages at the end of a run that
+       it thinks would otherwise be easy to miss in the middle of  other  out-
        put.
 
-       b. Generally, remember that latexmk does its work by running other pro-
-       grams.  Your first priority in dealing with errors should be to examine
-       what went wrong with the individual programs.  Then you need to correct
-       the causes of errors in the runs of these programs.  (Often these  come
-       from  errors in the source document, but they could also be about miss-
-       ing LaTeX packages, etc.)
+       b.  Generally,  remember  that  latexmk  does its work by running other
+
+
+
+                                 7 April 2024                               26
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+       programs.  Your first priority in dealing with errors should be to  ex-
+       amine  what  went wrong with the individual programs.  Then you need to
+       correct the causes of errors in the runs  of  these  programs.   (Often
+       these  come  from errors in the source document, but they could also be
+       about missing LaTeX packages, etc.)
 
        c. If latexmk doesn't run the programs the way you would like, then you
        need to look in this documentation at the list of command line  options
@@ -1708,18 +1745,6 @@ DEALING WITH ERRORS, PROBLEMS, ETC
 
        f.  There's  a  useful trick that can be used when you use lualatex in-
        stead of pdflatex (and in some related  situations).   The  problem  is
-
-
-
-                                31 January 2024                             26
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        that  latexmk won't notice a dependency on a file, bar.baz say, that is
        input by the lua code in your document instead of by  the  LaTeX  part.
        (Thus  if you change bar.baz and rerun latexmk, then latexmk will think
@@ -1748,6 +1773,19 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
+
+
+
+
+                                 7 April 2024                               27
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
 AUXILIARY AND OUTPUT DIRECTORIES
        Running  *latex and the associated programs generate a number of files,
        it is often convenient to arrange for the generated files to  be  in  a
@@ -1774,18 +1812,6 @@ AUXILIARY AND OUTPUT DIRECTORIES
        tex programs, these directories default to the current  directory,  and
        then the generated files aren't segregated.  If the two directories are
        the  same,  as  is the simplest situation, then all generated files are
-
-
-
-                                31 January 2024                             27
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        written to the same directory, and one often simply refers to the  out-
        put directory, without mentioning a separate aux directory.
 
@@ -1813,13 +1839,25 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        Latexmk also turns emulation on if it is found to be  needed,  as  fol-
        lows.   Suppose  emulation is initially off, but the aux and output di-
        rectories are different.  Then latexmk invokes *latex with an  -aux-di-
-       rectory  option and after the run finds that it hasn't been obeyed, no-
-       tably because the .log file is in the output directory rather than  the
-       aux  directory.  Latexmk then sets emulation on, and retries.  Conceiv-
-       ably, it could move all the appropriate generated files from the output
-       directory to the aux directory; but there is such a  large  variety  of
-       possibilities for these files that this is hard to identify all of them
-       reliably except for simple cases.
+       rectory  option  and  after  the  run finds that it hasn't been obeyed,
+
+
+
+                                 7 April 2024                               28
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+       notably because the .log file is in the output  directory  rather  than
+       the  aux directory.  Latexmk then sets emulation on, and retries.  Con-
+       ceivably, it could move all the appropriate generated  files  from  the
+       output  directory to the aux directory; but there is such a large vari-
+       ety of possibilities for these files that this is hard to identify  all
+       of them reliably except for simple cases.
 
        Note  that  the  emulation issue only arises when the user has arranged
        for the the aux and output directories to be different.   When  instead
@@ -1839,50 +1877,50 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        cause of compatibility issues, is of .fls files: See below.
 
        Note  that  xelatex  when  invoked  with its -no-pdf option, as latexmk
-       does, generates an .xdv file, which  would  appear  to  have  the  same
+       does, generates an .xdv file, which would appear to have the same  sta-
+       tus  as  a  .dvi file generated by latex.  Nevertheless, latexmk treats
+       .xdv as an intermediate file that is found in the aux directory.   This
+       is  to  match MiKTeX's treatment of the -aux-directory option.  As fur-
+       ther justification, one can say that under modern  conditions  an  .xdv
+       file is (almost) always an intermediate file.  Historically, the situa-
+       tion  with  .dvi files from latex was different, and currently dvi pre-
+       viewers do exist.
 
 
+       Variables and options for directories: The variables  for  setting  the
+       aux  and output directories are $aux_dir and $out_dir, with correspond-
+       ing command line options -auxdir (or -aux-directory)  and  -outdir  (or
+       -output-directory).   When a value for these is blank (which is the de-
+       fault value), it implies the use of a default: For the  aux  directory,
+       the default is to set it equal to the output directory.  For the output
+       directory, the default is to be the current directory.
 
-                                31 January 2024                             28
+       For the turning on and off of the emulation mode, there is the configu-
+       ration  variable  $emulate_aux  and the options -emulate-aux-dir, -emu-
+       late-aux-dir-, -noemulate-aux-dir.
 
 
+       Interaction with -cd option: When the -cd option is used (or the equiv-
+       alent setting of $do_cd variable), then latexmk changes the working di-
+       rectory to the document directory before invoking *latex.  If  the  aux
+       and/or  output  directories are given by relative paths, e.g., by -out-
+       dir=output for a directory named "output",  then  the  directories  are
+       relative to the document directory, rather than relative to the working
 
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+                                 7 April 2024                               29
 
 
-       status as a .dvi file generated by latex.  Nevertheless, latexmk treats
-       .xdv  as an intermediate file that is found in the aux directory.  This
-       is to match MiKTeX's treatment of the -aux-directory option.   As  fur-
-       ther  justification,  one  can say that under modern conditions an .xdv
-       file is (almost) always an intermediate file.  Historically, the situa-
-       tion with .dvi files from latex was different, and currently  dvi  pre-
-       viewers do exist.
 
 
-       Variables  and  options  for directories: The variables for setting the
-       aux and output directories are $aux_dir and $out_dir, with  correspond-
-       ing  command  line  options -auxdir (or -aux-directory) and -outdir (or
-       -output-directory).  When a value for these is blank (which is the  de-
-       fault  value),  it implies the use of a default: For the aux directory,
-       the default is to set it equal to the output directory.  For the output
-       directory, the default is to be the current directory.
 
-       For the turning on and off of the emulation mode, there is the configu-
-       ration variable $emulate_aux and the  options  -emulate-aux-dir,  -emu-
-       late-aux-dir-, -noemulate-aux-dir.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       Interaction with -cd option: When the -cd option is used (or the equiv-
-       alent setting of $do_cd variable), then latexmk changes the working di-
-       rectory  to  the document directory before invoking *latex.  If the aux
-       and/or output directories are given by relative paths, e.g.,  by  -out-
-       dir=output  for  a  directory  named "output", then the directories are
-       relative to the document directory, rather than relative to the working
        directory that was in effect when latexmk was invoked. This matches the
-       behavior of *latex as invoked with the provided command line  directory
-       argument(s)  after  the change of working directory to the document di-
+       behavior  of *latex as invoked with the provided command line directory
+       argument(s) after the change of working directory to the  document  di-
        rectory.
 
        Automatic creation of aux and output directories: Unlike *latex, if la-
@@ -1891,171 +1929,161 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
        If the document uses the \include macro to read a .tex file from a sub-
        directory, *latex will attempt to write an extra aux file to the corre-
-       sponding  subdirectory  of  the  aux  directory.   If  the subdirectory
-       doesn't exist, then *latex will complain that it can't  write  the  aux
+       sponding subdirectory  of  the  aux  directory.   If  the  subdirectory
+       doesn't  exist,  then  *latex will complain that it can't write the aux
        file.  After the run of *latex, latexmk detects this situation, creates
-       the  necessary  directory,  and  reruns *latex with the error situation
+       the necessary directory, and reruns *latex  with  the  error  situation
        corrected.
 
        Choice of aux and output directories: Often the aux and output directo-
-       ries are given as subdirectories of the document  directory,  e.g.,  by
+       ries  are  given  as subdirectories of the document directory, e.g., by
        -outdir=output. But it is possible to provide, for example, an absolute
-       path  or  a  path  relative  to a parent directory, e.g., "/tmp/foo" or
+       path or a path relative to a  parent  directory,  e.g.,  "/tmp/foo"  or
        "../output".  Be aware that in general this can cause problems, notably
-       with makeindex or bibtex.  This is because  modern  versions  of  these
-       programs,  by default, will refuse to work when they find that they are
+       with  makeindex  or  bibtex.   This is because modern versions of these
+       programs, by default, will refuse to work when they find that they  are
        asked to write to a file in a directory that appears not to be the cur-
-       rent working directory or one of its subdirectories.  This is  part  of
-
-
-
-                                31 January 2024                             29
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
+       rent  working  directory or one of its subdirectories.  This is part of
        security measures by the whole TeX system that try to prevent malicious
        or errant TeX documents from incorrectly messing with a user's files.
 
-       By  default,  latexmk  evades  this  issue:  Before  running bibtex and
+       By default, latexmk  evades  this  issue:  Before  running  bibtex  and
        makeindex, latexmk changes working directory to the aux directory, with
        appropriate settings of search paths.  The use or non-use of this trick
-       is governed by the variables $bibtex_fudge and  $makeindex_fudge.   Un-
-       fortunately,  the  trick sometimes makes bibtex and makeindex unable to
+       is  governed  by the variables $bibtex_fudge and $makeindex_fudge.  Un-
+       fortunately, the trick sometimes makes bibtex and makeindex  unable  to
        find files.
 
        If necessary the trick can be turned off. But this is incompatible with
-       an aux directory like, "/tmp/foo" of "../output").  If you really  have
+       an  aux directory like, "/tmp/foo" of "../output").  If you really have
        to deal with this situation, and only if you have to deal with it, then
-       you  need to disable the security measures (and assume any risks).  One
+       you need to disable the security measures (and assume any risks).   One
        way of doing this is to temporarily set an operating system environment
-       variable openout_any to "a" (as in  "all"),  to  override  the  default
+       variable  openout_any  to  "a"  (as  in "all"), to override the default
        "paranoid" setting.
 
-       Certain  names  of  aux and output directories not allowed on Microsoft
+       Certain names of aux and output directories not  allowed  on  Microsoft
        Windows: It is natural to want to use the name "aux" for the aux direc-
-       tory, e.g., by using the option -auxdir=aux.  But on Microsoft  operat-
+       tory,  e.g., by using the option -auxdir=aux.  But on Microsoft operat-
        ing systems "aux" is one of the names that is not allowed for a file or
-       directory.   I  find  it  useful to standardize on a name like "auxdir"
-       (e.g., by -auxdir=auxdir); this works independently of  operating  sys-
+       directory.  I find it useful to standardize on  a  name  like  "auxdir"
+       (e.g.,  by  -auxdir=auxdir); this works independently of operating sys-
        tem.
 
-       Location  of .fls file: Much of the dependency information that latexmk
+       Location of .fls file: Much of the dependency information that  latexmk
        uses comes from the .fls file generated when *latex is invoked with the
-       -recorder option, which latexmk does by default.  It may seem  rational
-       that  this  is  written  to the aux directory.  But in fact versions of
-       MiKTeX prior to Oct. 2020 wrote it to the output directory.  Later ver-
-       sions do write it to the aux directory.  To  deal  with  this,  latexmk
-       does  two  things:  First, if latexmk finds that the .fls file has only
-       been generated in the "wrong" directory, then latexmk copies it to  the
-       expected directory, after which latexmk's operation continues correctly
-       independently  of  the behavior of *latex. Second it allows its idea of
-       the "correct" (or expected) directory to be configured by the  variable
-       $fls_uses_aux_dir.   This  defaults  to zero, to correspond to MiKTeX's
-       current behavior.
 
 
 
-ALLOWING FOR CHANGE OF OUTPUT FILE TYPE
-       When one of the latex engines is run, the usual situation is that latex
-       produces a .dvi file, while pdflatex and lualatex produce a .pdf  file.
-       For xelatex the default is to produce a .pdf file, but to optimize pro-
-       cessing  time  latexmk  runs xelatex its -no-pdf option so that it pro-
-       duces an .xdv file.  Further processing by  latexmk  takes  this  as  a
-       starting point.
+                                 7 April 2024                               30
 
-       However, the actual output file may differ from the normal expectation;
-       and  then  latexmk can adjust its processing to accommodate this situa-
-       tion.  The difference in output file type can happen for  two  reasons:
-       One  is  that  for latex, pdflatex and lualatex the document itself can
 
 
 
-                                31 January 2024                             30
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+       -recorder  option, which latexmk does by default.  It may seem rational
+       that this is written to the aux directory.  But  in  fact  versions  of
+       MiKTeX prior to Oct. 2020 wrote it to the output directory.  Later ver-
+       sions  do  write  it  to the aux directory.  To deal with this, latexmk
+       does two things: First, if latexmk finds that the .fls  file  has  only
+       been  generated in the "wrong" directory, then latexmk copies it to the
+       expected directory, after which latexmk's operation continues correctly
+       independently of the behavior of *latex. Second it allows its  idea  of
+       the  "correct" (or expected) directory to be configured by the variable
+       $fls_uses_aux_dir.  This defaults to zero, to  correspond  to  MiKTeX's
+       current behavior.
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
+ALLOWING FOR CHANGE OF OUTPUT FILE TYPE
+       When one of the latex engines is run, the usual situation is that latex
+       produces  a .dvi file, while pdflatex and lualatex produce a .pdf file.
+       For xelatex the default is to produce a .pdf file, but to optimize pro-
+       cessing time latexmk runs xelatex its -no-pdf option so  that  it  pro-
+       duces  an  .xdv  file.   Further  processing by latexmk takes this as a
+       starting point.
 
-       override the defaults. The other is that there may be a  configuration,
+       However, the actual output file may differ from the normal expectation;
+       and then latexmk can adjust its processing to accommodate  this  situa-
+       tion.   The  difference in output file type can happen for two reasons:
+       One is that for latex, pdflatex and lualatex the  document  itself  can
+       override  the defaults. The other is that there may be a configuration,
        or misconfiguration, such that the program that latexmk invokes to com-
-       pile  the  document is not the expected one, or is given options incom-
+       pile the document is not the expected one, or is given  options  incom-
        patible with what latexmk initially expects.
 
-       Under latex and pdflatex, control of the output format by the  document
-       is  done by setting the \pdfoutput macro.  Under lualatex, the \output-
+       Under  latex and pdflatex, control of the output format by the document
+       is done by setting the \pdfoutput macro.  Under lualatex, the  \output-
        mode macro is used instead.
 
        One example of an important use-case for document control of the output
-       format is a document that uses the psfrag package to  insert  graphical
+       format  is  a document that uses the psfrag package to insert graphical
        elements in the output file. The psfrag package achieves its effects by
        inserting postscript code in the output of the compilation of the docu-
-       ment.   This entails the use of compilation to a .dvi file, followed by
-       the use of conversion to a postscript  file  (either  directly,  as  by
-       dvips  or  implicitly,  as an intermediate step by dvipdf).  Then it is
-       useful to force output to be of the .dvi format by  inserting  \pdfout-
+       ment.  This entails the use of compilation to a .dvi file, followed  by
+       the  use  of  conversion  to  a postscript file (either directly, as by
+       dvips or implicitly, as an intermediate step by dvipdf).   Then  it  is
+       useful  to  force output to be of the .dvi format by inserting \pdfout-
        put=0 in the preamble of the document.
 
-       Another  example  is where the document uses graphics file of the .pdf,
-       .jpg, and png types.  With the default setting for the  graphicx  pack-
-       age,  these can be processed in compilation to .pdf but not with compi-
-       lation to .dvi.  In this case, it is useful to insert  \pdfoutput=1  in
-       the  preamble  of the document to force compilation to .pdf output for-
+       Another example is where the document uses graphics file of  the  .pdf,
+       .jpg,  and  png types.  With the default setting for the graphicx pack-
+       age, these can be processed in compilation to .pdf but not with  compi-
+       lation  to  .dvi.  In this case, it is useful to insert \pdfoutput=1 in
+       the preamble of the document to force compilation to .pdf  output  for-
        mat.
 
        In all of these cases, it is needed that latexmk has to adjust its pro-
-       cessing to deal with a mismatch between the actual output  format  (out
-       of  .pdf,  .dvi,  .xdv) and the initially expected output, if possible.
-       Latexmk does this provided the following conditions are met.
+       cessing  to  deal with a mismatch between the actual output format (out
 
-       The first is that latexmk's $allow_switch configuration variable is set
-       to a non-zero value as it is by default.  If this variable is  zero,  a
-       mismatch of filetypes in the compilation results in an error.
 
-       The  second condition for latexmk to be able to handle a change of out-
-       put type is that no explicit requests for .dvi or .ps output files  are
-       made.    Explicit  requests  are  by  the  -dvi  and  -ps,  -print=dvi,
-       -print=ps, -view=dvi, and -view=ps options, and by  corresponding  set-
-       tings  of  the $dvi_mode, $postscript_mode, $print_type, and $view con-
-       figuration variables.  The print-type and view-type  restrictions  only
-       apply when printing and viewing are explicitly requested, respectively.
-       For  this  purpose,  the use of the -pdfdvi and -pdfps options (and the
-       corresponding setting of the $pdf_mode variable) does not count  as  an
-       explicit  request  for the .dvi and .ps files; they are merely regarded
-       as a request for making a .pdf file together with an  initial  proposal
-       for the processing route to make it.
 
-       Note that when accommodating a change in output file type, there is in-
-       volved  a  substantial change in the network of rules that latexmk uses
-       in its actions.  The second condition applied to accommodate  a  change
-       is to avoid situations where the change in the rule network is too rad-
-       ical to be readily handled automatically.
+                                 7 April 2024                               31
 
 
 
 
-                                31 January 2024                             31
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+       of .pdf, .dvi, .xdv) and the initially expected  output,  if  possible.
+       Latexmk does this provided the following conditions are met.
 
+       The first is that latexmk's $allow_switch configuration variable is set
+       to  a  non-zero value as it is by default.  If this variable is zero, a
+       mismatch of filetypes in the compilation results in an error.
+
+       The second condition for latexmk to be able to handle a change of  out-
+       put  type is that no explicit requests for .dvi or .ps output files are
+       made.   Explicit  requests  are  by  the  -dvi  and  -ps,   -print=dvi,
+       -print=ps,  -view=dvi,  and -view=ps options, and by corresponding set-
+       tings of the $dvi_mode, $postscript_mode, $print_type, and  $view  con-
+       figuration  variables.   The print-type and view-type restrictions only
+       apply when printing and viewing are explicitly requested, respectively.
+       For this purpose, the use of the -pdfdvi and -pdfps  options  (and  the
+       corresponding  setting  of the $pdf_mode variable) does not count as an
+       explicit request for the .dvi and .ps files; they are  merely  regarded
+       as  a  request for making a .pdf file together with an initial proposal
+       for the processing route to make it.
+
+       Note that when accommodating a change in output file type, there is in-
+       volved a substantial change in the network of rules that  latexmk  uses
+       in  its  actions.  The second condition applied to accommodate a change
+       is to avoid situations where the change in the rule network is too rad-
+       ical to be readily handled automatically.
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 CONFIGURATION/INITIALIZATION (RC) FILES
-       In  this section is explained which configuration files are read by la-
-       texmk. Subsequent sections "How  to  Set  Variables  in  Initialization
-       Files",  "Format  of  Command  Specifications",  "List of Configuration
-       Variables Usable in Initialization Files", "Custom  Dependencies",  and
-       "Advanced  Configuration"  give  details  on what can be configured and
+       In this section is explained which configuration files are read by  la-
+       texmk.  Subsequent  sections  "How  to  Set Variables in Initialization
+       Files", "Format of  Command  Specifications",  "List  of  Configuration
+       Variables  Usable  in Initialization Files", "Custom Dependencies", and
+       "Advanced Configuration" give details on what  can  be  configured  and
        how.
 
        Latexmk can be customized using initialization files, which are read at
@@ -2063,7 +2091,7 @@ CONFIGURATION/INITIALIZATION (RC) FILES
 
        1) The system RC file, if it exists.
           On a UNIX system, latexmk searches the following directories for a
-          system RC file, which may be named either "LatexMk" or  "latexmkrc".
+          system  RC file, which may be named either "LatexMk" or "latexmkrc".
        The
           directories are searched in the following order, and latexmk uses
           the first such file it finds (if any):
@@ -2072,79 +2100,93 @@ CONFIGURATION/INITIALIZATION (RC) FILES
           "/usr/local/share/latexmk",
           "/usr/local/lib/latexmk".
           On a MS-Windows system it looks just in "C:\latexmk".
-          On  a cygwin system (i.e., a MS-Windows system in which Perl is that
+          On a cygwin system (i.e., a MS-Windows system in which Perl is  that
        of cygwin), latexmk looks in the directories
           "/cygdrive/c/latexmk",
           "/etc",
+
+
+
+                                 7 April 2024                               32
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
           "/opt/local/share/latexmk",
           "/usr/local/share/latexmk",
           "/usr/local/lib/latexmk".
 
-       If the environment variable LATEXMKRCSYS is set, its value is  used  as
+       If  the  environment variable LATEXMKRCSYS is set, its value is used as
        the name of the system RC file, instead of any of the above.
 
        2) The user's RC file, if it exists.  This can be in one of two places.
-       The  traditional one is ".latexmkrc" in the user's home directory.  The
-       other possibility is "latexmk/latexmkrc" in the user's  XDG  configura-
-       tion  home  directory.  The actual file read is the first of "$XDG_CON-
-       FIG_HOME/latexmk/latexmkrc" or "$HOME/.latexmkrc" which  exists.   (See
+       The traditional one is ".latexmkrc" in the user's home directory.   The
+       other  possibility  is "latexmk/latexmkrc" in the user's XDG configura-
+       tion home directory.  The actual file read is the first  of  "$XDG_CON-
+       FIG_HOME/latexmk/latexmkrc"  or  "$HOME/.latexmkrc" which exists.  (See
        https://specifications.freedesktop.org/basedir-spec/basedir-spec-lat-
        est.html for details on the XDG Base Directory Specification.)
 
-       Here  $HOME  is  the  user's  home  directory.  [Latexmk determines the
-       user's home directory as follows:  It is the value of  the  environment
-       variable  HOME,  if this variable exists, which normally is the case on
-       UNIX-like systems (including Linux and OS-X).  Otherwise  the  environ-
-       ment  variable USERPROFILE is used, if it exists, which normally is the
+       Here $HOME is the  user's  home  directory.   [Latexmk  determines  the
+       user's  home  directory as follows:  It is the value of the environment
+       variable HOME, if this variable exists, which normally is the  case  on
+       UNIX-like  systems  (including Linux and OS-X).  Otherwise the environ-
+       ment variable USERPROFILE is used, if it exists, which normally is  the
        case on MS-Windows systems. Otherwise a blank string is used instead of
        $HOME, in which case latexmk does not look for an RC file in it.]
 
-       $XDG_CONFIG_HOME is the value  of  the  environment  variable  XDG_CON-
-       FIG_HOME  if  it  exists.  If this environment variable does not exist,
-       but $HOME is non-blank, then $XDG_CONFIG_HOME is  set  to  the  default
-       value  of  $HOME/.config.  Otherwise $XDG_CONFIG_HOME is blank, and la-
+       $XDG_CONFIG_HOME  is  the  value  of  the environment variable XDG_CON-
+       FIG_HOME if it exists.  If this environment variable  does  not  exist,
+       but  $HOME  is  non-blank,  then $XDG_CONFIG_HOME is set to the default
+       value of $HOME/.config.  Otherwise $XDG_CONFIG_HOME is blank,  and  la-
        texmk does not look for an RC file under it.
 
 
-
-                                31 January 2024                             32
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
-       3) The RC file in the current working  directory.   This  file  can  be
-       named  either "latexmkrc" or ".latexmkrc", and the first of these to be
+       3)  The  RC  file  in  the current working directory.  This file can be
+       named either "latexmkrc" or ".latexmkrc", and the first of these to  be
        found is used, if any.
 
        4) Any RC file(s) specified on the command line with the -r option.
 
        Each RC file is a sequence of Perl commands.  Naturally, a user can use
-       this in creative ways.  But for most purposes, one simply  uses  a  se-
+       this  in  creative  ways.  But for most purposes, one simply uses a se-
        quence of assignment statements that override some of the built-in set-
-       tings  of Latexmk.  Straightforward cases can be handled without knowl-
-       edge of the Perl language by using the examples  in  this  document  as
+       tings of Latexmk.  Straightforward cases can be handled without  knowl-
+       edge  of  the  Perl  language by using the examples in this document as
        templates.  Comment lines are introduced by the "#" character.
 
-       Note  that  command  line options are obeyed in the order in which they
+       Note that command line options are obeyed in the order  in  which  they
        are written; thus any RC file specified on the command line with the -r
-       option can override previous options but can be  itself  overridden  by
-       later  options on the command line.  There is also the -e option, which
+       option  can  override  previous options but can be itself overridden by
+       later options on the command line.  There is also the -e option,  which
        allows initialization code to be specified in latexmk's command line.
 
         For possible examples of code for in an RC file, see the directory ex-
-       ample_rcfiles in the distribution  of  latexmk  (e.g.,  at  http://mir-
+       ample_rcfiles  in  the  distribution  of  latexmk (e.g., at http://mir-
        ror.ctan.org/support/latexmk/example_rcfiles).
 
 
+
+
+
+                                 7 April 2024                               33
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
 HOW TO SET VARIABLES IN INITIALIZATION FILES
-       The  important  variables  that  can be configured are described in the
-       section "List  of  configuration  variables  usable  in  initialization
-       files".   (See  the  earlier section "Configuration/Initialization (rc)
-       Files" for the files where the configurations are  done.)   Syntax  for
+       The important variables that can be configured  are  described  in  the
+       section  "List  of  configuration  variables  usable  in initialization
+       files".  (See the earlier  section  "Configuration/Initialization  (rc)
+       Files"  for  the  files where the configurations are done.)  Syntax for
        setting these variables is of the following forms:
 
                            $bibtex = 'bibtex %O %S';
@@ -2157,60 +2199,60 @@ HOW TO SET VARIABLES IN INITIALIZATION FILES
 
                            @default_files = ('paper', 'paper1');
 
-       for  the  setting  of an array of strings.  It is possible to append an
+       for the setting of an array of strings.  It is possible  to  append  an
        item to an array variable as follows:
 
                            push @default_files, 'paper2';
 
-       Note that simple "scalar" variables have names  that  begin  with  a  $
+       Note  that  simple  "scalar"  variables  have names that begin with a $
        character and array variables have names that begin with a @ character.
        Each statement ends with a semicolon.
 
-       Strings  should  be  enclosed  in single quotes.  (You could use double
-       quotes, as in many programming languages.  But then the  Perl  program-
-       ming  language  brings  into  play some special rules for interpolating
-       variables into strings.  People not fluent in Perl will want  to  avoid
+       Strings should be enclosed in single quotes.   (You  could  use  double
+       quotes,  as  in many programming languages.  But then the Perl program-
+       ming language brings into play some  special  rules  for  interpolating
+       variables  into  strings.  People not fluent in Perl will want to avoid
+       these complications.)
 
+       You can do much more complicated things, but for this you will need  to
+       consult a manual for the Perl programming language.
 
 
-                                31 January 2024                             33
 
 
+FORMAT OF COMMAND SPECIFICATIONS
+       Some  of  the variables set the commands that latexmk uses for carrying
+       out its work, for example to generate a .dvi file from a .tex  file  or
+       to  view a postscript file.  This section describes some important fea-
+       tures of how the commands are specified.  (Note that some of the possi-
+       bilities listed here do not apply to the $kpsewhich variable;  see  its
+       documentation.)
 
+       Placeholders:  Supposed you wanted latexmk to use the command elatex in
+       place  of  the  regular  latex  command,  and suppose moreover that you
+       wanted to give it the option "--shell-escape".  You could  do  this  by
+       the following setting:
 
+            $latex = 'elatex --shell-escape %O %S';
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+       The  two  items  starting with the % character are placeholders.  These
 
 
-       these complications.)
 
-       You  can do much more complicated things, but for this you will need to
-       consult a manual for the Perl programming language.
+                                 7 April 2024                               34
 
 
 
 
-FORMAT OF COMMAND SPECIFICATIONS
-       Some of the variables set the commands that latexmk uses  for  carrying
-       out  its  work, for example to generate a .dvi file from a .tex file or
-       to view a postscript file.  This section describes some important  fea-
-       tures of how the commands are specified.  (Note that some of the possi-
-       bilities  listed  here do not apply to the $kpsewhich variable; see its
-       documentation.)
 
-       Placeholders:  Supposed you wanted latexmk to use the command elatex in
-       place of the regular latex  command,  and  suppose  moreover  that  you
-       wanted  to  give  it the option "--shell-escape".  You could do this by
-       the following setting:
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-            $latex = 'elatex --shell-escape %O %S';
 
-       The two items starting with the % character  are  placeholders.   These
-       are  substituted by appropriate values before the command is run.  Thus
-       %S will be replaced by the source file that elatex will be applied  to,
-       and  %O will be replaced by any options that latexmk has decided to use
+       are substituted by appropriate values before the command is run.   Thus
+       %S  will be replaced by the source file that elatex will be applied to,
+       and %O will be replaced by any options that latexmk has decided to  use
        for this command.  (E.g., if you used the -silent option in the invoca-
-       tion of latexmk,  it results in the replacement  of  %O  by  "-interac-
+       tion  of  latexmk,   it  results in the replacement of %O by "-interac-
        tion=batchmode".)
 
        The available placeholders are:
@@ -2219,123 +2261,125 @@ FORMAT OF COMMAND SPECIFICATIONS
               the setting of a jobname by  the -jobname option or the $jobname
               configuration value.
 
-       %B     base  of  filename  for  current command.  E.g., if a postscript
-              file document.ps is being made from the dvi  file  document.dvi,
+       %B     base of filename for current command.   E.g.,  if  a  postscript
+              file  document.ps  is being made from the dvi file document.dvi,
               then the basename is document.
 
-       %D     destination  file  (e.g.,  the  name of the postscript file when
+       %D     destination file (e.g., the name of  the  postscript  file  when
               converting a dvi file to postscript).
 
        %O     options
 
-       %P     If the variable $pre_tex_code is non-empty, then %P  is  substi-
-              tuted   by  the  contents  of  $pre_tex_code  followed  by  \in-
-              put{SOURCE}, where SOURCE stands for  the  name  of  the  source
+       %P     If  the  variable $pre_tex_code is non-empty, then %P is substi-
+              tuted  by  the  contents  of  $pre_tex_code  followed  by   \in-
+              put{SOURCE},  where  SOURCE  stands  for  the name of the source
               file.  Appropriate quoting is done.  This enables TeX code to be
-              passed  to  one  of the *latex engines to be executed before the
+              passed to one of the *latex engines to be  executed  before  the
               source file is read.
 
-              If the variable $pre_tex_code is the empty string,  then  %P  is
+              If  the  variable  $pre_tex_code is the empty string, then %P is
+              equivalent to %S.
 
+       %R     root filename.
 
+              By default this is the basename of the main tex  file.   However
+              the  value  can  be changed by the use of the -jobname option or
+              the $jobname configuration variable.  This is then the  basename
+              for  files like the .aux and .log files produced by running *la-
+              tex, as well for the main .dvi, .pdf, .ps and/or .xdvi files.
 
-                                31 January 2024                             34
+       %S     source file (e.g., the name of the dvi file  when  converting  a
+              .dvi file to ps).
 
+       %T     The name of the primary tex file.
 
+       %U     If  the  variable  $pre_tex_code is non-empty, then its value is
+              substituted for %U (appropriately quoted).  Otherwise it is  re-
+              placed by a null string.
 
+       %Y     Name of directory for auxiliary output files (see the configura-
+              tion variable $aux_dir).  A directory separation character ('/')
+              is appended if $aux_dir is non-empty and does not end in a suit-
+              able character, with suitable characters being those appropriate
+              to  UNIX  and MS-Windows, i.e., ':', '/' and '\'.   Note that if
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
+                                 7 April 2024                               35
 
-              equivalent to %S.
 
-       %R     root filename.  This is the base name for the main tex file.
 
-              By  default  this is the basename of the main tex file.  However
-              the value can be changed by the use of the  -jobname  option  or
-              the $jobname configuration variable.
 
-       %S     source  file  (e.g.,  the name of the dvi file when converting a
-              .dvi file to ps).
 
-       %T     The name of the primary tex file.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-       %U     If the variable $pre_tex_code is non-empty, then  its  value  is
-              substituted  for %U (appropriately quoted).  Otherwise it is re-
-              placed by a null string.
 
-       %Y     Name of directory for auxiliary output files (see the configura-
-              tion variable $aux_dir).  A directory separation character ('/')
-              is appended if $aux_dir is non-empty and does not end in a suit-
-              able character, with suitable characters being those appropriate
-              to UNIX and MS-Windows, i.e., ':', '/' and '\'.   Note  that  if
-              after  initialization,  $out_dir is set, but $aux_dir is not set
-              (i.e., it is blank), then latexmk  sets  $aux_dir  to  the  same
+              after initialization,  $out_dir is set, but $aux_dir is not  set
+              (i.e.,  it  is  blank),  then  latexmk sets $aux_dir to the same
               value $out_dir.
 
-       %Z     Name  of directory for output files (see the configuration vari-
-              able $out_dir).  A directory separation character ('/')  is  ap-
-              pended  if  $out_dir is non-empty and does not end in a suitable
-              character, with suitable characters being those  appropriate  to
+       %Z     Name of directory for output files (see the configuration  vari-
+              able  $out_dir).   A directory separation character ('/') is ap-
+              pended if $out_dir is non-empty and does not end in  a  suitable
+              character,  with  suitable characters being those appropriate to
               UNIX and MS-Windows, i.e., ':', '/' and '\'.
 
-       If  for  some  reason you need a literal % character in your string not
+       If for some reason you need a literal % character in  your  string  not
        subject to the above rules, use "%%".
 
-       Appropriate quoting will be applied to the filename  substitutions,  so
-       you  mustn't  supply them yourself even if the names of your files have
+       Appropriate  quoting  will be applied to the filename substitutions, so
+       you mustn't supply them yourself even if the names of your  files  have
        spaces in them.  (But if your TeX filenames have spaces in them, beware
-       that some older versions of the TeX  program  cannot  correctly  handle
-       filenames  containing spaces.)  In case latexmk's quoting does not work
-       correctly on your system, you can turn it off -- see the  documentation
+       that  some  older  versions  of the TeX program cannot correctly handle
+       filenames containing spaces.)  In case latexmk's quoting does not  work
+       correctly  on your system, you can turn it off -- see the documentation
        for the variable $quote_filenames.
 
-       See  the default values in the section "List of configuration variables
+       See the default values in the section "List of configuration  variables
        usable in initialization files" for what is normally the most appropri-
        ate usage.
 
        If you omit to supply any placeholders whatever in the specification of
-       a command, latexmk will supply what its author thinks  are  appropriate
+       a  command,  latexmk will supply what its author thinks are appropriate
        defaults.  This gives compatibility with configuration files for previ-
        ous versions of latexmk, which didn't use placeholders.
 
-       "Detaching"  a  command: Normally when latexmk runs a command, it waits
+       "Detaching" a command: Normally when latexmk runs a command,  it  waits
        for the command to run to completion.  This is appropriate for commands
+       like latex, of course.  But for previewers, the command should normally
+       run  detached,  so that latexmk gets the previewer running and then re-
+       turns to its next task (or exits if there is nothing else to  do).   To
+       achieve  this  effect  of  detaching a command, you need to precede the
+       command name with "start ", as in
 
+            $dvi_previewer = 'start xdvi %O %S';
 
+       This will be translated to whatever is appropriate for  your  operating
+       system.
 
-                                31 January 2024                             35
+       Notes: (1) In some circumstances, latexmk will always run a command de-
+       tached.   This  is the case for a previewer in preview continuous mode,
+       since otherwise previewing continuously makes no sense.  (2) This  pre-
+       cludes  the  possibility  of running a command named start.  (3) If the
+       word start occurs more than  once  at  the  beginning  of  the  command
+       string,  that is equivalent to having just one.  (4) Under cygwin, some
+       complications happen, since cygwin amounts to a complicated merging  of
+       UNIX  and  MS-Windows.   See  the  source code for how I've handled the
+       problem.
 
+       Command names containing spaces: Under MS-Windows it is common that the
 
 
 
+                                 7 April 2024                               36
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       like latex, of course.  But for previewers, the command should normally
-       run detached, so that latexmk gets the previewer running and  then  re-
-       turns  to  its next task (or exits if there is nothing else to do).  To
-       achieve this effect of detaching a command, you  need  to  precede  the
-       command name with "start ", as in
 
-            $dvi_previewer = 'start xdvi %O %S';
 
-       This  will  be translated to whatever is appropriate for your operating
-       system.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-       Notes: (1) In some circumstances, latexmk will always run a command de-
-       tached.  This is the case for a previewer in preview  continuous  mode,
-       since  otherwise previewing continuously makes no sense.  (2) This pre-
-       cludes the possibility of running a command named start.   (3)  If  the
-       word  start  occurs  more  than  once  at  the beginning of the command
-       string, that is equivalent to having just one.  (4) Under cygwin,  some
-       complications  happen, since cygwin amounts to a complicated merging of
-       UNIX and MS-Windows.  See the source code  for  how  I've  handled  the
-       problem.
 
-       Command names containing spaces: Under MS-Windows it is common that the
        name of a command includes spaces, since software is often installed in
        a subdirectory of "C:\Program Files".  Such command names should be en-
        closed in double quotes, as in
@@ -2344,46 +2388,35 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        %S';
             $pdf_previewer   =   'start   "c:/Program   Files/SumatraPDF/Suma-
        traPDF.exe" %O %S';
-            $pdf_previewer  =  'start "c:/Program Files/SumatraPDF (x86)/Suma-
+            $pdf_previewer = 'start "c:/Program  Files/SumatraPDF  (x86)/Suma-
        traPDF.exe" %O %S';
 
 
-       (Note about the above example: Under  MS-Windows  forward  slashes  are
+       (Note  about  the  above  example: Under MS-Windows forward slashes are
        equivalent to backslashes in a filename under almost all circumstances,
-       provided  that  the  filename is inside double quotes.  It is easier to
+       provided that the filename is inside double quotes.  It  is  easier  to
        use forward slashes in examples like the one above, since then one does
-       not have to worry about the rules for dealing with forward  slashes  in
+       not  have  to worry about the rules for dealing with forward slashes in
        strings in the Perl language.)
 
-       Command  names  under  Cygwin: If latexmk is executed by Cygwin's Perl,
+       Command names under Cygwin: If latexmk is executed  by  Cygwin's  Perl,
        be particularly certain that pathnames in commands have forward slashes
-       not the usual backslashes for the  separator  of  pathname  components.
-       See  the  above  examples.  Backslashes often get misinterpreted by the
+       not  the  usual  backslashes  for the separator of pathname components.
+       See the above examples.  Backslashes often get  misinterpreted  by  the
        Unix shell used by Cygwin's Perl to execute external commands.  Forward
        slashes don't suffer from this problem, and (when quoted, as above) are
        equally acceptable to MS-Windows.
 
-       Using MS-Windows file associations: A useful trick  under  modern  ver-
+       Using  MS-Windows  file  associations: A useful trick under modern ver-
        sions of MS-Windows (e.g., WinXP) is to use just the command 'start' by
        itself:
 
             $dvi_previewer = 'start %S';
 
-
-
-                                31 January 2024                             36
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        Under MS-Windows, this will cause to be run whatever program the system
-       has  associated  with  dvi  files.   (The same applies for a postscript
+       has associated with dvi files.  (The  same  applies  for  a  postscript
        viewer and a pdf viewer.)  But note that this trick is not always suit-
-       able for the pdf previwer, if your system has acroread for the  default
+       able  for the pdf previwer, if your system has acroread for the default
        pdf viewer.  As explained elsewhere, acroread under MS-Windows does not
        work well with latex and latexmk, because acroread locks the pdf file.
 
@@ -2392,18 +2425,30 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
             $lpr  = 'NONE lpr';
 
-       This  typically  is  used when an appropriate command does not exist on
+       This typically is used when an appropriate command does  not  exist  on
        your system.  The string after the "NONE" is effectively a comment.
 
        Options to commands: Setting the name of a command can be used not only
        for changing the name of the command called, but also to add options to
-       command.  Suppose you want latexmk to use latex  with  source  specials
-       enabled.   Then  you  might use the following line in an initialization
+       command.   Suppose  you  want latexmk to use latex with source specials
+       enabled.  Then you might use the following line  in  an  initialization
        file:
 
+
+
+
+                                 7 April 2024                               37
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
             $latex = 'latex --src-specials %O %S';
 
-       Running a subroutine instead of an external command: Use  a  specifica-
+       Running  a  subroutine instead of an external command: Use a specifica-
        tion starting with "internal", as in
 
             $latex = 'internal mylatex %O %S';
@@ -2413,78 +2458,95 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
                 return system 'latex', @args;
             }
 
-       For  some  of the more exotic possibilities that then become available,
-       see the section "Advanced configuration: Some extra resources  and  ad-
-       vanced  tricks".  Also  see some of the examples in the directory exam-
+       For some of the more exotic possibilities that then  become  available,
+       see  the  section "Advanced configuration: Some extra resources and ad-
+       vanced tricks". Also see some of the examples in  the  directory  exam-
        ple_rcfiles in the latexmk distribution.
 
-       Advanced tricks: Normally one specifies a single command for  the  com-
-       mands  invoked by latexmk.  Naturally, if there is some complicated ad-
-       ditional processing you need to do in your special situation,  you  can
+       Advanced  tricks:  Normally one specifies a single command for the com-
+       mands invoked by latexmk.  Naturally, if there is some complicated  ad-
+       ditional  processing  you need to do in your special situation, you can
        write a script (or batch file) to do the processing, and then configure
        latexmk to use your script in place of the standard program.
 
-       You  can  also  use a Perl subroutine instead of a script -- see above.
+       You can also use a Perl subroutine instead of a script  --  see  above.
        This is generally the most flexible and portable solution.
 
        It is also possible to configure latexmk to run multiple commands.  For
-       example, if when running pdflatex to generate a pdf  file  from  a  tex
+       example,  if  when  running  pdflatex to generate a pdf file from a tex
        file you need to run another program after pdflatex to perform some ex-
        tra processing, you could do something like:
 
-            $pdflatex  =  'pdflatex  --shell-escape %O %S; pst2pdf_for_latexmk
+            $pdflatex = 'pdflatex --shell-escape  %O  %S;  pst2pdf_for_latexmk
        %B';
 
+       This  definition  assumes  you  are using a UNIX-like system (which in-
+       cludes Linux and OS-X), so that the two commands to be  run  are  sepa-
+       rated by the semicolon in the middle of the string.
 
+       If you are using MS-Windows, you would replace the above line by
 
-                                31 January 2024                             37
+          $pdflatex = 'cmd /c pdflatex --shell-escape %O %S'
+                      . '&& pst2pdf_for_latexmk %B';
 
+       Here,  the  UNIX  command  separator ; is replaced by &&.  In addition,
+       there is a problem that some versions of Perl on MS-Windows do not obey
+       the command separator; this problem is overcome by explicitly  invoking
+       the MS-Windows command-line processor cmd.exe.
 
 
+LIST OF CONFIGURATION VARIABLES USABLE IN INITIALIZATION FILES
+       In  this  section  are  specified the variables whose values can be ad-
+       justed to configure latexmk.   (See  the  earlier  section  "Configura-
+       tion/Initialization  (rc) Files" for the files where the configurations
+       are done.)
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
+                                 7 April 2024                               38
 
-       This definition assumes you are using a  UNIX-like  system  (which  in-
-       cludes  Linux  and  OS-X), so that the two commands to be run are sepa-
-       rated by the semicolon in the middle of the string.
 
-       If you are using MS-Windows, you would replace the above line by
 
-          $pdflatex = 'cmd /c pdflatex --shell-escape %O %S'
-                      . '&& pst2pdf_for_latexmk %B';
 
-       Here, the UNIX command separator ; is replaced  by  &&.   In  addition,
-       there is a problem that some versions of Perl on MS-Windows do not obey
-       the  command separator; this problem is overcome by explicitly invoking
-       the MS-Windows command-line processor cmd.exe.
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-LIST OF CONFIGURATION VARIABLES USABLE IN INITIALIZATION FILES
-       In this section are specified the variables whose  values  can  be  ad-
-       justed  to  configure  latexmk.   (See  the earlier section "Configura-
-       tion/Initialization (rc) Files" for the files where the  configurations
-       are done.)
 
        Default values are indicated in brackets.  Note that for variables that
-       are  boolean  in character, concerning whether latexmk does or does not
-       behave in a certain way, a non-zero value, normally 1, indicates  true,
-       i.e.,  the behavior occurs, while a zero value indicates a false value,
+       are boolean in character, concerning whether latexmk does or  does  not
+       behave  in a certain way, a non-zero value, normally 1, indicates true,
+       i.e., the behavior occurs, while a zero value indicates a false  value,
        i.e., the behavior does not occur.
 
 
+       $allow_subdir_creation [1]
+
+              Specify action to take when message(s) in the .log file indicate
+              a  failure of an attempt by a *latex compilation to write a file
+              to a subdirectory of the output directory because the  subdirec-
+              tory didn't exist.
+
+              If the value if $allow_subdir_creation is 0, no action is taken.
+              If  it  is 1, then the appropriate subdirectory is created and a
+              rerun of *latex is triggered, but only if the file being written
+              is an .aux file.  (This happens, for example,  if  the  document
+              includes  a  file from a subdirectory of the document directory,
+              by the \include command.  If the value of $allow_subdir_creation
+              is 2, then the subdirectory creation is  done  independently  of
+              which type of file is in question.
+
+
        $allow_switch [1]
 
-              This controls what happens when the output extension  of  latex,
-              pdflatex,  lualatex  or  xelatex  differs from what is expected.
+              This  controls  what happens when the output extension of latex,
+              pdflatex, lualatex or xelatex differs  from  what  is  expected.
               (The possible extensions are .dvi, .pdf, .xdv.)  This can happen
-              with the use of the \pdfoutput macro in a document compiled  un-
-              der  latex or pdflatex, or with the use of the \outputmode macro
+              with  the use of the \pdfoutput macro in a document compiled un-
+              der latex or pdflatex, or with the use of the \outputmode  macro
               under lualatex.  It can also happen with certain kinds of incor-
               rect configuration.
 
-              In such a case, latexmk can appropriately adjust its network  of
+              In  such a case, latexmk can appropriately adjust its network of
               rules.  The adjustment is made if $allow_switch is on, and if no
               request for a dvi or ps file has been made.
 
@@ -2492,18 +2554,22 @@ LIST OF CONFIGURATION VARIABLES USABLE IN INITIALIZATION FILES
 
 
        $always_view_file_via_temporary [0]
-              Whether  .ps and .pdf files are initially to be made in a tempo-
-              rary directory and then moved to the final location.  (This  ap-
+              Whether .ps and .pdf files are initially to be made in a  tempo-
+              rary  directory and then moved to the final location.  (This ap-
               plies to dvips, dvipdf, and ps2pdf operations, and the filtering
               operators on .dvi and .ps files.  It does not apply to pdflatex,
-              unfortunately,  since  pdflatex  provides no way of specifying a
+              unfortunately, since pdflatex provides no way  of  specifying  a
               chosen name for the output file.)
 
               This use of a temporary file solves a problem that the making of
+              these files can occupy a substantial time.  If a viewer (notably
+              gv) sees that the file has changed, it may read the new file be-
+              fore the program writing the file has not yet finished its work,
+              which  can cause havoc.
 
 
 
-                                31 January 2024                             38
+                                 7 April 2024                               39
 
 
 
@@ -2512,64 +2578,64 @@ LIST OF CONFIGURATION VARIABLES USABLE IN INITIALIZATION FILES
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              these files can occupy a substantial time.  If a viewer (notably
-              gv) sees that the file has changed, it may read the new file be-
-              fore the program writing the file has not yet finished its work,
-              which  can cause havoc.
-
               See the $pvc_view_file_via_temporary variable for a setting that
-              applies only if preview-continuous mode (-pvc option)  is  used.
+              applies  only  if preview-continuous mode (-pvc option) is used.
               See $tmpdir for the setting of the directory where the temporary
               file is created.
 
 
        $analyze_input_log_always [1]
 
-              After  a run of latex (etc), always analyze .log for input files
-              in the <...> and (...) constructions.  Otherwise,  only  do  the
+              After a run of latex (etc), always analyze .log for input  files
+              in  the  <...>  and (...) constructions.  Otherwise, only do the
               analysis when fls file doesn't exist or is out of date.
 
-              Under  normal  circumstances,  the data in the fls file is reli-
+              Under normal circumstances, the data in the fls  file  is  reli-
               able, and the test of the log file gets lots of false positives;
-              usually $analyze_input_log_always is best set to zero.  But  the
-              test  of the log file is needed at least in the following situa-
-              tion: When a user needs to persuade latexmk that a certain  file
-              is  a  source file, and latexmk doesn't otherwise find it.  Then
-              the user can write code that causes a  line  with  (...)  to  be
-              written  to log file.  One important case is for lualatex, which
-              doesn't always generate lines in the .fls  file  for  input  lua
-              files.   (The  situation  with lualatex is HIGHLY version depen-
-              dent, e.g., there was a big  change  between  TeXLive  2016  and
+              usually  $analyze_input_log_always is best set to zero.  But the
+              test of the log file is needed at least in the following  situa-
+              tion:  When a user needs to persuade latexmk that a certain file
+              is a source file, and latexmk doesn't otherwise find  it.   Then
+              the  user  can  write  code  that causes a line with (...) to be
+              written to log file.  One important case is for lualatex,  which
+              doesn't  always  generate  lines  in the .fls file for input lua
+              files.  (The situation with lualatex is  HIGHLY  version  depen-
+              dent,  e.g.,  there  was  a  big change between TeXLive 2016 and
               TeXLive 2017.)
 
-              To  keep  backward compatibility with older versions of latexmk,
+              To keep backward compatibility with older versions  of  latexmk,
               the default is to set $analyze_input_log_always to 1.
 
 
        $auto_rc_use [1]
-              Whether to automatically read the standard  initialization  (rc)
+              Whether  to  automatically read the standard initialization (rc)
               files, which are the system RC file, the user's RC file, and the
               RC file in the current directory.  The command line option -norc
-              can  be used to turn this setting off.  Each RC file co2uld also
-              turn this setting off, i.e., it could set $auto_rc_use  to  zero
+              can be used to turn this setting off.  Each RC file  could  also
+              turn  this  setting off, i.e., it could set $auto_rc_use to zero
               to prevent automatic reading of the later RC files.
 
-              This  variable does not affect the reading of RC files specified
+              This variable does not affect the reading of RC files  specified
               on the command line by the -r option.
 
        $aux_dir [""]
-              The aux directory, i.e., the directory in which auxiliary  files
+              The  aux directory, i.e., the directory in which auxiliary files
               (aux, log, etc) are to be written by a run of *latex.
 
-              If  this  variable is not set, but $out_dir is set, then latexmk
-              takes the aux directory to equal the output directory  which  is
+              If this variable is not set, but $out_dir is set,  then  latexmk
+              takes  the  aux directory to equal the output directory which is
               the directory to which final output files are to be written.
 
-              If  neither  variable  is  set,  then the current directory when
+              If neither variable is set, then the current directory when *la-
+              tex is invoked is used both for the aux and output directories.
+
+              If the aux and output directories are distinct, then the aux di-
+              rectory contains all generated files with the exception of  "fi-
+              nal  output  files",  which  are  defined to be .dvi, .ps, .pdf,
 
 
 
-                                31 January 2024                             39
+                                 7 April 2024                               40
 
 
 
@@ -2578,64 +2644,64 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              *latex is invoked is used both for the aux and  output  directo-
-              ries.
-
-              If the aux and output directories are distinct, then the aux di-
-              rectory  contains all generated files with the exception of "fi-
-              nal output files", which are defined  to  be  .dvi,  .ps,  .pdf,
               .synctex, and .synctex.gz files.
 
-              See  the  section  AUXILIARY AND OUTPUT DIRECTORIES for more de-
+              See the section AUXILIARY AND OUTPUT DIRECTORIES  for  more  de-
               tails.
 
 
 
        $aux_out_dir_report [0]
-              If this variable is set to 1, then prior to  the  processing  of
+              If  this  variable  is set to 1, then prior to the processing of
               each primary .tex file, list the settings for aux and output di-
-              rectories,  after  they  have  been normalized from the settings
+              rectories, after they have been  normalized  from  the  settings
               specified during initialization.
 
-              This report gives a reminder of  where  to  look  for  generated
+              This  report  gives  a  reminder  of where to look for generated
               files.
 
-              The  report  is  done per primary .tex file, because of possible
-              directory changes for each file (when the -cd option  is  used).
+              The report is done per primary .tex file,  because  of  possible
+              directory  changes  for each file (when the -cd option is used).
               In the simplest cases, the directory names are the same as orig-
               inally specified.  But in general some clean up/normalization is
-              performed;  this  helps  performance and cleans up output to the
+              performed; this helps performance and cleans up  output  to  the
               screen.
 
               If this variable is set to 2, then halt after reporting the set-
-              tings for the aux and out directories,  rather  than  continuing
-              with  processing  of  tex files.  This setting is primarily used
-              for debugging configuration issues.   See  the  -dir-report-only
+              tings  for  the  aux and out directories, rather than continuing
+              with processing of tex files.  This setting  is  primarily  used
+              for  debugging  configuration  issues.  See the -dir-report-only
               option.
 
 
        $bad_warning_is_error [0]
-              Whether  to treat bad warnings reported by *latex in log file as
-              errors. The  specifications  of  the  warning  messages  are  in
+              Whether to treat bad warnings reported by *latex in log file  as
+              errors.  The  specifications  of  the  warning  messages  are in
               @bad_warnings.
 
 
        @bad_warnings
-              Array  of  regular  expressions  specifying messages in log file
-              that are officially treated as warnings rather  than  errors  by
-              *latex,  but  which  a  user may treat as errors: See $bad_warn-
+              Array of regular expressions specifying  messages  in  log  file
+              that  are  officially  treated as warnings rather than errors by
+              *latex, but which a user may treat  as  errors:  See  $bad_warn-
               ing_is_error.
 
-              Currently the default set of these warnings is those about  \end
+              Currently  the default set of these warnings is those about \end
               occurring inside constructs.
 
 
        $banner [0]
-              If  nonzero, the banner message is printed across each page when
+              If nonzero, the banner message is printed across each page  when
+              converting  the  dvi  file to postscript.  Without modifying the
+              variable $banner_message, this is equivalent to  specifying  the
+              -d option.
 
+              Note that if $banner is nonzero, the $postscript_mode is assumed
+              and the postscript file is always generated, even if it is newer
 
 
-                                31 January 2024                             40
+
+                                 7 April 2024                               41
 
 
 
@@ -2644,17 +2710,11 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              converting the dvi file to postscript.   Without  modifying  the
-              variable  $banner_message,  this is equivalent to specifying the
-              -d option.
-
-              Note that if $banner is nonzero, the $postscript_mode is assumed
-              and the postscript file is always generated, even if it is newer
               than the dvi file.
 
        $banner_intensity [0.95]
               Equivalent to the -bi option, this is a decimal number between 0
-              and 1 that specifies how dark to print the banner message. 0  is
+              and  1 that specifies how dark to print the banner message. 0 is
               black, 1 is white.  The default is just right if your toner car-
               tridge isn't running too low.
 
@@ -2663,19 +2723,19 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               dvi file to postscript.  This is equivalent to the -bm option.
 
        $banner_scale [220.0]
-              A  decimal  number  that  specifies how large the banner message
-              will be printed.  Experimentation is necessary to get the  right
-              scale  for  your message, as a rule of thumb the scale should be
-              about equal to 1100 divided by the number of characters  in  the
-              message.   The  Default  is just right for 5 character messages.
+              A decimal number that specifies how  large  the  banner  message
+              will  be printed.  Experimentation is necessary to get the right
+              scale for your message, as a rule of thumb the scale  should  be
+              about  equal  to 1100 divided by the number of characters in the
+              message.  The Default is just right for  5  character  messages.
               This is equivalent to the -bs option.
 
        @BIBINPUTS
-              This is an array variable, now mostly obsolete,  that  specifies
-              directories  where  latexmk  should look for .bib files.  By de-
-              fault it is set from the BIBINPUTS environment variable  of  the
-              operating  system.   If  that environment variable is not set, a
-              single element list consisting of the current directory is  set.
+              This  is  an array variable, now mostly obsolete, that specifies
+              directories where latexmk should look for .bib  files.   By  de-
+              fault  it  is set from the BIBINPUTS environment variable of the
+              operating system.  If that environment variable is  not  set,  a
+              single  element list consisting of the current directory is set.
               The format of the directory names depends on your operating sys-
               tem, of course.  Examples for setting this variable are:
 
@@ -2685,59 +2745,61 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
                       @BIBINPUTS = ( ".", "//server/bibfiles" );
                       @BIBINPUTS = ( ".", "/usr/local/texmf/bibtex/bib" );
 
-              Note  that  under  MS  Windows,  either a forward slash "/" or a
-              backward slash "\" can be used to separate pathname  components,
-              so  the  first  two  and the second two examples are equivalent.
-              Each backward slash should be doubled to avoid running afoul  of
-              Perl's  rules for writing strings. Generally, it is simplest al-
+              Note that under MS Windows, either a  forward  slash  "/"  or  a
+              backward  slash "\" can be used to separate pathname components,
+              so the first two and the second  two  examples  are  equivalent.
+              Each  backward slash should be doubled to avoid running afoul of
+              Perl's rules for writing strings. Generally, it is simplest  al-
               ways to use forward slashes instead of backward slashes.
 
               Important note: This variable is now mostly obsolete in the cur-
-              rent version of latexmk, since it now uses a  better  method  of
-              searching  for  files  using the kpsewhich command.  However, if
+              rent  version  of  latexmk, since it now uses a better method of
+              searching for files using the kpsewhich  command.   However,  if
               your system is an unusual one without the kpsewhich command, you
               may need to set the variable @BIBINPUTS.
 
 
+       $biber ["biber %O %S"]
+              The biber processing program.
 
 
-                                31 January 2024                             41
 
 
 
 
+                                 7 April 2024                               42
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       $biber ["biber %O %S"]
-              The biber processing program.
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        $biber_silent_switch ["--onlylog"]
-              Switch(es) for the biber processing program when silent mode  is
+              Switch(es)  for the biber processing program when silent mode is
               on.
 
        $bibtex ["bibtex %O %S"]
               The BibTeX processing program.
 
        $bibtex_fudge [1]
-              When  using  bibtex, whether to change directory to $aux_dir be-
+              When using bibtex, whether to change directory to  $aux_dir  be-
               fore running bibtex.
 
               The need arises as follows:
 
-              a. With bibtex before about 2019, if the filename  given  to  it
+              a.  With  bibtex  before about 2019, if the filename given to it
               contains a path component, there was a bug that bibtex would not
-              find  extra  aux  files,  as produced by the \include command in
+              find extra aux files, as produced by  the  \include  command  in
               TeX.
 
-              b. With all moderately recent versions  of  bibtex,  bibtex  may
+              b.  With  all  moderately  recent versions of bibtex, bibtex may
               refuse to write its bbl and blg files, for security reasons, for
               certain cases of the path component of the filename given to it.
 
-              However,  there  are  also rare cases where the change-directory
-              method prevents bibtex from finding certain bib  or  bst  files.
+              However, there are also rare cases  where  the  change-directory
+              method  prevents  bibtex  from finding certain bib or bst files.
               Then $bibtex_fudge needs to be set to 0.
 
 
@@ -2748,26 +2810,30 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
        $bibtex_use [1]
               Under what conditions to run bibtex or biber.  When latexmk dis-
-              covers  from the log file that one (or more) bibtex/biber-gener-
-              ated bibliographies are used, it can run bibtex or  biber  when-
-              ever  it  appears  necessary  to regenerate the bbl file(s) from
-              their source bib  database  file(s).   But  sometimes,  the  bib
+              covers from the log file that one (or more)  bibtex/biber-gener-
+              ated  bibliographies  are used, it can run bibtex or biber when-
+              ever it appears necessary to regenerate  the  bbl  file(s)  from
+              their  source  bib  database  file(s).   But  sometimes, the bib
               file(s) are not available (e.g., for a document obtained from an
               external archive), but the bbl files are provided.  In that case
-              use  of  bibtex or biber will result in incorrect overwriting of
-              the precious  bbl  files.   The  variable  $bibtex_use  controls
-              whether  this  happens,  and  also  controls whether or not .bbl
+              use of bibtex or biber will result in incorrect  overwriting  of
+              the  precious  bbl  files.   The  variable  $bibtex_use controls
+              whether this happens, and also  controls  whether  or  not  .bbl
               files are deleted in a cleanup operation.
 
               The possible values of $bibtex_use are:
-                0: never use bibtex or biber; never delete  .bbl  files  in  a
+                0:  never  use  bibtex  or biber; never delete .bbl files in a
               cleanup.
                 1: only use bibtex or biber if the bib file(s) exist; never
                 delete .bbl files in a cleanup.
+                1.5: only use bibtex or biber if the bib files exist;
+                conditionally delete .bbl files in  a  cleanup  (i.e.,  delete
+              them only when
+                the bib files all exist).
 
 
 
-                                31 January 2024                             42
+                                 7 April 2024                               43
 
 
 
@@ -2776,64 +2842,64 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-                1.5: only use bibtex or biber if the bib files exist;
-                conditionally  delete  .bbl  files  in a cleanup (i.e., delete
-              them only when
-                the bib files all exist).
                 2: run bibtex or biber whenever it appears necessary to update
-              the bbl file(s), without testing for the existence  of  the  bib
+              the  bbl  file(s),  without testing for the existence of the bib
               files; always delete .bbl files in a cleanup.
 
-              Note:  When biber is being used, conditional use of biber can be
-              problematic.  From latexmk's point of view the problem  is  that
+              Note: When biber is being used, conditional use of biber can  be
+              problematic.   From  latexmk's point of view the problem is that
               because of how biber works, a full knowledge of its source files
               can only be obtained after running biber.  In contrast, for bib-
-              tex,  full  information  on which bib files are used is obtained
+              tex, full information on which bib files are  used  is  obtained
               from the .aux file(s) after a run of *latex.  But for biber, the
-              corresponding information is somewhat incomplete; this  the  in-
-              formation  obtained  in  the  .bcf file that is generated by the
+              corresponding  information  is somewhat incomplete; this the in-
+              formation obtained in the .bcf file that  is  generated  by  the
               biblatex package during a run of *latex.
 
 
        $cleanup_includes_cusdep_generated [0]
-              If nonzero, specifies that cleanup also deletes files  that  are
+              If  nonzero,  specifies that cleanup also deletes files that are
               generated by custom dependencies.  (When doing a clean up, e.g.,
               by use of the -C option, custom dependencies are those listed in
               the .fdb_latexmk file from a previous run.)
 
 
        $cleanup_includes_generated [0]
-              If  nonzero,  specifies that cleanup also deletes files that are
+              If nonzero, specifies that cleanup also deletes files  that  are
               detected in the fls file (or failing that, in log file) as being
-              generated.  It will also include files  made  from  these  first
+              generated.   It  will  also  include files made from these first
               generation generated files.
 
-              This  operation  is  somewhat dangerous, and can have unintended
-              consequences, since the files to be deleted are determined  from
-              a  file  created by *latex, which can contain erroneous informa-
+              This operation is somewhat dangerous, and  can  have  unintended
+              consequences,  since the files to be deleted are determined from
+              a file created by *latex, which can contain  erroneous  informa-
               tion. Therefore this variable is turned off by default, and then
               files to be deleted are restricted to those explicitly specified
-              by   patterns   configured   in   the    variables    clean_ext,
+              by    patterns    configured   in   the   variables   clean_ext,
               clean_full_ext, and @generated_exts.  Standard cases (e.g., .log
-              files)  appear  in latexmk's initial value for the array @gener-
+              files) appear in latexmk's initial value for the  array  @gener-
               ated_exts.
 
        $cleanup_mode [0]
-              If nonzero, specifies cleanup mode: 1 for full  cleanup,  2  for
-              cleanup  except  for .dvi, .ps and .pdf files, 3 for cleanup ex-
-              cept for dep and aux files.  (There is also  extra  cleaning  as
+              If  nonzero,  specifies  cleanup mode: 1 for full cleanup, 2 for
+              cleanup except for .dvi, .ps and .pdf files, 3 for  cleanup  ex-
+              cept  for  dep  and aux files.  (There is also extra cleaning as
               specified by the $clean_ext, $clean_full_ext and @generated_exts
               variables.)
 
-              This  variable  is  equivalent to specifying one of the -c or -C
-              options.  But there should be no need to set this variable  from
+              This variable is equivalent to specifying one of the  -c  or  -C
+              options.   But there should be no need to set this variable from
               an RC file.
 
+       $clean_ext [""]
+              Extra extensions of files for latexmk to remove when any of  the
+              clean-up  options  (-c  or  -C)  is selected.  The value of this
+              variable is a string  containing  the  extensions  separated  by
+              spaces.
 
 
 
-
-                                31 January 2024                             43
+                                 7 April 2024                               44
 
 
 
@@ -2842,12 +2908,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       $clean_ext [""]
-              Extra  extensions of files for latexmk to remove when any of the
-              clean-up options (-c or -C) is  selected.   The  value  of  this
-              variable  is  a  string  containing  the extensions separated by
-              spaces.
-
               It is also possible to specify a more general pattern of file to
               be deleted, by using the place holder %R, as in commands, and it
               is also possible to use wildcards.  Thus setting
@@ -2856,116 +2916,122 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               files-%R/*";
 
               in an initialization file will imply that when a clean-up opera-
-              tion  is  specified,  not  only  is  the  standard  set of files
-              deleted, but also files of the form FOO.out,  FOO-blx.bib,  FOO-
-              figures*.log,  and  pythontex-files-FOO/*,  where FOO stands for
+              tion is specified,  not  only  is  the  standard  set  of  files
+              deleted,  but  also files of the form FOO.out, FOO-blx.bib, FOO-
+              figures*.log, and pythontex-files-FOO/*, where  FOO  stands  for
               the basename of the file being processed (as in FOO.tex).
 
-              Most of the files to be deleted are relative  to  the  directory
-              specified  by  $aux_dir.  Note that if $out_dir but not $aux_dir
-              is set, then in its initialization, latexmk sets $aux_dir  equal
-              to  $out_dir.   A  normal  situation  is therefore that $aux_dir
-              equals $out_dir, which is the only case  directly  supported  by
-              TeXLive,  unlike  MiKTeX.   Note  that even with TeXLive latexmk
+              Most  of  the  files to be deleted are relative to the directory
+              specified by $aux_dir.  Note that if $out_dir but  not  $aux_dir
+              is  set, then in its initialization, latexmk sets $aux_dir equal
+              to $out_dir.  A normal  situation  is  therefore  that  $aux_dir
+              equals  $out_dir,  which  is the only case directly supported by
+              TeXLive, unlike MiKTeX.  Note that  even  with  TeXLive  latexmk
               does now support different values for the directories -- see the
               explanation of the $emulate_aux variable.
 
               If $out_dir and $aux_dir different, latexmk actually deletes any
               files of the specified names in both $aux_dir and $out_dir; this
-              is because under certain error conditions, the files may be  put
-              in  $out_dir instead of $aux_dir.  This also handles the case of
+              is  because under certain error conditions, the files may be put
+              in $out_dir instead of $aux_dir.  This also handles the case  of
               deleting any fls file, since that file is in $out_dir.
 
-              The filenames specified for a clean-up operation can  refer  not
-              only  to regular files but also to directories.  Directories are
+              The  filenames  specified for a clean-up operation can refer not
+              only to regular files but also to directories.  Directories  are
               only deleted if they are empty.  An example of an application is
-              to pythontex, which creates files  in  a  particular  directory.
-              You  can  arrange  to remove both the files and the directory by
+              to  pythontex,  which  creates  files in a particular directory.
+              You can arrange to remove both the files and  the  directory  by
               setting
 
                   $clean_ext = "pythontex-files-%R/* pythontex-files-%R";
 
-              See also the (array) variable  @generated_exts.   In  the  past,
-              this  variable  had certain uses beyond that of $clean_ext.  But
-              now, they accomplish the same things.  In fact,  after  initial-
-              ization  including  the  processing of command line options, la-
+              See  also  the  (array)  variable @generated_exts.  In the past,
+              this variable had certain uses beyond that of  $clean_ext.   But
+              now,  they  accomplish the same things.  In fact, after initial-
+              ization including the processing of command  line  options,  la-
               texmk simply appends the list of extensions in $clean_ext to the
               array @generated_exts.
 
        $clean_full_ext [""]
-              Extra extensions of files for latexmk to remove when the -C  op-
-              tion  is  selected, i.e., extensions of files to remove when the
+              Extra  extensions of files for latexmk to remove when the -C op-
+              tion is selected, i.e., extensions of files to remove  when  the
               .dvi, etc files are to be cleaned-up.
 
+              More general patterns are allowed, as for $clean_ext.
 
+              The  files  specified by $clean_full_ext to be deleted are rela-
+              tive to the directory specified by $out_dir.
 
-                                31 January 2024                             44
 
 
 
+                                 7 April 2024                               45
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              More general patterns are allowed, as for $clean_ext.
 
-              The files specified by $clean_full_ext to be deleted  are  rela-
-              tive to the directory specified by $out_dir.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        $compiling_cmd [""], $failure_cmd [""], $warning_cmd [""], $success_cmd
        [""]
 
-              These  variables  specify  commands that are executed at certain
-              points of compilations.  One motivation for their  existence  is
-              to  allow  very useful convenient visual indications of compila-
-              tion status even when the window receiving the screen output  of
-              the  compilation is hidden.  This is particularly useful in pre-
+              These variables specify commands that are  executed  at  certain
+              points  of  compilations.  One motivation for their existence is
+              to allow very useful convenient visual indications  of  compila-
+              tion  status even when the window receiving the screen output of
+              the compilation is hidden.  This is particularly useful in  pre-
               view-continuous mode.
 
-              The commands are executed  at  the  following  points:  $compil-
-              ing_cmd  at the start of compilation, $success_cmd at the end of
-              a completely successful compilation, $failure_cmd at the end  of
+              The  commands  are  executed  at  the following points: $compil-
+              ing_cmd at the start of compilation, $success_cmd at the end  of
+              a  completely successful compilation, $failure_cmd at the end of
               an unsuccessful compilation, $warning_cmd at the of an otherwise
               successful compilation that gives warnings about undefined cita-
               tions or references or about multiply defined references. If any
-              of  above  variables  is  undefined or blank (the default situa-
+              of above variables is undefined or  blank  (the  default  situa-
               tion), then the corresponding command is not executed.
 
-              However, when $warning_cmd is not set, then in  the  case  of  a
-              compilation  with  warnings  about  references or citations, but
-              with no other error, one or  other  of  $success_cmd  or  $fail-
-              ure_cmd  is  used  (if  it  is  set) according to the setting of
+              However,  when  $warning_cmd  is  not set, then in the case of a
+              compilation with warnings about  references  or  citations,  but
+              with  no  other  error,  one  or other of $success_cmd or $fail-
+              ure_cmd is used (if it is  set)  according  to  the  setting  of
               $warnings_as_errors.
 
               An example of a simple setting of these variables is as follows
 
-                  $compiling_cmd = "xdotool search  --name  \"%D\"  set_window
+                  $compiling_cmd  =  "xdotool  search --name \"%D\" set_window
               --name \"%D compiling\"";
-                  $success_cmd    =  "xdotool  search --name \"%D\" set_window
+                  $success_cmd   = "xdotool search  --name  \"%D\"  set_window
               --name \"%D OK\"";
                   $warning_cmd   = "xdotool search --name \"%D\" ".
                                    "set_window --name \"%D CITE/REF ISSUE\"";
-                  $failure_cmd   = "xdotool search  --name  \"%D\"  set_window
+                  $failure_cmd    =  "xdotool  search --name \"%D\" set_window
               --name \"%D FAILURE\"";
 
-              These  assume  that  the  program xdotool is installed, that the
-              previewer is using an X-Window system for display, and that  the
-              title  of the window contains the name of the displayed file, as
-              it normally does.  When the commands are  executed,  the  place-
-              holder  string  %D  is  replaced  by the name of the destination
+              These assume that the program xdotool  is  installed,  that  the
+              previewer  is using an X-Window system for display, and that the
+              title of the window contains the name of the displayed file,  as
+              it  normally  does.   When the commands are executed, the place-
+              holder string %D is replaced by  the  name  of  the  destination
               file, which is the previewed file.  The above commands result in
               an appropriate string being appended to the filename in the win-
               dow title: " compiling", " OK", or " FAILURE".
 
-              Other placeholders that can be used are %S, %T, and %R, with  %S
-              and  %T normally being identical. These can be useful for a com-
-              mand  changing  the  title  of  the  edit  window.  The   visual
+              Other  placeholders that can be used are %S, %T, and %R, with %S
+              and %T normally being identical. These can be useful for a  com-
+              mand  changing  the title of the edit window. The visual indica-
+              tion in a window title can useful, since the user does not  have
+              to  keep shifting attention to the (possibly hidden) compilation
+              window to know the status of the compilation.
+
+              More complicated situations can best be handled  by  defining  a
+              Perl  subroutine to invoke the necessary commands, and using the
 
 
 
-                                31 January 2024                             45
+                                 7 April 2024                               46
 
 
 
@@ -2974,12 +3040,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              indication in a window title can useful, since the user does not
-              have  to keep shifting attention to the (possibly hidden) compi-
-              lation window to know the status of the compilation.
-
-              More complicated situations can best be handled  by  defining  a
-              Perl  subroutine to invoke the necessary commands, and using the
               "internal" keyword in the definitions to get the  subroutine  to
               be invoked.  (See the section "Format of Command Specifications"
               for how to do this.)
@@ -3028,10 +3088,16 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               current  directory.  This is a convenience: just run latexmk and
               it will process an appropriate set of files.  But sometimes  you
               want only some of these files to be processed.  In this case you
+              can  list the files to be processed by setting @default_files in
+              an initialization file (e.g., the file "latexmkrc" in  the  cur-
+              rent  directory).  Then if no files are specified on the command
+              line then the files you specify by  setting  @default_files  are
+              processed.
 
 
 
-                                31 January 2024                             46
+
+                                 7 April 2024                               47
 
 
 
@@ -3040,12 +3106,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              can  list the files to be processed by setting @default_files in
-              an initialization file (e.g., the file "latexmkrc" in  the  cur-
-              rent  directory).  Then if no files are specified on the command
-              line then the files you specify by  setting  @default_files  are
-              processed.
-
               Three examples:
 
                    @default_files = ("paper_current");
@@ -3094,26 +3154,26 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               Name of file to receive list(s) of dependencies at the end of  a
               run,  to be used if $dependents_list is set.  If the filename is
               "-", then the dependency list is set to stdout  (i.e.,  normally
+              the screen).
 
 
+       $do_cd [0]
+              Whether  to  change working directory to the directory specified
+              for the main source file  before  processing  it.   The  default
 
-                                31 January 2024                             47
 
 
+                                 7 April 2024                               48
 
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              the screen).
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       $do_cd [0]
-              Whether  to  change working directory to the directory specified
-              for the main source file before processing it.  The default  be-
-              havior  is  not to do this, which is the same as the behavior of
-              *latex programs.  This variable is set by the -cd and  -cd-  op-
+              behavior is not to do this, which is the same as the behavior of
+              *latex  programs.   This variable is set by the -cd and -cd- op-
               tions on latexmk's command line.
 
        $dvi_filter [empty]
@@ -3122,64 +3182,64 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        $dvilualatex ["dvilualatex %O %S"]
-              Specifies  the  command  line to invoke the dvilualatex program.
-              Note that as with other programs, you can use this variable  not
-              just  to  change  the name of the program used, but also specify
+              Specifies the command line to invoke  the  dvilualatex  program.
+              Note  that as with other programs, you can use this variable not
+              just to change the name of the program used,  but  also  specify
               options to the program.  E.g.,
 
-                                  $dvilualatex =  "dvilualatex  --src-specials
+                                  $dvilualatex  =  "dvilualatex --src-specials
               %O %S";
 
-              To  do  a  coordinated setting of all of $dvilualatex, $hilatex,
+              To do a coordinated setting of all  of  $dvilualatex,  $hilatex,
               $latex, $pdflatex, $lualatex, and $xelatex, see the section "Ad-
               vanced Configuration".
 
 
        $dvi_mode [See below for default]
-              If one, generate a dvi version of the document by use of  latex.
+              If  one, generate a dvi version of the document by use of latex.
               Equivalent to the -dvi option.
 
               If 2, generate a dvi version of the document by use of dviluala-
               tex.  Equivalent to the -dvilua option.
 
-              The  variable  $dvi_mode  defaults  to 0, but if no explicit re-
-              quests are made for other types of file (postscript, pdf),  then
-              $dvi_mode  will  be  set  to 1.  In addition, if a request for a
-              file for which a .dvi file is a prerequisite  and  $dvi_mode  is
+              The variable $dvi_mode defaults to 0, but  if  no  explicit  re-
+              quests  are made for other types of file (postscript, pdf), then
+              $dvi_mode will be set to 1.  In addition, if  a  request  for  a
+              file  for  which  a .dvi file is a prerequisite and $dvi_mode is
               zero, then $dvi_mode is set to 1.
 
 
 
        $dvilualatex_silent_switch ["-interaction=batchmode"]
-              Switch(es)  for  the dvilualatex program (specified in the vari-
+              Switch(es) for the dvilualatex program (specified in  the  vari-
               able $dvilualatex) when silent mode is on.
 
-              See details of the $latex_silent_switch  for  other  information
+              See  details  of  the $latex_silent_switch for other information
               that equally applies to $dvilualatex_silent_switch.
 
 
        $dvi_previewer ["start xdvi %O %S" under UNIX]
-              The  command  to  invoke a dvi-previewer.  [Under MS-Windows the
+              The command to invoke a dvi-previewer.   [Under  MS-Windows  the
+              default  is "start"; then latexmk arranges to use the MS-Windows
+              start program, which will cause to be run whatever  command  the
+              system has associated with .dvi files.]
 
+              Important  note:  Normally you will want to have a previewer run
+              detached, so that latexmk doesn't  wait  for  the  previewer  to
 
 
-                                31 January 2024                             48
 
+                                 7 April 2024                               49
 
 
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-              default is "start"; then latexmk arranges to use the  MS-Windows
-              start  program,  which will cause to be run whatever command the
-              system has associated with .dvi files.]
 
-              Important note: Normally you will want to have a  previewer  run
-              detached, so that latexmk doesn't wait for the previewer to ter-
-              minate  before continuing its work.  So normally you should pre-
-              fix the command by "start ", which  flags  to  latexmk  that  it
+              terminate  before  continuing  its work.  So normally you should
+              prefix the command by "start ", which flags to latexmk  that  it
               should  do  the  detaching  of the previewer itself (by whatever
               method is appropriate to the operating system).   But  sometimes
               letting latexmk do the detaching is not appropriate (for a vari-
@@ -3227,26 +3287,27 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               Switch(es) for dvips program when pdf file is  to  be  generated
               from .ps file.
 
+       $dvips_silent_switch ["-q"]
+              Switch(es) for dvips program when silent mode is on.
 
+       $dvi_update_command [""]
+              When  the  dvi  previewer  is  set  to  be  updated by running a
 
-                                31 January 2024                             49
 
 
+                                 7 April 2024                               50
 
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       $dvips_silent_switch ["-q"]
-              Switch(es) for dvips program when silent mode is on.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-       $dvi_update_command [""]
-              When  the  dvi  previewer is set to be updated by running a com-
-              mand, this is the command that is run.  See the information  for
-              the variable $dvi_update_method for further information, and see
-              information  on  the  variable $pdf_update_method for an example
-              for the analogous case of a pdf previewer.
+
+              command, this is the command that is run.  See  the  information
+              for the variable $dvi_update_method for further information, and
+              see  information on the variable $pdf_update_method for an exam-
+              ple for the analogous case of a pdf previewer.
 
        $dvi_update_method [2 under UNIX, 1 under MS-Windows]
               How the dvi viewer updates its display when  the  dvi  file  has
@@ -3273,7 +3334,7 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               variable  $dvi_update_method.   The default value is the one ap-
               propriate for xdvi on a UNIX system.
 
-       $emulate_aux [0]
+       $emulate_aux [1]
               Whether to emulate the use of aux directory  when  $aux_dir  and
               $out_dir are different, rather than using the -aux-directory op-
               tion  for the *latex programs.  (MiKTeX supports -aux-directory,
@@ -3291,21 +3352,22 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               output directory provided to *latex is set to be the desired aux
               directory. After that, any files that need to be in  the  output
               directory  will  be moved there by latexmk. (These are the files
-              with extensions .dvi, .ps,  .pdf,  .synctex,  .synctex.gz,  and,
+              with extensions .dvi, .ps, .pdf, .synctex, .synctex.gz, and, de-
+              pending on the setting of the $fls_uses_out_dir  variable,  also
+              the .fls file.)
 
 
 
-                                31 January 2024                             50
 
 
 
+                                 7 April 2024                               51
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              depending on the setting of the $fls_uses_out_dir variable, also
-              the .fls file.)
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
        $failure_cmd [undefined]
@@ -3357,11 +3419,15 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               latexmk needs to determine whether a particular  file  has  been
               produced  during a just-concluded run of some rule/program or is
               leftover from a previous run. (An example is the production of a
-              .bcf file by the biblatex package during  a  run  of  *latex  to
+              .bcf file by the biblatex package during a run of *latex to pro-
+              vide bibliographic information to the biber program.  If a  .bcf
+              file  is  not  produced  during  a current run of *latex, but is
+              leftover from a previous run, then latexmk has to conclude  that
+              the  .tex  document has changed so that biber is no longer to be
 
 
 
-                                31 January 2024                             51
+                                 7 April 2024                               52
 
 
 
@@ -3370,10 +3436,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              provide  bibliographic  information  to the biber program.  If a
-              .bcf file is not produced during a current run of *latex, but is
-              leftover from a previous run, then latexmk has to conclude  that
-              the  .tex  document has changed so that biber is no longer to be
               used.)
 
               Latexmk's criterion that a file has been produced during  a  run
@@ -3424,21 +3486,21 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        'out', 'toc', 'blg', 'ilg', 'log', 'xdv' )]
 
               This  contains a list of extensions for files that are generated
+              during processing, and that should  be  deleted  during  a  main
+              clean  up  operation,  as invoked by the command line option -c.
+              (The use of -C or -gg gives this clean up and more.)
 
 
 
-                                31 January 2024                             52
 
+                                 7 April 2024                               53
 
 
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-              during processing, and that should  be  deleted  during  a  main
-              clean  up  operation,  as invoked by the command line option -c.
-              (The use of -C or -gg gives this clean up and more.)
 
               The default values are extensions for standard  files  generated
               by  *latex,  bibtex, and the like.  (Note that the clean up also
@@ -3490,10 +3552,14 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               changed.  But consider for example a latex package  that  causes
               an  encapsulated postscript file (an "eps" file) to be made that
               is to be read in on the next run.  The file contains  a  comment
+              line  giving  its  creation  date and time.  On the next run the
+              time changes, latex sees that the  eps  file  has  changed,  and
+              therefore  reruns  latex.  This causes an infinite loop, that is
+              only terminated because latexmk has a limit  on  the  number  of
 
 
 
-                                31 January 2024                             53
+                                 7 April 2024                               54
 
 
 
@@ -3502,10 +3568,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              line  giving  its  creation  date and time.  On the next run the
-              time changes, latex sees that the  eps  file  has  changed,  and
-              therefore  reruns  latex.  This causes an infinite loop, that is
-              only terminated because latexmk has a limit  on  the  number  of
               runs to guard against pathological situations.
 
               But the changing line has no real effect, since it is a comment.
@@ -3556,10 +3618,14 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
        $jobname [""]
 
               This  specifies the jobname, i.e., the basename that is used for
+              generated files (.aux, .log, .dvi, .ps,  .pdf,  etc).   If  this
+              variable  is a null string, then the basename is the basename of
+              the main tex file.  (At present, the string in  $jobname  should
+              not contain spaces.)
 
 
 
-                                31 January 2024                             54
+                                 7 April 2024                               55
 
 
 
@@ -3568,11 +3634,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              generated files (.aux, .log, .dvi, .ps,  .pdf,  etc).   If  this
-              variable  is a null string, then the basename is the basename of
-              the main tex file.  (At present, the string in  $jobname  should
-              not contain spaces.)
-
               The  placeholder  '%A' is permitted. This will be substituted by
               the basename of the TeX file.  The primary purpose is when a va-
               riety of tex files are to be processed, and you want  to  use  a
@@ -3622,10 +3683,15 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               .bib files.
 
 
+       $kpsewhich_show [0]
+              Whether  to show diagnostics about invocations of kpsewhich: the
+              command line use to invoke it and the results.   These  diagnos-
+              tics  are shown if $kpsewhich_show is non-zero or if diagnostics
+              mode is on.  (But in the second case, lots of other  diagnostics
 
 
 
-                                31 January 2024                             55
+                                 7 April 2024                               56
 
 
 
@@ -3634,11 +3700,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       $kpsewhich_show [0]
-              Whether  to show diagnostics about invocations of kpsewhich: the
-              command line use to invoke it and the results.   These  diagnos-
-              tics  are shown if $kpsewhich_show is non-zero or if diagnostics
-              mode is on.  (But in the second case, lots of other  diagnostics
               are  also  shown.)   Without  these diagnostics there is nothing
               visible in latexmk's screen output about  invocations  of  kpse-
               which.
@@ -3689,9 +3750,14 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
                   add_input_ext( 'latex', 'asdf' );
 
+              add  the  extension 'asdf to latex_input_extensions.  (Naturally
+              with such an extension, you should have made an appropriate cus-
+              tom dependency for latexmk, and should also have done the appro-
+              priate programming in the LaTeX source file to enable  the  file
 
 
-                                31 January 2024                             56
+
+                                 7 April 2024                               57
 
 
 
@@ -3700,10 +3766,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              add  the  extension 'asdf to latex_input_extensions.  (Naturally
-              with such an extension, you should have made an appropriate cus-
-              tom dependency for latexmk, and should also have done the appro-
-              priate programming in the LaTeX source file to enable  the  file
               to  be  read.   The standard extensions are handled by LaTeX and
               its graphics/graphicx packages.)
 
@@ -3755,9 +3817,13 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               ("Program Files") contains a space which would otherwise be mis-
               interpreted.
 
+       $lualatex ["lualatex %O %S"]
+              Specifies the command line for the LaTeX processing program that
+              is to be used when the lualatex program is called for (e.g.,  by
 
 
-                                31 January 2024                             57
+
+                                 7 April 2024                               58
 
 
 
@@ -3766,9 +3832,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       $lualatex ["lualatex %O %S"]
-              Specifies the command line for the LaTeX processing program that
-              is to be used when the lualatex program is called for (e.g.,  by
               the option -lualatex.
 
               To  do  a  coordinated setting of all of $dvilualatex, $hilatex,
@@ -3820,61 +3883,62 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               The maximum number of times latexmk will run *latex  before  de-
               ciding  that  there may be an infinite loop and that it needs to
               bail out, rather than rerunning *latex again to  resolve  cross-
+              references, etc.  The default value covers all normal cases.
 
+              (Note  that  the  "etc"  covers  a lot of cases where one run of
 
 
-                                31 January 2024                             58
 
+                                 7 April 2024                               59
 
 
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-              references, etc.  The default value covers all normal cases.
 
-              (Note that the "etc" covers a lot of cases where one run of *la-
-              tex generates files to be read in on a later run.)
+              *latex generates files to be read in on a later run.)
 
        $MSWin_back_slash [1]
-              This  configuration  variable only has an effect when latexmk is
-              running under MS-Windows.  With the default value of 1 for  this
-              variable,  when  a command is executed under MS-Windows, latexmk
-              substitutes "\" for the separator character  between  components
-              of  a  directory name.  Internally, latexmk uses "/" for the di-
-              rectory separator character, which  is  the  character  used  by
+              This configuration variable only has an effect when  latexmk  is
+              running  under MS-Windows.  With the default value of 1 for this
+              variable, when a command is executed under  MS-Windows,  latexmk
+              substitutes  "\"  for the separator character between components
+              of a directory name.  Internally, latexmk uses "/" for  the  di-
+              rectory  separator  character,  which  is  the character used by
               Unix-like systems.
 
-              For  almost  all programs and for almost all filenames under MS-
-              Windows, both "\" and "/" are acceptable as the directory  sepa-
-              rator  character,  provided at least that filenames are properly
+              For almost all programs and for almost all filenames  under  MS-
+              Windows,  both "\" and "/" are acceptable as the directory sepa-
+              rator character, provided at least that filenames  are  properly
               quoted.  But it is possible that programs exist that only accept
-              "\" on the command line, since that is  the  standard  directory
-              separator  for MS-Windows.  So for safety latexmk makes the sub-
+              "\"  on  the  command line, since that is the standard directory
+              separator for MS-Windows.  So for safety latexmk makes the  sub-
               stitution from "/" to "\", by default.
 
-              However there are also programs on MS-Windows for which  a  back
+              However  there  are also programs on MS-Windows for which a back
               slash "\" is interpreted differently than as a directory separa-
-              tor;  for these the directory separator should be "/".  Programs
-              with this behavior  include  all  the  *latex  programs  in  the
-              TeXLive  implementation  (but  not  the  MiKTeX implementation).
-              Hence if you use TeXLive on MS-Windows,  then  $MSWin_back_slash
+              tor; for these the directory separator should be "/".   Programs
+              with  this  behavior  include  all  the  *latex  programs in the
+              TeXLive implementation  (but  not  the  MiKTeX  implementation).
+              Hence  if  you use TeXLive on MS-Windows, then $MSWin_back_slash
               should be set to zero.
 
 
        $new_viewer_always [0]
-              This  variable  applies  to  latexmk  only in continuous-preview
+              This variable applies  to  latexmk  only  in  continuous-preview
               mode.  If $new_viewer_always is 0, latexmk will check for a pre-
-              viously running previewer on the same file, and if one  is  run-
-              ning  will  not  start a new one.  If $new_viewer_always is non-
-              zero, this check will be skipped, and latexmk will behave as  if
+              viously  running  previewer on the same file, and if one is run-
+              ning will not start a new one.  If  $new_viewer_always  is  non-
+              zero,  this check will be skipped, and latexmk will behave as if
               no viewer is running.
 
+
        $out_dir [""]
               If non-blank, this variable specifies the output directory.
 
-              This  is  the  directory in which final output files are written
+              This is the directory in which the main output files are written
               (dvi, ps, pdf, synctex, synctex.gz).  In addition,  if  the  aux
               directory  equals  the  output  directory, as is the case by de-
               fault, then other generated files are in effect written  to  the
@@ -3889,7 +3953,9 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-                                31 January 2024                             59
+
+
+                                 7 April 2024                               60
 
 
 
@@ -3898,6 +3964,40 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+       $out2_dir [""]
+              (Experimental new feature.)
+
+              If  non-blank,  this  variable specifies the final-output direc-
+              tory, i.e., the directory for the final output files.   If  this
+              variable  is  blank (its default value), the final-output direc-
+              tory is the same as the output directory.
+
+              See the description of the option -out2dir for an explanation of
+              the rationale for the idea of separate output  and  final-output
+              directories.
+
+              If  the  final-output directory is different from the output di-
+              rectory, then after a full round of compilations  of  the  docu-
+              ment,  the  relevant set of files is copied here from the output
+              directory.  The files copied are  specified  by  the  @out2_exts
+              variable, and by default are those with extensions 'hnt', 'pdf',
+              'ps',  'synctex',  'synctex.gz',  and a basename the same as for
+              the main *latex compilation.
+
+
+       @out2_exts [( 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz' )]
+
+              This variable lists the extensions of the files to be copied  to
+              the  final-output  directory.  The basename of the files is that
+              for the main *latex  compilation  (corresponding  to  the  value
+              specified  by  the  placeholder  %R).  More general names may be
+              specified in the same way as for the  @generated_exts  variable,
+              by inclusion of %R in a pattern, e.g.,
+
+                  push @out2_exts, '%R-2up.pdf';
+
+
+
        $pdf_mode [0]
               If  zero,  do  NOT  generate  a pdf version of the document.  If
               equal to 1, generate a pdf version of the document using  pdfla-
@@ -3918,6 +4018,18 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
        $pdflatex ["pdflatex %O %S"]
               Specifies the command line for the LaTeX processing program in a
+
+
+
+                                 7 April 2024                               61
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
               version that makes a pdf file instead of a dvi file.
 
               An example use of this variable is to add certain options to the
@@ -3952,18 +4064,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               See details of the %latex_input_extensions for other information
               that equally applies to %pdflatex_input_extensions.
 
-
-
-
-                                31 January 2024                             60
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        $pdflatex_silent_switch ["-interaction=batchmode"]
               Switch(es) for the pdflatex program (specified in  the  variable
               $pdflatex) when silent mode is on.
@@ -3985,6 +4085,17 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               file.   By  default, for pdf files this association is to OS-X's
               preview, which is quite satisfactory.
 
+
+
+                                 7 April 2024                               62
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
               WARNING:  Problem under MS-Windows: if acroread is used  as  the
               pdf  previewer,  and  it is actually viewing a pdf file, the pdf
               file cannot be updated.  Thus makes acroread  a  bad  choice  of
@@ -4019,17 +4130,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               Note that acroread under MS-Windows (but not UNIX) locks the pdf
               file, so the default value is then 3.
 
-
-
-                                31 January 2024                             61
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
               Arranging to use a command to get a previewer explicitly updated
               requires three variables to be set.  For example:
 
@@ -4050,6 +4150,18 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               variable  $pdf_update_method.   The default value is the one ap-
               propriate for gv on a UNIX system.
 
+
+
+
+                                 7 April 2024                               63
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
        $pid_position[1 under UNIX, -1 under MS-Windows]
               The variable $pid_position is used  to  specify  which  word  in
               lines  of  the output from $pscmd corresponds to the process ID.
@@ -4085,17 +4197,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-
-
-                                31 January 2024                             62
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        $preview_continuous_mode [0]
               If  nonzero,  run a previewer to view the document, and continue
               running latexmk to keep .dvi up-to-date.  Equivalent to the -pvc
@@ -4114,6 +4215,19 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               mended not to be set from an RC file, otherwise you could  waste
               lots of paper.
 
+
+
+
+
+                                 7 April 2024                               64
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
        $print_type = ["auto"]
               Type  of  file  to  printout:  possibilities  are "auto", "dvi",
               "none", "pdf", or "ps".   See the option -print= for the meaning
@@ -4150,18 +4264,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
               Note  that  gv  could be used with the -watch option updates its
               display whenever the postscript file changes, whereas  ghostview
-
-
-
-                                31 January 2024                             63
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
               does  not.  However, different versions of gv have slightly dif-
               ferent ways of writing this  option.   You  can  configure  this
               variable appropriately.
@@ -4181,6 +4283,17 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               in yourself, whenever it is needed.
 
 
+
+
+                                 7 April 2024                               65
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
        $ps_previewer_landscape ["start gv -swap %O %S", but start %O %S under
        MS-Windows]
               The command to invoke a ps-previewer in landscape mode.
@@ -4217,17 +4330,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               The period of inactivity, in minutes, after which pvc mode times
               out.  This is used if $pvc_timeout is nonzero.
 
-
-
-                                31 January 2024                             64
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        $pvc_view_file_via_temporary [1]
               The same as $always_view_file_via_temporary, except that it only
               applies in preview-continuous mode (-pvc option).
@@ -4247,6 +4349,17 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               correctly treated by the operating system in  passing  arguments
               to programs.)
 
+
+
+                                 7 April 2024                               66
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
        $rc_report [1]
               After  initialization,  whether  to  give a list of the RC files
               read.
@@ -4282,18 +4395,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
               [Comment  to  technically savvy readers: *latex doesn't actually
               need the modified search path.  But,  surprisingly,  dvipdf  and
-
-
-
-                                31 January 2024                             65
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
               dvips  do, because sometimes graphics files get generated in the
               output or aux directories.]
 
@@ -4313,6 +4414,18 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
               Note: On MS Windows, this is clock time.  On other OSs it is the
               CPU  time  used (by latexmk and the child processes it invokes).
+
+
+
+                                 7 April 2024                               67
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
               The OS-dependence is because of a limitation of Windows.  If you
               wish to force the use of clock instead of CPU time, you can set
 
@@ -4348,18 +4461,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               subject to a minimum value give by the $min_sleep_time variable.
               But a zero value is also allowed.
 
-
-
-
-                                31 January 2024                             66
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
               A value of exactly 0 gives no delay between checks  for  source-
               file  changes; it typically results in 100% CPU usage, which may
               not be desirable.
@@ -4378,191 +4479,194 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
               For  backward  compatibility,  if  you  choose  to   set   $tex-
               file_search,  it  is  a string of space-separated filenames, and
-              then latexmk replaces @default_files with the filenames in $tex-
-              file_search to which is added "*.tex".
+              then latexmk  replaces  @default_files  with  the  filenames  in
+
+
+
+                                 7 April 2024                               68
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+              $texfile_search to which is added "*.tex".
 
        $success_cmd [undefined]
               See the documentation for $compiling_cmd.
 
        $tmpdir [See below for default]
-              Directory to store temporary files  that  latexmk  may  generate
+              Directory  to  store  temporary  files that latexmk may generate
               while running.
 
-              The  default  under MSWindows (including cygwin), is to set $tm-
-              pdir to the value of the first of whichever of the system  envi-
-              ronment  variables  TMPDIR or TEMP exists, otherwise to the cur-
-              rent directory.  Under other operating systems (expected  to  be
-              UNIX/Linux,  including  OS-X),  the  default is the value of the
-              system environment  variable  TMPDIR  if  it  exists,  otherwise
+              The default under MSWindows (including cygwin), is to  set  $tm-
+              pdir  to the value of the first of whichever of the system envi-
+              ronment variables TMPDIR or TEMP exists, otherwise to  the  cur-
+              rent  directory.   Under other operating systems (expected to be
+              UNIX/Linux, including OS-X), the default is  the  value  of  the
+              system  environment  variable  TMPDIR  if  it  exists, otherwise
               "/tmp".
 
        $use_make_for_missing_files [0]
               Whether to use make to try and make files that are missing after
-              a  run of *latex, and for which a custom dependency has not been
-              found.  This is generally useful only when latexmk  is  used  as
-              part  of  a bigger project which is built by using the make pro-
+              a run of *latex, and for which a custom dependency has not  been
+              found.   This  is  generally useful only when latexmk is used as
+              part of a bigger project which is built by using the  make  pro-
               gram.
 
               Note that once a missing file has been made, no further calls to
-              make will be made on a subsequent run of latexmk to  update  the
-              file.   Handling  this  problem is the job of a suitably defined
-              Makefile.  See the section "USING latexmk WITH make" for how  to
-              do  this.   The intent of calling make from latexmk is merely to
+              make  will  be made on a subsequent run of latexmk to update the
+              file.  Handling this problem is the job of  a  suitably  defined
+              Makefile.   See the section "USING latexmk WITH make" for how to
+              do this.  The intent of calling make from latexmk is  merely  to
               detect dependencies.
 
        $view ["default"]
-              Which kind of file is to be previewed if a  previewer  is  used.
-              The  possible  values  are  "default",  "dvi", "ps", "pdf".  The
+              Which  kind  of  file is to be previewed if a previewer is used.
+              The possible values are  "default",  "dvi",  "ps",  "pdf".   The
               value of "default" means that the "highest" of the kinds of file
+              generated is to be used (among .dvi, .ps and .pdf).
 
 
+       $warnings_as_errors [0]
+              Normally  latexmk copies the behavior of latex in treating unde-
+              fined references and citations and multiply  defined  references
+              as  conditions  that give a warning but not an error.  The vari-
+              able $warnings_as_errors controls whether this behavior is modi-
+              fied.
 
-                                31 January 2024                             67
+              When the variable is non-zero, latexmk at the  end  of  its  run
+              will  return  a  non-zero status code to the operating system if
+              any of the files processed gives a warning about  problems  with
+              citations or references (i.e., undefined citations or references
+              or multiply defined references).  This is after latexmk has com-
+              pleted  all  the runs it needs to try and resolve references and
+              citations.  Thus $warnings_as_errors being  nonzero  causes  la-
+              texmk to treat such warnings as errors, but only when they occur
+              on the last run of *latex and only after processing is complete.
 
 
 
+                                 7 April 2024                               69
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              generated is to be used (among .dvi, .ps and .pdf).
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-       $warnings_as_errors [0]
-              Normally latexmk copies the behavior of latex in treating  unde-
-              fined  references  and citations and multiply defined references
-              as conditions that give a warning but not an error.   The  vari-
-              able $warnings_as_errors controls whether this behavior is modi-
-              fied.
 
-              When  the  variable  is  non-zero, latexmk at the end of its run
-              will return a non-zero status code to the  operating  system  if
-              any  of  the files processed gives a warning about problems with
-              citations or references (i.e., undefined citations or references
-              or multiply defined references).  This is after latexmk has com-
-              pleted all the runs it needs to try and resolve  references  and
-              citations.   Thus  $warnings_as_errors  being nonzero causes la-
-              texmk to treat such warnings as errors, but only when they occur
-              on the last run of *latex and only after processing is complete.
-              A non-zero value $warnings_as_errors can be set by the  command-
+              A  non-zero value $warnings_as_errors can be set by the command-
               line option -Werror.
 
               The default behavior is normally satisfactory in the usual edit-
-              compile-edit  cycle.  But, for example, latexmk can also be used
-              as part of a build process for some bigger  project,  e.g.,  for
-              creating  documentation  in the build of a software application.
-              Then it is often sensible to treat citation and reference  warn-
-              ings  as  errors  that  require  the overall build process to be
+              compile-edit cycle.  But, for example, latexmk can also be  used
+              as  part  of  a build process for some bigger project, e.g., for
+              creating documentation in the build of a  software  application.
+              Then  it is often sensible to treat citation and reference warn-
+              ings as errors that require the  overall  build  process  to  be
               aborted.  Of course, since multiple runs of *latex are generally
-              needed to resolve references and citations, what matters is  not
+              needed  to resolve references and citations, what matters is not
               the warnings on the first run, but the warnings on the last run;
               latexmk takes this into account appropriately.
 
-              In  addition,  when  preview-continuous mode is used, a non-zero
-              value for $warnings_as_errors changes the use  of  the  commands
-              $failure_cmd,  $warning_cmd,  and  $success_cmd after a complia-
+              In addition, when preview-continuous mode is  used,  a  non-zero
+              value  for  $warnings_as_errors  changes the use of the commands
+              $failure_cmd, $warning_cmd, and $success_cmd  after  a  complia-
               tion.  If there are citation or reference warnings, but no other
-              errors, the behavior is as follows. If $warning_cmd is  set,  it
-              is  used.  If it is not set, then then if $warnings_as_errors is
-              non-zero and $failure_cmd is set, then $failure_cmd.   Otherwise
-              $success_cmd  is used, if it is set.  (The foregoing explanation
+              errors,  the  behavior is as follows. If $warning_cmd is set, it
+              is used.  If it is not set, then then if $warnings_as_errors  is
+              non-zero  and $failure_cmd is set, then $failure_cmd.  Otherwise
+              $success_cmd is used, if it is set.  (The foregoing  explanation
               is rather complicated, because latexmk has to deal with the case
               that one or more of the commands isn't set.)
 
 
        $xdv_mode [0]
-              If one, generate an xdv version of the document by use of  xela-
+              If  one, generate an xdv version of the document by use of xela-
               tex.
 
 
        $xdvipdfmx ["xdvipdfmx -E -o %D %O %S"]
 
-              The  program  to  make a pdf file from an xdv file (used in con-
+              The program to make a pdf file from an xdv file  (used  in  con-
               junction with xelatex when $pdf_mode=5).
 
+       $xdvipdfmx_silent_switch ["-q"]
+              Switch(es) for the xdvipdfmx program when silent mode is on.
+
+       $xelatex ["xelatex %O %S"]
+              Specifies  the  command line for the LaTeX processing program of
+              when the xelatex program is called for.  See  the  documentation
+              of  the -xelatex option for some special properties of latexmk's
+              use of xelatex.
 
+              Note about xelatex: latexmk uses xelatex to make an .xdv  rather
+              than  .pdf  file, with the .pdf file being created in a separate
+              step.  This is enforced by the use of the -no-pdf option.  If %O
+              is part of the command for invoking xelatex, then  latexmk  will
+              insert the -no-pdf option automatically, otherwise you must pro-
+              vide  the option yourself.  See the documentation for the -pdfxe
+              option for why latexmk makes a .xdv file rather than a .pdf file
+              when xelatex is used.
 
-                                31 January 2024                             68
 
 
 
+                                 7 April 2024                               70
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       $xdvipdfmx_silent_switch ["-q"]
-              Switch(es) for the xdvipdfmx program when silent mode is on.
 
-       $xelatex ["xelatex %O %S"]
-              Specifies the command line for the LaTeX processing  program  of
-              when  the  xelatex program is called for.  See the documentation
-              of the -xelatex option for some special properties of  latexmk's
-              use of xelatex.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-              Note  about xelatex: latexmk uses xelatex to make an .xdv rather
-              than .pdf file, with the .pdf file being created in  a  separate
-              step.  This is enforced by the use of the -no-pdf option.  If %O
-              is  part  of the command for invoking xelatex, then latexmk will
-              insert the -no-pdf option automatically, otherwise you must pro-
-              vide the option yourself.  See the documentation for the  -pdfxe
-              option for why latexmk makes a .xdv file rather than a .pdf file
-              when xelatex is used.
 
-              To  do  a  coordinated setting of all of $dvilualatex, $hilatex,
+              To do a coordinated setting of all  of  $dvilualatex,  $hilatex,
               $latex, $pdflatex, $lualatex, and $xelatex, see the section "Ad-
               vanced Configuration".
 
 
        %xelatex_input_extensions
-              This variable specifies the extensions tried by latexmk when  it
-              finds  that  an xelatex run resulted in an error that a file has
-              not been found, and the file  is  given  without  an  extension.
-              This  typically  happens  when  LaTeX  commands of the form \in-
-              put{file} or \includegraphics{figure}, when the relevant  source
+              This  variable specifies the extensions tried by latexmk when it
+              finds that an xelatex run resulted in an error that a  file  has
+              not  been  found,  and  the  file is given without an extension.
+              This typically happens when LaTeX  commands  of  the  form  \in-
+              put{file}  or \includegraphics{figure}, when the relevant source
               file does not exist.
 
-              In  this  situation, latexmk searches for custom dependencies to
-              make the missing file(s), but restricts  it  to  the  extensions
-              specified  by  the  variable %xelatex_input_extensions.  The de-
+              In this situation, latexmk searches for custom  dependencies  to
+              make  the  missing  file(s),  but restricts it to the extensions
+              specified by the variable  %xelatex_input_extensions.   The  de-
               fault extensions are 'tex', 'pdf', 'jpg, and 'png'.
 
               See details of the %latex_input_extensions for other information
               that equally applies to %xelatex_input_extensions.
 
        $xelatex_silent_switch ["-interaction=batchmode"]
-              Switch(es) for the xelatex program (specified  in  the  variable
+              Switch(es)  for  the  xelatex program (specified in the variable
               $xelatex) when silent mode is on.
 
-              See  details  of  the $latex_silent_switch for other information
+              See details of the $latex_silent_switch  for  other  information
               that equally applies to $xelatex_silent_switch.
 
 
 
 
 CUSTOM DEPENDENCIES
-       In any RC file a set of custom dependencies can be set up to convert  a
+       In  any RC file a set of custom dependencies can be set up to convert a
        file with one extension to a file with another.  An example use of this
        would be to allow latexmk to convert a .fig file to .eps to be included
        in the .tex file.
 
 
-
-                                31 January 2024                             69
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
    Defining a custom dependency:
        The old method of configuring latexmk to use a custom dependency was to
-       directly  manipulate  the @cus_dep_list array that contains information
-       defining the custom dependencies.  (See  the  section  "Old  Method  of
-       Defining  Custom  Dependencies"  for details.) This method still works,
+       directly manipulate the @cus_dep_list array that  contains  information
+       defining  the  custom  dependencies.   (See  the section "Old Method of
+       Defining Custom Dependencies" for details.) This  method  still  works,
        but is no longer preferred.
 
        A better method is to use the subroutines that allow convenient manipu-
@@ -4574,95 +4678,106 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
        The arguments are as follows:
 
+
+
+
+                                 7 April 2024                               71
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
        from extension:
-              The extension of the file we are converting from  (e.g.  "fig").
+              The  extension  of the file we are converting from (e.g. "fig").
               It is specified without a period.
 
        to extension:
               The extension of the file we are converting to (e.g. "eps").  It
               is specified without a period.
 
-       must:  If  non-zero,  the file from which we are converting must exist,
-              if it doesn't exist latexmk will give an error message and  exit
+       must:  If non-zero, the file from which we are converting  must  exist,
+              if  it doesn't exist latexmk will give an error message and exit
               unless the -f option is specified.  If must is zero and the file
-              we  are  converting from doesn't exist, then no action is taken.
+              we are converting from doesn't exist, then no action  is  taken.
               Generally, the appropriate value of must is zero.
 
        function:
-              The name of the subroutine that latexmk should call  to  perform
-              the  file  conversion.   The first argument to the subroutine is
+              The  name  of the subroutine that latexmk should call to perform
+              the file conversion.  The first argument to  the  subroutine  is
               the base name of the file to be converted without any extension.
-              The subroutines are declared in the syntax of Perl.   The  func-
-              tion  should  return 0 if it was successful and a nonzero number
+              The  subroutines  are declared in the syntax of Perl.  The func-
+              tion should return 0 if it was successful and a  nonzero  number
               if it failed.
 
 
-       Naturally add_cus_dep adds a custom dependency with the specified  from
-       and  to extensions.  If a custom dependency has been previously defined
-       (e.g., in an rcfile that was read earlier), then it is replaced by  the
+       Naturally  add_cus_dep adds a custom dependency with the specified from
+       and to extensions.  If a custom dependency has been previously  defined
+       (e.g.,  in an rcfile that was read earlier), then it is replaced by the
        new one.
 
-       The  subroutine remove_cus_dep removes the specified custom dependency.
+       The subroutine remove_cus_dep removes the specified custom  dependency.
        The subroutine show_cus_dep causes a list of the currently defined cus-
        tom dependencies to be sent to the screen output.
 
 
    How custom dependencies are used:
        An instance of a custom dependency rule is created whenever latexmk de-
-       tects that a run of *latex needs to read a file, like a graphics  file,
-       whose  extension  is the to-extension of a custom dependency.  Then la-
-       texmk examines whether a file exists with the same name, but  with  the
-
+       tects  that a run of *latex needs to read a file, like a graphics file,
+       whose extension is the to-extension of a custom dependency.   Then  la-
+       texmk  examines  whether a file exists with the same name, but with the
+       corresponding from-extension, as specified  in  the  custom-dependency.
+       If  it  does, then a corresponding instance of the custom dependency is
+       created, after which the rule is invoked whenever the destination  file
+       (the one with the to-extension) is out-of-date with respect to the cor-
+       responding source file.
 
+       To  make the new destination file, the Perl subroutine specified in the
+       rule is invoked, with an argument that is the base name of the files in
+       question.  Simple cases just involve a subroutine invoking an  external
+       program;  this  can  be  done by following the templates below, even by
+       those without knowledge of the Perl programming language.   Of  course,
+       experts could do something much more elaborate.
 
-                                31 January 2024                             70
+       One  item  in the specification of each custom-dependency rule, labeled
+       "must" above, specifies how the rule should be applied when the  source
+       file fails to exist.
 
 
 
+                                 7 April 2024                               72
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       corresponding  from-extension,  as  specified in the custom-dependency.
-       If it does, then a corresponding instance of the custom  dependency  is
-       created,  after which the rule is invoked whenever the destination file
-       (the one with the to-extension) is out-of-date with respect to the cor-
-       responding source file.
 
-       To make the new destination file, the Perl subroutine specified in  the
-       rule is invoked, with an argument that is the base name of the files in
-       question.   Simple cases just involve a subroutine invoking an external
-       program; this can be done by following the  templates  below,  even  by
-       those  without  knowledge of the Perl programming language.  Of course,
-       experts could do something much more elaborate.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-       One item in the specification of each custom-dependency  rule,  labeled
-       "must"  above, specifies how the rule should be applied when the source
-       file fails to exist.
 
-       When latex reports that an input file (e.g., a graphics file) does  not
+       When  latex reports that an input file (e.g., a graphics file) does not
        exist, latexmk tries to find a source file and a custom dependency that
        can be used to make it.  If it succeeds, then it creates an instance of
-       the  custom  dependency  and invokes it to make the missing file, after
+       the custom dependency and invokes it to make the  missing  file,  after
        which the next pass of latex etc will be able to read the newly created
        file.
 
-       Note for advanced usage: The operating  system's  environment  variable
+       Note  for  advanced  usage: The operating system's environment variable
        TEXINPUTS can be used to specify a search path for finding files by la-
-       tex  etc.   Correspondingly,  when  a missing file is reported, latexmk
-       looks in the directories specified in TEXINPUTS as well as in the  cur-
-       rent  directory, to find a source file from which an instance of a cus-
+       tex etc.  Correspondingly, when a missing  file  is  reported,  latexmk
+       looks  in the directories specified in TEXINPUTS as well as in the cur-
+       rent directory, to find a source file from which an instance of a  cus-
        tom dependency can be used to make the missing file.
 
 
    Function to implement custom dependency, traditional method:
-       The function that implements a custom dependency gets  the  information
+       The  function  that implements a custom dependency gets the information
        on the files to be processed in two ways.  The first is through its one
-       argument;  the argument contains the base name of the source and desti-
+       argument; the argument contains the base name of the source and  desti-
        nation files.  The second way is described later.
 
-       A simple and typical example of code in an initialization rcfile  using
+       A  simple and typical example of code in an initialization rcfile using
        the first method is:
 
            add_cus_dep( 'fig', 'eps', 0, 'fig2eps' );
@@ -4670,45 +4785,45 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
                system( "fig2dev -Leps \"$_[0].fig\" \"$_[0].eps\"" );
            }
 
-       The  first  line adds a custom dependency that converts a file with ex-
+       The first line adds a custom dependency that converts a file  with  ex-
        tension "fig", as created by the xfig program, to an encapsulated post-
-       script file, with extension "eps".  The remaining lines define  a  sub-
-       routine  that  carries  out  the  conversion.  If a rule for converting
-       "fig" to "eps" files already exists (e.g., from  a  previously  read-in
-       initialization  file),  the latexmk will delete this rule before making
+       script  file,  with extension "eps".  The remaining lines define a sub-
+       routine that carries out the conversion.   If  a  rule  for  converting
+       "fig"  to  "eps"  files already exists (e.g., from a previously read-in
+       initialization file), the latexmk will delete this rule  before  making
        the new one.
 
+       Suppose  latexmk  is  using this rule to convert a file "figure.fig" to
+       "figure.eps".  Then it will invoke the fig2eps  subroutine  defined  in
+       the  above  code with a single argument "figure", which is the basename
+       of each of the files (possibly with a path component).   This  argument
+       is  referred to by Perl as $_[0].  In the example above, the subroutine
+       uses the Perl command system to invoke the program fig2dev.  The double
+       quotes around the string are a Perl idiom that signify that each string
+       of the form of a variable name, $_[0] in this case, is  to  be  substi-
+       tuted by its value.
 
+       If  the  return  value of the subroutine is non-zero, then latexmk will
+       assume an error occurred during the execution of  the  subroutine.   In
+       the  above  example, no explicit return value is given, and instead the
+       return value is the value returned by the last  (and  only)  statement,
+       i.e., the invocation of system, which returns the value 0 on success.
 
+       If  you  use  pdflatex,  lualatex or xelatex instead of latex, then you
 
-                                31 January 2024                             71
 
 
+                                 7 April 2024                               73
 
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-       Suppose latexmk is using this rule to convert a  file  "figure.fig"  to
-       "figure.eps".   Then  it  will invoke the fig2eps subroutine defined in
-       the above code with a single argument "figure", which is  the  basename
-       of  each  of the files (possibly with a path component).  This argument
-       is referred to by Perl as $_[0].  In the example above, the  subroutine
-       uses the Perl command system to invoke the program fig2dev.  The double
-       quotes around the string are a Perl idiom that signify that each string
-       of  the  form  of a variable name, $_[0] in this case, is to be substi-
-       tuted by its value.
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-       If the return value of the subroutine is non-zero,  then  latexmk  will
-       assume  an  error  occurred during the execution of the subroutine.  In
-       the above example, no explicit return value is given, and  instead  the
-       return  value  is  the value returned by the last (and only) statement,
-       i.e., the invocation of system, which returns the value 0 on success.
 
-       If you use pdflatex, lualatex or xelatex instead  of  latex,  then  you
-       will  probably  prefer to convert your graphics files to pdf format, in
-       which case you would replace the above code in an  initialization  file
+       will probably prefer to convert your graphics files to pdf  format,  in
+       which  case  you would replace the above code in an initialization file
        by
 
            add_cus_dep( 'fig', 'pdf, 0, 'fig2pdf' );
@@ -4716,63 +4831,62 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
                system( "fig2dev -Lpdf \"$_[0].fig\" \"$_[0].pdf\"" );
            }
 
-       Note  1: In the command lines given in the system commands in the above
-       examples, double quotes have been inserted around the file  names  (im-
-       plemented  by '\"' in the Perl language).  They immunize the running of
-       the program against special characters in filenames.  Very often  these
-       quotes  are  not  necessary, i.e., they can be omitted.  But it is nor-
-       mally safer to keep them in.  Even though the rules  for  quoting  vary
-       between  operating  systems,  command  shells  and individual pieces of
+       Note 1: In the command lines given in the system commands in the  above
+       examples,  double  quotes have been inserted around the file names (im-
+       plemented by '\"' in the Perl language).  They immunize the running  of
+       the  program against special characters in filenames.  Very often these
+       quotes are not necessary, i.e., they can be omitted.  But  it  is  nor-
+       mally  safer  to  keep them in.  Even though the rules for quoting vary
+       between operating systems, command  shells  and  individual  pieces  of
        software, the quotes in the above examples do not cause problems in the
        cases I have tested.
 
-       Note 2: One case in which the quotes are important is  when  the  files
-       are  in  a subdirectory and your operating system is Microsoft Windows.
-       Then the separator character for directory components can be  either  a
-       forward  slash  '/' or Microsoft's more usual backward slash '\'.  For-
-       ward slashes are generated by latexmk,  to  maintain  its  sanity  from
-       software  like  MiKTeX  that mixes both directory separators; but their
+       Note  2:  One  case in which the quotes are important is when the files
+       are in a subdirectory and your operating system is  Microsoft  Windows.
+       Then  the  separator character for directory components can be either a
+       forward slash '/' or Microsoft's more usual backward slash  '\'.   For-
+       ward  slashes  are  generated  by  latexmk, to maintain its sanity from
+       software like MiKTeX that mixes both directory  separators;  but  their
        correct use normally requires quoted filenames.  (See a log file from a
-       run of MiKTeX (at least in v. 2.9) for an example of the  use  of  both
+       run  of  MiKTeX  (at least in v. 2.9) for an example of the use of both
        directory separators.)
 
-       Note  3:  The subroutines implementing custom dependencies in the exam-
-       ples given just have  a  single  line  invoking  an  external  program.
-       That's  the usual situation.  But since the subroutines are in the Perl
-       language, you can implement much more  complicated  processing  if  you
+       Note 3: The subroutines implementing custom dependencies in  the  exam-
+       ples  given  just  have  a  single  line  invoking an external program.
+       That's the usual situation.  But since the subroutines are in the  Perl
+       language,  you  can  implement  much more complicated processing if you
        need it.
 
 
+   Removing custom dependencies, and when you might need to do this:
+       If you have some general custom dependencies defined in the  system  or
+       user  initialization  file,  you may find that for a particular project
+       they are undesirable.  So you might want to delete the  unneeded  ones.
+       A  situation  where this would be desirable is where there are multiple
+       custom dependencies with the same from-extension or the same  to-exten-
+       sion.  In  that case, latexmk might choose a different one from the one
+       you want for a specific project.  As an example, to remove any "fig" to
+       "eps" rule you would use:
 
+           remove_cus_dep( 'fig', 'eps' );
 
+       If you have complicated sets of custom dependencies, you  may  want  to
+       get  a  listing  of the custom dependencies.  This is done by using the
+       line
 
-
-                                31 January 2024                             72
+           show_cus_dep();
 
 
 
 
+                                 7 April 2024                               74
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-   Removing custom dependencies, and when you might need to do this:
-       If  you  have some general custom dependencies defined in the system or
-       user initialization file, you may find that for  a  particular  project
-       they  are  undesirable.  So you might want to delete the unneeded ones.
-       A situation where this would be desirable is where there  are  multiple
-       custom  dependencies with the same from-extension or the same to-exten-
-       sion. In that case, latexmk might choose a different one from  the  one
-       you want for a specific project.  As an example, to remove any "fig" to
-       "eps" rule you would use:
 
-           remove_cus_dep( 'fig', 'eps' );
 
-       If  you  have  complicated sets of custom dependencies, you may want to
-       get a listing of the custom dependencies.  This is done  by  using  the
-       line
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-           show_cus_dep();
 
        in an initialization file.
 
@@ -4780,29 +4894,29 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
    Function implementing custom dependency, alternative methods:
        So far the examples for functions to implement custom dependencies have
        used the argument of the function to specify the base name of converted
-       file.   This  method  has been available since very old versions of la-
+       file.  This method has been available since very old  versions  of  la-
        texmk, and many examples can be found, e.g., on the web.
 
-       However in later versions of latexmk the internal structure of the  im-
+       However  in later versions of latexmk the internal structure of the im-
        plementation of its "rules" for the steps of processing, including cus-
        tom dependencies, became much more powerful.  The function implementing
        a custom dependency is executed within a special context where a number
-       of  extra  variables  and subroutines are defined.  Publicly documented
-       ones, intended to be long-term stable,  are  listed  below,  under  the
+       of extra variables and subroutines are  defined.   Publicly  documented
+       ones,  intended  to  be  long-term  stable, are listed below, under the
        heading "Variables and subroutines for processing a rule".
 
-       Examples  of  their  use is given in the following examples, concerning
+       Examples of their use is given in the  following  examples,  concerning
        multiple index files and glossaries.
 
-       The only index-file conversion built-in to latexmk is  from  an  ".idx"
-       file  written on one run of *latex to an ".ind" file to be read in on a
-       subsequent run.  But with the index.sty package, for example,  you  can
-       create  extra indexes with extensions that you configure.  Latexmk does
+       The  only  index-file  conversion built-in to latexmk is from an ".idx"
+       file written on one run of *latex to an ".ind" file to be read in on  a
+       subsequent  run.   But with the index.sty package, for example, you can
+       create extra indexes with extensions that you configure.  Latexmk  does
        not know how to deduce the extensions from the information it has.  But
-       you can easily write a custom dependency.  For example  if  your  latex
+       you  can  easily  write a custom dependency.  For example if your latex
        file uses the command "\newindex{special}{ndx}{nnd}{Special index}" you
-       will  need  to  get latexmk to convert files with the extension .ndx to
-       .nnd.  The most elementary method is to define a custom  dependency  as
+       will need to get latexmk to convert files with the  extension  .ndx  to
+       .nnd.   The  most elementary method is to define a custom dependency as
        follows:
 
            add_cus_dep( 'ndx', 'nnd', 0, 'ndx2nnd' );
@@ -4811,25 +4925,14 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
            }
            push @generated_exts, 'ndx', 'nnd';
 
-
-
-                                31 January 2024                             73
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
-       Notice  the  added line compared with earlier examples.  The extra line
+       Notice the added line compared with earlier examples.  The  extra  line
        gets the extensions "ndx" and "nnd" added to the list of extensions for
        generated files; then the extra index files will be deleted by clean-up
        operations
 
-       But if you have yet more indexes with yet different  extensions,  e.g.,
-       "adx"  and  "and", then you will need a separate function for each pair
-       of extensions.  This is quite annoying.   You  can  use  the  Run_subst
+       But  if  you have yet more indexes with yet different extensions, e.g.,
+       "adx" and "and", then you will need a separate function for  each  pair
+       of  extensions.   This  is  quite  annoying.  You can use the Run_subst
        function to simplify the definitions to use a single function:
 
            add_cus_dep( 'ndx', 'nnd', 0, 'dx2nd' );
@@ -4839,6 +4942,18 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
            }
            push @generated_exts, 'ndx', 'nnd', 'adx', 'and';
 
+
+
+
+                                 7 April 2024                               75
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
        You could also instead use
 
            add_cus_dep( 'ndx', 'nnd', 0, 'dx2nd' );
@@ -4848,48 +4963,37 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
            }
            push @generated_exts, 'ndx', 'nnd', 'adx', 'and';
 
-       This  last example uses the command specification in $makeindex, and so
-       any customization you have made for the standard index also applies  to
+       This last example uses the command specification in $makeindex, and  so
+       any  customization you have made for the standard index also applies to
        your extra indexes.
 
        Similar techniques can be applied for glossaries.
 
        Those of you with experience with Makefiles, may get concerned that the
-       .ndx  file  is  written during a run of *latex and is always later than
+       .ndx file is written during a run of *latex and is  always  later  than
        the .nnd last read in.  Thus the .nnd appears to be perpetually out-of-
-       date.  This situation, of circular dependencies, is endemic  to  latex,
-       and  is  one  of the issues that latexmk is programmed to overcome.  It
-       examines the contents of the files (by use of  a  checksum),  and  only
+       date.   This  situation, of circular dependencies, is endemic to latex,
+       and is one of the issues that latexmk is programmed  to  overcome.   It
+       examines  the  contents  of  the files (by use of a checksum), and only
        does a remake when the file contents have actually changed.
 
-       Of  course  if you choose to write random data to the .nnd (or the .aux
-       file, etc) that changes on each new run, then you will have a  problem.
+       Of course if you choose to write random data to the .nnd (or  the  .aux
+       file,  etc) that changes on each new run, then you will have a problem.
        For real experts: See the %hash_calc_ignore_pattern if you have to deal
        with such problems.
 
 
    Old Method of Defining Custom Dependencies:
-       In  much  older versions of latexmk, the only method of defining custom
-       dependencies was to directly manipulate the table of  custom  dependen-
+       In much older versions of latexmk, the only method of  defining  custom
+       dependencies  was  to directly manipulate the table of custom dependen-
        cies.  This is contained in the @cus_dep_list array.  It is an array of
-       strings,  and each string in the array has four items in it, each sepa-
-       rated by a space, the  from-extension,  the  to-extension,  the  "must"
-       item,  and the name of the subroutine for the custom dependency.  These
+       strings, and each string in the array has four items in it, each  sepa-
+       rated  by  a  space,  the  from-extension, the to-extension, the "must"
+       item, and the name of the subroutine for the custom dependency.   These
        were all defined above.
 
-
-
-                                31 January 2024                             74
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
        An example of the old method of defining custom dependencies is as fol-
-       lows. It is the code in an RC file to ensure  automatic  conversion  of
+       lows.  It  is  the code in an RC file to ensure automatic conversion of
        .fig files to .eps files:
 
            push @cus_dep_list, "fig eps 0 fig2eps";
@@ -4897,61 +5001,44 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
                return system( "fig2dev -Lps \"$_[0].fig\" \"$_[0].eps\"" );
            }
 
-       This  method  still  works,  and is almost equivalent to the code given
-       earlier that used the add_cus_dep subroutine.  However, the old  method
-       doesn't  delete any previous custom-dependency for the same conversion.
+       This method still works, and is almost equivalent  to  the  code  given
+       earlier  that used the add_cus_dep subroutine.  However, the old method
+       doesn't delete any previous custom-dependency for the same  conversion.
        So the new method is preferable.
 
 
 
-Advanced configuration: Some extra resources and advanced tricks
-       For most purposes, simple configuration for latexmk along the lines  of
-       the  examples  given  is  sufficient.  But sometimes you need something
-       harder.  In this section, I indicate some extra possibilities.   Gener-
-       ally  to  use  these, you need to be fluent in the Perl language, since
-       this is what is used in the rc files.
 
-       See also the section DEALING WITH ERRORS, PROBLEMS, ETC.  See also  the
-       examples in the directory example_rcfiles in the latexmk distributions.
-       Even if none of the examples apply to your case, they may give you use-
-       ful ideas
 
 
-   Utility subroutines
-       ensure_path( var, values ...)
+                                 7 April 2024                               76
 
-              The  first parameter is the name of one of the system's environ-
-              ment variables for search paths.  The remaining  parameters  are
-              values  that  should  be in the variable.  For each of the value
-              parameters, if it isn't already in  the  variable,  then  it  is
-              prepended to the variable; in that case the environment variable
-              is  created  if it doesn't already exist. For separating values,
-              the character appropriate the the operating system  is  used  --
-              see the configuration variable $search_path_separator.
 
-              Example:
-
-                ensure_path( 'TEXINPUTS', './custom_cls_sty_files//' );
-
-              (In this example, the trailing '//' is documented by TeX systems
-              to  mean that *latex search for files in the specified directory
-              and in all subdirectories.)
-
-              Technically  ensure_path  works  by  setting   Perl's   variable
-              $ENV{var},  where  var  is the name of the target variable.  The
-              changed value is then passed as an environment variable  to  any
-              invoked programs.
 
 
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
-                                31 January 2024                             75
 
+ADVANCED CONFIGURATION: SOME EXTRA RESOURCES AND ADVANCED TRICKS
+       For  most purposes, simple configuration for latexmk along the lines of
+       the examples given is sufficient.  But  sometimes  you  need  something
+       harder.   In this section, I indicate some extra possibilities.  Gener-
+       ally to use these, you need to be fluent in the  Perl  language,  since
+       this is what is used in the rc files.
 
+       In  this  section,  I include first, a description of a number of vari-
+       ables and subroutines that provide, among other things, access  to  la-
+       texmk's internal data structures for handling dependencies.  Then I de-
+       scribe  the hook mechanism whereby at certain points in the processing,
+       latexmk can call user-defined subroutines.
 
+       See also the section DEALING WITH ERRORS, PROBLEMS, ETC.  See also  the
+       examples in the directory example_rcfiles in the latexmk distributions.
+       Even if none of the examples apply to your case, they may give you use-
+       ful ideas
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
    Variables and subroutines for processing a rule
@@ -4974,44 +5061,155 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               Note that the exact contents of this variable for a  given  rule
               may be dependent on the version of latexmk
 
+       $$Pbase
+              This  gives the basename for the rule.  Generally, it determines
+              the names of generated files.  E.g., for a run  of  *latex,  the
+              name of the .log file is the aux directory concatenated with the
+              basename and then `.log'.
+
+              For  a  *latex  rule, the basename is without a directory compo-
+              nent.  For other rules, it includes the directory component  (if
+              any is used).
+
+              This (annoying) difference is associated with the different ways
+              in  which  the commands invoked by latexmk work when the command
+              line includes a name for a source file that includes a directory
+
+
+
+                                 7 April 2024                               77
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+              component.  For the *latex commands, the directory of the source
+              file is irrelevant to  the  directory  component  the  generated
+              files, which instead is determined by the values in the -aux-di-
+              rectory and/or -output-directory options.
+
+              In contrast, many other programs (e.g., biber, bibtex) put their
+              generated files in the same directory as the source file, merely
+              with a changed extension.
+
+              Note the double dollar signs: In Perl terms, the variable $Pbase
+              is  a  reference  to a variable that contains the basename.  The
+              second dollar sign derefences the reference to give  the  actual
+              value.   (A  reference is is used rather like a pointer, and the
+              `P' (for `pointer') at the start of the variable name is a  con-
+              vention  used in latexmk to indicate that the variable is a ref-
+              erence variable.)
+
+
+       $$Pdest
+              This gives the name of the main output file if  any.   Note  the
+              double dollar signs.
+
+
        $$Psource
               This gives the name of the primary source file.  Note the double
               dollar signs.
 
-       $$Pdest
-              This  gives  the  name of the main output file if any.  Note the
-              double dollar signs.
+
+       add_hook( <stack_name>, <subroutine> )
+              See the section `Hooks' for more details.
+
+              This adds the subroutine specified in the second argument to la-
+              texmk's  stack of hooks specified by the stack name.  It returns
+              1 on sucess, and zero otherwise (e.g.,  if  the  specified  hook
+              stack doesn't exist).
+
+              The  subroutine  can  be specified by a reference to the subrou-
+              tine, as in
+
+                  add_hook( 'after_xlatex_analysis', mmz_analyze )
+
+              Given that the subroutine mmz_analyze has been defined in the rc
+              file.
+
+              The subroutine can be specified by a string whose value  is  the
+              name of the subroutine, e.g.,
+
+                  add_hook( 'after_xlatex_analysis', 'mmz_analyze' )
+
+              In  simple  cases, the subroutine can be an anonymous subroutine
+              defined in the call to add_hooks,
+
+                  add_hook( 'after_main_pdf', sub{ print
+
+
+
+
+                                 7 April 2024                               78
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+              Observe that on success, the subroutine should return 0 (like  a
+              call  to  Perl's  system subroutine), so normally this should be
+              coded explicitly.  If  a  hook  subroutine  returns  a  non-zero
+              value, latexmk treats that as an error condition.
+
+
+
+       ensure_path( var, values ...)
+
+              The  first parameter is the name of one of the system's environ-
+              ment variables for search paths.  The remaining  parameters  are
+              values  that  should  be in the variable.  For each of the value
+              parameters, if it isn't already in  the  variable,  then  it  is
+              prepended to the variable; in that case the environment variable
+              is  created  if it doesn't already exist. For separating values,
+              the character appropriate the the operating system  is  used  --
+              see the configuration variable $search_path_separator.
+
+              Example:
+
+                ensure_path( 'TEXINPUTS', './custom_cls_sty_files//' );
+
+              (In this example, the trailing '//' is documented by TeX systems
+              to  mean that *latex search for files in the specified directory
+              and in all subdirectories.)
+
+              Technically  ensure_path  works  by  setting   Perl's   variable
+              $ENV{var},  where  var  is the name of the target variable.  The
+              changed value is then passed as an environment variable  to  any
+              invoked programs.
 
 
        pushd( path ), popd()
-              These subroutines are used when  it  is  needed  to  temporarily
+              These  subroutines  are  used  when  it is needed to temporarily
               change the working directory, as in
 
                    pushd( 'some_directory' );
-                   ...  Processing  done  with 'some_directory' as the working
+                   ... Processing done with 'some_directory'  as  the  working
               directory
                    popd()
 
-              They perform exactly the same function as the  commands  of  the
+              They  perform  exactly  the same function as the commands of the
               same names in operating system command shells like bash on Unix,
               and cmd.exe on the Windows.
 
 
        rdb_add_generated( file, ... )
               This subroutine is to be used in the context of a rule, that is,
-              from  within  a  subroutine that is carrying out processing of a
+              from within a subroutine that is carrying out  processing  of  a
               rule.  Such is the case for the subroutine implementing a custom
-              dependency, or the subroutine invoked by  using  the  "internal"
-              keyword  in  the command specification like that in the variable
+              dependency,  or  the  subroutine invoked by using the "internal"
+              keyword in the command specification like that in  the  variable
               $latex.
 
-              Its arguments are a sequence of filenames  which  are  generated
-              during  the  running of the rule.  The names might arise from an
-              analysis of the results of the run, e.g., in a log file, or from
 
 
 
-                                31 January 2024                             76
+                                 7 April 2024                               79
 
 
 
@@ -5020,70 +5218,79 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-              knowledge  of  properties  of  the   specific   rule.    Calling
-              rdb_add_generated  with these filenames ensures that these files
-              are flagged as generated by the rule in latexmk's internal  data
+              Its  arguments  are  a sequence of filenames which are generated
+              during the running of the rule.  The names might arise  from  an
+              analysis of the results of the run, e.g., in a log file, or from
+              knowledge   of   properties   of  the  specific  rule.   Calling
+              rdb_add_generated with these filenames ensures that these  files
+              are  flagged as generated by the rule in latexmk's internal data
               structures.  Basically, no action is taken if the files have al-
               ready been flagged as generated.
 
-              A  main  purpose  of  using this subroutine is for the situation
-              when a generated file is also the source file for some rule,  so
-              that  latexmk  can  correctly link the dependency information in
+              A main purpose of using this subroutine  is  for  the  situation
+              when  a generated file is also the source file for some rule, so
+              that latexmk can correctly link the  dependency  information  in
               its network of rules.
 
               Note: Unlike some other subroutines in this section, there is no
-              argument for a rule for rdb_add_generated. Instead, the  subrou-
-              tine  is  to be invoked during the processing of a rule when la-
+              argument  for a rule for rdb_add_generated. Instead, the subrou-
+              tine is to be invoked during the processing of a rule  when  la-
               texmk has set up an appropriate context (i.e., appropriate vari-
-              ables).  In contrast, subroutines with a rule  argument  can  be
+              ables).   In  contrast,  subroutines with a rule argument can be
               used also outside a rule context.
 
 
        rdb_ensure_file( $rule, file )
-              This  subroutine ensures that the given file is among the source
+              This subroutine ensures that the given file is among the  source
               files for the specified rule.  It is typically used when, during
-              the processing of a rule, it is known that  a  particular  extra
+              the  processing  of  a rule, it is known that a particular extra
               file is among the dependencies that latexmk should know, but its
-              default  methods  don't  find  the dependency. Almost always the
-              first  argument  is  the  name  of  the  rule  currently   being
+              default methods don't find the  dependency.  Almost  always  the
+              first   argument  is  the  name  of  the  rule  currently  being
               processed, so it is then appropriate to specify it by $rule.
 
-              For  examples of its use, see some of the files in the directory
-              example_rcfiles of latexmk's distribution.  Currently the  cases
-              that  use  this  subroutine  are bib2gls-latexmkrc, exceltex_la-
-              texmkrc and texinfo-latexmkrc.  These illustrate  typical  cases
-              where  latexmk's normal processing fails to detect certain extra
+              For examples of its use, see some of the files in the  directory
+              example_rcfiles  of latexmk's distribution.  Currently the cases
+              that use this  subroutine  are  bib2gls-latexmkrc,  exceltex_la-
+              texmkrc  and  texinfo-latexmkrc.  These illustrate typical cases
+              where latexmk's normal processing fails to detect certain  extra
               source files.
 
               Note that rdb_ensure_file only has one filename argument, unlike
               other subroutines in this section.  If you want to apply its ac-
-              tion to multiple files,  you  will  need  one  call  to  rdb_en-
+              tion  to  multiple  files,  you  will  need  one call to rdb_en-
               sure_file for each file.
 
 
+       rdb_ensure_files_here( file, ... )
+              Like subroutine rdb_ensure_files, except that (a) it assumes the
+              context is of a rule, and the files  are  to  be  added  to  the
+              source list for that rule; (b) multiple files are allowed.
+
+
        rdb_remove_files( $rule, file, ... )
               This  subroutine  removes  one or more files from the dependency
               list for the given rule.
 
 
-       rdb_remove_generated( file, ... )
-              This subroutine is to be used in the context of a rule, that is,
-              from within a subroutine that is carrying out  processing  of  a
-              rule.   It  performs  the  opposite action to rdb_add_generated.
-              Its effect is to ensure that the given filenames are not  listed
-              in  latexmk's internal data structures as being generated by the
-              rule.
 
 
+                                 7 April 2024                               80
 
 
-                                31 January 2024                             77
 
 
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+       rdb_remove_generated( file, ... )
+              This subroutine is to be used in the context of a rule, that is,
+              from within a subroutine that is carrying out  processing  of  a
+              rule.   It  performs  the  opposite action to rdb_add_generated.
+              Its effect is to ensure that the given filenames are not  listed
+              in  latexmk's internal data structures as being generated by the
+              rule.
 
 
        rdb_list_source( $rule )
@@ -5114,9 +5321,43 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
               silent mode.
 
 
+       test_gen_file_time ( <file> )
+              This  subroutine  is  used in the context of a rule.  It returns
+              true or false according to whether or not a file  of  the  given
+              name  both  exists  and  was  generated in the latest run of the
+              rule.  If the subroutine returns false,  but  the  file  exists,
+              then the file is a leftover from a previous run.
+
+              The  test  for  a  file  being  generated  on the current run is
+              whether the modification time of the file is at least as  recent
+              as  the time that the run of the rule was started.  An allowance
+              for the granularity of the values of modification time  on  file
+              systems  is  made.   See  the description of the variable $file-
+              time_causality_threshold for details.
+
+              In addition, latexmk makes allowance  for  the  possiblity  that
+              files  are  hosted on a different computer than that running la-
+              texmk and that the system clock times on the two  computers  are
+
+
+
+                                 7 April 2024                               81
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+              mismatched.   Latexmk  automatically  detects  (and reports) any
+              significant mismatch and corrects for it.
+
+
+
    Coordinated Setting of Commands for *latex
        To set all of $dvilualatex, $hilatex, $latex, $pdflatex, $lualatex, and
-       $xelatex  to a common pattern, you can use one of the following subrou-
+       $xelatex to a common pattern, you can use one of the following  subrou-
        tines, std_tex_cmds, alt_tex_cmds, and set_tex_cmds.
 
        To get the standard commands, use
@@ -5124,39 +5365,28 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
           &std_tex_cmds;
 
        This results in $latex = 'latex %O %S', and similarly for $dvilualatex,
-       $hilatex, $pdflatex, $lualatex, and $xelatex.  Note  the  ampersand  in
-       the  invocation;  this  indicates  to  Perl  that a subroutine is being
-       called.  (The use of this subroutine enables you to  override  previous
-       redefinitions  of  the $latex, etc variables, which might have occurred
+       $hilatex,  $pdflatex,  $lualatex,  and $xelatex.  Note the ampersand in
+       the invocation; this indicates to  Perl  that  a  subroutine  is  being
+       called.   (The  use of this subroutine enables you to override previous
+       redefinitions of the $latex, etc variables, which might  have  occurred
        in an earlier-read rc file.)
 
-       To be able to use the string provided by the -pretex option  (if  any),
+       To  be  able to use the string provided by the -pretex option (if any),
        you can use
 
           &alt_tex_cmds;
 
-       This  results in $latex = 'latex %O %P', etc.  Again note the ampersand
-       in the invocation; this indicates to Perl that a  subroutine  is  being
+       This results in $latex = 'latex %O %P', etc.  Again note the  ampersand
+       in  the  invocation;  this indicates to Perl that a subroutine is being
        called.
 
        A more general way of specifying the variables is using
 
-
-
-                                31 January 2024                             78
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
          set_tex_cmds( 'CMD_SPEC' );
 
-       Here  CMD_SPEC  is  the command line without the program name. This re-
-       sults in $latex = 'latex CMD_SPEC', and similarly for  $pdflatex,  etc.
-       (An  ampersand  preceding  the  subroutine  name is not necessary here,
+       Here CMD_SPEC is the command line without the program  name.  This  re-
+       sults  in  $latex = 'latex CMD_SPEC', and similarly for $pdflatex, etc.
+       (An ampersand preceding the subroutine  name  is  not  necessary  here,
        since the parentheses show Perl that a subroutine is being invoked.)
 
        An example that provides the --interaction=batchmode option to the *la-
@@ -5164,52 +5394,152 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
          set_tex_cmds( '--interaction=batchmode %O %S' );
 
-       This results in $latex = 'latex --interaction=batchmode %O %S  ',  etc.
-       Note  that  when  '%O' appears after the added option, as here, options
+       This  results  in $latex = 'latex --interaction=batchmode %O %S ', etc.
+       Note that when '%O' appears after the added option,  as  here,  options
        provided on the command line to latexmk can override the supplied one.
 
        A more general command line can be set up by using the placeholder '%C'
        in CMD_SPEC.  The '%C' is substituted by the basic name of the command,
        i.e., whichever of 'latex', 'pdflatex', etc is appropriate.  (More than
-       one occurrence of '%C' is allowed.)  For example to  use  the  develop-
+       one  occurrence  of  '%C' is allowed.)  For example to use the develop-
        ment/pre-release versions of latex, etc, which have names, 'latex-dev',
        'pdflatex-dev', etc, you could use
 
+
+
+                                 7 April 2024                               82
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
          set_tex_cmds( '%C-dev %O %S' );
 
        This results in $latex = 'latex-dev %O %S', etc.  (The pre-release pro-
-       grams  latex-dev  etc  are provided in current distributions of TeXLive
+       grams latex-dev etc are provided in current  distributions  of  TeXLive
        and MiKTeX.)
 
 
-   Advanced configuration: Using latexmk with make
-       This section is targeted only at advanced users who use the  make  pro-
-       gram for complex projects, as for software development, with the depen-
-       dencies specified by a Makefile.
+   Hooks
+       Latexmk  provides  a  way to arrange for user-defined subroutines to be
+       called at certain points in the processing.  These can be used to  con-
+       figure  appropriate behavior and actions beyond latexmk's normal behav-
+       ior.  For a good example of how they can be  used  to  accommodate  la-
+       texmk's behavior to particular packages, see the file memoize_latexmkrc
+       in the example_rcfiles subdirectory of the latexmk distribution.  (In a
+       standard  TeXLive  installation,  that  subdirectory  is to be found in
+       texmf-dist/doc/support/latexmk/)
 
-       Now  the  basic  task  of latexmk is to run the appropriate programs to
-       make a viewable version of a LaTeX document.  However, the  usual  make
-       program  is not suited to this purpose for at least two reasons.  First
-       is that the use of LaTeX involves circular dependencies (e.g., via .aux
-       files), and these cannot be handled by the standard make program.  Sec-
-       ond is that in a large document the set  of  source  files  can  change
-       quite  frequently,  particularly  with included graphics files; in this
-       situation keeping a Makefile manually updated is inappropriate and  er-
-       ror-prone, especially when the dependencies can be determined automati-
-       cally.  Latexmk solves both of these problems robustly.
+       The hook mechanism is complementary to the method of redefining command
+       strings like $pdflatex etc.  The two methods have  overlapping  domains
+       of usefulness.
+
+       Note  that  the  hook  mechanism is newly made public in v. 4.84 of la-
+       texmk.  It is subject  to  change  and  improvement  as  experience  is
+       gained.
+
+       The  hooks  are arranged in named hook stacks, and a hook subroutine is
+       added to a given stack by  latexmk's  add_hook  subroutine  (documented
+       above).   The  currently available stacks are as follows, listed in the
+       approximate order in which they are encountered in processing  a  docu-
+       ment:
+
+
+         before_xlatex
+           The subroutines in this hook stack are called just before a
+           *latex programs is run.
 
-       Thus  for  many  standard LaTeX documents latexmk can be used by itself
-       without the make program.  In a complex project it simply needs  to  be
-       suitably  configured.  A standard configuration would be to define cus-
-       tom dependencies to make graphics files from their source files  (e.g.,
-       as  created  by  the  xfig program).  Custom dependencies are latexmk's
-       equivalent of pattern rules in Makefiles.
 
-       Nevertheless there are projects for which a  Makefile  is  appropriate,
+         after_xlatex
+           The  subroutines  in this hook stack are called after a *latex pro-
+         grams is
+           run.  Before the subroutines are called, latexmk has done some  im-
+         mediate
+           postprocessing, e.g., to move the generated pdf file from the aux
+           directory to the output directory when $emulate_aux is set to 1.
 
 
+         after_xlatex_analysis
+           The  subroutines  in  this  hook stack are called after latexmk has
+         done its
+           dependency analysis after a *latex programs is run.  Subroutines in
+         this
+           stack provide a useful way of adding items to the dependency infor-
+         mation
+           associated with particular packages and that latexmk doesn't
 
-                                31 January 2024                             79
+
+
+                                 7 April 2024                               83
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
+           automatically deal with.
+
+
+         after_main_pdf
+           The subroutines in this hook stack are  called  after  one  of  the
+         rules that
+           creates  the document's pdf file. (This covers any of pdflatex, lu-
+         alatex,
+           dvipdf, ps2pdf, xdvipdfmx.)
+
+
+         cleanup
+           The subroutines in this hook stack are called whenever  latexmk  is
+         about
+           to  do a cleanup operation.  They can be used, for example, to tai-
+         lor the
+           deleted files to the pecularities of particular packages  when  la-
+         texmk's
+           general  mechanisms  for specifying files to be deleted are too in-
+         flexible.
+
+           These subroutines are called before latexmk does  any  of  its  own
+         file
+           deletion;  thus  the hook subroutines have access to all the gener-
+         ated
+           files that give package-specific information.
+
+
+         cleanup_extra_full
+           The subroutines in this hook stack are called in  addition  to  the
+         ones in
+           the  cleanup stack, whenever a full cleanup operation is to be done
+         (i.e.,
+           one that includes the pdf, ps etc files).  They are called  immedi-
+         ately
+           after those in the cleanup stack, but still before latexmk does any
+         of
+           its own file deletion.
+
+
+       (Any  other stacks defined in latexmk.pl but not listed above are to be
+       regarded as experimental and subject to change.)
+
+       Each subroutine should return 0 on success  and  a  non-zero  value  on
+       failure.   This matches the convention used for running programs, e.g.,
+       by Perl's system subroutine, and the matching convention used for  sub-
+       routines for custom dependencies in latexmk.
+
+       For  most of the hook stacks, the subroutines are called in the context
+       of a rule, with variables  like  $rule  defined.   However,  some  hook
+       stacks,  like  the  cleanup ones, are called from outside any rule; and
+       latexmk adjusts the relevant variables to refer  to  the  overall  task
+       (i.e., of processing a particular main .tex file).
+
+
+
+
+                                 7 April 2024                               84
 
 
 
@@ -5218,15 +5548,39 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+   Advanced configuration: Using latexmk with make
+       This  section  is targeted only at advanced users who use the make pro-
+       gram for complex projects, as for software development, with the depen-
+       dencies specified by a Makefile.
+
+       Now the basic task of latexmk is to run  the  appropriate  programs  to
+       make  a  viewable version of a LaTeX document.  However, the usual make
+       program is not suited to this purpose for at least two reasons.   First
+       is that the use of LaTeX involves circular dependencies (e.g., via .aux
+       files), and these cannot be handled by the standard make program.  Sec-
+       ond  is  that  in  a  large document the set of source files can change
+       quite frequently, particularly with included graphics  files;  in  this
+       situation  keeping a Makefile manually updated is inappropriate and er-
+       ror-prone, especially when the dependencies can be determined automati-
+       cally.  Latexmk solves both of these problems robustly.
+
+       Thus for many standard LaTeX documents latexmk can be  used  by  itself
+       without  the  make program.  In a complex project it simply needs to be
+       suitably configured.  A standard configuration would be to define  cus-
+       tom  dependencies to make graphics files from their source files (e.g.,
+       as created by the xfig program).   Custom  dependencies  are  latexmk's
+       equivalent of pattern rules in Makefiles.
+
+       Nevertheless  there  are  projects for which a Makefile is appropriate,
        and it is useful to know how to use latexmk from a Makefile.  A typical
        example would be to generate documentation for a software project.  Po-
-       tentially  the  interaction  with the rest of the rules in the Makefile
+       tentially the interaction with the rest of the rules  in  the  Makefile
        could be quite complicated, for example if some of the source files for
        a LaTeX document are generated by the project's software.
 
        In this section, I give a couple of examples of how latexmk can be use-
-       fully invoked from a Makefile.  The examples use specific  features  of
-       current  versions  of  GNU make, which is the default on both linux and
+       fully  invoked  from a Makefile.  The examples use specific features of
+       current versions of GNU make, which is the default on  both  linux  and
        OS-X systems.  They may need modifications for other versions of make.
 
        The simplest method is simply to delegate all the relevant tasks to la-
@@ -5238,33 +5592,45 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
            %.pdf : %.tex FORCE_MAKE
                latexmk -pdf -dvi- -ps- $<
 
-       (Note: the last line must be introduced by a tab for  the  Makefile  to
-       function  correctly!)  Naturally, if making try.pdf from its associated
-       LaTeX file try.tex were the only task to be performed, a direct use  of
-       latexmk  without  a  Makefile would normally be better.  The benefit of
-       using a Makefile for a LaTeX document would be  in  a  larger  project,
+       (Note:  the  last  line must be introduced by a tab for the Makefile to
+       function correctly!)  Naturally, if making try.pdf from its  associated
+       LaTeX  file try.tex were the only task to be performed, a direct use of
+       latexmk without a Makefile would normally be better.   The  benefit  of
+       using  a  Makefile  for  a LaTeX document would be in a larger project,
        where lines such as the above would be only be a small part of a larger
        Makefile.
 
        The above example has a pattern rule for making a .pdf file from a .tex
-       file,  and it is defined to use latexmk in the obvious way.  There is a
+       file, and it is defined to use latexmk in the obvious way.  There is  a
+
+
+
+                                 7 April 2024                               85
+
+
+
+
+
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+
+
        conventional  default  target  named  "all",  with  a  prerequisite  of
-       try.pdf.   So  when  make is invoked, by default it makes try.pdf.  The
-       only complication is  that  there  may  be  many  source  files  beyond
+       try.pdf.  So when make is invoked, by default it  makes  try.pdf.   The
+       only  complication  is  that  there  may  be  many  source files beyond
        try.tex, but these aren't specified in the Makefile, so changes in them
-       will  not by themselves cause latexmk to be invoked.  Instead, the pat-
-       tern rule is equipped with a "phony" prerequisite FORCE_MAKE; this  has
-       the  effect  of  causing the rule to be always out-of-date, so that la-
-       texmk is always run.  It is latexmk that decides whether any action  is
-       needed,  e.g., a rerun of pdflatex.  Effectively the Makefile delegates
-       all decisions to latexmk, while make has no knowledge of  the  list  of
+       will not by themselves cause latexmk to be invoked.  Instead, the  pat-
+       tern  rule is equipped with a "phony" prerequisite FORCE_MAKE; this has
+       the effect of causing the rule to be always out-of-date,  so  that  la-
+       texmk  is always run.  It is latexmk that decides whether any action is
+       needed, e.g., a rerun of pdflatex.  Effectively the Makefile  delegates
+       all  decisions  to  latexmk, while make has no knowledge of the list of
        source files except for primary LaTeX file for the  document.  If there
        are, for example, graphics files to be made, these must be made by cus-
        tom dependencies configured in latexmk.
 
-       But  something better is needed in more complicated situations, for ex-
+       But something better is needed in more complicated situations, for  ex-
        ample, when the making of graphics files needs to be specified by rules
-       in the Makefile.  To do this, one can use a Makefile like  the  follow-
+       in  the  Makefile.  To do this, one can use a Makefile like the follow-
        ing:
 
             TARGETS = document1.pdf document2.pdf
@@ -5272,18 +5638,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
             LATEXMK = latexmk -recorder -use-make -deps \
                   -e 'warn qq(In Makefile, turn off custom dependencies\n);' \
                   -e '@cus_dep_list = ();' \
-
-
-
-                                31 January 2024                             80
-
-
-
-
-
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
-
-
                   -e 'show_cus_dep();'
             all : $(TARGETS)
             $(foreach file,$(TARGETS),$(eval -include $(DEPS_DIR)/$(file)P))
@@ -5295,75 +5649,75 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
             %.pdf : %.fig
                    fig2dev -Lpdf $< $@
 
-       (Again,  the  lines  containing  the  commands  for the rules should be
+       (Again, the lines containing the  commands  for  the  rules  should  be
        started with tabs.)  This example was inspired by how GNU automake han-
        dles automatic dependency tracking of C source files.
 
-       After each run of latexmk, dependency information is put in a  file  in
-       the  .deps subdirectory.  The Makefile causes these dependency files to
+       After  each  run of latexmk, dependency information is put in a file in
+       the .deps subdirectory.  The Makefile causes these dependency files  to
        be read by make, which now has the full dependency information for each
-       target .pdf file.  To make things less trivial it  is  specificed  that
-       two  files document1.pdf and document2.pdf are the targets.  The depen-
+       target  .pdf  file.   To make things less trivial it is specificed that
+       two files document1.pdf and document2.pdf are the targets.  The  depen-
        dency files are .deps/document1.pdfP and .deps/document2.pdfP.
 
-       There is now no need for the phony prerequisite for the  rule  to  make
+       There  is  now  no need for the phony prerequisite for the rule to make
        .pdf files from .tex files.  But I have added a rule to make .pdf files
-       from  .fig  files produced by the xfig program; these are commonly used
-       for graphics insertions in LaTeX documents.   Latexmk  is  arranged  to
+       from .fig files produced by the xfig program; these are  commonly  used
+       for  graphics  insertions  in  LaTeX documents.  Latexmk is arranged to
        output a dependency file after each run.  It is given the -recorder op-
-       tion,  which  improves its detection of files generated during a run of
-       pdflatex; such files should not be in the dependency list.  The -e  op-
-       tions  are  used  to  turn off all custom dependencies, and to document
-       this.  Instead the -use-make is used to delegate the making of  missing
-       files to make itself.
+       tion, which improves its detection of files generated during a  run  of
+       pdflatex;  such files should not be in the dependency list.  The -e op-
+       tions are used to turn off all custom  dependencies,  and  to  document
 
-       Suppose  in  the LaTeX file there is a command \includegraphics{graph},
-       and an xfig file "graph.fig" exists.  On a first run, pdflatex  reports
-       a  missing  file, named "graph". Latexmk succeeds in making "graph.pdf"
-       by calling "make graph.pdf", and after completion of its work, it lists
-       "fig.pdf" among the dependents of the file latexmk is making.  Then let
-       "fig.fig" be updated, and then let make be  run.   Make  first  remakes
-       "fig.pdf", and only then reruns latexmk.
 
-       Thus  we  now  have  a method by which all the subsidiary processing is
-       delegated to make.
 
-       Escaping of characters in dependency lists: There are  certain  special
-       characters  that need to be escaped when names of files and directories
-       containing them appear in a dependency list used  by  a  make  program.
-       Generally, such special characters are best avoided.
+                                 7 April 2024                               86
 
-       By  default,  latexmk  does no escaping of this kind, and the user will
-       have to arrange to deal with the issue separately, if the relevant spe-
-       cial characters are used.  Note that the rules for escaping  depend  on
-       which make program is used, and on its version.
 
 
 
 
-                                31 January 2024                             81
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+       this.   Instead the -use-make is used to delegate the making of missing
+       files to make itself.
 
+       Suppose in the LaTeX file there is a  command  \includegraphics{graph},
+       and  an xfig file "graph.fig" exists.  On a first run, pdflatex reports
+       a missing file, named "graph". Latexmk succeeds in  making  "graph.pdf"
+       by calling "make graph.pdf", and after completion of its work, it lists
+       "fig.pdf" among the dependents of the file latexmk is making.  Then let
+       "fig.fig"  be  updated,  and  then let make be run.  Make first remakes
+       "fig.pdf", and only then reruns latexmk.
 
+       Thus we now have a method by which all  the  subsidiary  processing  is
+       delegated to make.
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+       Escaping  of  characters in dependency lists: There are certain special
+       characters that need to be escaped when names of files and  directories
+       containing  them  appear  in  a dependency list used by a make program.
+       Generally, such special characters are best avoided.
 
+       By default, latexmk does no escaping of this kind, and  the  user  will
+       have to arrange to deal with the issue separately, if the relevant spe-
+       cial  characters  are used.  Note that the rules for escaping depend on
+       which make program is used, and on its version.
 
-       One  special case is of spaces, since those are particularly prevalent,
-       notably in standard choices of name for a user's  home  directory.   So
-       latexmk  does  provide  an  option  to  escape  spaces.  See the option
+       One special case is of spaces, since those are particularly  prevalent,
+       notably  in  standard  choices of name for a user's home directory.  So
+       latexmk does provide an  option  to  escape  spaces.   See  the  option
        -deps_escape=... and the variable $deps_escape for details.
 
 
 
 NON_ASCII CHARACTERS IN FILENAMES, RC FILES, ETC
        Modern operating systems and file systems allow non-ASCII characters in
-       the names of files and directories  that  encompass  the  full  Unicode
+       the  names  of  files  and  directories that encompass the full Unicode
        range.  Mostly, latexmk deals with these correctly.  However, there are
-       some  situations in which there are problems, notably on Microsoft Win-
+       some situations in which there are problems, notably on Microsoft  Win-
        dows.  Prior to version 4.77, latexmk had problems with non-ASCII file-
-       names on Windows, even though there were no corresponding  problems  on
+       names  on  Windows, even though there were no corresponding problems on
        macOS and Linux.  These problems are corrected in the present version.
 
        DETAILS TO BE FILLED IN
@@ -5376,47 +5730,47 @@ SEE ALSO
 
 BUGS (SELECTED)
        Sometimes a viewer (gv) tries to read an updated .ps or .pdf file after
-       its  creation is started but before the file is complete.  Work around:
+       its creation is started but before the file is complete.  Work  around:
        manually refresh (or reopen) display.  Or use one of the other preview-
        ers and update methods.
 
-       (The following isn't really a bug, but concerns  features  of  preview-
-       ers.)   Preview  continuous mode only works perfectly with certain pre-
-       viewers: Xdvi on UNIX/Linux works for  dvi  files.   Gv  on  UNIX/Linux
-       works  for  both  postscript  and pdf.  Ghostview on UNIX/Linux needs a
-       manual update (reopen); it views postscript and pdf.  Gsview under  MS-
-       Windows  works  for both postscript and pdf, but only reads the updated
-       file when its screen is refreshed.   Acroread  under  UNIX/Linux  views
-       pdf,  but  the  file needs to be closed and reopened to view an updated
-       version.  Under MS-Windows, acroread locks its input file  and  so  the
-       pdf  file  cannot  be updated.  (Remedy: configure latexmk to use suma-
-       trapdf instead.)
 
-THANKS TO
-       Authors of previous versions.  Many users with their feedback, and  es-
-       pecially David Coppit (username david at node coppit.org) who made many
-       useful  suggestions  that contributed to version 3, and Herbert Schulz.
-       (Please note that the e-mail addresses are not written in  their  stan-
-       dard form to avoid being harvested too easily.)
 
-AUTHOR
-       Current  version,  by  John Collins (Version 4.83).  Report bugs etc to
-       his e-mail (jcc8 at psu.edu).
 
-       Released     version     can      be      obtained      from      CTAN:
+                                 7 April 2024                               87
 
 
 
-                                31 January 2024                             82
 
 
+LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
+       (The  following  isn't  really a bug, but concerns features of preview-
+       ers.)  Preview continuous mode only works perfectly with  certain  pre-
+       viewers:  Xdvi  on  UNIX/Linux  works  for dvi files.  Gv on UNIX/Linux
+       works for both postscript and pdf.  Ghostview  on  UNIX/Linux  needs  a
+       manual  update (reopen); it views postscript and pdf.  Gsview under MS-
+       Windows works for both postscript and pdf, but only reads  the  updated
+       file  when  its  screen  is refreshed.  Acroread under UNIX/Linux views
+       pdf, but the file needs to be closed and reopened to  view  an  updated
+       version.   Under  MS-Windows,  acroread locks its input file and so the
+       pdf file cannot be updated.  (Remedy: configure latexmk  to  use  suma-
+       trapdf instead.)
 
-LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
+THANKS TO
+       Authors  of previous versions.  Many users with their feedback, and es-
+       pecially David Coppit (username david at node coppit.org) who made many
+       useful suggestions that contributed to version 3, and  Herbert  Schulz.
+       (Please  note  that the e-mail addresses are not written in their stan-
+       dard form to avoid being harvested too easily.)
 
+AUTHOR
+       Current version, by John Collins (Version 4.85).  Report  bugs  etc  to
+       his e-mail (jcc8 at psu.edu).
 
-       <http://www.ctan.org/pkg/latexmk/>,   and  from  the  author's  website
+       Released      version      can      be      obtained     from     CTAN:
+       <http://www.ctan.org/pkg/latexmk/>,  and  from  the  author's   website
        <https://www.cantab.net/users/johncollins/latexmk/>.
        Modifications and enhancements by Evan McLean (Version 2.0)
        Original script called "go" by David J. Musliner (RCS Version 3.2)
@@ -5449,30 +5803,6 @@ LATEXMK(1)                  General Commands Manual                 LATEXMK(1)
 
 
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-                                31 January 2024                             83
+                                 7 April 2024                               88
 
 
diff --git a/support/texshop/README.txt b/support/texshop/README.txt
index e3cde65c75..7e02938c30 100644
--- a/support/texshop/README.txt
+++ b/support/texshop/README.txt
@@ -7,4 +7,4 @@ The main author is Richard Koch, koch@uoregon.edu, with supporting contributions
 Consult the program web site, https://pages.uoregon.edu/koch/texshop/texshop.html,
 for full source code, an extensive Changes document, and other information.
 
-The current version, 5.31, was released on March 24, 2024.
\ No newline at end of file
+The current version, 5.32, was released on April 10, 2024.
\ No newline at end of file
diff --git a/support/texshop/texshop531.html b/support/texshop/texshop531.html
deleted file mode 100644
index cd43529456..0000000000
--- a/support/texshop/texshop531.html
+++ /dev/null
@@ -1,19 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-  <title>TeXShop</title>
-  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-  <style type="text/css" media="screen">@import "v1.css";</style>
-</head>
-
-<body>
-
-<p> Version 5.31, released two days after the 5.30 release, fixes two bugs in that release:
-<ul>
-<li> The first bug caused the Preview window to advance a page after each typesetting job in Single  and Double Page modes. 
-<li>The second bug caused new projects to set magnification to 100 when initially typeset.
-</ul>
-
-</body>
-</html>
diff --git a/support/texshop/texshop532.html b/support/texshop/texshop532.html
new file mode 100644
index 0000000000..eadbfaa2fa
--- /dev/null
+++ b/support/texshop/texshop532.html
@@ -0,0 +1,25 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+  <title>TeXShop</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+  <style type="text/css" media="screen">@import "v1.css";</style>
+</head>
+
+<body>
+
+<p> Version 5.32 fixes one bug. The following process will trigger the process for a few people but probably not you. Create a source window using the menu command "New". Enter one or two lines of text and then save the file using the menu command "Save As". Quit TeXShop and restart it again. Open the new source file. The file's name will be added to TeXShop's "Window" menu, but the corresponding source window will not appear. It seems that TeXShop has created a source file which it cannot display. This is an alarming bug.
+
+<p> Here is the good news. There is nothing wrong with the file; it contains the correct text and can easily be opened using a trick. Even better, the bug only occurs if the user has selected "Syntax Color expl3 Code" in the TeXShop Source Window. This menu is a toggle which turns expl3 coloring on or off. When a window first opens, it is off.
+The only problem is that TeXShop has a hidden preference which turns the item on by default when windows are first opened:
+<pre>
+   defaults write TeXShop expl3SyntaxColoring YES
+</pre>
+Only users who set this hidden preference are likely to see the bug.
+
+<p> The bug has nothing to do with TeXShop's file saving code. It is a bug in TeXShop's syntax coloring code. When opening a source file, TeXShop syntax colors the source just before making the window visible. If the syntax coloring fails, the window is never made visible.
+TeXShop 5.32 fixes one step in the expl3 syntax coloring routine. After that, the routine does not fail and all windows open correctly.
+
+</body>
+</html>
diff --git a/systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl b/systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl
index 04fa18c7ef..7f9bc3d86d 100644
--- a/systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl
+++ b/systems/texlive/tlnet/tlpkg/installer/ctan-mirrors.pl
@@ -40,16 +40,20 @@ $mirrors = {
     },
     'Japan' => {
       'https://ftp.jaist.ac.jp/pub/CTAN/' => 1,
+      'https://ftp.kddilabs.jp/CTAN/' => 1,
       'https://ftp.yz.yamagata-u.ac.jp/pub/CTAN/' => 1,
+      'https://jp.mirrors.cicku.me/ctan/' => 1,
     },
     'Korea' => {
       'http://ftp.ktug.org/tex-archive/' => 1,
-      'https://ftp.kaist.ac.kr/tex-archive/' => 1,
       'https://kr.mirrors.cicku.me/ctan/' => 1,
       'https://lab.uklee.pe.kr/tex-archive/' => 1,
       'https://mirror.kakao.com/CTAN/' => 1,
       'https://mirror.navercorp.com/CTAN/' => 1,
     },
+    'Singapore' => {
+      'https://sg.mirrors.cicku.me/ctan/' => 1,
+    },
     'Taiwan' => {
       'https://ctan.mirror.twds.com.tw/tex-archive/' => 1,
     },
@@ -174,6 +178,9 @@ $mirrors = {
       'https://mirror.quantum5.ca/CTAN/' => 1,
       'https://muug.ca/mirror/ctan/' => 1,
     },
+    'Costa Rica' => {
+      'https://mirrors.ucr.ac.cr/CTAN/' => 1,
+    },
     'USA' => {
       'http://mirrors.ibiblio.org/pub/mirrors/CTAN/' => 1,
       'https://ctan.math.illinois.edu/' => 1,
diff --git a/systems/texlive/tlnet/tlpkg/texlive.tlpdb b/systems/texlive/tlnet/tlpkg/texlive.tlpdb
index 69e08227fb..57639db9aa 100644
--- a/systems/texlive/tlnet/tlpkg/texlive.tlpdb
+++ b/systems/texlive/tlnet/tlpkg/texlive.tlpdb
@@ -26,11 +26,11 @@ depend container_split_src_files/1
 depend frozen/0
 depend minrelease/2016
 depend release/2024
-depend revision/70904
+depend revision/70911
 
 name 00texlive.image
 category TLCore
-revision 70890
+revision 70906
 shortdesc TeX Live files only in the source repository
 longdesc The files here are not copied by the installer and containers
 longdesc are not built for them; they exist only in the source
@@ -2449,6 +2449,7 @@ runfiles size=14462
  tlpkg/tlpsrc/js-misc.tlpsrc
  tlpkg/tlpsrc/jsclasses.tlpsrc
  tlpkg/tlpsrc/jslectureplanner.tlpsrc
+ tlpkg/tlpsrc/jsonparse.tlpsrc
  tlpkg/tlpsrc/jumplines.tlpsrc
  tlpkg/tlpsrc/junicode.tlpsrc
  tlpkg/tlpsrc/junicodevf.tlpsrc
@@ -72065,7 +72066,7 @@ containerchecksum 889eae40b82f31c7c4b3a17740399c763dabec7986fcb39261b252afff69a0
 
 name collection-latexextra
 category Collection
-revision 70890
+revision 70906
 shortdesc LaTeX additional packages
 relocated 1
 longdesc A very large collection of add-on packages for LaTeX.
@@ -72811,6 +72812,7 @@ depend jmsdelim
 depend jobname-suffix
 depend joinbox
 depend jslectureplanner
+depend jsonparse
 depend jumplines
 depend jvlisting
 depend kalendarium
@@ -73611,7 +73613,7 @@ depend zref-vario
 depend zwgetfdate
 depend zwpagelayout
 containersize 7148
-containerchecksum 495c5a9627a2d75f18463a6696310088a2a3bc4c501153574159c363588c233534d55270e154e200bef95673c4c683f77e316058c1a421379a5a1a3acc1de807
+containerchecksum 3394936bdc6a2283e23b6d24a97644abd0789802cf8ef10eb1fadbbdd8e4deab85935000bb02d9e20bb89f2e0b18ca7406d8339b9e6750221eacf71bace31552
 
 name collection-latexrecommended
 category Collection
@@ -105129,11 +105131,11 @@ catalogue-topics dvi-pdf
 
 name dvipdfmx.aarch64-linux
 category TLCore
-revision 70489
+revision 70910
 shortdesc aarch64-linux files of dvipdfmx
-containersize 412872
-containerchecksum 869f12ecd59645f8b310e2e5bd76a48d80a0a80847e40b714d3d1feae8312957a4fda4bed4f43ef1a937c3a547398db87934fa6fbdc823d056784b260c39d2b3
-binfiles arch=aarch64-linux size=277
+containersize 413136
+containerchecksum c14ef476efb90763115136497617beb6eb38e91b826d322039deea5d4cda9a1aafd6bde1bee58266183bbc7716b57d4b7ae5a66ecaf36c70c122e500fd1e7934
+binfiles arch=aarch64-linux size=278
  bin/aarch64-linux/dvipdfm
  bin/aarch64-linux/dvipdfmx
  bin/aarch64-linux/dvipdft
@@ -105171,11 +105173,11 @@ binfiles arch=amd64-netbsd size=346
 
 name dvipdfmx.armhf-linux
 category TLCore
-revision 70489
+revision 70910
 shortdesc armhf-linux files of dvipdfmx
-containersize 349384
-containerchecksum 98c4232a93f5c7e49eb1a9beeb6c351b2e876e20fafd7aa62cf33693279bc78d6c7aa64d81afc6ad5e1cb10701f6ead0ec6dfbb1e6268857f31b1d8df41ba039
-binfiles arch=armhf-linux size=218
+containersize 381520
+containerchecksum e8459092bc227b5316d976339943b2ecc01b325700b62158e301d5ea7571c036dc0e828cc0c72ce1cc9c1ba1e2c7f4c6f40d75fc63f15824f2afeb5825945232
+binfiles arch=armhf-linux size=183
  bin/armhf-linux/dvipdfm
  bin/armhf-linux/dvipdfmx
  bin/armhf-linux/dvipdft
@@ -168678,6 +168680,32 @@ catalogue-license lppl1.3
 catalogue-topics teaching planning
 catalogue-version 1.13
 
+name jsonparse
+category Package
+revision 70906
+shortdesc Parse, store and access JSON data in LaTeX documents
+relocated 1
+longdesc This package provides an easy way to read in JSON data from
+longdesc files or strings in LaTeX documents, parse the data and store
+longdesc it in a user-defined token variable.
+containersize 3132
+containerchecksum e771c9e734cf71d615425ca678a010f7c7faf23394ca8826b8bdb0ca8d6e07be02ca52808d57c625c07c692602b916d3a815a8c7bcf46cefee794e09e5a25ddb
+doccontainersize 373912
+doccontainerchecksum 7a1a7297d16e034484471de43a1a6594c1259a923c471b3c42f5dd97ad1e723a6c0f557ec4170b16108092e500c29cc5e8c97fd37913818457d33f3b71d56d16
+docfiles size=104
+ RELOC/doc/latex/jsonparse/LICENCE
+ RELOC/doc/latex/jsonparse/README.md details="Readme"
+ RELOC/doc/latex/jsonparse/jsonparse-doc.pdf details="Package documentation"
+ RELOC/doc/latex/jsonparse/jsonparse-doc.tex
+runfiles size=4
+ RELOC/tex/latex/jsonparse/jsonparse.sty
+catalogue-contact-bugs https://github.com/jasperhabicht/jsonparse/issues
+catalogue-contact-repository https://github.com/jasperhabicht/jsonparse
+catalogue-ctan /macros/latex/contrib/jsonparse
+catalogue-license lppl1.3c
+catalogue-topics data-manip
+catalogue-version 0.5.5
+
 name jumplines
 category Package
 revision 37553
@@ -186322,7 +186350,7 @@ binfiles arch=x86_64-solaris size=1
 
 name latexmk
 category Package
-revision 70853
+revision 70909
 shortdesc Fully automated LaTeX document generation
 longdesc Latexmk completely automates the process of generating a LaTeX
 longdesc document. Given the source files for a document, latexmk issues
@@ -186334,11 +186362,11 @@ longdesc files), and reruns LaTeX, etc., whenever a source file has
 longdesc changed. Thus a previewer can offer a display of the document's
 longdesc latest state.
 depend latexmk.ARCH
-containersize 117260
-containerchecksum 4087cb4ee820e524008e23154da94a32526fa5095b44557df5c9df1cdfb4cae3d7b5ca3680782b71fb7b15838fc939060490f4c978875ba7f58f664b8008f106
-doccontainersize 551848
-doccontainerchecksum 2873b21f9bcac24bc923e93cf9516ddd3c365cbb3a19e4ff53bd7e62f46cab113d8775ee07a9fa33081514ef455296fe2c0d0164ede6e31dc4d37bcacf35c22d
-docfiles size=300
+containersize 119144
+containerchecksum be74224df53e6ad9a7d251a447cedef3c961ae2e96238950d5938c1b3b3eca8d61038092eb319ab3458555c45af221251069a5dc0a1e8099dab65a8249a2f053
+doccontainersize 570016
+doccontainerchecksum 645163e960d4b1c49ef0c50897ee25941d0c43d99eaced8b6079c1c070b3caa8d288d72fd9edcd5dc640a39e6bc7d2da4a418e67a475f21aa6afadfb15bd4533
+docfiles size=311
  texmf-dist/doc/man/man1/latexmk.1
  texmf-dist/doc/man/man1/latexmk.man1.pdf
  texmf-dist/doc/support/latexmk/CHANGES
@@ -186359,6 +186387,7 @@ docfiles size=300
  texmf-dist/doc/support/latexmk/example_rcfiles/hyperxmp-latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/knitr-latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/lualatex_latexmkrc
+ texmf-dist/doc/support/latexmk/example_rcfiles/memoize_latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/minted_latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/mpost_latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/nomenclature_latexmkrc
@@ -186368,7 +186397,7 @@ docfiles size=300
  texmf-dist/doc/support/latexmk/example_rcfiles/pythontex-latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/sagetex_latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/schulz-texshop-latexmkrc
- texmf-dist/doc/support/latexmk/example_rcfiles/splitindex.latexmkrc
+ texmf-dist/doc/support/latexmk/example_rcfiles/splitindex_latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/sweave_latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/tex4ht-latexmkrc
  texmf-dist/doc/support/latexmk/example_rcfiles/texinfo-latexmkrc
@@ -186391,14 +186420,14 @@ docfiles size=300
  texmf-dist/doc/support/latexmk/latexmk.cmd
  texmf-dist/doc/support/latexmk/latexmk.pdf details="Manual page, PDF"
  texmf-dist/doc/support/latexmk/latexmk.txt details="Manual page, text format"
-runfiles size=127
+runfiles size=129
  texmf-dist/scripts/latexmk/latexmk.pl
 catalogue-also latexn prv arara
 catalogue-contact-home https://www.cantab.net/users/johncollins/latexmk/index.html
 catalogue-ctan /support/latexmk
 catalogue-license gpl2
 catalogue-topics compilation
-catalogue-version 4.83
+catalogue-version 4.85
 
 name latexmk.aarch64-linux
 category Package
@@ -204463,7 +204492,7 @@ binfiles arch=x86_64-linuxmusl size=3994
 
 name luakeys
 category Package
-revision 65533
+revision 70908
 shortdesc A Lua module for parsing key-value options
 relocated 1
 longdesc This package provides a Lua module that can parse key-value
@@ -204473,13 +204502,13 @@ longdesc entirely by using the Lua language and does not rely on TeX.
 longdesc Therefore this package can only be used with the TeX engine
 longdesc LuaTeX. Since luakeys uses LPeg, the parsing mechanism should
 longdesc be pretty robust.
-containersize 14240
-containerchecksum 618719877ab11bb672c319bcc078a625bc92b4d3a783eff8414f6c9597ec8ea3225822afbeb0d1bb04e8889cc3003f4a1ed8063e1ecca410ec6f0170fa55eb00
-doccontainersize 435504
-doccontainerchecksum be88aac81b85730c0cd85ab76541b8af01ca85326a4449168062ff80690db7d90669dff794b3f5926f1344a0de03289958fd4d2cf0cd2eb4b593dd052577e01c
-docfiles size=121
+containersize 14364
+containerchecksum 64e22903929524b18510119dd984d6566e3a458b4187d40ff250d713201464be84a045ffaa7a37da9537fa24b57010a66cbf7fe35278bf4c04ee08a4bf362e49
+doccontainersize 435984
+doccontainerchecksum df341e883eb443eeefaad10dc0968486905d5a6f359f9e48d93a0296d2a78a3949a35e65572144a92fee0e45d6e4fd818fbca75a427c7ee94be79ac851676fef
+docfiles size=122
  RELOC/doc/luatex/luakeys/README.md details="Readme"
- RELOC/doc/luatex/luakeys/documentation.tex
+ RELOC/doc/luatex/luakeys/luakeys-doc.tex
  RELOC/doc/luatex/luakeys/luakeys.pdf details="Package documentation"
 runfiles size=19
  RELOC/tex/luatex/luakeys/luakeys-debug.sty
@@ -204492,7 +204521,7 @@ catalogue-contact-repository https://github.com/Josef-Friedrich/luakeys
 catalogue-ctan /macros/luatex/generic/luakeys
 catalogue-license lppl1.3c
 catalogue-topics keyval luatex
-catalogue-version 0.13.0
+catalogue-version 0.14.0
 
 name lualatex-doc-de
 category Package
@@ -254839,7 +254868,7 @@ catalogue-version 0.13
 
 name pdfmanagement-testphase
 category Package
-revision 70778
+revision 70907
 shortdesc LaTeX PDF management testphase bundle
 relocated 1
 longdesc This is a temporary package, which is used during a test phase
@@ -254852,11 +254881,11 @@ longdesc allow users and package authors to safely test the code. At a
 longdesc later stage it will be integrated into the LaTeX kernel (or in
 longdesc parts into permanent support packages), and the current
 longdesc testphase bundle will be removed.
-containersize 54136
-containerchecksum 8f07d45095f27be9e29ed896ff9b4b4c37429aa0dfb3483a226f74b5e449efcaf30f6f565563a604feee11f2b612ff0d9bc3dcdc708e0c153156f9f6ddc1bc4d
-doccontainersize 8499128
-doccontainerchecksum 4ca0e65b5c128f58856636eaf805bed9d967f0597e5f46e722fcdcee58c7b3b9e981667578be24b07d6b0d758584eea61fee12a439c7377ef9e1b49423e536a3
-docfiles size=2797
+containersize 54608
+containerchecksum 9e35569e6d5dd4ebf18d5937059c44f2139926aaac80f7c9c2ad0431150b3ec1d3b8cfcf08029903611aea70c0ad2d6e27532c4f59ba677bd27819bbda4cd8ef
+doccontainersize 8522084
+doccontainerchecksum da0fbe53e7eb93ce5d282a3e82c27bd7abe8883903001d815d3ee733d98f6b9bff8aded829f8a73b2568b781852e815d267554250086248c712ae46f7a6a3d64
+docfiles size=2799
  RELOC/doc/latex/pdfmanagement-testphase/CHANGELOG.md
  RELOC/doc/latex/pdfmanagement-testphase/README.md details="Readme"
  RELOC/doc/latex/pdfmanagement-testphase/hyperref-generic.pdf
@@ -254879,9 +254908,9 @@ docfiles size=2797
  RELOC/doc/latex/pdfmanagement-testphase/pdfmanagement-firstaid.pdf
  RELOC/doc/latex/pdfmanagement-testphase/pdfmanagement-testphase.pdf details="Package documentation"
  RELOC/doc/latex/pdfmanagement-testphase/update-metadata.txt
-srccontainersize 140084
-srccontainerchecksum b68079b63666be1c2fd9dfb4d319c152b71a49942a4fb2ad4b6127856dc2bbffd4138af3c42e40a89ff1cf025aa7a6136971edb155b1661b80493d86f1105bdb
-srcfiles size=203
+srccontainersize 140848
+srccontainerchecksum 446bf68b594ed9e839f3d1d16df561be3f7b24e9174dc57da6e9d27b6ebc92254ce86d0bf9648d974da83b00b3a02b6d7162ed2260f0006e07eaacac1b670778
+srcfiles size=205
  RELOC/source/latex/pdfmanagement-testphase/hyperref-generic.dtx
  RELOC/source/latex/pdfmanagement-testphase/l3backend-testphase.dtx
  RELOC/source/latex/pdfmanagement-testphase/l3pdfannot.dtx
@@ -254902,7 +254931,7 @@ srcfiles size=203
  RELOC/source/latex/pdfmanagement-testphase/pdfmanagement-firstaid.dtx
  RELOC/source/latex/pdfmanagement-testphase/pdfmanagement-testphase.dtx
  RELOC/source/latex/pdfmanagement-testphase/pdfmanagement-testphase.ins
-runfiles size=107
+runfiles size=110
  RELOC/tex/latex/pdfmanagement-testphase/color-ltx.sty
  RELOC/tex/latex/pdfmanagement-testphase/colorspace-patches-tmp-ltx.sty
  RELOC/tex/latex/pdfmanagement-testphase/hgeneric-testphase.def
@@ -254924,7 +254953,7 @@ catalogue-contact-repository https://github.com/latex3/pdfresources
 catalogue-ctan /macros/latex/contrib/pdfmanagement-testphase
 catalogue-license lppl1.3c
 catalogue-topics latex-devel pdf-feat
-catalogue-version 0.96g
+catalogue-version 0.96h
 
 name pdfmarginpar
 category Package
@@ -313678,7 +313707,7 @@ binfiles arch=x86_64-solaris size=1
 
 name tex4ht
 category Package
-revision 70827
+revision 70911
 shortdesc Convert (La)TeX to HTML/XML
 longdesc A converter from TeX and LaTeX to SGML-based formats such as
 longdesc (X)HTML, MathML, OpenDocument, and Docbook, providing a
@@ -313699,10 +313728,10 @@ longdesc files from them is nontrivial, and generally done with the
 longdesc Makefile in development, from which the TeX4ht package in TeX
 longdesc Live is updated.
 depend tex4ht.ARCH
-containersize 1129580
-containerchecksum 272d845f2c914b6598404c945439e1817cff2f6097f3ccacfe1cfcb6629baaa0aee1b6ae87361d1c3fa80d75f07082e56115f07fbb2c25c83cdb818da36ad0fa
-doccontainersize 136384
-doccontainerchecksum a8c2aaa758c00e1760a66f6a46fa141ceda64f9f56a8fab28eb6c630a74d00950c6a5e1ac7a7e3049c3c5d477ac6c216b93769852647452873c596a6c5d462ef
+containersize 1129584
+containerchecksum 959d10674b606ab47bda962f21c4052cdab61f68e97f56675ec9796c0e156f577a516079100458cadcbc80aa14c94a244028380ae1b3952f0896d852076dedcd
+doccontainersize 136388
+doccontainerchecksum 941de9c89da47bace19e3aa78e96a086534c6244adb941fefbf3a287414bf99bdf67d91bcb4817f806e00506f43bd952f5d31bdccb6044450cb02a5f115f870a
 docfiles size=260
  texmf-dist/doc/generic/tex4ht/Makefile
  texmf-dist/doc/generic/tex4ht/README details="Readme"
@@ -313774,8 +313803,8 @@ docfiles size=260
  texmf-dist/doc/generic/tex4ht/mn56.html
  texmf-dist/doc/generic/tex4ht/mn5x.png
  texmf-dist/doc/generic/tex4ht/mn6x.png
-srccontainersize 1495652
-srccontainerchecksum c41d243e0eca915e3bf4950f7109156a91dc14aede8d85888071a6beafd089094f6da1718a42bdddfb1a159d780f48557a6a894563d5bd264572d5c3b392657c
+srccontainersize 1491620
+srccontainerchecksum 38964df96a3b433ffe9d1ea451ff178623337bbe35f4e06837c9bf73aec22f88671e9cc04c83b746de82866f02c111311f712d646001ef06eb02f3b1e6239af6
 srcfiles size=4647
  texmf-dist/source/generic/tex4ht/ChangeLog
  texmf-dist/source/generic/tex4ht/Makefile
diff --git a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5 b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5
index 2c9f8f2772..70da7d6a0b 100644
--- a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5
+++ b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.md5
@@ -1 +1 @@
-5636a2ed5f60663b8f813b0af93914aa  texlive.tlpdb
+bbfd9b854a5e9f1b42596353c2193a32  texlive.tlpdb
diff --git a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512 b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512
index dca3577063..efe7882130 100644
--- a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512
+++ b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512
@@ -1 +1 @@
-9cc28e1c59bd12c71936e32466eb88ce19ab9beb66a88bf7a68a0e3bc4d9c333e1a3b5a7e72c2f084066471913c3c13a39a1da299cf9ef748d9a6fb9e120d54c  texlive.tlpdb
+6e1b8b3937e0085f93b99cbef24545cb803e5f2e297c8fe5c65644d39368fe9eda6dd3a4fef81cffe80ff9a9a80f9a159329a0c323082f92a89c151d5be4e97c  texlive.tlpdb
diff --git a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc
index 06a3b2a38f..75c956619d 100644
--- a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc
+++ b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.sha512.asc
@@ -1,11 +1,11 @@
 -----BEGIN PGP SIGNATURE-----
 
-iQEzBAEBCgAdFiEE2PL4YFeoV+QqiBBqTOGHfhlDjHAFAmYV01sACgkQTOGHfhlD
-jHAMXgf+OQ8SdEMppyImkH7PjhW+l7lTptn/1XEh9OA28npIczcud+3lZZLyKHSa
-O76rgqy2jnU7Q87e3y7dXMAaxXPk45cArmIuuB2zyxiMwhSNNVknk9P3+0psuk+C
-GrlnogrBtBEdDqb3h1sp0SM3hCH2pv15OhDiCnu6aseY/rU7YYasttdVTXJeDyB1
-FHT6ivGe2n4E5Z5Navwm8rE248rJ0TWMNvrK7YvmPzqr2tz38cY4Ypas/Y/2xnOs
-5eZLWXY2RVgwKjLk6e1Lphumf9EPc2ohnFF2b4TU3npnYRJOQihvtx6A56TGTST8
-R+Fvm15/qnyMslUkdG4h2gs3Uja3zw==
-=DTJb
+iQEzBAEBCgAdFiEE2PL4YFeoV+QqiBBqTOGHfhlDjHAFAmYXJPUACgkQTOGHfhlD
+jHD1gQf8CtJA8AY+6bPqDbYsfGknPX1F6YQ6b242vRarI9B5oe42j87RCYUZThMy
+ItUt7nokMyk3ivX7fWClaaQ2MFWaNReZ5S1uONIzCaMo18SpluFNqqdqoFfFe/IL
+k4N1Ujo4wMZFfHvd/7V+ohK5NZqsbIRuB7FRbo++fDMQ9Gm2OZeELnv1YF1rdafO
+p3Q4YqhMpnABAWdt8vVKgrYFu/GKxrqWkJ0QkRpXGEu1qbA7T/F8c4e1UsaGDNJA
+nSZKJLq5un/3eITdY1gmc1YTErpdCETxdA/6zsBkD8Y+BgHO9bBfrGijLe54/o2o
+mYtRuZpdggPkrBFGMYK83katpxu8+A==
+=Qjvn
 -----END PGP SIGNATURE-----
diff --git a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz
index 6543d2c7d7..892e2025fc 100644
--- a/systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz
+++ b/systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz
diff --git a/timestamp b/timestamp
index 14fc3f4215..74105822d4 100644
--- a/timestamp
+++ b/timestamp
@@ -2,4 +2,4 @@
 #   The source CTAN of this site's material:
 dante.ctan.org
 #   The year-month-day-hour-minute of this site's material:
-2024-04-10-02-02
+2024-04-11-02-02