| 1 |
% \iffalse meta-comment |
| 2 |
% |
| 3 |
% Copyright 2024 |
| 4 |
% The LaTeX Project and any individual authors listed elsewhere |
| 5 |
% in this file. |
| 6 |
% |
| 7 |
% This file is part of the LaTeX base system. |
| 8 |
% -—————————————— |
| 9 |
% |
| 10 |
% It may be distributed and/or modified under the |
| 11 |
% conditions of the LaTeX Project Public License, either version 1.3c |
| 12 |
% of this license or (at your option) any later version. |
| 13 |
% The latest version of this license is in |
| 14 |
% https://www.latex-project.org/lppl.txt |
| 15 |
% and version 1.3c or later is part of all distributions of LaTeX |
| 16 |
% version 2008 or later. |
| 17 |
% |
| 18 |
% This file has the LPPL maintenance status "maintained". |
| 19 |
% |
| 20 |
% The list of all files belonging to the LaTeX base distribution is |
| 21 |
% given in the file `manifest.txt'. See also `legal.txt' for additional |
| 22 |
% information. |
| 23 |
% |
| 24 |
% The list of derived (unpacked) files belonging to the distribution |
| 25 |
% and covered by LPPL is defined by the unpacking scripts (with |
| 26 |
% extension .ins) which are part of the distribution. |
| 27 |
% |
| 28 |
% \fi |
| 29 |
% Filename: ltnews40.tex |
| 30 |
% |
| 31 |
% This is issue 40 of LaTeX News. |
| 32 |
|
| 33 |
\NeedsTeXFormat{LaTeX2e}[2020-02-02] |
| 34 |
|
| 35 |
\documentclass{ltnews} |
| 36 |
|
| 37 |
%% Maybe needed only for Chris' inadequate system: |
| 38 |
\providecommand\Dash {\unskip \textemdash} |
| 39 |
|
| 40 |
%% NOTE: Chris' preferred hyphens! |
| 41 |
%% \showhyphens{parameters} |
| 42 |
%% \hyphenation{because} |
| 43 |
|
| 44 |
\usepackage[T1]{fontenc} |
| 45 |
|
| 46 |
\usepackage{lmodern,url,hologo} |
| 47 |
|
| 48 |
\usepackage{csquotes} |
| 49 |
\usepackage{multicol} |
| 50 |
\usepackage{color} |
| 51 |
|
| 52 |
\providecommand\hook[1]{\texttt{#1}} |
| 53 |
|
| 54 |
\providecommand\meta[1]{$\langle$\textrm{\itshape#1}$\rangle$} |
| 55 |
\providecommand\option[1]{\texttt{#1}} |
| 56 |
\providecommand\env[1]{\texttt{#1}} |
| 57 |
\providecommand\Arg[1]{\texttt\{\meta{#1}\texttt\}} |
| 58 |
|
| 59 |
|
| 60 |
\providecommand\eTeX{\hologo{eTeX}} |
| 61 |
\providecommand\XeTeX{\hologo{XeTeX}} |
| 62 |
\providecommand\LuaTeX{\hologo{LuaTeX}} |
| 63 |
\providecommand\pdfTeX{\hologo{pdfTeX}} |
| 64 |
\providecommand\MiKTeX{\hologo{MiKTeX}} |
| 65 |
\providecommand\CTAN{\textsc{ctan}} |
| 66 |
\providecommand\TL{\TeX\,Live} |
| 67 |
|
| 68 |
|
| 69 |
\providecommand\githubissue[2][]{\ifhmode\unskip\fi |
| 70 |
\quad\penalty500\strut\nobreak\hfill |
| 71 |
\mbox{\small\slshape(% |
| 72 |
\href{https://github.com/latex3/latex2e/issues/\getfirstgithubissue#2 \relax}% |
| 73 |
{github issue#1 #2}% |
| 74 |
)}% |
| 75 |
\par\smallskip} |
| 76 |
|
| 77 |
|
| 78 |
% same for issues in the tagging repository: |
| 79 |
|
| 80 |
\providecommand\taggingissue[2][]{\ifhmode\unskip\fi |
| 81 |
\quad\penalty500\strut\nobreak\hfill |
| 82 |
\mbox{\small\slshape(% |
| 83 |
\href{https://github.com/latex3/tagging-project/issues/\getfirstgithubissue#2 \relax}% |
| 84 |
{github tagging issue#1 #2}% |
| 85 |
)}% |
| 86 |
\par\smallskip} |
| 87 |
|
| 88 |
%% But Chris has to mostly disable \href for his TEXPAD app: |
| 89 |
%% \def\href #1#2{#2} % Only For Chris' deficient TeX engine |
| 90 |
|
| 91 |
% simple solution right now (just link to the first issue if there are several) |
| 92 |
\def\getfirstgithubissue#1 #2\relax{#1} |
| 93 |
|
| 94 |
\providecommand\sxissue[1]{\ifhmode\unskip |
| 95 |
\else |
| 96 |
% githubissue preceding |
| 97 |
\vskip-\smallskipamount |
| 98 |
\vskip-\parskip |
| 99 |
\fi |
| 100 |
\quad\penalty500\strut\nobreak\hfill |
| 101 |
\mbox{\small\slshape(\url{https://tex.stackexchange.com/#1})}\par} |
| 102 |
|
| 103 |
\providecommand\gnatsissue[2]{\ifhmode\unskip\fi |
| 104 |
\quad\penalty500\strut\nobreak\hfill |
| 105 |
\mbox{\small\slshape(% |
| 106 |
\href{https://www.latex-project.org/cgi-bin/ltxbugs2html?pr=#1\%2F\getfirstgithubissue#2 \relax}% |
| 107 |
{gnats issue #1/#2}% |
| 108 |
)}% |
| 109 |
\par} |
| 110 |
|
| 111 |
|
| 112 |
|
| 113 |
\let\cls\pkg |
| 114 |
\providecommand\env[1]{\texttt{#1}} |
| 115 |
\providecommand\acro[1]{\textsc{#1}} |
| 116 |
|
| 117 |
\vbadness=1400 % accept slightly empty columns |
| 118 |
|
| 119 |
|
| 120 |
\let\finalpagebreak\pagebreak % for TUB (if they use it) |
| 121 |
\let\finalvspace\vspace % for document layout fixes |
| 122 |
|
| 123 |
\makeatletter |
| 124 |
% maybe not the greatest design but normally we wouldn't have subsubsections |
| 125 |
\renewcommand{\subsubsection}{% |
| 126 |
\@startsection {subsubsection}{2}{0pt}{1.5ex \@plus 1ex \@minus .2ex}% |
| 127 |
{-1em}{\@subheadingfont\colonize}% |
| 128 |
} |
| 129 |
\providecommand\colonize[1]{#1:} |
| 130 |
\makeatother |
| 131 |
|
| 132 |
|
| 133 |
% Undo ltnews's \verbatim@font with active < and > |
| 134 |
\makeatletter |
| 135 |
\def\verbatim@font{\normalsize\ttfamily} |
| 136 |
\makeatother |
| 137 |
|
| 138 |
|
| 139 |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
| 140 |
\providecommand\tubcommand[1]{} |
| 141 |
\tubcommand{\input{tubltmac}} |
| 142 |
|
| 143 |
\publicationmonth{November} |
| 144 |
%\publicationyear{2024 --- DRAFT version for upcoming release} |
| 145 |
\publicationyear{2024} |
| 146 |
|
| 147 |
\publicationissue{40} |
| 148 |
|
| 149 |
\begin{document} |
| 150 |
|
| 151 |
\maketitle |
| 152 |
{\hyphenpenalty=10000 \exhyphenpenalty=10000 \spaceskip=3.33pt \hbadness=10000 |
| 153 |
\tableofcontents} |
| 154 |
|
| 155 |
\setlength\rightskip{0pt plus 3em} |
| 156 |
|
| 157 |
\medskip |
| 158 |
|
| 159 |
|
| 160 |
\section{Thirty years of \LaTeXe{}} |
| 161 |
|
| 162 |
In summer 1994, i.e., thirty years ago, \LaTeXe{} saw its first public |
| 163 |
release. Back then it was meant to be an intermediate version (hence |
| 164 |
the $\varepsilon$) on the way to a major new version (the mythical |
| 165 |
\LaTeX3) that we expected to take a couple of more years to reach |
| 166 |
maturity. It took much more than that in the end\Dash nominally, |
| 167 |
\LaTeXe{} is still with us today. |
| 168 |
|
| 169 |
However, under the hood, \LaTeXe{} changed a lot throughout these |
| 170 |
thirty years, as one can see, for example, when looking through the |
| 171 |
forty newsletters~\cite{40:ltnews} that accompanied the \LaTeX{} |
| 172 |
releases that happened in the meantime. |
| 173 |
|
| 174 |
During the first two decades, the \LaTeX{} kernel was kept largely |
| 175 |
stable with only minimal bug fix activities. During that period |
| 176 |
additional functionality was mostly provided through new or |
| 177 |
extended packages that could be loaded in the document preamble. This |
| 178 |
included many of the ideas targeted for \LaTeX3{}, e.g., \pkg{expl3} |
| 179 |
(\LaTeX3 programming language), \pkg{xparse} (new document command |
| 180 |
interface), \pkg{xtemplate} (a configuration mechanism), and many |
| 181 |
others. |
| 182 |
|
| 183 |
Initially, this approach worked well and provided good backward |
| 184 |
compatibility; however, over time it became apparent that keeping all |
| 185 |
developments confined to packages was more and more problematical. |
| 186 |
Features or bug fixes that should have been generally available, i.e., |
| 187 |
part of the kernel, were only available in packages, so a lot of |
| 188 |
dependencies between packages were introduced and resulted in |
| 189 |
convoluted code that was difficult to manage. For example, |
| 190 |
\pkg{hyperref} had to rewrite a lot of kernel (and package) macros, so |
| 191 |
the code and behavior of other packages had to change depending on |
| 192 |
whether or not \pkg{hyperref} was loaded or not. |
| 193 |
|
| 194 |
Thus, in 2015 the \LaTeX{} team decided to change the policy and |
| 195 |
(re)start active kernel development, see~\cite{40:ltnews22}. To ensure |
| 196 |
continuous backward compatibility we introduced at the same time the |
| 197 |
\pkg{latexrelease} package that enables users to roll back changes to |
| 198 |
the \LaTeX{} kernel to an earlier release, in case this is necessary |
| 199 |
to successfully rerun a document produced at that time. |
| 200 |
|
| 201 |
As a consequence of this policy change the last decade saw a larger |
| 202 |
number of enhancements and corrections that were made part of the |
| 203 |
\LaTeX{} kernel. Overall, we can confidently say that the new |
| 204 |
approach has worked well and enabled us to modernize \LaTeX{} and ensure |
| 205 |
that it remains relevant without compromising one of the cornerstones |
| 206 |
of \LaTeX{}: its outstanding ability to reprocess old documents |
| 207 |
written many years ago. |
| 208 |
|
| 209 |
\tubcommand\newpage |
| 210 |
Being able to update and modernize the kernel sources allowed us to |
| 211 |
embark in 2019 on the multi-year \enquote{\LaTeX{} Tagged PDF} project |
| 212 |
with the goal of automatically providing accessible PDF documents with |
| 213 |
\LaTeX{}. While there are several more project phases to complete, the |
| 214 |
milestones already reached allow users to generate PDF/UA compliant |
| 215 |
documents if the input is restricted to a (growing) subset of packages |
| 216 |
and document classes; see next section and previous newsletters. |
| 217 |
|
| 218 |
A big change happened with the 2020-02-02 release as part of the project activity, |
| 219 |
albeit somewhat obfuscated by us as \enquote{Improved load-times for |
| 220 |
\pkg{expl3}}. While technically correct, what it really meant is |
| 221 |
that we had finally integrated the programming layer of \LaTeX3, |
| 222 |
i.e., the ideas originally sketched out around 1992. Or saying it |
| 223 |
differently: with that date the original ideas for \LaTeX3 became a |
| 224 |
reality as part of the standard \LaTeX{} kernel. |
| 225 |
|
| 226 |
With the programming layer available under the hood we were then able to |
| 227 |
provide new concepts and extensions as part of \LaTeX{}, |
| 228 |
e.g., the hook management system, a new mark mechanism, core |
| 229 |
functionality for tagging and PDF resource management, a consistent |
| 230 |
key/value interface, and more recently the socket and plug mechanism. |
| 231 |
|
| 232 |
More will follow while we continue to work on modernizing \LaTeX{} and |
| 233 |
bringing the Tagged PDF project to a truly successful completion\Dash so |
| 234 |
stay tuned and watch this space for future announcements in the next |
| 235 |
newsletters. |
| 236 |
|
| 237 |
|
| 238 |
|
| 239 |
\section{News from the \enquote{\LaTeX{} Tagged PDF} project} |
| 240 |
|
| 241 |
\subsection{Engine support:\ An important update} |
| 242 |
|
| 243 |
As detailed below, work is progressing on the Tagged PDF |
| 244 |
project. There are many drivers for this work, including legal changes |
| 245 |
in many places which will increasingly require well-tagged PDFs |
| 246 |
including full support for mathematics. As part of the work on this, |
| 247 |
we are looking at the technical abilities of the \TeX{} engines. |
| 248 |
|
| 249 |
With \XeTeX{}, it is impossible to reliably produce tagged PDFs due to |
| 250 |
engine limitations. The increasing importance of tagged PDFs means |
| 251 |
that this requires a move away from \XeTeX{}. We will continue to |
| 252 |
address issues with \XeTeX{} support in team-maintained \LaTeX{} code |
| 253 |
on a best-effort basis. No \emph{new} functionality will be added for |
| 254 |
\XeTeX{} by the \LaTeX{} team. It is likely that over time |
| 255 |
functionality may become more restricted, and users are urged to |
| 256 |
migrate \XeTeX{} documents to \LuaTeX{}. |
| 257 |
|
| 258 |
For \pdfTeX{}, tagging is available and we are able to support |
| 259 |
mathematics by including relevant \TeX{} source or by using |
| 260 |
externally-generated MathML. Only \LuaTeX{} is capable of |
| 261 |
\emph{automatic} generation of MathML as part of a \LaTeX{} run. Thus |
| 262 |
\pdfTeX{} continues to be supported for existing material, but for new |
| 263 |
documents, moving to \LuaTeX{} is recommended. |
| 264 |
|
| 265 |
We cannot make statements about the support for other engines such as |
| 266 |
(u)p\TeX{}, as we don't use these programs nor have in depth knowledge |
| 267 |
of their functionalities. To the best of our knowledge, core \LaTeX{} |
| 268 |
works well with these engines, but if and to what extent tagging can |
| 269 |
be supported will remain to be seen. If relevant information becomes |
| 270 |
available to us we will provide an update in future editions of the |
| 271 |
\LaTeX{} newsletter. |
| 272 |
|
| 273 |
|
| 274 |
\subsection{Tagging support for external packages} |
| 275 |
|
| 276 |
At \url{https://latex3.github.io/tagging-project/tagging-status/} we |
| 277 |
show the status of many \LaTeX{} packages and classes with respect to |
| 278 |
PDF tagging. We also started to improve tagging support in external |
| 279 |
packages. If the \texttt{firstaid} key is used in addition to the |
| 280 |
\texttt{phase-III} key, basic commands of several packages, including |
| 281 |
\pkg{amsthm} and \pkg{fancyvrb}, can now be used. |
| 282 |
|
| 283 |
|
| 284 |
\subsection{Improved table tagging} |
| 285 |
|
| 286 |
The tagging of tabulars has been extended: it is now possible to tag |
| 287 |
row headers and to create cells that span more than one row. |
| 288 |
|
| 289 |
The interface to this functionality is not finalized but can be |
| 290 |
accessed in the current release by specifying the row and columns to |
| 291 |
be treated as headers. For example |
| 292 |
% |
| 293 |
\begin{verbatim} |
| 294 |
\tagpdfsetup{ |
| 295 |
table/header-rows={1,2}, |
| 296 |
table/header-columns={1} } |
| 297 |
\end{verbatim} |
| 298 |
would specify that in the following tables the first two rows and |
| 299 |
first column of each row should be tagged as heading entries. |
| 300 |
|
| 301 |
Similarly you may add a RowSpan attribute to tag a cell that spans |
| 302 |
two rows using: |
| 303 |
\begin{verbatim} |
| 304 |
\tagpdfsetup{table/multirow={2}} |
| 305 |
\end{verbatim} |
| 306 |
|
| 307 |
|
| 308 |
\subsection{Automatic MathML tagging} |
| 309 |
|
| 310 |
When Lua\LaTeX{} is being used, and the \pkg{luamml} package is |
| 311 |
available, and if the document uses the \pkg{unicode-math} package, |
| 312 |
then the math module will automatically convert each math formula to |
| 313 |
MathML and use it to attach MathML associated files (or MathML |
| 314 |
Structure elements) to the tagged PDF. This new feature can be |
| 315 |
disabled with \verb+\tagpdfsetup{math/mathml/luamml/load=false}+. More |
| 316 |
options to configure MathML tagging can be found in the documentation |
| 317 |
of \pkg{latex-lab-math}. |
| 318 |
|
| 319 |
|
| 320 |
\subsection{Change behavior of tagging sockets with two arguments} |
| 321 |
|
| 322 |
When calling tagging sockets with two arguments using |
| 323 |
\cs{UseTaggingSocket} when tagging is suspended, previous versions of |
| 324 |
\LaTeXe{} dropped both arguments. This behavior has been changed to |
| 325 |
drop the first argument and preserve the second one instead, thereby |
| 326 |
allowing tagging sockets to be used to wrap existing content which |
| 327 |
should still appear in a non-tagging context. |
| 328 |
|
| 329 |
Since no tagging sockets currently provided by \LaTeX{} use two |
| 330 |
arguments we do not expect this change to affect any existing |
| 331 |
documents, but if a custom tagging socket has been defined outside of |
| 332 |
the kernel it might need to be adapted to be compatible with the new |
| 333 |
behavior. |
| 334 |
% |
| 335 |
\githubissue{1500} |
| 336 |
|
| 337 |
|
| 338 |
|
| 339 |
|
| 340 |
\section{Changes to the \LaTeX{} kernel} |
| 341 |
|
| 342 |
\subsection{Handling paragraph continuation} |
| 343 |
|
| 344 |
Already \LaTeX~2.09 offered some automation to detect whether or not |
| 345 |
text after a list or some other display environment is meant to be a |
| 346 |
continuation of the current paragraph or should start a new one. The |
| 347 |
document-level syntax for this is that a blank line after such an |
| 348 |
environment signals to \LaTeX{} that it should start a new paragraph; |
| 349 |
whilst no blank line signals that there should be no new paragraph and |
| 350 |
the text should be considered a continuation. |
| 351 |
|
| 352 |
Unfortunately, there were a number of cases where the original 2.09 |
| 353 |
approach failed, e.g., with |
| 354 |
\begin{flushleft} |
| 355 |
\ttfamily |
| 356 |
\ \ \{\meta{local customizations}\\ |
| 357 |
\ \ \cs{begin}\{equation\} a<b \cs{end}\{equation\}\} \\ |
| 358 |
\ \ \meta{some text} |
| 359 |
\end{flushleft} |
| 360 |
the \meta{some text} incorrectly started a new paragraph. Bug reports |
| 361 |
about this behavior can be traced back to the time \LaTeXe{} was |
| 362 |
developed, e.g., one test file from 1992 has a note that the above |
| 363 |
case was unfortunately not resolvable despite some improvements made |
| 364 |
back then. The main cause of the issue (as you probably guessed) is |
| 365 |
that the mechanism failed whenever the environment was executed within |
| 366 |
a group (\texttt{\{...\}}, \cs{begingroup}/\cs{endgroup}, or |
| 367 |
\cs{bgroup}/\cs{egroup} pair) that was closed before the next blank |
| 368 |
line was reached. |
| 369 |
|
| 370 |
While most of the time this could be visually corrected by adding some |
| 371 |
explicit \cs{noindent}, the situation got worse when we tried to |
| 372 |
implement tagged PDFs resulting in incorrect structures or worse. |
| 373 |
|
| 374 |
We therefore made a new attempt to resolve this problem in every |
| 375 |
situation and this new solution is rolled out in the current release. |
| 376 |
|
| 377 |
|
| 378 |
\subsection{Avoid bogus \enquote{no item} error} |
| 379 |
|
| 380 |
The commands \cs{addvspace} and \cs{addpenalty} generated the famous |
| 381 |
error message \enquote{Something's wrong---perhaps a missing \cs{item}} |
| 382 |
when they were encountered outside vertical mode. Most of the time |
| 383 |
this error was bogus and if not, then it was generated several times |
| 384 |
rather than once. |
| 385 |
|
| 386 |
Once upon a time (in \LaTeX{}~2.09) it was necessary that these |
| 387 |
commands were used only in vertical mode, but with \LaTeXe{} in 1994, |
| 388 |
we changed the internals but simply overlooked that this error message |
| 389 |
then had become useless. In this release, i.e.,~30 years too late, we |
| 390 |
have finally lifted the ban and from now on this error should only |
| 391 |
show up if there is indeed a missing \cs{item}. |
| 392 |
% |
| 393 |
\githubissue{1460} |
| 394 |
|
| 395 |
|
| 396 |
\subsection[Switch to T1 as default encoding in documents |
| 397 |
using \cs{DocumentMetadata}] |
| 398 |
{Switch to T1 as default encoding in documents\\\mbox\qquad |
| 399 |
using \cs{DocumentMetadata}} |
| 400 |
|
| 401 |
As it is well known, the font encoding \texttt{OT1} supports only 128 |
| 402 |
characters and has various problems and quirks notably for languages |
| 403 |
different to English. Nevertheless \texttt{OT1} is the default |
| 404 |
encoding in \LaTeX{} and this cannot be easily changed without |
| 405 |
affecting many documents as the \texttt{T1} version of the fonts have |
| 406 |
slightly different metrics. |
| 407 |
|
| 408 |
The introduction of the \cs{DocumentMetadata} command, which announces |
| 409 |
\emph{new} code and changes that can also affect the layout gives us |
| 410 |
now the opportunity to make this step. So with this version a use of |
| 411 |
\cs{DocumentMetadata} with (pdf)\LaTeX{} will setup \texttt{T1} as |
| 412 |
default font encoding.\footnote{The Unicode engines will continue to |
| 413 |
use \texttt{TU} as the encoding.} To ensure that scalable fonts are used, |
| 414 |
the package \pkg{cm-super} has to be installed. Users who want to |
| 415 |
revert to the \texttt{OT1} encoding in their document can do so with |
| 416 |
\verb+\usepackage[OT1]{fontenc}+. |
| 417 |
|
| 418 |
|
| 419 |
|
| 420 |
|
| 421 |
\section{Code improvements} |
| 422 |
|
| 423 |
\subsection[Avoiding key--value option clashes between classes and packages] |
| 424 |
{Avoiding key--value option clashes between classes\\\mbox\qquad and packages} |
| 425 |
|
| 426 |
In \LaTeX{} News~35~\cite{40:ltnews35} we introduced key--value option |
| 427 |
processing to the kernel. Following the standard for \LaTeXe{} |
| 428 |
options, keyval options given to the \cs{documentclass} line were |
| 429 |
treated as global and so parsed by every package. However, with |
| 430 |
keyvals, the likelihood of a name clash between a class-specific |
| 431 |
option and one used by a package is much higher than it is with simple |
| 432 |
strings. We have therefore refined the mechanism in the current |
| 433 |
release. |
| 434 |
|
| 435 |
When a class uses the kernel keyval processor, any options it |
| 436 |
recognizes are recorded and any packages using the keyval processor |
| 437 |
will then \emph{skip} these \enquote{global} options. To allow for the |
| 438 |
case where a class directly uses an option which should be global (for |
| 439 |
example \texttt{draft}), a new key property \texttt{.pass-to-packages} |
| 440 |
has been added. This can then be set to indicate that this key is not |
| 441 |
to be skipped. For example |
| 442 |
\begin{verbatim} |
| 443 |
\DeclareKeys{ |
| 444 |
draft .if = {ifl@cls@draft}, |
| 445 |
draft .pass-to-packages = true, |
| 446 |
mode .store = \cls@mode |
| 447 |
} |
| 448 |
\end{verbatim} |
| 449 |
in a class would create two options, \texttt{draft} and |
| 450 |
\texttt{mode}. The \texttt{draft} option will be treated in the normal |
| 451 |
way by packages using keyvals, but they will ignore the \texttt{mode} |
| 452 |
option: it is effectively marked as \enquote{private} to the class. |
| 453 |
% |
| 454 |
\githubissue{1279} |
| 455 |
|
| 456 |
\subsection{Improvement to \textup{\XeTeX}\ \cs{showhyphens}} |
| 457 |
|
| 458 |
When using \cs{showhyphens} with \XeTeX, missing character warnings |
| 459 |
would be generated for any character not in Latin Modern. This has |
| 460 |
been corrected and the warnings are suppressed. |
| 461 |
% |
| 462 |
\githubissue{1380} |
| 463 |
|
| 464 |
\subsection{Improved error raised for empty hook name} |
| 465 |
|
| 466 |
When using the hook management, both hook and label names (if |
| 467 |
specified) should be non-empty. Before, empty hook and empty label names both |
| 468 |
raised the same label-specific error: |
| 469 |
\begin{verbatim} |
| 470 |
! LaTeX hooks Error: Empty code label on line .. |
| 471 |
Using 'top-level' instead. |
| 472 |
\end{verbatim} |
| 473 |
This has now been improved. Now an empty hook name generates |
| 474 |
\begin{verbatim} |
| 475 |
! LaTeX hooks Error: Empty hook name on line .. |
| 476 |
\end{verbatim} |
| 477 |
% |
| 478 |
\githubissue{1423} |
| 479 |
|
| 480 |
\subsection{Provide counter representations for link targets} |
| 481 |
|
| 482 |
To create unique target names for links the package \pkg{hyperref} |
| 483 |
uses a special counter representation \verb+\theH+\meta{counter}. To |
| 484 |
ensure that this counter representation exists, \pkg{hyperref} |
| 485 |
redefined the commands \verb+\@definecounter+, \verb+\@addtoreset+ and |
| 486 |
\verb+\refstepcounter+. This counter representation is also needed for |
| 487 |
the Tagged PDF project and so these augmented command definitions |
| 488 |
have now been incorporated into the kernel. Thus from now on every |
| 489 |
\verb+\newcounter{+\meta{counter}\verb+}+ will define not only |
| 490 |
\verb+\the+\meta{counter} but also \verb+\theH+\meta{counter}. |
| 491 |
|
| 492 |
\subsection{Extending \cs{refstepcounter}} |
| 493 |
|
| 494 |
For many years, the package \pkg{hyperref} had been redefining |
| 495 |
\verb+\refstepcounter+ and adding code that creates link targets. The |
| 496 |
kernel definition has now been extended with socket interfaces that |
| 497 |
will allow \pkg{hyperref} to avoid the redefinitions. The new |
| 498 |
interfaces are also used by the Tagged PDF code that needs target |
| 499 |
names to resolve references between structures. |
| 500 |
|
| 501 |
|
| 502 |
\section{Bug fixes} |
| 503 |
|
| 504 |
\subsection{Fix wrong file type in a rollback warning} |
| 505 |
|
| 506 |
When \LaTeX{} is rolled back to date \meta{date1} and a class or |
| 507 |
package with minimum date requirement \meta{date2} is to be loaded, a |
| 508 |
rollback warning is raised if \meta{date2} is later than \meta{date1}: |
| 509 |
\begin{verbatim} |
| 510 |
LaTeX Warning: Suspicious rollback/min-date |
| 511 |
date given. |
| 512 |
A minimal date of YYYY-MM-DD has been |
| 513 |
specified for package '<pkgname>'. |
| 514 |
But this is in conflict with a rollback |
| 515 |
request to YYYY-MM-DD. |
| 516 |
\end{verbatim} |
| 517 |
|
| 518 |
In some cases this message showed a wrong file type, i.e., |
| 519 |
\verb|document class '<pkgname>'| or \verb|package '<clsname>'|. This |
| 520 |
has now been corrected. |
| 521 |
% |
| 522 |
\githubissue{870} |
| 523 |
|
| 524 |
\subsection*{Fix existence check of document environments} |
| 525 |
|
| 526 |
\cs{NewDocumentEnvironment} and friends define (or redefine) a |
| 527 |
document environment using the space-trimmed \meta{envname}, but the |
| 528 |
existence check for \meta{envname} was done without space |
| 529 |
trimming. Thus when the user-specified \meta{envname} consists of |
| 530 |
leading and/or trailing space(s), it may lead to erroneously silent |
| 531 |
environment declaration. For example, in |
| 532 |
\begin{flushleft} |
| 533 |
\ttfamily |
| 534 |
\ \ \verb=\NewDocumentEnvironment{myenv}{}{begin}{end}=\\ |
| 535 |
\ \ \verb*=\NewDocumentEnvironment{ myenv }{}{begin}{end}=\kern-1cm |
| 536 |
\end{flushleft} |
| 537 |
the first line defines a new environment \env{myenv} but the second |
| 538 |
line would check existence for \verb*| myenv | (which is not yet |
| 539 |
defined), then redefine \env{myenv} environment without raising any |
| 540 |
errors. This has now been corrected. |
| 541 |
% |
| 542 |
\githubissue{1399} |
| 543 |
|
| 544 |
\subsection{Handling of global keys with spaces} |
| 545 |
|
| 546 |
If the global (class) options contained spaces around key names, |
| 547 |
\cs{ProcessKeyOptions} would fail to remove known keys from the list |
| 548 |
of unused global options and \cs{OptionNotUsed} would mistakenly add |
| 549 |
space-surrounded key names to that list. The first issue was corrected as |
| 550 |
a hotfix in patch level 1 of the November 2023 release (but |
| 551 |
unfortunately not mentioned in~\cite{40:ltnews38}) and the second in the current |
| 552 |
release. |
| 553 |
% |
| 554 |
\githubissue{1238} |
| 555 |
|
| 556 |
\subsection{File list entries for rolled back packages/classes} |
| 557 |
|
| 558 |
When the rollback mechanism for packages and classes was introduced in |
| 559 |
2018~\cite{40:ltnews28}, loading of the selected historic release was |
| 560 |
not recorded in the file list used by \cs{listfiles}. This has now |
| 561 |
been corrected so that the extended usage~\cite{40:ltnews39} |
| 562 |
\begin{verbatim} |
| 563 |
\listfiles[hashes,sizes] |
| 564 |
\end{verbatim} |
| 565 |
now gives more complete and less confusing info. |
| 566 |
% |
| 567 |
\githubissue{1413} |
| 568 |
|
| 569 |
\subsection{\pkg{doc}:\ \cs{PrintDescribeMacro} in preamble} |
| 570 |
|
| 571 |
In \pkg{doc} version 2 it was possible to alter the definition of |
| 572 |
\cs{PrintDescribeMacro} and similar commands in preamble. In version 3 |
| 573 |
this stopped working because they were reset at the end of the |
| 574 |
preamble. This has now been implemented differently and changes in the |
| 575 |
preamble are possible again. |
| 576 |
% |
| 577 |
\githubissue{1000} |
| 578 |
|
| 579 |
|
| 580 |
\subsection{Avoid low-level error if \cs{ShowHooks} is used late} |
| 581 |
|
| 582 |
If \cs{ShowHooks} was used to examine a package hook after the |
| 583 |
package was loaded, a low level error resulted. This has now been |
| 584 |
corrected. |
| 585 |
% |
| 586 |
\githubissue{1513} |
| 587 |
|
| 588 |
\subsection{Avoid code duplication in rollback} |
| 589 |
|
| 590 |
When the kernel uses \cs{AddToHook} in a region that might be rolled |
| 591 |
back (which happens in a few places) and a document requests a |
| 592 |
rollback, then we have the situation that the hook already contains |
| 593 |
code to which we added the same (or slightly different) code during |
| 594 |
the rollback; this results in code duplication or, worse, in |
| 595 |
errors. This has now been corrected by dropping any such code chunk |
| 596 |
(if there is one) prior to adding the rollback code. |
| 597 |
% |
| 598 |
\githubissue{1407} |
| 599 |
|
| 600 |
|
| 601 |
\subsection{Passing template keys using \cs{KeyValue}} |
| 602 |
|
| 603 |
With the move of the template code to the kernel, internal |
| 604 |
functions were reviewed to improve efficiency. However, there |
| 605 |
was an oversight in how |
| 606 |
passing key values from one setting to another was implemented, |
| 607 |
such that using \cs{KeyValue} could result in an infinite |
| 608 |
loop. This has now been fixed. |
| 609 |
% |
| 610 |
\githubissue{1486} |
| 611 |
|
| 612 |
|
| 613 |
|
| 614 |
\section{Changes to packages in the \pkg{amsmath} category} |
| 615 |
|
| 616 |
\subsection{Extend support for \cs{dots}} |
| 617 |
|
| 618 |
The implementation of \cs{dots} in \pkg{amsmath} has the feature that |
| 619 |
it selects different dots depending on the symbol that follows: e.g., |
| 620 |
dots between commas would normally be on the baseline, while dots |
| 621 |
between binary or relational symbols would be raised. However, when |
| 622 |
symbols such as \cs{cong} were protected from expansion in moving |
| 623 |
arguments (so that they worked in places such as headings) it had the |
| 624 |
unfortunate side-effect that the \cs{dots} magic stopped working for |
| 625 |
them. This has now been corrected. |
| 626 |
% |
| 627 |
\githubissue{1265} |
| 628 |
|
| 629 |
|
| 630 |
|
| 631 |
%\section{Changes to packages in the \pkg{graphics} category} |
| 632 |
|
| 633 |
\section{Changes to packages in the \pkg{tools} category} |
| 634 |
|
| 635 |
\subsection{Modification to generation of the \file{.tex} from \pkg{fileerr}} |
| 636 |
|
| 637 |
The \pkg{fileerr} extraction has been modified to write |
| 638 |
\texttt{rename-to-empty-base.tex} rather than \texttt{.tex} to comply |
| 639 |
with an expected security change in \TeX{}~Live 2025. The |
| 640 |
\texttt{build.lua} file for the \pkg{tools} has been modified to |
| 641 |
rename \texttt{rename-to-empty-base.tex} to \texttt{.tex} after |
| 642 |
unpacking. However if using \textsf{docstrip} directly rather than |
| 643 |
using \textsf{l3build} or the unpacked zip file from \CTAN{}, the user |
| 644 |
must now rename the file and install as \texttt{.tex}. |
| 645 |
% |
| 646 |
\githubissue{1412} |
| 647 |
|
| 648 |
|
| 649 |
\subsection{\pkg{array}:\ Improve \texttt{>\{...\}} specifier} |
| 650 |
|
| 651 |
If the argument of \texttt{>\{...\}} ended with a command accepting a |
| 652 |
trailing optional argument, e.g., defined for example with |
| 653 |
\verb=\NewDocumentCommand\foo{o}{...}=, one could get low-level |
| 654 |
parsing errors. This has now been corrected. |
| 655 |
% |
| 656 |
\githubissue{1468} |
| 657 |
|
| 658 |
|
| 659 |
\subsection{\pkg{array}:\ Tagging support for \cs{cline}} |
| 660 |
|
| 661 |
In the last release we added tagging support for \pkg{array}, |
| 662 |
\pkg{longtable} and other tabular packages, but we overlooked that the |
| 663 |
kernel definition for \cs{cline} also needs modification because the |
| 664 |
rule generated by the command needs to be tagged as an |
| 665 |
artifact. Furthermore, the processing of a \cs{cline} looks to the |
| 666 |
algorithm as if another row is added (which is technically what |
| 667 |
happens), thus it was also necessary to decrement the internal row |
| 668 |
counter to get a correct row count. This has now been corrected in |
| 669 |
\pkg{array}, which is automatically loaded for tagging, so that all |
| 670 |
these packages are now fully compatible with the tagging code if it is |
| 671 |
turned on. |
| 672 |
% |
| 673 |
\taggingissue{134} |
| 674 |
|
| 675 |
|
| 676 |
|
| 677 |
\subsection{\pkg{longtable}:\ Extend caption type} |
| 678 |
|
| 679 |
The \pkg{longtable} package has been extended and now provides the command |
| 680 |
\cs{LTcaptype} (stemming from the \pkg{ltcaption} package) to change |
| 681 |
the counter and caption type used by the \cs{caption} command from |
| 682 |
longtable. So with \verb+\renewcommand\LTcaptype{figure}+, a |
| 683 |
longtable will step the figure counter instead of the table counter |
| 684 |
and produce an entry in the list of figures. An empty definition, |
| 685 |
\verb+\renewcommand\LTcaptype{}+, will suppress increasing of the |
| 686 |
counter. This makes it easy to define an unnumbered variant of |
| 687 |
longtable: |
| 688 |
\begin{verbatim} |
| 689 |
\newenvironment{longtable*} |
| 690 |
{\renewcommand\LTcaptype{}\longtable} |
| 691 |
{\endlongtable} |
| 692 |
\end{verbatim} |
| 693 |
|
| 694 |
\subsection{\pkg{longtable}:\ Prevent \cs{pagegoal} exceeding maximum value} |
| 695 |
|
| 696 |
An internal guard has been added to avoid \TeX\ errors if |
| 697 |
\verb=\pagegoal= is increased beyond the maximum value for a |
| 698 |
\TeX\ dimension. |
| 699 |
% |
| 700 |
\githubissue{1495} |
| 701 |
|
| 702 |
|
| 703 |
|
| 704 |
\section{Changes to \pkg{l3build}} |
| 705 |
|
| 706 |
To support third-party developers testing their code against pre-release |
| 707 |
\LaTeX{}, a new switch \verb|--dev| has been added to \pkg{l3build}. |
| 708 |
This allows the developer to run |
| 709 |
\begin{verbatim} |
| 710 |
l3build check |
| 711 |
\end{verbatim} |
| 712 |
to run their test suite against the current release of \LaTeX{} and |
| 713 |
\begin{verbatim} |
| 714 |
l3build check --dev |
| 715 |
\end{verbatim} |
| 716 |
to run exactly the same tests using the development release of |
| 717 |
\LaTeX{}. |
| 718 |
|
| 719 |
%\section{Changes to files in the \pkg{cyrillic} category} |
| 720 |
|
| 721 |
\begin{thebibliography}{9}\frenchspacing |
| 722 |
|
| 723 |
%\fontsize{9.3}{11.3}\selectfont |
| 724 |
|
| 725 |
\bibitem{40:Lamport} |
| 726 |
Leslie Lamport. |
| 727 |
\newblock \emph{{\LaTeX}: {A} Document Preparation System: User's Guide and Reference |
| 728 |
Manual}. |
| 729 |
\newblock \mbox{Addison}-Wesley, Reading, MA, USA, 2nd edition, 1994. |
| 730 |
\newblock ISBN 0-201-52983-1. |
| 731 |
\newblock Reprinted with corrections in 1996. |
| 732 |
|
| 733 |
\bibitem{40:ltnews} \LaTeX{} Project Team. |
| 734 |
\emph{\LaTeXe{} news 1--39}. June 2024. |
| 735 |
\url{https://latex-project.org/news/latex2e-news/ltnews.pdf} |
| 736 |
|
| 737 |
\bibitem{40:ltnews22} \LaTeX{} Project Team. |
| 738 |
\emph{\LaTeXe{} news 22}. January 2015. |
| 739 |
\url{https://latex-project.org/news/latex2e-news/ltnews22.pdf} |
| 740 |
|
| 741 |
\bibitem{40:ltnews28} \LaTeX{} Project Team. |
| 742 |
\emph{\LaTeXe{} news 28}. April 2018. |
| 743 |
\url{https://latex-project.org/news/latex2e-news/ltnews28.pdf} |
| 744 |
|
| 745 |
\bibitem{40:ltnews35} \LaTeX{} Project Team. |
| 746 |
\emph{\LaTeXe{} news 35}. June 2022. |
| 747 |
\url{https://latex-project.org/news/latex2e-news/ltnews35.pdf} |
| 748 |
|
| 749 |
\bibitem{40:ltnews38} \LaTeX{} Project Team. |
| 750 |
\emph{\LaTeXe{} news 38}. November 2023. |
| 751 |
\url{https://latex-project.org/news/latex2e-news/ltnews38.pdf} |
| 752 |
|
| 753 |
\bibitem{40:ltnews39} \LaTeX{} Project Team. |
| 754 |
\emph{\LaTeXe{} news 39}. June 2024. |
| 755 |
\url{https://latex-project.org/news/latex2e-news/ltnews39.pdf} |
| 756 |
|
| 757 |
\end{thebibliography} |
| 758 |
|
| 759 |
\end{document} |