[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: ltnews31 copy editing (fb6c6a94)

[Will Robertson]

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

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

commit fb6c6a9433366768f8ed128540538d68837bd5c8
Author: Will Robertson <wspr81 at gmail.com>
Date:   Wed Jan 1 22:27:31 2020 +0800

    ltnews31 copy editing


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

fb6c6a9433366768f8ed128540538d68837bd5c8
 base/doc/ltnews31.tex | 47 ++++++++++++++++++++++++-----------------------
 1 file changed, 24 insertions(+), 23 deletions(-)

diff --git a/base/doc/ltnews31.tex b/base/doc/ltnews31.tex
index d5805a5b..93cf6003 100644
--- a/base/doc/ltnews31.tex
+++ b/base/doc/ltnews31.tex
@@ -143,14 +143,14 @@ This document is under construction \ldots
 
 \section{Concerning this pre-release \ldots}
 
-In TeXLive 2020 the Lua\LaTeX{} format will use the new LuaHB\TeX{}
+In \TeX{}Live 2020 the Lua\LaTeX{} format will use the new LuaHB\TeX{}
 engine, which is Lua\TeX{} with an embedded HarfBuzz library.
 HarfBuzz can be used by setting a suitable renderer in the font
-declaration. An interface for that is provided by \pkg{fontspec}.
+declaration. A basic interface for that is provided by \pkg{fontspec}.
 This additional font renderer will greatly improve the shaping of
 various scripts, which are currently handled correctly only by
 \XeTeX{}.  To simplify the testing of the new engine, binaries have
-been already added to MiKTeX and TeXLive 2019 and both have changed
+been already added to MiK\TeX{} and \TeX{}Live 2019 and both have changed
 the Lua\LaTeX-dev format to use it.
 
 
@@ -160,7 +160,7 @@ the Lua\LaTeX-dev format to use it.
 The \LaTeX3 programming layer, \pkg{expl3}, has over the past decade moved from
 being largely experimental to broadly stable. It is now used in a significant
 number of third-party packages, most notably \pkg{xparse} for defining
-interfaces in cases where no \pkg{expl3} code is \enquote{visible}. Most
+interfaces in cases where no \pkg{expl3} code is \enquote{visible}. In addition, most
 \LaTeX{} documents compiled using \XeTeX{} or \LuaTeX{} load \pkg{fontspec},
 which is written using \pkg{expl3}.
 
@@ -198,8 +198,8 @@ swash letters (\texttt{sw}). By using \cs{fontshape} those shapes can
 be explicitly selected and for the swash letter shapes there is also
 \cs{swshape} and \cs{textsw} available.
 
-In the original font selection implementation a request to new shape
-always a canceled the current one. With the 2020 release of \LaTeX{}
+In the original font selection implementation a request to select a new shape
+always overrode the current current. With the 2020 release of \LaTeX{}
 this has changed and \cs{fontshape} can now be used to combine small
 capitals with italics, slanted or swash letters, either by explicitly
 asking for \texttt{scit}, etc., or by asking for italics when typesetting
@@ -213,13 +213,13 @@ with respect to italics, slanted or swash. Finally, if you want to
 reset the shape back to normal you can use \cs{normalshape} which is a
 shorthand for \cs{upshape}\cs{ulcshape}.
 
-The way how shapes combine with each other is not hardwired but is
+The way that shapes combine with each other is not hardwired but is
 customizable and extensible if there is ever a need for it. The
 mappings are defined through \cs{DeclareFontShapeChangeRule} and the
 details for developers are documented in \texttt{source2e.pdf}.
 
 The ideas for this interface extension has been pioneered in
-\pkg{fontspec} by Will Roberson for Unicode engines and in
+\pkg{fontspec} by Will Robertson for Unicode engines and in
 \pkg{fontaxes} by Andreas Bühmann and Michael Ummels for \pdfTeX{} and
 used in many font support packages.
 
@@ -231,7 +231,7 @@ Many of the the newer font families also come provided with additional
 weights (thin, semi-bold, ultra-bold, etc.\@) or several running lengths
 such a condensed or extra-condensed. In some cases the number of
 different series values is really impressive, for example, Noto Sans
-offers 36 from ultra-light extra condensed to ultra-bold medium width.
+offers 36 fonts from ultra-light extra condensed to ultra-bold medium width.
 
 Already in its original design NFSS supported 9 weight levels from
 ultra-light (\texttt{ul}) to ultra-bold (\texttt{ub}) and also 9 width
@@ -246,19 +246,19 @@ using the standard NFSS mechanisms.
 Over the course of the last year a small number of individuals,
 notably, Bob Tennent, Michael Sharpe and Marc Penninga worked hard to
 bring this unsatisfying situation back under control and today we are
-happy to report and the internal font support files for more than a
-hundred font families are back to follow the standard NFSS conventions
-so that combing them is now again rather nice and easy (of course,
+happy to report that the internal font support files for more than a
+hundred font families are back to following the standard NFSS conventions
+so that combining them is now again rather nice and easy (of course,
 there is still the task of choosing combinations that visually work
 well together, but from a technical perspective they can now easily
 matched).
 
 
-In the original font selection implementation a request to series
-always canceled the current one. This was reasonable because there
+In the original font selection implementation, a request to select a new series
+always overode the current one. This was reasonable because there
 were nearly no fonts available that offered anything other than a
 medium or a bold series. Now that this has changed and families such
-as Noto Sans are available, combing weight and width into a single
+as Noto Sans are available, combining weight and width into a single
 attribute is no longer appropriate. With the 2020 release of \LaTeX{}
 the series management therefore changed to allow for independently
 setting the weight and the width attribute of the series.
@@ -273,7 +273,7 @@ face and that would still allow  using \cs{textbf} inside. This then would
 select a bold condensed face and not a rather odd-looking
 bold-extended face in the middle of condensed type.
 
-The expectation is that this is largely used by class and package
+The expectation is that this functionality is largely used by class and package
 designers, but given that the low-level NFSS commands are usable on
 the document level and not really difficult to apply, there are
 probably also a number of users who will enjoy using the new
@@ -301,7 +301,7 @@ support packages.
 
 With the 2020 release of \LaTeX{} this feature is now available out
 of the box.  In addition we also offer a document-level interface to adjust the
-behavior high-level series commands \cs{textbf}, \cs{textmd} and their
+behavior of the high-level series commands \cs{textbf}, \cs{textmd} and their
 declaration forms \cs{bfseries} and \cs{mdseries} so that they can
 have different effects for the serif, sans serif and typewriter
 families used in a document.
@@ -312,8 +312,8 @@ For example, specifying
   \DeclareFontSeriesDefault[tt]{md}{lc}
 \end{verbatim}
 in the document preamble would result in \cs{textbf} producing
-semi-bold (\texttt{sb}) when typesetting in roman typeface and second
-declaration means that typewriter is by default (medium series) using
+semi-bold (\texttt{sb}) when typesetting in roman typeface and
+that typewriter is by default (medium series \texttt{md}) using
 a light-condensed face. The optional argument here can be either
 \texttt{rm}, \texttt{sf} or \texttt{tt} to indicate one of the three
 main font families in a document; if omitted you will change the
@@ -397,7 +397,7 @@ defaults that are sans serif if you typeset in \cs{textsf} and
 monospaced if you typeset using \cs{texttt} and not always serifed.
 
 
-\textsf{This is most noticeably with \cs{oldstylenums} which are now
+\textsf{This is most noticeable with \cs{oldstylenums} which are now
   taken from \texttt{TS1} so that you no longer get
   \textrm{\oldstylenums{123}} but \oldstylenums{123} when typesetting
   in sans serif fonts}\texttt{ and \oldstylenums{123} when using
@@ -453,7 +453,7 @@ written to the \texttt{.log} file.
 \githubissue{172}
 
 
-\subsection{Fix inconsistent setting hook setting when loading packages}
+\subsection{Fix inconsistent hook setting when loading packages}
 
 When a package is loaded
 \texttt{\textbackslash}\textit{package}\texttt{.sty-h@@k} is set, but
@@ -496,7 +496,7 @@ even if they had exactly the same content.
 \githubissue{190}
 
 
-\subsection{Ensure that \texttt{multicols} is not loosing text}
+\subsection{Ensure that \texttt{multicols} is not losing text}
 
 The \texttt{multicols} environment needs a set of consecutive boxes to
 collect column material. The way those got allocated could result in
@@ -507,7 +507,7 @@ allocate boxes below 255, but nowadays the \LaTeX{} allocation routine
 allows allocating boxes below and above 255. So the assumption that
 asking for, say 20 boxes you get a consecutive sequence of box
 registers was no longer true and so some of the column material could
-end in 255 and got overwritten. This has now been corrected by
+end in box 255 and be overwritten. This has now been corrected by
 allocating all necessary boxes above 255 if there aren't enough
 registers available.
 %
@@ -575,6 +575,7 @@ primitives
 \end{itemize}
 In particular, note that \cs{Umathcode} is used as a marker primitive for
 this capability.
+% This sentence is a bit opaque. I assume it means that we use Umathcode when testing if an engine is Umath aware. Maybe something like "Note that it has become standard practice to check for Unicode-aware engines with the existence of the \cs{Umathcode} primitive." would be more clear?