[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: Minor adjustments (9cab8168)

[Frank Mittelbach]

Repository : https://github.com/latex3/latex2e
On branch  : ltnew33
Link       : https://github.com/latex3/latex2e/commit/9cab81680b99953113a5e0b3d062be0185a16099

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

commit 9cab81680b99953113a5e0b3d062be0185a16099
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Fri May 28 12:00:55 2021 +0200

    Minor adjustments


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

9cab81680b99953113a5e0b3d062be0185a16099
 base/doc/ltnews33.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index 7a0ae57c..d57b8932 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -1,4 +1,4 @@
- % \iffalse meta-comment
+% \iffalse meta-comment
 %
 % Copyright 2019-2021
 % The LaTeX Project and any individual authors listed elsewhere
@@ -243,12 +243,12 @@ insertion of \enquote{color commands}) to these elements at shipout.
 In one of the recent \LaTeX{} releases we improved the interface
 for specifying file names so that they can now safely contain spaces
 (as is common these days),
-more than one dot character, and also UTF-8 characters
+more than one dot character, and also \acro{utf-8} characters
 outside the \acro{ascii} range. 
 In the past this was only possible by applying a special syntax
 in the case of spaces, 
 while file names with several dots often failed, 
-as did most UTF-8 characters.
+as did most \acro{utf-8} characters.
 
 
 \subsubsection{Consequences for file names in \cs{include}}
@@ -570,7 +570,7 @@ Sans, so that you get
 \def\myfont#1{{\let\labelitemfont\empty\fontfamily{lmss}\selectfont#1}}%
 %
 \myfont\labelitemi, \myfont\labelitemii, \myfont\labelitemiii\ and
-\myfont\labelitemiv\,; while the second variant freezes the font family
+\!\!\myfont\labelitemiv\,; while the second variant freezes the font family
 and shape, but leaves the series as a variable quantity, so that an
 \env{itemize} in a bold context would show bolder symbols. Making
 \cs{labelitemfont} empty would give you back the buggy old behavior.
@@ -617,7 +617,7 @@ This change also fixed one anomaly present in the past:
 in a tabular preamble of the form
 \finalvspace*{-.3\baselineskip}
 \begin{quote}
-  \hspace*{-.75em}\verb={l=\texttt{\string>}\verb={raggedright}p{10cm}r}=           % stupid class
+  \hspace*{-.15em}\verb={l=\texttt{\string>}\verb={raggedright}p{10cm}r}=    % stupid class
 \end{quote}
 \finalvspace*{-.3\baselineskip}
 a \cs{\textbackslash} in the second column would have the definition
@@ -881,7 +881,7 @@ affect page breaking in existing documents, a rollback to
 \pkg{longtable 4.13} (\file{longtable-2020-01-07.sty}) is supported.
 %
 \gnatsissue{tools}{2914 3396 3512}
-\githubissue{133 183 464 561}
+\githubissue{133 137 183 464 561}
 
 
 \subsection{\pkg{trace}: Additions to \cs{traceon}}