LaTeX News 40 edits by KB

Author: josephwright

base/doc/ltnews40.tex

@@ -159,15 +159,15 @@
 
 \section{Thirty years of \LaTeXe{}}
 
-Summer 1994, i.e., thirty years ago, \LaTeXe{} saw its first public
+In summer 1994, i.e., thirty years ago, \LaTeXe{} saw its first public
 release. Back then it was meant to be an intermediate version (hence
 the $\epsilon$) on the way to a major new version (the mythical
 \LaTeX3) that we expected to take a couple of more years to reach
 maturity. It took much more than that in the end\Dash nominally,
 \LaTeXe{} is still with us today.
 
 However, under the hood, \LaTeXe{} changed a lot throughout these
-thirty years as one can see, for example, when looking through the
+thirty years, as one can see, for example, when looking through the
 forty newsletters~\cite{40:ltnews} that accompanied the \LaTeX{}
 releases that happened in the meantime.
 
@@ -182,9 +182,9 @@ \section{Thirty years of \LaTeXe{}}
 
 Initially, this approach worked well and provided good backward
 compatibility; however, over time it became apparent that keeping all
-developments confined to packages got more and more problematical.
+developments confined to packages was more and more problematical.
 Features or bug fixes that should have been generally available, i.e.,
-being part of the kernel, were only available in packages, so a lot of
+part of the kernel, were only available in packages, so a lot of
 dependencies between packages were introduced and resulted in
 convoluted code that was difficult to manage. For example,
 \pkg{hyperref} had to rewrite a lot of kernel (and package) macros, so
@@ -200,8 +200,8 @@ \section{Thirty years of \LaTeXe{}}
 
 As a consequence of this policy change the last decade saw a larger
 number of enhancements and corrections that were made part of the
-\LaTeX{} kernel. Overall, we can confidentially say that the new
-approach worked well and enabled us to modernize \LaTeX{} and ensure
+\LaTeX{} kernel. Overall, we can confidently say that the new
+approach has worked well and enabled us to modernize \LaTeX{} and ensure
 that it remains relevant without compromising one of the cornerstones
 of \LaTeX{}: its outstanding ability to reprocess old documents
 written many years ago.
@@ -273,11 +273,11 @@ \subsection{Engine support: An important update}
 \subsection{Tagging support for external packages}
 
 At \url{https://latex3.github.io/tagging-project/tagging-status/} we
-show the status of many \LaTeX{} Packages and Classes with respect to
+show the status of many \LaTeX{} packages and classes with respect to
 PDF tagging.  We also started to improve tagging support in external
 packages. If the \texttt{firstaid} key is used in addition to the
-\texttt{phase-III} key basic commands of packages including
-\pkg{amsthm} and \pkg{fancyvrb} can now be used.
+\texttt{phase-III} key basic commands of several packages, including
+\pkg{amsthm} and \pkg{fancyvrb}, can now be used.
 
 
 \subsection{Improved table tagging}
@@ -287,14 +287,14 @@ \subsection{Improved table tagging}
 
 The interface to this functionality is not finalized but can be
 accessed in the current release by specifying the row and columns to
-be treated as headers.
+be treated as headers. For example
 
 \begin{verbatim}
 \tagpdfsetup{
  table/header-rows={1,2},
  table/header-columns={1} }
 \end{verbatim}
-Would specify that in the following tables the first two rows and
+would specify that in the following tables the first two rows and
 first column of each row should be tagged as heading entries.
 
 Similarly you may add a RowSpan attributes to tag a cell that spans
@@ -306,8 +306,8 @@ \subsection{Improved table tagging}
 
 \subsection{Automatic MathML tagging}
 
-When Lua\LaTeX{} is being used and the \pkg{luamml} package is
-available and if the document uses the \pkg{unicode-math} package,
+When Lua\LaTeX{} is being used, and the \pkg{luamml} package is
+available, and if the document uses the \pkg{unicode-math} package,
 then the math module will automatically convert each math formula to
 MathML and use it to attach MathML associated files (or MathML
 Structure elements) to the tagged PDF. This new feature can be
@@ -319,7 +319,7 @@ \subsection{Automatic MathML tagging}
 \subsection{Change behavior of tagging sockets with two arguments}
 
 When calling tagging sockets with two arguments using
-\cs{UseTaggingSocket} when tagging is suspended previous versions of
+\cs{UseTaggingSocket} when tagging is suspended, previous versions of
 \LaTeXe{} dropped both arguments.  This behavior has been changed to
 drop the first argument and preserve the second one instead, thereby
 allowing tagging sockets to be used to wrap existing content which
@@ -328,7 +328,7 @@ \subsection{Change behavior of tagging sockets with two arguments}
 Since no tagging sockets currently provided by \LaTeX{} use two
 arguments we do not expect this change to affect any existing
 documents, but if a custom tagging socket has been defined outside of
-the kernel it might need to be adapted be compatible with the new
+the kernel it might need to be adapted to be compatible with the new
 behavior.
 %
 \githubissue{1500}
@@ -340,7 +340,7 @@ \section{Changes to the \LaTeX{} kernel}
 
 \subsection{Handling paragraph continuation}
 
-Already \LaTeX~2.09 offered some automatism to detect whether or not
+Already \LaTeX~2.09 offered some automation to detect whether or not
 text after a list or some other display environment is meant to be a
 continuation of the current paragraph or should start a new one.  The
 document-level syntax for this is that a blank line after such an
@@ -377,7 +377,7 @@ \subsection{Handling paragraph continuation}
 \subsection{Avoid bogus \enquote{no item} error}
 
 The commands \cs{addvspace} and \cs{addpenalty} generated the famous
-error message \enquote{Something's wrong--perhaps a missing \cs{item}}
+error message \enquote{Something's wrong---perhaps a missing \cs{item}}
 when they were encountered outside vertical mode. Most of the time
 this error was bogus and if not, then it was generated several times
 rather than once.
@@ -397,16 +397,16 @@ \subsection{Switch to T1 as default encoding in documents using \cs{DocumentMeta
 As it is well known, the font encoding \texttt{OT1} supports only 128
 characters and has various problems and quirks notably for languages
 different to English.  Nevertheless \texttt{OT1} is the default
-encoding in \LaTeX{} and this can not be easily changed without
+encoding in \LaTeX{} and this cannot be easily changed without
 affecting many documents as the \texttt{T1} version of the fonts have
 slightly different metrics.
 
 The introduction of the \cs{DocumentMetadata} command, which announces
 \emph{new} code and changes that can also affect the layout gives us
 now the opportunity to make this step. So with this version a use of
 \cs{DocumentMetadata} with (pdf)\LaTeX{} will setup \texttt{T1} as
-default font encoding\footnote{The Unicode engines will continue to
-use \texttt{TU} as encoding.}. To ensure that scalable fonts are used,
+default font encoding.\footnote{The Unicode engines will continue to
+use \texttt{TU} as the encoding.} To ensure that scalable fonts are used,
 the package \pkg{cm-super} has to be installed. Users who want to
 revert to the \texttt{OT1} encoding in their document can do so with
 \verb+\usepackage[OT1]{fontenc}+.
@@ -418,7 +418,7 @@ \section{Code improvements}
 
 \subsection{Avoiding keyval option clashes between classes and packages}
 
-In \LaTeX{} News~35~\cite{40:ltnews35} we introduced keyval option
+In \LaTeX{} News~35~\cite{40:ltnews35} we introduced key--value option
 processing to the kernel. Following the standard for \LaTeXe{}
 options, keyval options given to the \cs{documentclass} line were
 treated as global and so parsed by every package. However, with
@@ -448,7 +448,6 @@ \subsection{Avoiding keyval option clashes between classes and packages}
 %
 \githubissue{1279}
 
-
 \subsection{Improvement to \XeTeX\ \cs{showhyphens}}
 
 When using \cs{showhyphens} with \XeTeX, missing character warnings
@@ -460,13 +459,13 @@ \subsection{Improvement to \XeTeX\ \cs{showhyphens}}
 \subsection{Improved error raised by empty hook}
 
 When using the hook management, both hook and label names (if
-specified) should be non-empty. Before empty hook and empty label both
-raised the same label-specific error.
+specified) should be non-empty. Before, empty hook and empty label names both
+raised the same label-specific error:
 \begin{verbatim}
 ! LaTeX hooks Error: Empty code label on line ....
   Using 'top-level' instead.
 \end{verbatim}
-This has now been improved. Now empty hook raises
+This has now been improved. Now an empty hook raises
 \begin{verbatim}
 ! LaTeX hooks Error: Empty hook on line ....
 \end{verbatim}
@@ -530,7 +529,7 @@ \subsection*{Fix existence check of document environments}
   \NewDocumentEnvironment{ myenv }{}{begin}{end}
 \end{verbatim}
 the first line defines a new environment \env{myenv} but the second
-line would check existence for \env{ myenv } (which is not yet
+line would check existence for \verb*| myenv | (which is not yet
 defined), then redefine \env{myenv} environment without raising any
 errors.  This has now been corrected.
 %
@@ -563,9 +562,9 @@ \subsection{File list entries for rolled back packages/classes}
 
 \subsection{\pkg{doc}:\ \cs{PrintDescribeMacro} in preamble}
 
-In \pkg{doc} version 2 it was possible alter the definition of
+In \pkg{doc} version 2 it was possible to alter the definition of
 \cs{PrintDescribeMacro} and similar commands in preamble. In version 3
-this stopped working because they go reset at the end of the
+this stopped working because they were reset at the end of the
 preamble. This has now been implemented differently and changes in the
 preamble are possible again.
 %
@@ -599,7 +598,7 @@ \subsection{Passing template keys using \cs{KeyValue}}
 functions were reviewed to improve efficiency. However, there
 was an oversight in how
 passing key values from one setting to another was implemented,
-meaning that using \cs{KeyValue} could result in an infinite
+such that using \cs{KeyValue} could result in an infinite
 loop. This has now been fixed.
 %
 \githubissue{1486}
@@ -641,7 +640,7 @@ \subsection{Modification to generation of the \file{.tex} from \pkg{fileerr}}
 \githubissue{1412}
 
 
-\subsection{\pkg{array}: Improve \texttt{>\{...\}} specifier}
+\subsection{\pkg{array}:\ Improve \texttt{>\{...\}} specifier}
 
 If the argument of \texttt{>\{...\}} ended with a command accepting a
 trailing optional argument, e.g., defined for example with
@@ -651,7 +650,7 @@ \subsection{\pkg{array}: Improve \texttt{>\{...\}} specifier}
 \githubissue{1468}
 
 
-\subsection{\pkg{array}: Tagging support for \cs{cline}}
+\subsection{\pkg{array}:\ Tagging support for \cs{cline}}
 
 In the last release we added tagging support for \pkg{array},
 \pkg{longtable} and other tabular packages, but we overlooked that the
@@ -661,15 +660,15 @@ \subsection{\pkg{array}: Tagging support for \cs{cline}}
 algorithm as if another row is added (which is technically what
 happens), thus it was also necessary to decrement the internal row
 counter to get a correct row count. This has now been corrected in
-\pkg{array} which is automatically loaded for tagging, so that all
+\pkg{array}, which is automatically loaded for tagging, so that all
 these packages are now fully compatible with the tagging code if it is
 turned on.
 %
 \taggingissue{134}
 
 
 
-\subsection{\pkg{longtable}: Extend caption type}
+\subsection{\pkg{longtable}:\ Extend caption type}
 
 The \pkg{longtable} package has been extended and now provides the command
 \cs{LTcaptype} (stemming from the \pkg{ltcaption} package) to change
@@ -686,7 +685,7 @@ \subsection{\pkg{longtable}: Extend caption type}
   {\endlongtable}
 \end{verbatim}
 
-\subsection{\pkg{longtable}: Prevent \cs{pagegoal} exceeding maximum value}
+\subsection{\pkg{longtable}:\ Prevent \cs{pagegoal} exceeding maximum value}
 
 An internal guard has been added to avoid \TeX\ errors if
 \verb=\pagegoal= is increased beyond the maximum value for a
@@ -698,7 +697,7 @@ \subsection{\pkg{longtable}: Prevent \cs{pagegoal} exceeding maximum value}
 
 \section{Changes to \pkg{l3build}}
 
-To support third-party developers test their code against pre-release
+To support third-party developers testing their code against pre-release
 \LaTeX{}, a new switch \verb|--dev| has been added to \pkg{l3build}.
 This allows the developer to run
 \begin{verbatim}
@@ -726,7 +725,7 @@ \section{Changes to \pkg{l3build}}
 \newblock Reprinted with corrections in 1996.
 
 \bibitem{40:ltnews} \LaTeX{} Project Team.
-  \emph{\LaTeXe{} news 1--39}. June, 2024.
+  \emph{\LaTeXe{} news 1--39}. June 2024.
   \url{https://latex-project.org/news/latex2e-news/ltnews.pdf}
 
 \bibitem{40:ltnews22} \LaTeX{} Project Team.