[latex3-commits] [latex3/latex2e] develop: some source cleanup (no output change) (3902ce18)

[github at latex-project.org]

Repository : https://github.com/latex3/latex2e
On branch  : develop
Link       : https://github.com/latex3/latex2e/commit/3902ce18a3c0233097da51f24aa6528874855975

>---------------------------------------------------------------

commit 3902ce18a3c0233097da51f24aa6528874855975
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Mon Oct 30 19:50:46 2023 +0100

    some source cleanup (no output change)


>---------------------------------------------------------------

3902ce18a3c0233097da51f24aa6528874855975
 base/doc/ltnews38.tex | 43 ++++++++++++++++++++++---------------------
 1 file changed, 22 insertions(+), 21 deletions(-)

diff --git a/base/doc/ltnews38.tex b/base/doc/ltnews38.tex
index aa1f9524..0255f205 100644
--- a/base/doc/ltnews38.tex
+++ b/base/doc/ltnews38.tex
@@ -146,8 +146,9 @@
 \section{News from the \enquote{\LaTeX{} Tagged PDF} project}
 
 The multi-year project to automatically tag \LaTeX{} documents in
-order to make them accessible~\cite{38:blueprint} is progressing steadily (at this
-point in time mainly as experimental \texttt{latex-lab} code).
+order to make them accessible~\cite{38:blueprint} is progressing
+steadily (at this point in time mainly as experimental
+\texttt{latex-lab} code).
 
 Just recently we added support for automatic tagging of tabular
 structures including environments from \pkg{tabularx} and
@@ -159,15 +160,15 @@ configuration possibilities\Dash these will be added in the future.
 Nevertheless, with this new addition we are more or less able to
 automatically tag any document that confines itself to the commands
 and environments described in Leslie Lamport's \emph{\LaTeX{}
-Manual}~\cite{38:Lamport} by simply adding a single configuration line at the
-top.
+Manual}~\cite{38:Lamport} by simply adding a single configuration line
+at the top.
 
 In addition, a number of extension packages that go beyond Lamport are
 already supported, most importantly perhaps \pkg{amsmath} (providing
-extended math capabilities) and \pkg{hyperref} (enhancing \LaTeX{} with
-interactive hyperlinking features). Also already supported are some of the
-major bibliography support packages such as \pkg{natbib} and
-\pkg{biblatex}.
+extended math capabilities) and \pkg{hyperref} (enhancing \LaTeX{}
+with interactive hyperlinking features). Also already supported are
+some of the major bibliography support packages such as \pkg{natbib}
+and \pkg{biblatex}.
 
 For now activation is done through the line
 \begin{verbatim}
@@ -178,28 +179,28 @@ The math and the tabular support are not yet incorporated into
 \texttt{phase-III} but need their own activation, so that we can
 better experiment with additions and code adjustments.
 
-The \texttt{latex-lab} bundle contains various 
-(still untagged) documentation files about the new code that can
-be accessed with \verb|texdoc -l latex-lab|.
+The \texttt{latex-lab} bundle contains various (still untagged)
+documentation files about the new code that can be accessed with
+\verb|texdoc -l latex-lab|.
 
 \subsection{A GitHub repository dedicated to the project}
 
 We have also started a new GitHub repository mainly intended for
 reporting issues, and offering a platform for discussions. For
-example, there is one discussion on ways to extend the \LaTeX{} \texttt{tabular}
-syntax to allow describing the logical structure of tables (e.g.,
-which cells are header cells, etc.).
+example, there is one discussion on ways to extend the \LaTeX{}
+\env{tabular} syntax to allow describing the logical structure of
+tables (e.g., which cells are header cells, etc.).
 
 Having all issues and discussions related to the project in a single
 place instead of being spread across multiple repositories such as
-\texttt{latex2e}, \texttt{latex3}, \texttt{tagpdf}, \texttt{hyperref},
-\texttt{pdfresources}, etc., helps people to find information easily
+\pkg{latex2e}, \pkg{latex3}, \pkg{tagpdf}, \pkg{hyperref},
+\pkg{pdfresources}, etc., helps people to find information easily
 and report any issue related to the project without needing to know in which
 code repository the problematic code resides.
 
 You find this repository at
 \url{https://github.com/latex3/tagging-project} and the mentioned
-discussion on \texttt{tabular} syntax at
+discussion on \env{tabular} syntax at
 \url{https://github.com/latex3/tagging-project/discussions/1}.
 
 Your feedback is important and reporting what doesn't yet work is
@@ -427,7 +428,7 @@ pre-loaded programming layer.  Programmers can check the date of
 \pkg{expl3} they are using in the \texttt{.log}, as it appears both at
 the start and end in the format
 \begin{verbatim}
-L3 programming layer <YYYY-MM-DD>
+  L3 programming layer <YYYY-MM-DD>
 \end{verbatim}
 just after the line which identifies the format (\texttt{LaTeX2e}, etc.).
 %
@@ -436,16 +437,16 @@ just after the line which identifies the format (\texttt{LaTeX2e}, etc.).
 
 \section{Code improvements}
 
-\subsection{Support for tabs in \cs{verb*} and \texttt{verbatim*}}
+\subsection{Support for tabs in \cs{verb*} and \env{verbatim*}}
 
 \LaTeX{} converts a single tab to a single space, which is then treated like a
 \enquote{real} space in typesetting. The same has been true to date inside
 \cs{verb}, but was done in a way that meant that they remained as normal spaces
 even in \cs{verb*}, etc. We have now adjusted the code so that tabs are
 retained within the argument to \cs{verb} and \cs{verb*}, and the
-\texttt{verbatim} and \texttt{verbatim*} environments independently from
+\env{verbatim} and \env{verbatim*} environments independently from
 spaces, and are set up to print in the same way spaces do. This means that they
-now generate visible spaces inside \cs{verb*} and \texttt{verbatim*}, and their
+now generate visible spaces inside \cs{verb*} and \env{verbatim*}, and their
 behavior can be adjusted if required to be different from that of spaces.
 %
 \githubissue{1085}