[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnews36: as coming back from kb (00b84962)

[Frank Mittelbach]

Repository : https://github.com/latex3/latex2e
On branch  : ltnews36
Link       : https://github.com/latex3/latex2e/commit/00b84962873f2537ffc6d9b68abdea9c72fa6ad8

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

commit 00b84962873f2537ffc6d9b68abdea9c72fa6ad8
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Sun Oct 30 11:18:20 2022 +0100

    as coming back from kb


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

00b84962873f2537ffc6d9b68abdea9c72fa6ad8
 base/doc/ltnews36.tex | 51 +++++++++++++++++++++++++++------------------------
 1 file changed, 27 insertions(+), 24 deletions(-)

diff --git a/base/doc/ltnews36.tex b/base/doc/ltnews36.tex
index 0960e3d2..ea6ef4d5 100644
--- a/base/doc/ltnews36.tex
+++ b/base/doc/ltnews36.tex
@@ -150,8 +150,8 @@ improve one or the other interface.
 The only really important functionality that was added is described in
 the next section: the ability to easily define document-level commands
 and environments that accept a key/value list in one of its (usually
-optional) arguments including the ability to determine if the argument
-does contain such a key/value list or just a single
+optional) arguments, including the ability to determine if the argument
+does in fact contain such a key/value list or just a single
 \enquote{classical} value.
 
 For the \enquote{Tagged \LaTeX{} Project} this functionality is very
@@ -163,7 +163,7 @@ overwrite default tagging if that becomes necessary in a document.
 \section{Auto-detecting key--value arguments}
 
 To allow extension of the core \LaTeX{} syntax, \pkg{ltcmd} now supports
-a \texttt{={...}} modifier when grabbing arguments. This modifier instructs
+a \texttt{={...}}\ modifier when grabbing arguments. This modifier instructs
 \LaTeX{} that the argument should be passed to the underlying code as
 a set of key/values. If the argument does not \enquote{look like} a set
 of key/values, it will be converted into a single key--value pair, with
@@ -186,13 +186,13 @@ only \texttt{=} outside of math mode will generally cause
 interpretation as key/value material.
 
 In case the argument contains a \enquote{textual} \texttt{=} sign that
-is mistaken as key/value indicator you can hide it using a brace
+is mistaken as a key/value indicator you can hide it using a brace
 group as you would do in other places, e.g.,
 \begin{verbatim}
 \caption[{Use of = signs}]
         {Use of = signs in optional arguments}
 \end{verbatim}
-However, because a \texttt{=} sign in math mode are already ignored, this
+However, because \texttt{=} signs in math mode are already ignored, this
 should seldom be necessary.
 
 
@@ -239,27 +239,30 @@ otherwise English input
 \end{verbatim}
 yields
 %\begin{quotation}
-  \MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}.
+%  \MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}.
 %\end{quotation}
+   \IfFormatAtLeastTF{2023/11/01}%
+       {\MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}}%
+       {RAGIP HULÛS\.I ÖZDEM}.
 
 \section{Code improvements}
 
-\subsection{Support for slanted small caps in the EC-fonts }
+\subsection{Support for slanted small caps in the EC fonts}
 For some time \LaTeX{} has supported the combination of the shapes
-small caps and italic/slanted. The EC-fonts contain slanted small caps fonts
+small caps and italic/slanted. The EC fonts contain slanted small caps fonts
 but using them required the loading of an external package. Suitable font definitions
 have now been added to \pkg{t1cmd.fd} and so from now on
 \begin{verbatim}
- \textsc{\textsl{slanted small}}
- \textsc{\textit{italic small caps}}
+ \textsc{\textsl{slanted small caps}};
+ \textsc{\textit{italic small caps}};
  \bfseries
- \textsc{\textsl{bold slanted small caps}}
+ \textsc{\textsl{bold slanted small caps}};
  \textsc{\textit{bold italic small caps}}
 \end{verbatim}
 will give the expected result: {\fontfamily{cmr}
-\textsc{\textsl{slanted small}} \textsc{\textit{italic small caps}}
+\textsc{\textsl{slanted small caps}}; \textsc{\textit{italic small caps}};
 \bfseries
-\textsc{\textsl{bold slanted small caps}} \textsc{\textit{bold italic small caps}}}
+\textsc{\textsl{bold slanted small caps}}; \textsc{\textit{bold italic small caps}}}
 %
 \githubissue{782}
 
@@ -314,7 +317,7 @@ already contains footnotes.
 
 
 \subsection{Robust commands in package options}
-With the standard key-based option handler added at the last release,
+With the standard key-based option handler added in the last release,
 or with contributed packages offering similar features, users may
 expect to be able to use a package option such as
 \verb|[font=\bfseries]|.
@@ -353,14 +356,14 @@ callbacks are not used.
 \githubissue{830}
 
 
-\subsection{Rule based ordering for \LuaTeX\ callback handlers}
+\subsection{Rule-based ordering for \LuaTeX\ callback handlers}
 
 In \hologo{LuaLaTeX} the callback handlers used to be called in the order
 in which they were registered in, but this was often rather fragile.
 It depends a lot on the load order and any attempts to enforce a
-different order required to unregister and reregister the handlers to
-be reordered. Additionally even if some ordering constraints where
-enforced that way another package loaded later could accidentally
+different order required unregistering and reregistering the handlers to
+be reordered. Additionally, even if some ordering constraints where
+enforced that way, another package loaded later could accidentally
 overwrite it.
 
 To improve this, we now order the callback handlers based on ordering
@@ -392,7 +395,7 @@ rules explicitly.
 \subsection{Prevent \TeX{} from losing a \cs{smash}}
 
 When \TeX{} is typesetting a fraction, it will rebox the material in
-either numerator or the denominator depending on which is wider. If
+either the numerator or denominator, depending on which is wider. If
 the repackaged part consists of a single box, that box gets new
 dimensions and if it was built using a \cs{smash} that effect vanishes
 (because a smash is nothing other than zeroing some box dimension,
@@ -440,7 +443,7 @@ approach altogether.
 %
 \githubissue{921}
 
-\subsection{Reporting of unused global issues when using key--value processing}
+\subsection{Reporting of unused global options when using key--value processing}
 
 Using the new key--value option processor did not properly report any unused
 global options when it was used in handling class options. This has now been
@@ -452,15 +455,15 @@ corrected.
 %\section{Changes to packages in the \pkg{amsmath} category}
 
 
-
+\newpage
 \section{Changes to packages in the \pkg{graphics} category}
 
 \subsection{Fix a \cs{mathcolor} bug}
 
 The \cs{mathcolor} command introduced in \cite{36:ltnews35} needs to
-scan for following sub and superscripts, but if it did so at the end
+scan for following sub- and superscripts, but if it did so at the end
 of an alignment cell, e.g., in a \texttt{array} environment, the
-\texttt{\&} was evaluated too early causing some internal errors. This
+\texttt{\&} was evaluated too early, causing some internal errors. This
 is now properly guarded for.
 %
 \githubissue{901}
@@ -473,7 +476,7 @@ is now properly guarded for.
 
 \subsection{\pkg{array}: Correctly identify single-line m-cells}
 
-Cells in m-columns that only contain a single line are supposed to
+Cells in m-columns that contain only a single line are supposed to
 behave like single-line p-cells and align at the same baseline. To
 test for the condition, \pkg{array} used to compare the height of the cell to
 the height of the strut used for the table rows. However, the height of that