[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: Comments from Barbara (bd8dba00)

[David Carlisle]

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

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

commit bd8dba009d088d6b85923b2dd8461114dcb944f8
Author: David Carlisle <d.p.carlisle at gmail.com>
Date:   Tue Jan 14 22:09:16 2020 +0000

    Comments from Barbara
    
    not done- p.1, col.1, p.4 contents items -- spacing in "Fix inconsistent ,,,"
        entry rather wide; overly restricted \raggedright (inconsequential)
    
      done - p.1, col.2, l.4 -- "\LaTeX-dev" is partly \tt, partly not.
        Looks awkward, but isn't consequential.  (But seelast line of
        para.3, same column.)
    
     done - p.1, col.2, l.6 -- "readily-available", hyphen not needed (but
        maybe a British convention?)
    
      done- p.1, col.2, para.3, l.7 -- "scripts, which", comma not wanted; it
        makes it sound like "all" scripts are involved, not just those
        affected by XeTeX
    
      done - p.2, col.1, para.3, l.5 -- "(scsl" needs closing paren
    
      done - p.2, col.1, l.-2 -- "such a condensed" ==> "such as ..."
    
      done - p.2, col.2, para.3, l.-1 -- "now easily matched" ==> "now be ..."
    
      done- p.3, col.1, para.2, l.5 -- "bold-extend face" ==> "bold-extended ..."
    
      done - p.3, col.1, l.-4 -- "If there are a more", omit "a"
    
      done (changed to "entry")- p.3, col.2, para.1, l.-2 -- "to use the level", which level?  unclear
    
      done- p.3, col.2, para.2, l.4 -- "Latin based", add hyphen
    
     done (added "with the")  - p.3, col.2, para.3 ll.8-9 -- "doesn't blend in well chosen document
        font". "blend in with ...", "... with the chosen ...", something else?
    
     not done yet - pp.3-4, ll.-1 - 3 -- "declaration reverts ... changes .. pick up ..."
        This is multiple clauses/sentences and needs to be broken up more
        clearly.
    
      done ("if it")- p.4, col.2, ll.2-3 -- "but it was loaded several times", maybe
        "when it ..." or "if it ..."?
    
     done - p.4, col.2, para.6, l.-2 -- "different height" ==> "... heights"
    
      no change (although no significance)- p.5, col.1, l;ast para, l.2 -- single quotes around "pdfTeX
        utilities, is usage single vs. double quotes significant?
    
      done - p.5, col.1, last para, l.-2 -- "bar \ifincsname", correct, but
        perhaps confusing to non-English speakers; maybe "except"
    
    that's it.
    
                                                    -- bb


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

bd8dba009d088d6b85923b2dd8461114dcb944f8
 base/doc/ltnews31.tex | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/base/doc/ltnews31.tex b/base/doc/ltnews31.tex
index c365e527..e0489652 100644
--- a/base/doc/ltnews31.tex
+++ b/base/doc/ltnews31.tex
@@ -137,12 +137,12 @@
 This document is under construction \ldots
 
 
-\section{Experiences with the \LaTeX\texttt{-dev} formats}
+\section{Experiences with the \LaTeX-dev formats}
 
 As reported in the previous \emph{\LaTeX{} News}, we have made a pre-release
-version of the \LaTeX{} kernel available as \LaTeX\texttt{-dev}. Overall, the
+version of the \LaTeX{} kernel available as \LaTeX-dev. Overall, the
 approach of having an explicit testing release has been positive: it is now
-readily-available in \TeX{} systems and is getting real use beyond the team.
+readily available in \TeX{} systems and is getting real use beyond the team.
 
 The current
 release has been tested by a number of users, and we have had useful feedback
@@ -159,7 +159,7 @@ engine, which is Lua\TeX{} with an embedded HarfBuzz library.
 HarfBuzz can be used by setting a suitable renderer in the font
 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
+various scripts which are currently handled correctly only by
 \XeTeX{}.  To simplify the testing of the new engine, binaries have
 been already added to MiK\TeX{} and \TeX{}Live 2019 and both have changed
 the Lua\LaTeX-dev format to use it.
@@ -204,7 +204,7 @@ entirely, but to support older formats, this is still recommended at present.
 
 Over time more and more fonts have become available for use with
 \LaTeX{}. Many such font families offer additional shapes, e.g., small
-caps italics (\texttt{scit}), small caps slanted (\texttt{scsl} or
+caps italics (\texttt{scit}), small caps slanted (\texttt{scsl}) or
 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.
@@ -249,7 +249,7 @@ used in many font support packages.
 
 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
+such as a condensed or extra-condensed. In some cases the number of
 different series values is really impressive, for example, Noto Sans
 offers 36 fonts from ultra-light extra condensed to ultra-bold medium width.
 
@@ -270,7 +270,7 @@ 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
+well together, but from a technical perspective they can now be easily
 matched).
 
 
@@ -312,7 +312,7 @@ developers are documented in \texttt{source2e.pdf}.
 With additional weights and widths available in many font families it
 becomes more likely that somebody wants to match, say, a medium weight
 serif family with a semi-light sans serif family or that with one
-family one wants to use the bold-extend face when \cs{textbf} is used
+family one wants to use the bold-extended face when \cs{textbf} is used
 while with another it should be bold (not extended) or semibold, etc.
 
 In the past this kind of extension was made available with the
@@ -358,7 +358,7 @@ emphasis. For example,
 \end{verbatim}
 uses italics for the first, small capitals for the second, and italic
 small capitals for the third level (provided you use a font that
-supports these shapes).  If there are a more nesting levels than
+supports these shapes).  If there are more nesting levels than
 provided, \LaTeX{} uses the declarations stored in \cs{emreset} (by
 default \cs{ulcshape}\cs{upshape}) for the next level and then
 restarts the list.
@@ -372,7 +372,7 @@ be used for emphasis.
 Of course, this only works if the declarations in the list entries
 actually change the font and not, for example, just the color. In such
 a scenario one has to add \cs{emforce} to the entry which directs the
-mechanism to use the level, even if the font attributes appear to be
+mechanism to use the entry, even if the font attributes appear to be
 unchanged.
 
 
@@ -381,12 +381,12 @@ unchanged.
 
 Given that \pdfTeX{} can only handle fonts with up to 256 glyphs a
 single font encoding can only support a few languages. The \texttt{T1}
-encoding, for example, does support many of the Latin based scripts,
+encoding, for example, does support many of the Latin-based scripts,
 but if you want to write in Greek or Russian you need to switch
 encodings to \texttt{LGR} or \texttt{T2A}. Given that not every font
 family offers glyphs in such encodings, you may end up with some
 default family (e.g., Computer Modern) that doesn’t blend in well
-chosen document font.  For such cases NFSS now offers
+with the chosen document font.  For such cases NFSS now offers
 \cs{DeclareFontFamilySubstitution}, for example:
 \begin{verbatim}
   \DeclareFontFamilySubstitution{LGR}
@@ -495,7 +495,7 @@ written to the \texttt{.log} file.
 
 When a package is loaded
 \texttt{\textbackslash}\textit{package}\texttt{.sty-h@@k} is set, but
-it was loaded several times it was unset again. Relevant only to
+if it was loaded several times it was unset again. Relevant only to
 package developers.
 %
 \githubissue{198}
@@ -555,7 +555,7 @@ protection. All of them have now been made robust.
 The \texttt{multicols} environment was setting \cs{maxdepth} when
 splitting boxes but the way the internal interfaces of \LaTeX{} are
 designed it should have used \cs{@maxdepth} instead. As a result
-balanced boxed multicols sometimes ended up having different height
+balanced boxed multicols sometimes ended up having different heights
 even if they had exactly the same content.
 %
 \githubissue{190}
@@ -644,7 +644,7 @@ these have been present in \pdfTeX{} since the release of version
 2019. Similarly, the full set of utility primitives have been
 available in \XeTeX{} from the 2019 \TeX{}~Live release, and have
 always been available in \LuaTeX{} (some by Lua emulation). p\TeX{}
-and up\TeX{} gained all of the above bar \cs{ifincsname} for
+and up\TeX{} gained all of the above except \cs{ifincsname} for
 \TeX{}~Live 2019, and will have that primitive from the 2020 release.
 
 At the same time, engines which are fully Unicode-capable must all