% \iffalse meta-comment
%
% Copyright 2019-2020
% The LaTeX Project and any individual authors listed elsewhere
% in this file.
%
% This file is part of the LaTeX base system.
% -------------------------------------------
%
% It may be distributed and/or modified under the
% conditions of the LaTeX Project Public License, either version 1.3c
% of this license or (at your option) 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 file has the LPPL maintenance status "maintained".
%
% The list of all files belonging to the LaTeX base distribution is
% given in the file `manifest.txt'. See also `legal.txt' for additional
% information.
%
% The list of derived (unpacked) files belonging to the distribution
% and covered by LPPL is defined by the unpacking scripts (with
% extension .ins) which are part of the distribution.
%
% \fi
% Filename: ltnews33.tex
%
% This is issue 33 of LaTeX News.

\NeedsTeXFormat{LaTeX2e}[2020-02-02]

\documentclass{ltnews}
\usepackage[T1]{fontenc}

\usepackage{lmodern,url,hologo}

\usepackage{csquotes}
\usepackage{multicol}

\providecommand\hook[1]{\texttt{#1}}

\providecommand\meta[1]{$\langle$\textrm{\itshape#1}$\rangle$}
\providecommand\option[1]{\texttt{#1}}
\providecommand\env[1]{\texttt{#1}}
\providecommand\Arg[1]{\texttt\{\meta{#1}\texttt\}}


\providecommand\eTeX{\hologo{eTeX}}
\providecommand\XeTeX{\hologo{XeTeX}}
\providecommand\LuaTeX{\hologo{LuaTeX}}
\providecommand\pdfTeX{\hologo{pdfTeX}}
\providecommand\MiKTeX{\hologo{MiKTeX}}
\providecommand\CTAN{\textsc{ctan}}
\providecommand\TL{\TeX\,Live}
\providecommand\githubissue[2][]{\ifhmode\unskip\fi
     \quad\penalty500\strut\nobreak\hfill
     \mbox{\small\slshape(%
       \href{https://github.com/latex3/latex2e/issues/\getfirstgithubissue#2 \relax}%
          	    {github issue#1 #2}%
           )}%
     \par\smallskip}

% simple solution right now (just link to the first issue if there are more)
\def\getfirstgithubissue#1 #2\relax{#1}

\providecommand\sxissue[1]{\ifhmode\unskip\fi
     \quad\penalty500\strut\nobreak\hfill
     \mbox{\small\slshape(\url{https://tex.stackexchange.com/#1})}\par}

\providecommand\gnatsissue[2]{\ifhmode\unskip\fi
     \quad\penalty500\strut\nobreak\hfill
     \mbox{\small\slshape(%
       \href{https://www.latex-project.org/cgi-bin/ltxbugs2html?pr=#1\%2F\getfirstgithubissue#2 \relax}%
          	    {gnats issue #1/#2}%
           )}%
     \par}

\let\cls\pkg
\providecommand\env[1]{\texttt{#1}}
\providecommand\acro[1]{\textsc{#1}}

\vbadness=1400  % accept slightly empty columns


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\providecommand\tubcommand[1]{}
\tubcommand{\input{tubltmac}}

\publicationmonth{June}
\publicationyear{2021 --- Draft Version}

\publicationissue{33}

\begin{document}

\tubcommand{\addtolength\textheight{4.2pc}}   % only for TUB

\maketitle
{\hyphenpenalty=10000 \spaceskip=3.33pt \hbadness=10000 \tableofcontents}

\setlength\rightskip{0pt plus 3em}


\medskip


\section{Introduction}

The focus of the June 2020 release is to provide further important
building blocks for producing reliable tagged PDF output in the future
(see \cite{33:blueprint}), they are discussed in the next two
sections. In addition we included a number of smaller enhancement and
fixes that are outlined on the next pages. As usual, more detail can
on individual changes can be found in the \texttt{changes.txt} files
in the distribution and, of course, in the documented
sources~\cite{33:source2e}.




\section{Extending the hook concept to paragraphs}

Largely triggered by the need for better control of paragraph text
processing, in particular when producing tagged PDF output, we have
extended the paragraph processing of \LaTeX{} so that the kernel gains
control both at the start and the end of each paragraph. This is done
in a manner that is (or should be) transparent to packages and user
documents.

Beside the internal control points for exclusive use of the \LaTeX{}
kernel we also implemented four public hooks that can be used by
packages or user via the hook management declarations to achieve
special effects or implement manipulations that in the past were only
possible through redefinitions of \cs{everypar} or \cs{par} with the
usual issue that such changes would conflict with changes in other
packages.

The documentation of the hooks together with a few examples is
provided in \file{ltpara-doc.pdf} and for those who want to study the
(quite interesting) code is found in
\file{ltpara-code.pdf}. Additionally it is included as part of the
full kernel documentation in \file{source2e.pdf}.



\section{Extending the hook concept to commands}

Up to now the hook management covered hooks for a few core areas, such
as hooks for the \cs{shipout} process or those in the \env{document}
environment, as well as generic hooks for file loading (helpful for
patching) and for arbitrary environments (executed by \cs{begin} and
\cs{end}).

This has now been extended to add \hook{/before} and \hook{/after}
hooks to any (document-level) command---in theory at that is.  In
practice the new generic \hook{cmd} hooks, especially the
\hook{cmd/.../after} hooks may fail with commands that are too complex
to be automatically patched and break them if the hook is filled with
code.  The restrictions are documented in \texttt{ltcmdhooks-doc.pdf}.

However, given that these hooks are mainly meant for package
developers to provide a better interoperability between different
packages and between packages and the \LaTeX{} kernel, these
restrictions are of minor importance: for commands where the mechanism
can't be applied, one is in the same situation as before and for all
others there will be a noticeable improvement.  This is especially
important for our big project providing accessible and tagged PDF
output~\cite{33:blueprint}, because for this we will eventually have
to patch many third-party packages and this is only feasible, if it can
be done in controlled and standardized ways.




\section{Other changes to the \LaTeX{} kernel}

\subsection{Adjusting \env{itemize} labels with \cs{labelitemfont}}

The command \cs{labelitemfont} was in fact already introduced with the
\LaTeX\ release 2020-02-02, but back then we forgot to describe it, so
we do this now. Its purpose is to resolve some bad formatting issues
with the \env{itemize} environment and at the same time make it easier
to adjust its layout if necessary. What could happen in the past was the
\env{itemize} labels, e.g., the \textbullet{}, would sometimes react to
surrounding font changes and could suddenly change shape, for example
to \textit{\textbullet}.

Now \cs{labelitemfont} is applied to each
label defaulting to \cs{normalfont} which will prevent this behavior.
By choosing a different settings other effects can be achieved, for example
\begin{verbatim}
  \renewcommand\labelitemfont
     {\normalfont\fontfamily{lmss}\selectfont}
  \renewcommand\labelitemfont
     {\rmfamily\normalshape}
\end{verbatim}
The first will take the symbols from Latin Modern Sans so that you get
%
\def\myfont#1{{\let\labelitemfont\empty\fontfamily{lmss}\selectfont#1}}
%
\myfont\labelitemi, \myfont\labelitemii, \myfont\labelitemiii\ and
\myfont\labelitemiv, while the second variant freezes the font family
and shape, but leave the series variable, so that an \env{itemize} in
a bold context would show bolder symbols. Making it empty would give
you the buggy old behavior back.
%
\githubissue{497}


\subsection{A note on file names with spaces, dots or UTF-8 characters}

In one of the recent \LaTeX{} releases we improved the interface
for specifying file names so that they can now safely contain spaces
(as is common on Windows but also elsewhere), UTF-8 characters
outside the \acro{ascii} range as well as names with several dots in
it. In the past this was only possible by applying a special syntax
(in cases of spaces), not at all for most UTF-8 characters and
not in all circumstances for files with several dots.

However, \TeX{} has a built-in rule saying that you can leave out the
extension if it is \texttt{.tex}. Because of that \verb=\input{file}=
or \verb=\input{file.tex}= both load \file{file.tex} if it
exists. While this is convenient most of the time it is a little
awkward in some scenarios (for example, when both \file{file} and
\file{file.tex} exist) and also when you manually try to implement
that rule.

\LaTeX{} therefore had one special syntax for \cs{include} and
\cs{includeonly}: they always expected that their arguments contains a
file name\footnote{In case of \cs{includeonly} a comma separated list
  of such names.} without its extension, which had to be
\texttt{.tex}.  Thus when you mistakenly wrote
\verb=\include{mychap.tex}= (for example, when you changed from \cs{input}
to \cs{include} somewhere), \LaTeX{} went ahead and looked for the
file \file{mychap.tex.tex} for inclusion and tried to write support
information to the file \file{mychap.tex.aux}.  The reason was that
\cs{include} had to construct both physical file names from the
argument and it didn't bother to do something special about the
extension \texttt{.tex}.

As a side effect of the new implementation this has now changed and
the argument of \cs{include} now gets the extension \texttt{.tex}
removed if it was used. Thus \verb=\include{mychap.tex}= now loads
\file{mychap.tex} and no longer looks for \file{mychap.tex.tex}.
%
\githubissue{486}


\subsection{\cs{end}\texttt{\textbraceleft document\textbraceright}
  should always start in v-mode}

Until now \verb=\end{document}= executed the code from the
\cs{AtEndDocument} hook as its first action. This meant that it was
executed in horizontal mode if the user left no empty line after the
last paragraph.  As a result one could get a spurious space added, for
example, when that code contained a \cs{write} statement. This was
fixed and now \cs{enddocument} first issues a \cs{par} to ensure that
it always starts out in vertical mode.
%
\githubissue{385}



\subsection{Allow extra space between name and address in \pkg{letter} class}

The \cs{opening} command in the \pkg{letter} class expects the
name and address to be separated by \verb=\\= but it didn't allow to
use an optional argument at this point to add some extra space after
the name. The coding has now been slightly altered to allow for this.
%
\githubissue{427}


\subsection[Add a Lua callback to \pkg{ltshipout} to provide
  a uniform location for applying custom attributes]
           {Add a Lua callback to \pkg{ltshipout} to provide
             a uniform
             \mbox\quad location for applying custom attributes}

Just before shipping out a page, a new \LuaTeX{} callback
\texttt{pre\_shipout\_filter} is now called to allow final
adjustments to the box to be shipped out. This is particularly for
Lua\TeX\ packages which flag certain elements of the page (e.g. using
attributes or properties) in order to apply certain effects to these
elements at shipout. An example for this is the \pkg{luacolor}
package which could insert the color commands using this callback.



\subsection{Improved copy\,\&\,paste support for \pdfTeX{} documents}

When compiling with \pdfTeX{}, additional information is added to the
PDF file to improve copying from and searching in text. This especially
allows ligatures to copy correctly from \pdfTeX{} generated PDF files in
most cases.

Since this has been integrated into the kernel, most documents should no
longer need to load the \pkg{cmap} package or input \texttt{glyphtounicode}.
%
\githubissue{465}


\subsection{Provide a hook in \cs{selectfont}}

After \cs{selectfont} has altered the font we run a hook so that
packages can make final adjustments. This functionality was originally
provided by the \pkg{everysel} package, the new implementation is
slightly different and uses the standard hook management.
%
\githubissue{444}


\subsection{Delay change of font series and shape to \cs{selectfont} call}

With the NFSS extensions introduced in 2020 the font series and shape
settings can be influenced by changes to the font family. The setting
is therefore delayed until \cs{selectfont} is executed to avoid
unnecessary or incorrect substitutions that may otherwise happen due
to the order of declarations.
%
\githubissue{444}



\subsection{Allow \cs{nocite} in preamble}

A natural place for \verb=\nocite{*}= would be the preamble of the
document, but for historical reasons \LaTeX{} issued an error message
if it was placed there. From the new release on it is now allowed in
the preamble.
%
\githubissue{424}



\subsection{Shipping out a page while bypassing hooks}

In the 2020 October release several hooks were added to the page
shipout process, e.g., to add some background or foreground material
to some or all pages. We now also added a \cs{RawShipout} command that
bypasses most of these hooks during the shipout. Some essential
internal bookkeeping still takes place such as updating the
\texttt{totalpages} counter or adding \texttt{shipout/firstpage} or
\texttt{shipout/lastpage} material if the page happens to be the first
or last.

\subsection{Robust commands in filename arguments}
The filename handling has been modified so that \verb|\string| is
applied while normalizing robust commands while determining the file
name.  Previously \verb|\input{\sqrt{2}}| would cause \LaTeX\ to loop indefinitely.
With the new behavior it accesses \verb|sqrt {2}.tex|.
%
\githubissue{481}


\subsection[Additional support for Unicode characters from the
  Latin Extended Additional block]
           {Additional support for Unicode characters from the Latin\\
             \mbox\quad Extended Additional block}

\LaTeX\ is quite capable of typesetting characters such as
\enquote{\d{m}}, but until now it lacked the Unicode mappings for some
characters that are used to write Sanskrit words in Latin
transliteration (as seen in books about yoga, Buddhist philosophy,
etc.). These have now been added so that such characters can be
entered directly instead of resorting to \verb=\d{m}= and so forth.
%
\githubissue{484}



\subsection{Always have color groups set up}

To use color in \LaTeX{} certain constructs, especially boxes, need an
extra layer of groups to ensure that the color setting does not
\emph{escape} and continue outside the box when it shouldn't. To
arrange for this the \LaTeX{} kernel defined a number of commands, e.g.,
\cs{color@begingroup} to be used in such places. They have been
initially no-ops and only the color packages redefined them to become
real groups. This arrangement complicates the coding as one has to
account for a group being there (or not there) depending of what is
loaded in the document. So now the kernel already adds the groups.
%
\githubissue{488}


\subsection{Execute \cs{par} at the end of \cs{marginpar} arguments}

In preparation for tagged PDF it is important to properly tag all
paragraphs and this requires running code at the beginning and end of
each. At the end of a paragraph this is done inside the \cs{par}
command, but the way \cs{marginpar} was coded, \LaTeX{} ended the
marginal note without ever explicitly calling \cs{par}. This has now
been changed.

Another case where this issue caused problems was the \pkg{lineno}
package where the last line was not numbered if the \cs{marginpar}
ended without a \cs{par} in the document.
%
\githubissue{489}



\subsection{Producing several footnote marks to one footnote}

It is sometimes necessary to reference the same footnote several
times, i.e., produce several footnote marks with the same number or
symbol. This is now always possible by placing a \cs{label} into the
\cs{footnote} and reference it with the command \cs{footref}
elsewhere.  This way marks referring to footnotes anywhere on the page
(including those in \texttt{minipage}s) can be generated.  In the past
this command was only available with certain classes or when loading
the \pkg{footmisc} package.
%
\githubissue{482}



\subsection[Providing the raw option list of packages or documentclass
  to key/value handlers]
           {Providing the raw option list of packages or documentclass\\
  \mbox\quad to key/value handlers}

\LaTeXe{} has always normalized space in option lists so\\
\verb|\documentclass[ a4paper , 12pt ]{article}|\\
processed the intended options \texttt{a4paper} and \texttt{12pt}.

Unfortunately the mechanism used was designed for the simple option
names of the standard option processing.  Many classes and packages 
now use extended \emph{keyval} processing, however this white space
normalization makes this difficult:
\verb|[bb=1 2 3 4]|
which might be expected to pass a bounding box of four numbers is
normalized to \texttt{bb=1234} and
\verb|[bb={1 2 3 4}]|\\
which might be expected to quote the spaces results in low level \TeX{}
parsing errors.


For compatibility reasons, the standard option processing has not been
changed however the original un-normalized package and class option lists
are now saved. They are not used in the standard processing, however
extended package option systems may use these \enquote{raw} option list
macros if they are defined.

The one change affecting the standard processing is that the low level
error mentioned above is now avoided as values (any tokens to the
right of an = sign) are removed from consideration from the
\enquote{unused option list}.  In this release \texttt{clip=true} and
\texttt{clip=false} both contribute \texttt{clip} to the list of
options that have been used.
%
\githubissue{85}



\subsection{Poor man's \cs{textasteriskcentered} if missing}

The \cs{textasteriskcentered} symbol, used as part of the set of
footnote symbols in \LaTeX{}, is assumed to be implemented by
every font in the \texttt{TS1} encoding (when \pdfTeX{} is used) or
in the \texttt{TU} encoding for the Unicode engines. Unfortunately,
that assumption is not correct for all fonts, for example, for the
\texttt{stix2} fonts don't offer the glyph, with the result that one
gets missing glyphs when using \cs{thanks} etc.

For that reason the definition for \cs{textasteriskcentered} was
altered to check if there is a glyph in the right position and if not
a normal \enquote{*} is used, slightly enlarged and lowered.  That may
not be perfect in all cases, but certainly better than nothing show
up.
%
\githubissue{502}



\subsection{Provide more ``dashes'' in encodings \texttt{OT1},
  \texttt{T1} and \texttt{TU}}

When pasting in text from external sources one sometimes encounters
the Unicode characters
%
\texttt{"2011} (non-breaking hyphen),
\texttt{"2012} (figure dash) and
\texttt{"2015} (horizontal bar)
%
in addition to the common \texttt{"2013} (en-dash) and \texttt{"2014}
(em-dash). In the past the first three characters produced an error
message when used with \pdfTeX{}. Now they typeset an approximation
(as they are unavailable in \texttt{OT1} or \texttt{T1} encoded fonts
used by \pdfTeX{}), e.g., the figure dash is approximated by an en-dash.

In Unicode engines they either work (if contained in the selected
Unicode font) or typeset nothing and produce a ``Missing character''
warning in the log file.

However, what works in all engines now, is to access the characters
via the command names \cs{textnonbreakinghyphen}, \cs{textfiguredash}
and \cs{texthorizontalbar}, respectively.
%
\githubissue{404}



\subsection{\env{filecontents} with \acro{utf-8} characters in file name}

Since a few releases back, the \env{filecontents} environment allows writing a
file with \acro{utf-8} characters in its name.  However there was a bug that
would not allow \emph{over}writing a file with \acro{utf-8} characters in the
name.  This has been fixed and now \env{filecontents} allows any characters in
the file name.
%
\githubissue{415}



\subsection{Extending \pkg{latexrelease} to declare an entire module}

In the 2020-10-01 release, \LaTeX's new hook management system was added to the
kernel (see \cite{33:ltnews32}) and, as with all changes to the kernel, it was
added to \pkg{latexrelease}, so that it is possible to roll back to a date where
such module didn't exist yet, or roll forward from an older release and have the
hook management system by loading the \pkg{latexrelease} package.

However rolling back from a later release to the 2020-10-01 release didn't quite
work because it would try to define all the commands from \pkg{lthooks} again,
and that would result in errors, as usual with commands defined with
\cs{newcommand} or in the case of \pkg{lthooks}, \cs{cs\_new:Npn}.

To solve this issue, now completely new modules can be defined in
\pkg{latexrelease} using \cs{NewModuleRelease}
and then when rolling back or forward it will know if the code
of the module has to be read or completely ignored.  More details can be
found in the \pkg{latexrelease} documentation (\verb|texdoc latexrelease|).
%
\githubissue{479}



\subsection{Small fix for rolling back prior to 2020-02-02}

Whereas the \pkg{latexrelease} package can usually emulate an older \LaTeX{}
kernel without much problem, rolling back to before the 2020-02-02 release
didn't work properly because the management of the \cs{ExplSyntaxOn/Off} status
for packages cannot be removed by the rollback without messing up catcodes after
an \pkg{expl3}-based package is loaded.  This has been fixed and now rollback is
more careful not to leave \pkg{ExplSyntaxOn} after a package ends.
%
\githubissue{504}



\subsection[Add \cs{tracingstacklevels}
  and \cs{tracinglostchars}\texttt{=3} to \cs{tracingall}]
           {Add \cs{tracingstacklevels}
             and \cs{tracinglostchars}\texttt{=3}\\
             \mbox\quad to \cs{tracingall}}

In July 2020 David Jones suggested an extension to \TeX{} engines, that
added the possibility to set \cs{tracinglostchars}\texttt{=3} to have an
error in case some character is missing from a font.  In previous years,
the warning for a missing character would be silently printed to the
\texttt{.log} file (if $\cs{tracinglostchars}>0$) and to the terminal
(if ${}>1$).  This extension was added for \TL{} and \MiKTeX{} (except
in Knuth's \TeX, of course) and now with $\cs{tracinglostchars}>2$ you
get an error on a missing glyph.

Later, in January 2021, Petr Olšák suggested yet another extension, a
new primitive parameter \cs{tracingstacklevels} that, when positive (and
when \cs{tracingmacros} is also positive), will print a visual
indication of the macro nesting level in \TeX's tracing information.

Both these changes were incorporated to \LaTeX's debugging macros
\cs{tracingall} and \cs{tracingnone}, so when you use them, the new
extensions are automatically activated/deactivated if your \TeX{}
distributions has a recent enough engine.  An example document
demonstrating these parameters is available in the linked GitHub issue.
%
\githubissue{524}


\subsection{Make \cs{\textbackslash} generally robust}

In 2018 most \LaTeX{} user-level commands were made robust including
\cs{\textbackslash}. However, \cs{\textbackslash} is redefined in
various environments and not all cases were caught, in particular its use as row
delimiter in \env{tablular} structures. This has now been corrected and
\cs{\textbackslash} should be robust in all standard
circumstances. Doing that also fixed one anomaly present in the past:
in a tabular preamble of the form
\begin{quote}
  \verb={l=\texttt{\string>}\verb={raggedright}p{10cm}r}=           % stupid class
\end{quote}
a \cs{\textbackslash} in the second column would have the definition
used by \cs{raggedright} and would not indicate the (premature) end of
the \env{tabular}, e.g.,
\begin{quote}
   \verb=a & b1 \\ b2 & c \\=
\end{quote}
would be a single row in that \env{tabular}. However, writing
\begin{quote}
   \verb=a &    \\ b2 & c \\=
\end{quote}
would give you two rows: due to the scanning process the
\cs{\textbackslash} directly following the \verb=&= still had
the \enquote{end the row} meaning and not the \enquote{start a new
  line in the second column} meaning.

With \cs{\textbackslash} now robust, the scanning after \verb=&= ends
when the command is seen and the second column is started and so now
both lines above consistently produce a single \env{tabular} row.

As before, you can use \cs{raggedright} \cs{arraybackslash} in the
\env{tabular} preamble to ensure that \cs{\textbackslash} is always
interpreted as a row separator when used in the column or you could
use \cs{tabularnewline} to explicitly ask for a new row even when
\cs{\textbackslash} has a different meaning in the current column.
%
\githubissue{548}



\section{Changes to packages in the \pkg{graphics} category}


\subsection{Removed spurious warning for generic graphics rules}

A previous release mistakenly caused a warning to appear when loading a graphics
file with an unknown extension through a generic graphics rule.  The warning
would incorrectly say that the file was not found, whereas the file would be
included correctly.  The warning now doesn't show up in that case.
%
\githubissue{516}


\subsection{Fixed loading \texttt{gzip}ped PostScript graphics files}

A previous release mistakenly changed the file searching mechanism and
compressed graphics files would raise an error when being loaded with
\cs{includegraphics}.  This has been fixed and now \texttt{gzip}ped graphics
load correctly.
%
\githubissue{519}





\section{Changes to packages in the \pkg{tools} category}

\subsection{\pkg{layout}: Support extra language options}
The package now recognizes \texttt{japanese} and \texttt{romanian} as
language options.
%
\githubissue[s]{353 and 529}


\subsection{\pkg{array} and \pkg{longtable}: Make \cs{\textbackslash} generally robust}

The fix for this issue was also applied to these packages, see above.
%
\githubissue{548}


\subsection{\pkg{longtable}: General bug fix update}
Minor update to \pkg{longtable} to fix bugs reported.  Notably the
possibility of incorrect page breaks if floats appear on the same page
that a \env{longtable} starts.  As this may affect page breaking in
existing documents, a rollback to \pkg{longtable 4.13}
(\file{longtable-2020-01-07.sty}) is supported.
%
\gnatsissue{tools}{2914 3396 3512}
\githubissue{133 183 464}


\subsection[\pkg{trace}: Add \cs{tracingstacklevels}
  and \cs{tracinglostchars}\texttt{=3} to \cs{traceon}]
           {\pkg{trace}: Add \cs{tracingstacklevels} and\\
  \mbox\quad \cs{tracinglostchars}\texttt{=3} to \cs{traceon}}

The enhancement mentioned earlier was also added to the \pkg{trace} package.
%
\iffalse
The \cs{tracingstacklevels} and \cs{tracinglostchars} extensions
mentioned earlier for \cs{tracingall} were also added for
\cs{traceon} in the \pkg{trace} package, so if you're using that you
can also benefit from these new debugging tools.
\fi
%
%
\githubissue{524}




\subsection{\pkg{bm}: Better support for commands with optional arguments}
Some uses of optional arguments that were supported by \cs{bm} stopped
being supported (in 2004) when \cs{kernel@ifnextchar} was used
internally by the format instead of \cs{@ifnextchar}. This update
handles both versions of this command and restores the original
behaviour.

In addition package options for guiding the use of \enquote{poor man's
  bold} in fallback situations were added.
%
\githubissue{554}

\section{Changes to packages in the \pkg{amsmath} category}

%\subsection{\pkg{amsmath}: Make \cs{\textbackslash} generally robust}

The fix for issue 548 was also applied in \pkg{amsmath}, see above.
%
\githubissue{548}


%\medskip

\begin{thebibliography}{9}

\fontsize{9.3}{11.3}\selectfont

\bibitem{33:blueprint} Frank Mittelbach and Chris Rowley:
  \emph{\LaTeX{} Tagged PDF — A blueprint for a large project}.\\
  \url{https://latex-project.org/publications/indexbyyear/2020/}

\bibitem{33:source2e}
  \emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
  \url{https://latex-project.org/help/documentation/}

\bibitem{33:ltnews32} \LaTeX{} Project Team:
  \emph{\LaTeXe{} news 32}.\\
  \url{https://latex-project.org/news/latex2e-news/ltnews32.pdf}

\end{thebibliography}



\end{document}
