Repository : https://github.com/latex3/latex2e
On branch : ltnew33
Link : https://github.com/latex3/latex2e/commit/95611e942036a8922502f0a62c554501b4af8bbe
>---------------------------------------------------------------
commit 95611e942036a8922502f0a62c554501b4af8bbe
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Fri May 28 11:20:26 2021 +0200
mods by kb and bb
>---------------------------------------------------------------
95611e942036a8922502f0a62c554501b4af8bbe
base/doc/ltnews33.tex | 50 +++++++++++++++++++++++++-------------------------
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index e13904ce..7a0ae57c 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
@@ -35,7 +35,7 @@
\documentclass{ltnews}
%%CCC Temporary definitions:
-\providecommand\Dash {---}
+\providecommand\Dash {\unskip ---}
@@ -247,7 +247,7 @@ more than one dot character, and also 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,
-whilst file names with several dots often failed,
+while file names with several dots often failed,
as did most UTF-8 characters.
@@ -262,10 +262,10 @@ exist) and also when you manually try to implement the rule.
\LaTeX{} therefore had one special syntax for \cs{include} and
\cs{includeonly}: they always expected that
-their arguments contains a
-file name\footnote{In case of \cs{includeonly} a comma separated list of such names.}
+their arguments contain a
+file name\footnote{In the case of \cs{includeonly}, a comma-separated list of such names.}
with no extension given,
- so that it had to be\texttt{.tex}. Thus,
+ so that it had to be \texttt{.tex}. Thus,
when you mistakenly wrote
\verb=\include{mychap.tex}= (for example,
because you changed from \cs{input}
@@ -303,7 +303,7 @@ 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|
-(and therefore very likely reports `file not found').
+(and therefore very likely reports ``file not found'').
%
\githubissue{481}
@@ -358,7 +358,7 @@ When compiling with \pdfTeX{}, additional information
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
+In particular, this allows the most common ligatures to be copied as
intended from all generated PDF files without the need to explicitly
load the package \pkg{cmap}.
%
@@ -404,7 +404,7 @@ in addition to the more common
In the past, these first three produced an error message when used
with \pdfTeX{} (since they are not available in \texttt{OT1} or
\texttt{T1} encoded fonts). They now typeset an approximation to the
-glyph: e.g., the `figure dash' is approximated by an en-dash.
+glyph: e.g., the ``figure dash'' is approximated by an en-dash.
With Unicode engines they either work (when the glyph is contained in
the selected Unicode font) or they typeset nothing, producing a
@@ -447,8 +447,8 @@ chaos surrounding the question: \enquote{which glyphs from the
\texttt{TS1} encoding are available in a given font?}. This was
done using an approach based on font families and collections, with
the differing glyph coverage of the \enquote*{text symbols} being
-indicated by assigning to a font family or collection a 'sub-encoding
-number' that indicates which glyphs from the \texttt{TS1} encoding are
+indicated by assigning to a font family or collection a ``sub-encoding
+number'' that indicates which glyphs from the \texttt{TS1} encoding are
guaranteed to be available when using a font from that family or
collection. This assignment ensures that \LaTeX{} always errs on the
side of caution, possibly claiming that a glyph is not available even
@@ -465,8 +465,8 @@ the approach very soon now.
\subsubsection
- [A note on the history of `text symbols']
- {A note on the history of `text symbols' and
+ [A note on the history of ``text symbols'']
+ {A note on the history of ``text symbols'' and
the \texttt{TS1} encoding}
@@ -484,8 +484,8 @@ existing fonts (at the time) and later new fonts that got developed
were unable to provide the full set of glyphs that made up the
\texttt{TS1} encoding. For existing free PostScript fonts people
took the extra effort and produced virtual fonts that faked (some) of
-the missing glyphs. But this was and is a time consuming effort so it
-was done only for a few basic fonts. But even then, only some fonts
+the missing glyphs. But this was and is a time-consuming effort so it
+was done for only a few basic fonts. But even then, only some fonts
included all glyphs from \texttt{TS1} so the \pkg{textcomp} already
back then contained a long list, dividing fonts into 5 categories
according to which glyphs were implemented and which were missing.
@@ -496,19 +496,19 @@ into the \LaTeX{} kernel
many new free fonts had appeared and
unfortunately the chaos around the question \enquote{which glyphs of
the \texttt{TS1} encoding are implemented by which font} had
-increased with it. Not only did one find many new holes it was next to
+increased with it. Not only did one find many new holes, it was next to
impossible to order the set of fonts into a reasonable set of
sub-encodings that are contained in each other in a single sequence.
In the end we decided on nine or ten sub-encodings with a reasonable
-number of fonts in each so that all font implemented all glyphs of the
+number of fonts in each so that all fonts implemented all glyphs of the
sub-encoding they got mapped to. Thus when typesetting with a font one
could be sure that a command like \cs{textcopyleft} would either
typeset the requested character (if the glyph was part of the
sub-encoding the font belonged to) or it would raise an error, saying
that the glyph is unavailable in that font. The mapping would ensure
that \LaTeX{} always errs on the side of caution, because it might
-claim a glyph is unavailable even though in fact it is.
+claim a glyph is unavailable even though in fact it is.\looseness-1
For example, the old \texttt{pcr} (PostScript Courier) font (as well
as most other older PS fonts) is mapped to sub-encoding 5 and
@@ -545,7 +545,7 @@ much more complete glyph set).
\subsection{Adjusting \env{itemize} labels with \cs{labelitemfont}}
The command \cs{labelitemfont} was introduced already with the
-\LaTeX\ release 2020-02-02, but back then we forgot to describe it so
+\LaTeX\ release 2020-02-02, but back then we forgot to describe it, so
we do this now. Its purpose is to resolve some bad formatting issues
with the \env{itemize} environment and also to make it easier to
adjust the layout when necessary. What could happen in the past was
@@ -567,7 +567,7 @@ examples:
The first definition will take the symbols from the font Latin Modern
Sans, so that you get
%
-\def\myfont#1{{\let\labelitemfont\empty\fontfamily{lmss}\selectfont#1}}
+\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
@@ -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}
- \verb={l=\texttt{\string>}\verb={raggedright}p{10cm}r}= % stupid class
+ \hspace*{-.75em}\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
@@ -819,7 +819,7 @@ Whereas the \pkg{latexrelease} package can usually emulate an older
management of the \cs{ExplSyntaxOn/Off} status for packages (after an
\pkg{expl3}-based package is loaded) cannot be removed by the rollback
without messing up the catcodes. This has been fixed so that rollback
-is now more careful not to leave \pkg{ExplSyntaxOn} after a package
+is now more careful not to leave \cs{ExplSyntaxOn} after a package
ends.
%
\githubissue{504}
@@ -867,7 +867,7 @@ language options.
\subsection{\pkg{array} and \pkg{longtable}: Make \cs{\textbackslash} generally robust}
-The fix for this issue was also applied to these packages, see above.
+The fix for this issue was also applied to these packages; see above.
%
\githubissue{548}
@@ -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 137 183 464 561}
+\githubissue{133 183 464 561}
\subsection{\pkg{trace}: Additions to \cs{traceon}}
@@ -910,7 +910,7 @@ In addition, package options for guiding the use of \enquote{poor
\section{Changes to packages in the \pkg{amsmath} category}
-The fix for issue 548 was also applied in \pkg{amsmath}, see above.
+The fix for issue 548 was also applied in \pkg{amsmath}; see above.
%
\githubissue{548}