[latex3-commits] [git/LaTeX3-latex3-latex2e] ltcmdhooks: fix typos and some clarifications in ltnews33 (9e836c7d)
Frank Mittelbach
frank.mittelbach at latex-project.org
Tue Apr 20 17:28:44 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : ltcmdhooks
Link : https://github.com/latex3/latex2e/commit/9e836c7db87b5e9d6b89de6e08e1f0bb21abde13
>---------------------------------------------------------------
commit 9e836c7db87b5e9d6b89de6e08e1f0bb21abde13
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Tue Apr 20 17:28:44 2021 +0200
fix typos and some clarifications in ltnews33
>---------------------------------------------------------------
9e836c7db87b5e9d6b89de6e08e1f0bb21abde13
base/doc/ltnews33.tex | 42 ++++++++++++++++++++++--------------------
1 file changed, 22 insertions(+), 20 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index b154eda1..b2114a7c 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -89,7 +89,7 @@
\providecommand\tubcommand[1]{}
\tubcommand{\input{tubltmac}}
-\publicationmonth{May}
+\publicationmonth{June}
\publicationyear{2021}
\publicationissue{33}
@@ -144,24 +144,23 @@ full kernel documentation in \file{source2e.pdf}.
Up to now the hook management covered hooks for a few core areas, such
as hooks for the \cs{shipout} process or those in the \env{document}
environment, as well as generic hooks for file loading (helpful for
-patching) and for abitrary environments (executed by \cs{begin} and
+patching) and for arbitrary environments (executed by \cs{begin} and
\cs{end}).
This has now been extended to add \hook{/before} and \hook{/after}
hooks to any (document-level) command---in theory at that is. In
practice the new generic \hook{cmd} hooks, especially the
\hook{cmd/.../after} hooks may fail with commands that are too complex
-to be automatically patched. If that is the case it will be detected
-and an appropriate error is generated. The restrictions are documented
-in \texttt{ltcmdhooks-doc.pdf}.
+to be automatically patched and break them if the hook is filled with
+code. The restrictions are documented in \texttt{ltcmdhooks-doc.pdf}.
However, given that these hooks are mainly meant for package
developers to provide a better interoperability between different
packages and between packages and the \LaTeX{} kernel, these
restrictions are of minor importance: for commands where the mechanism
can't be applied, one is in the same situation as before and for all
-others there will be a noticable improvement. This is especially
-important for our big project providing acessible and tagged PDF
+others there will be a noticeable improvement. This is especially
+important for our big project providing accessible and tagged PDF
output~\cite{33:blueprint}, because for this we will eventually have
to patch many third-party packages and this is only feasible, if it can
be done in controlled and standardized ways.
@@ -177,7 +176,7 @@ The command \cs{labelitemfont} was in fact already introduced with the
\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 at the same time make it easier
-to adjust its layout if necessary. What could happen in the past was the the
+to adjust its layout if necessary. What could happen in the past was the
\env{itemize} labels, e.g., the \textbullet{}, would sometimes react to
surrounding font changes and could suddenly change shape, for example
to \textit{\textbullet}.
@@ -206,7 +205,7 @@ you the buggy old behavior back.
\subsection{A note on file names with spaces, dots or UTF-8 characters}
-In one of the the recent \LaTeX{} releases we improved the interface
+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 on Windows but also elsewhere), UTF-8 characters
outside the \acro{ascii} range as well as names with several dots in
@@ -260,7 +259,7 @@ it always starts out in vertical mode.
\subsection{Allow extra space between name and address in \pkg{letter} class}
-The \cs{opening} command in the the \pkg{letter} class expects the
+The \cs{opening} command in the \pkg{letter} class expects the
name and address to be separated by \verb=\\= but it didn't allow to
use an optional argument at this point to add some extra space after
the name. The coding has now been slightly altered to allow for this.
@@ -306,7 +305,7 @@ slightly different and uses the standard hook management.
\subsection{Delay change of font series and shape to \cs{selectfont} call}
With the NFSS extensions introduced in 2020 the font series and shape
-settings be be influenced by changes to the font family. The setting
+settings can be influenced by changes to the font family. The setting
is therefore delayed until \cs{selectfont} is executed to avoid
unnecessary or incorrect substitutions that may otherwise happen due
to the order of declarations.
@@ -397,7 +396,7 @@ It is sometimes necessary to reference the same footnote several
times, i.e., produce several footnote marks with the same number or
symbol. This is now always possible by placing a \cs{label} into the
\cs{footnote} and reference it with the command \cs{footref}
-elsewhere. This way marks refering to footnotes anywhere on the page
+elsewhere. This way marks referring to footnotes anywhere on the page
(including those in \texttt{minipage}s) can be generated. In the past
this command was only available with certain classes or when loading
the \pkg{footmisc} package.
@@ -406,7 +405,8 @@ the \pkg{footmisc} package.
-\subsection{Providing the raw option list of packages or documentclass to key/value handlers}
+\subsection{Providing the raw option list of packages or documentclass
+ to key/value handlers}
\LaTeXe{} has always normalized space in option lists so\\
\verb|\documentclass[ a4paper , 12pt ]{article}|\\
@@ -415,25 +415,25 @@ processed the intended options \texttt{a4paper} and \texttt{12pt}.
Unfortunately the mechanism used was designed for the simple option
names of the standard option processing. Many classes and packages
now use extended \emph{keyval} processing, however this white space
-normalisation makes this difficult:
+normalization makes this difficult:
\verb|[bb=1 2 3 4]|
which might be expected to pass a bounding box of four numbers is
-normalised to \texttt{bb=1234} and
+normalized to \texttt{bb=1234} and
\verb|[bb={1 2 3 4}]|\\
which might be expected to quote the spaces results in low level \TeX{}
parsing errors.
For compatibility reasons, the standard option processing has not been
-changed however the original un-normalised package and class option lists
+changed however the original un-normalized package and class option lists
are now saved. They are not used in the standard processing, however
extended package option systems may use these \enquote{raw} option list
macros if they are defined.
The one change affecting the standard processing is that the low level
error mentioned above is now avoided as values (any tokens to the
-right of an = sign) are removed from consideration from the \enquote{unused
-option list}. In this release \texttt{clip=true} and
+right of an = sign) are removed from consideration from the
+\enquote{unused option list}. In this release \texttt{clip=true} and
\texttt{clip=false} both contribute \texttt{clip} to the list of
options that have been used.
%
@@ -461,9 +461,11 @@ up.
-\subsection{Provide more ``dashes'' in encodings \texttt{OT1}, \texttt{T1} and \texttt{TU}}
+\subsection{Provide more ``dashes'' in encodings \texttt{OT1},
+ \texttt{T1} and \texttt{TU}}
-When pasting in text from external sources one sometimes encounters the Unicode characters
+When pasting in text from external sources one sometimes encounters
+the Unicode characters
%
\texttt{"2011} (non-breaking hyphen),
\texttt{"2012} (figure dash) and
More information about the latex3-commits
mailing list.