[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: dropped resolved comments; added a few new ones; fixed a typo or two (902dd1c1)

[Frank Mittelbach]

Repository : https://github.com/latex3/latex2e
On branch  : ltnew33
Link       : https://github.com/latex3/latex2e/commit/902dd1c14e9644ea089afd21d1c63ab3a3d9f548

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

commit 902dd1c14e9644ea089afd21d1c63ab3a3d9f548
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Mon May 17 16:06:46 2021 +0200

    dropped resolved comments; added a few new ones; fixed a typo or two


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

902dd1c14e9644ea089afd21d1c63ab3a3d9f548
 base/doc/ltnews33.tex | 39 +++++++++++----------------------------
 1 file changed, 11 insertions(+), 28 deletions(-)

diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index 7f0aaaf0..67eb187d 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -41,7 +41,8 @@
 
 
 %%CCC  Do we need a cite for source2e.pdf ?
-
+%%FMi  We can as we have space but the link to the documentation page is fine as
+%%FMi  source2e.pdf is accessible from there
 
 
 %% NOTE:  Chris' preferred hyphens!
@@ -328,10 +329,7 @@ applied to normalize robust commands within the file name.
 Previously, for example, \verb|\input{\sqrt{2}}| would cause
 \LaTeX\ to loop indefinitely whereas with the new normalization
 it looks for the file named \verb|sqrt {2}.tex|
-%%FMi  (and reports a file not found failure instead).
-%%CCC : 
 (and therefore very likely reports ‘file not found’).
-
 %
 \githubissue{481}
 
@@ -358,16 +356,9 @@ characters in its name.  This has been fixed and now
 
 \subsection{Improved copy\,\&\,paste support for \pdfTeX{} documents}
 
-%%CCC Changed to rectify this problem (is it correct now?):
-%%FMi the above sounds as if ``in most cases things work without
-%%glyphtounicode but sometimes you need it ... which is wrong
-%%(sometimes you need cmap but glyphtounicode is now part of the
-%%kernel!
-When compiling with \pdfTeX{}, additional information %%CCC 
-(from the file \texttt{glyphtounicode.tex} 
-is now added
-automatically to the PDF file in order to improve copying from, and
-searching in, text.
+When compiling with \pdfTeX{}, additional information (from the file
+\texttt{glyphtounicode.tex} is now added automatically to the PDF file
+in order to improve copying from, and searching in, text.
 
 This in particular allows the most common ligatures to be copied as
 intended from all generated PDF files without the need to explicitly
@@ -535,9 +526,6 @@ sometimes react to surrounding font changes and could then suddenly
 change shape, for example to \textit{\textbullet}.
 
 This new command \cs{labelitemfont}, which defaults to \cs{normalfont}, 
-%%FMi to typeset
-%%FMi seems wrong (it is only  additionally applied
-%%CCC Added longer explanation, hope it is correct! 
 can be used to provide additional control in the typesetting of
 each label.  Thus by choosing
 different settings other effects can be achieved.  Here are two
@@ -643,7 +631,8 @@ As before, you can
 %%CCC But I thought that these quotes are necessary: 
 %%CCC  without them it was not clear to me that this was a single ‘code snippet’ 
 %%CCC  to be added verbatim to the preamble.
-put \cs{raggedright} \cs{arraybackslash} in the \env{tabular}'s
+%%FMi you can remove the sapce between the two \cs and add \allowbreak?
+put \cs{raggedright}\allowbreak\cs{arraybackslash} in the \env{tabular}'s
 preamble for a column to ensure that \cs{\textbackslash} is always
 interpreted as a tabular row separator when used in that column. And
 you can use \cs{tabularnewline} to explicitly ask for a new table row,
@@ -680,8 +669,6 @@ error message for each missing glyph.
 
 Later, in January 2021, Petr Olšák suggested yet another extension: 
 a new primitive
-%%FMi (avoid hyphenation)
-%%CCC OK.
 \mbox{parameter}
 %
 \cs{tracingstacklevels} that, when both it and \cs{tracingmacros} are
@@ -693,6 +680,7 @@ the current macro nesting level
 within %%FMi in, as part of ?
 the tracing information.
 %%CCC   ???  ENAIL SENT Monday 17th
+%%FMi   ??? leftover? I thought I explained
 
 Both these changes have now been added to \LaTeX's debugging macros
 \cs{tracingall} and \cs{tracingnone}, so that these two new extensions
@@ -782,7 +770,7 @@ documented sources~\cite{33:source2e}.
 
 \subsection{New for \pkg{latexrelease}: \cs{NewModuleRelease}}
 
-To explain the need for this new feature %%CCC
+To explain the need for this new feature
 we shall consider the following example:
 in the 2020-10-01 release, \LaTeX's new hook management system was
 added to the kernel (see \cite{33:ltnews32}) and, as with all changes
@@ -800,7 +788,7 @@ with \cs{newcommand} or (as in the case of \pkg{lthooks})
 
 To solve such issues, we now provide \cs{NewModuleRelease}
 so that completely
-new modules can be defined using the facilities of %%CCC Is this ckearer? 
+new modules can be defined using the facilities of
 \pkg{latexrelease} in such a way that,
 when rolling back or forward, the system will know whether the code of
 the new module has to be read or completely ignored.  More details on
@@ -832,13 +820,8 @@ ends.
 
 A previous release sometimes mistakenly caused a
 (false) warning message 
-%%FMi I think this needs to be kept:
-%%FMi file with an unknown extension.
-%%FMi %%CCC  through a generic graphics rule.  
-%%CCC  Try again: does this make sense now?
-to appear when using a generic graphics rule to fnd and load a graphics
+to appear when using a generic graphics rule to find and load a graphics
 file with an unknown extension.
-%%  a generic graphics rule.
 %
 The warning would incorrectly say that the file was not found, whereas
 the file would in fact be correctly loaded.  The warning now doesn't