[latex3-commits] [latex3/latex2e] develop: a few more updates to ltnews37 (as suggested by kb); 2 errata entries for tlc3 (e7b692b2)

github at latex-project.org github at latex-project.org
Sun May 28 11:25:15 CEST 2023


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

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

commit e7b692b2914bfc2ca9e61729e597995efdc808fb
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Sun May 28 11:25:15 2023 +0200

    a few more updates to ltnews37 (as suggested by kb);
    2 errata entries for tlc3


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

e7b692b2914bfc2ca9e61729e597995efdc808fb
 base/doc/ltnews37.tex | 130 ++++++++++++++++++++++++++------------------------
 base/doc/tlc3.err     |  10 ++++
 base/ltnews.cls       |  15 +++++-
 3 files changed, 90 insertions(+), 65 deletions(-)

diff --git a/base/doc/ltnews37.tex b/base/doc/ltnews37.tex
index 9cbf7f29..5527975c 100644
--- a/base/doc/ltnews37.tex
+++ b/base/doc/ltnews37.tex
@@ -113,10 +113,11 @@
 \let\finalvspace\vspace          % for document layout fixes
 
 % Undo ltnews's \verbatim at font with active < and >
-\makeatletter
-\def\verbatim at font{%
-  \normalsize\ttfamily}
-\makeatletter
+% (we have meta variables in verbatim, so keep it.)
+%\makeatletter
+%\def\verbatim at font{%
+%  \normalsize\ttfamily}
+%\makeatother
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \providecommand\tubcommand[1]{}
@@ -131,7 +132,7 @@
 
 \begin{document}
 
-\tubcommand{\addtolength\textheight{4.2pc}}   % only for TUB
+\tubcommand{\addtolength\textheight{4.1pc}}   % only for TUB
 
 \maketitle
 {\hyphenpenalty=10000 \exhyphenpenalty=10000 \spaceskip=3.33pt \hbadness=10000
@@ -139,6 +140,9 @@
 
 \setlength\rightskip{0pt plus 3em}
 
+% for ltnews37, squeeze to five pages.
+\tubcommand{\fontsize{9.6}{12}\selectfont}
+
 
 \medskip
 
@@ -146,7 +150,6 @@
 %\section{Introduction}
 
 
-
 \section{New functionality offered as part of the
   \enquote{\LaTeX{} Tagged PDF} project}
 
@@ -184,7 +187,7 @@ the following line:
 \DocumentMetadata{testphase={phase-III,math}}
 \end{verbatim}
 Note that the math tagging code at this point in time will clash with
-packages that redefine the \texttt{\$} (which then may lead to strange
+packages that redefine the \texttt{\$} character (which then may lead to strange
 errors) and that packages that use math mode for non-mathematical
 constructs may result in surprising output as far as tagging is
 concerned. Feedback on which packages fail with the code in one or
@@ -222,12 +225,12 @@ extension is completely compatible with older documents and packages.
 \AddToHook{cmd/verbatim at font/after}[hack]{\small}
 To declare a hook with arguments, use
 \begin{verbatim}
-\NewHookWithArguments {<hook>} {<num args>}
+\NewHookWithArguments {<hook>} {<num-args>}
 \end{verbatim}
-then, similarly, to use the code in the hook (supposing a hook declared
-with 2 arguments), write
+then, similarly, to use the code in the hook, supposing a hook declared
+with 2 arguments, write
 \begin{verbatim}
-\UseHookWithArguments {<hook>} {2} {<arg 1>} {<arg 2>}
+\UseHookWithArguments {<hook>} {2} {<arg1>} {<arg2>}
 \end{verbatim}
 
 Or, if you want to add some code to a hook that takes arguments, write
@@ -256,14 +259,14 @@ were also added.  The complete documentation can be found in the
 
 \subsubsection{Generic \texttt{cmd} hooks with arguments}
 
-Along with the possibility to pass arguments to a regular hook as
+Along with the possibility of passing arguments to a regular hook as
 discussed above, generic \hook{cmd} hooks can now access the arguments
-of the command they are patched into using the interface described in
+of the command they are patched into, using the interface described in
 the previous section.
 
 For example, if you were to add some code to the \cs{title} command
 using hooks, you could access the actual title given in the argument.
-For example, to write the title of the document in the terminal you
+Thus, to write the title of the document in the terminal you
 could use:
 \begin{verbatim}
   \AddToHookWithArguments{cmd/title/before}
@@ -278,7 +281,7 @@ they did before.
 
 \subsection{Providing copy and show functions for environments}
 
-To copy a command definition we have introduced \cs{NewCommandCopy} in
+To copy a command definition we introduced \cs{NewCommandCopy} in
 2022.  This even allows you to copy commands that consist of several internal
 components, such as robust commands or those with a complex signature.
 To do the same with environments, e.g., to define the environment
@@ -294,13 +297,13 @@ In addition, we offer a \cs{ShowEnvironment} command, which displays the
 argument. E.g., \verb=\ShowEnvironment{center}= results in the
 following output:
 \begin{verbatim}
-  > \begin{center}=environment:
-  > ->\trivlist \centering \item \relax .
-  <recently read> }
+  >> \begin{center}=environment:
+  >> ->>\trivlist \centering \item \relax .
+  <<recently read>> }
   l. ...\ShowEnvironment{center}
-  > \end{center}:
-  > ->\endtrivlist .
-  <recently read> }
+  >> \end{center}:
+  >> ->>\endtrivlist .
+  <<recently read>> }
   l. ...\ShowEnvironment{center}
 \end{verbatim}
 %
@@ -317,13 +320,13 @@ line.
 \githubissue{1015}
 
 \subsection{\cs{DeclareLowercaseMapping}, \cs{DeclareTitlecaseMapping}
-  and \cs{DeclareUppercaseMapping}}
+  and \cs{DeclareUppercaseMapping}\texorpdfstring{\raggedright}{}}
 
 The move from a case-changing approach using \cs{lccode} and \cs{uccode} data
 to one where information is stored by a kernel-managed structure left a gap in
 the ability of the user to \emph{tune} the case changing outcomes. This has now
 been addressed by the addition of three commands
-\begin{itemize}
+\begin{itemize}\tubcommand{\setlength{\parskip}{0pt}}%
   \item \cs{DeclareLowercaseMapping}
   \item \cs{DeclareTitlecaseMapping}
   \item \cs{DeclareUppercaseMapping}
@@ -361,7 +364,7 @@ by both the kernel and any other \enquote{consumer} packages.
 The \cs{samepage} declaration sets various parameters to
 \texttt{10000} to prevent undesired page breaks.  The
 \cs{predisplaypenalty} parameter has already by default a value of
-\texttt{10000} and to save space back in the days it was therefore not
+\texttt{10000}, and to save space in the past it was therefore not
 explicitly set. However, there are a few classes that change the
 parameter and as result the user might experience a page break in
 front of a display formula within the scope of \cs{samepage} when
@@ -404,17 +407,17 @@ Starting with this release, the number of values stored in \cs{newlabel} has bee
 
 Additionally, a hook with the name \texttt{label} has been 
 added. It takes one argument: the label string.
-Code added to the hook can refer to this argument with \verb+#1+. 
+Code added to the hook can refer to this argument with~\verb+#1+. 
 The hook is executed directly before the \cs{label} command writes to the \texttt{.aux} file
-but \emph{after} the \cs{@bsphack} command has done its spacing magic and it is located \emph{inside} a group, thus its code only affects the write operation. 
+but \emph{after} the \cs{@bsphack} command has done its spacing magic, and it is located \emph{inside} a group; thus, its code only affects the write operation. 
 
 \section{Code improvements}
 
 \subsection{Performance in checking file existence}
 
-The addition of hooks, etc., to file operations had a side-effect in that
-multiple checks were made that the file existed. In larger documents using
-lots of files, these file system operations caused non-trivial performance
+The addition of hooks, etc., to file operations had a side effect of making
+multiple checks that the file existed. In larger documents using
+many files, these file system operations caused non-trivial performance
 impact. We now cache the existence of files, such that these repeated filesystem
 calls are avoided.
 
@@ -431,9 +434,9 @@ Due to some problems in the code it wasn't possible to prevent
 The default quote and backquote characters in typewriter fonts are
 typographical quotes, e.g., the input
 \begin{verbatim}
-   \verb*/`prog 'my input'`/
+   \verb/`prog 'my input'`/
 \end{verbatim}
- is rendered as \verb*/`prog 'my input'`/ and not as
+ is rendered as \verb/`prog 'my input'`/ and not as
 %
 \begingroup              % code to mimic upquote.sty
 \catcode`'=\active
@@ -449,7 +452,7 @@ typographical quotes, e.g., the input
     \fi\fi}
 \endgroup
 %
-\verb*/`prog 'my input'`/ as preferred by many programmers.
+\verb/`prog 'my input'`/ as preferred by many programmers.
 
 This can be adjusted, for example, with the \pkg{upquote} package,
 which results in the second output. However, for historical reasons
@@ -469,9 +472,9 @@ processing. However, it only got a definition when
 \verb=\begin{document}= was executed, with a result that a user
 definition in the preamble was unconditionally overwritten at this
 point. To properly alert the user that this command is not freely
-available we now already provide a definition in the format so that
+available we now make a definition in the format, so that
 \cs{newcommand} and friends produce a proper error message instead of
-providing a definition that doesn't last.
+allowing a definition that doesn't last.
 %
 \githubissue{975}
 
@@ -502,11 +505,12 @@ adjust what is happening before, during, and after the
 can reset code they have altered (e.g., \cs{catcode}s during
 verbatim-like processing) and with \hook{shipout/background} and
 \hook{shipout/foreground} material can be added to the pages.
-Details are given in \cite{37:ltshipout-doc}. However, what was
+Details are given in \cite{37:ltshipout-doc}.
+
+However, still
 missing was a hook that allows a package writer to manipulate the
 completed page (with foreground and background attached) just before
 the actual shipout happens.
-
 For this we now provide the additional hook \hook{shipout}. One
 use case (sometimes needed in print production) is to mirror the
 whole page via \cs{reflectbox} including all the extra data that may
@@ -519,7 +523,7 @@ have been added into the fore- or background.
 \subsection{Displaying release information in the \texttt{.log}}
 
 \LaTeX{} displays its release information at the very beginning of the
-\LaTeX{} run on the terminal and also writes it to the transcript file
+\LaTeX{} run on the terminal, and also writes it to the transcript file
 if that is already opened at this point. While this is normally true,
 it is not the case if the \LaTeX{} run was started passing additional
 \TeX{} code on the command line, e.g.,
@@ -558,14 +562,14 @@ eventually be moved into \pkg{unicode-math}.
 
 \subsection{A fix for \cs{hspace}}
 
-The change to \cs{hspace}, done in 2020 to make it \pkg{calc} aware,
+The change to \cs{hspace}, done in 2020 to make it \pkg{calc}-aware,
 had the unfortunate side effect that starting a paragraph with
 \cs{hspace} would result in the execution of \cs{everypar} inside a
 group (i.e., any local changes would immediately be revoked, breaking,
 for example, \pkg{wrapfig} in that special situation).
 %
 This got fixed with the 2022-11 PL1 hotfix, so was already corrected in
-the previous release, but only now documented in the newsletter.
+the previous release, but is only now documented in the newsletter.
 %
 \githubissue{967}
 
@@ -586,11 +590,11 @@ class option \texttt{doc2}. This has now been corrected.
 A list and several other document elements add some vertical space in
 front of them. However this should not happen at the beginning of a
 box (such as a \env{minipage}) and normally it doesn't, because
-\TeX{} automatically drops such spaces at the start of a vertical
+\TeX{} automatically drops such space at the start of a vertical
 list. However, if there is some invisible material, such as a
-\cs{color} command, some \pkg{hyperref} anchor, a \cs{write} or
-something else, then the list is no longer empty and \TeX{} no longer
-drops spaces, hence the difference.
+\cs{color} command, a \pkg{hyperref} anchor, a \cs{write} or
+other such items, then the list is no longer empty and \TeX{} no longer
+drops the vertical space.
 
 With the new paragraph handling introduced in 2021 it is now finally
 possible to detect and avoid this problem and apply appropriate
@@ -603,7 +607,7 @@ correct.
 \subsection{A fix for \cs{NewCommandCopy} and \cs{ShowCommand}}
 
 When copying and showing definitions of (non-expandable) document commands
-(aka commands defined by \cs{NewDocumentCommand} and friends) containing empty
+(a.k.a.\ commands defined by \cs{NewDocumentCommand} and friends) containing empty
 or only \texttt{m}-type arguments, these commands were wrongly recognized as
 expandable ones.
 This is fixed in the present \LaTeX{} release.
@@ -657,9 +661,9 @@ When \LaTeXe{} was released, the team provided documentation for both document
 authors and package/class developers in the two files \texttt{usrguide} and
 \texttt{clsguide}. Over time, the team have augmented these documents as new
 methods have been added to the kernel. However, they retained their structure
-as starting from familiarity with \LaTeX{}~2.09. This meant that for new users,
+as assuming familiarity with \LaTeX{}~2.09. This meant that for new users,
 there was material which is no longer relevant, and less clarity than desirable
-in what approaches are recommended today.
+regarding the approaches that are recommended today.
 
 The two files have now been (partially) re-written, with the versions available
 previously now frozen as \texttt{usrguide-historic} and \texttt{clsguide-historic}.
@@ -681,24 +685,24 @@ want to cater for formats that are older than 2020.
 
 Or you know that your package is definitely not going to work with a
 format before a certain \meta{date}, in which case you could use
-\verb/\NeedsTeXFormat{LaTeX2e}[/\meta{date}\texttt] to ensure that any
-  user is alerted if their format is too old.
+\verb/\NeedsTeXFormat{LaTeX2e}[/\meta{date}\texttt] to ensure that
+users are alerted if their format is too old.
 
-The big problem is to know the exact \meta{date} to put into such
-commands and in the past that was not that easy to find. You could have 
+The big problem is knowing the exact \meta{date} to put into such
+commands; in the past, that was not that easy to find. You could have 
 looked in the file \file{changes.txt}, but that is hidden somewhere
 in your installation and if you try
-\verb*/texdoc -l changes.txt/ you get more than thirty results and the %*
+\verb/texdoc -l changes.txt/ you get more than thirty results and the %*
 right file is by no means the first.
 
 Yukai Chou (\textsf{@muzimuzhi}) kindly provided a patch for this, so that we now have
 the exact dates for each \LaTeX{} format listed in an easy to remember
 place: in \file{ltnews.pdf} and that file conveniently also contains all major
 features and changes to \LaTeX{} over the years\Dash one of which is
-most likely the reason you need the \meta{date} date in the first
+most likely the reason you need the \meta{date} in the first
 place.
 
-It is given in parentheses in the newsletter title, thus this
+The date is now given in parentheses in the newsletter title, thus this
 newsletter tells you that on
 %
 \makeatletter
@@ -714,18 +718,18 @@ out that the \LaTeX3 programming layer was added on 2020-02-02
 %
 \githubissue{982}
 
-\subsection{Fresh from the press: \enquote{The \LaTeX{} Companion, third edition} is now in print}
+\subsection{Fresh from the press:\ \enquote{The \LaTeX{} Companion, third~edition} is now in print}
 
 The third edition of \emph{The \LaTeX{} Companion} is now
-available. This is the end of five years of careful work and we hope
+available. This is the result of five years of careful work and we hope
 that it will provide our readers with all the information they need to
 successfully navigate the \LaTeX{} ecosystem and efficiently produce
 beautiful documents.
 
 Since the publication of the last edition (2004), a lot has happened in
 the \LaTeX{} world and thus a complete rewrite was necessary.  All
-chapters have been thoroughly revised and in many cases largely
-extended to describe new important functionality and features. More
+chapters have been thoroughly revised, and in many cases significantly
+extended, to describe new important functionality and features. More
 than 5,000 add-on packages have been analyzed in detail, out of which
 roughly 10\% have been chosen for inclusion in \emph{The \LaTeX{}
 Companion}. All important aspects of these packages are described to
@@ -734,7 +738,7 @@ for the decade to come.
 
 To cover what we thought worth describing today, the book nearly
 doubled in size. The print edition is therefore produced as a
-two-volume set and sold as a bundle. Both volumes come as hard-cover
+two-volume set and sold as a bundle. Both volumes come as hardcover
 with ribbons to easily mark pages in the book.
 
 To give you an idea of what is covered in the third edition you can
@@ -743,8 +747,8 @@ find some excerpts at
 \url{https://www.latex-project.org/news/2023/03/17/TLC3}
 \end{quote}
 
-The edition is also available as an eBook (Parts I and II combined)
-consisting of PDF and ePub format without DRM\@. Finally, the publisher
+The edition is also available as an eBook (Parts~I and~II combined)
+consisting of PDF and ePub format, without DRM\@. Finally, the publisher
 offers the combination of the printed books and the digital versions at
 a very attractive price not available anywhere else.
 
@@ -768,7 +772,7 @@ but for CJK (Chinese/Japanese/Korean) languages it is better to use a zero depth
 all characters have the same height and depth.  And even with
 Latin-based languages one might want to use the depth of a \cs{strut}
 or that of a parenthesis. So we now offer a way to adjust this while
-maintaining backward compatibility. Just redefine
+maintaining backward compatibility: redefine
 \cs{multicolmindepthstring} to hold whatever you want to get measured
 for its depth (the width is not relevant).
 %
@@ -792,10 +796,10 @@ page. This has now been fixed.
 
 \begin{thebibliography}{9}
 
-\fontsize{9.3}{11.3}\selectfont
+%\fontsize{9.3}{11.3}\selectfont
 
 \bibitem{37:ltshipout-doc} Frank Mittelbach, \LaTeX{}~Project~Team:
-  \emph{The \texttt{\upshape ltshipout} documentation}.\\
+  \emph{The~\texttt{\upshape ltshipout} documentation}.\\
   Run \texttt{texdoc} \texttt{ltshipout-doc} to view.
 
 \bibitem{37:lthooks-doc} Frank Mittelbach, Phelype Oleinik, \LaTeX{}~Project~Team:
diff --git a/base/doc/tlc3.err b/base/doc/tlc3.err
index 26d7905a..0ca42f92 100644
--- a/base/doc/tlc3.err
+++ b/base/doc/tlc3.err
@@ -738,6 +738,11 @@ longer honored.
 Chapter title not properly capitalized.
 \\ Already corrected in the digital version.
 
+\erroronpage{II-261}{para 3, l.3}{FMi}{2023/05/26}{s}
+Yoda spoke it seems: \ldots \u{and compare we should} \>
+\ldots \u{and you should compare}
+\\ Already corrected in the digital version.
+
 
 \CHAPTER{Chapter 13 --- Localizing Documents}
  
@@ -751,6 +756,11 @@ Chapter title not properly capitalized.
 
 \CHAPTER{Chapter 15 --- Bibliography Generation}
 
+\erroronpage{II-435}{code}{FMi}{2023/05/26}{s}
+\verb=\textcolor{See= \> \verb=\textcolor{blue}{See=
+\\ Already corrected in the digital version.
+
+
 
 \CHAPTER{Chapter 16 --- Managing Citations}
 
diff --git a/base/ltnews.cls b/base/ltnews.cls
index a57d9fc6..45ee3664 100644
--- a/base/ltnews.cls
+++ b/base/ltnews.cls
@@ -41,7 +41,7 @@
 
 \NeedsTeXFormat{LaTeX2e}
 
-\ProvidesClass{ltnews}[2017/12/13 v1.06  Standard LaTeX class]
+\ProvidesClass{ltnews}[2023/05/28 v1.08  Standard LaTeX class]
 
 % The configuration file, used for passing options.
 
@@ -474,7 +474,7 @@
       \parbox[t][7\baselineskip]{\textwidth}{%
          \@titlefont\@title\\[\medskipamount]
          \normalfont\normalsize\issuename~\@issue,
-         \@month~\@year~(\publicationdate)%
+         \@month~\@year~(\LaTeX\ release \publicationdate)%
       }%
    }]%
    \thispagestyle{titlepage}
@@ -519,6 +519,17 @@
       {1sp}{\@subheadingfont}%
 }
 
+
+% suggestion by Karl Berry (not integrated (yet))
+
+\newcommand{\ltnewssectformat}{%
+  \@headingfont
+  \frenchspacing
+  \raggedright
+  \hyphenpenalty=10000
+  \exhyphenpenalty=10000
+}
+
 % No section numbers.
 
 \setcounter{secnumdepth}{0}





More information about the latex3-commits mailing list.