[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: further edits to keep more text while staying at 6 pages (b04e7464)
Frank Mittelbach
frank.mittelbach at latex-project.org
Mon May 24 19:23:54 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : ltnew33
Link : https://github.com/latex3/latex2e/commit/b04e7464a63871435e2d3e32b75c5a96ed5678ab
>---------------------------------------------------------------
commit b04e7464a63871435e2d3e32b75c5a96ed5678ab
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Mon May 24 19:23:54 2021 +0200
further edits to keep more text while staying at 6 pages
>---------------------------------------------------------------
b04e7464a63871435e2d3e32b75c5a96ed5678ab
base/doc/ltnews33.tex | 87 +++++++++++++++++++++++++++++++--------------------
1 file changed, 53 insertions(+), 34 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index 04532f24..43e9bf38 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -1,5 +1,5 @@
%% Temporary: quick draft identification --
-%% This is Draft 3o.
+%% This is Draft 3p.
% \iffalse meta-comment
%
% Copyright 2019-2021
@@ -107,6 +107,7 @@
\newcommand\colonize[1]{#1:}
\makeatother
+\let\finalvspace\vspace % for document layout fixes
@@ -115,7 +116,7 @@
\tubcommand{\input{tubltmac}}
\publicationmonth{June}
-\publicationyear{2021 --- Draft Version 3o}
+\publicationyear{2021 --- Draft Version 3p}
\publicationissue{33}
@@ -236,35 +237,8 @@ insertion of \enquote{color commands}) to these elements at shipout.
-\section{Updates to the font selection scheme}
-
-
-\subsection{A new hook in \cs{selectfont}}
-
-After \cs{selectfont} has changed the font, we now run a hook (\hook{selectfont})
-so that packages can make final \mbox{adjustments}. This functionality was
-originally provided by the \pkg{everysel} package but our
-implementation is slightly different and uses the standard hook
-management.
-%
-\githubissue{444}
-
-
-\subsection{Change of font series/shape delayed until \cs{selectfont}}
-
-With the NFSS extensions introduced in 2020, the font series and shape
-settings can be influenced by changes to the font family. The
-settings of these two are now therefore delayed until \cs{selectfont}
-is executed; this avoids unnecessary or incorrect substitutions that
-may otherwise happen due to the order of declarations.
-%
-\githubissue{444}
-
-
\section{Improved handling of file names}
-
-
\subsection[File names with spaces, multiple dots or\\
\acro{utf-8} characters]
{File names with spaces, multiple dots or \acro{utf-8} characters}
@@ -352,6 +326,32 @@ characters in its name. This has been fixed and now
+\section{Updates to the font selection scheme}
+
+
+\subsection{A new hook in \cs{selectfont}}
+
+After \cs{selectfont} has changed the font, we now run a hook (\hook{selectfont})
+so that packages can make final \mbox{adjustments}. This functionality was
+originally provided by the \pkg{everysel} package but our
+implementation is slightly different and uses the standard hook
+management.
+%
+\githubissue{444}
+
+
+\subsection{Change of font series/shape delayed until \cs{selectfont}}
+
+With the NFSS extensions introduced in 2020, the font series and shape
+settings can be influenced by changes to the font family. The
+settings of these two are now therefore delayed until \cs{selectfont}
+is executed; this avoids unnecessary or incorrect substitutions that
+may otherwise happen due to the order of declarations.
+%
+\githubissue{444}
+
+
+
\section{Glyphs, characters \& encodings}
\subsection{Improved copy\,\&\,paste for \pdfTeX{} documents}
@@ -457,7 +457,8 @@ to load this package in order to access glyphs such as
%%FMi if this block is dropped we are back to 6 pages
%%FMi it reads nice, but as I said it is not correct really as that was always the case only less granular
- \iffalse
+ \iftrue %%FMi keep this (if if a bit incorrect)
+
At this time the opprtunity was also taken to bring some order to the
chaos surrounding the question: \enquote{which glyphs from
the \texttt{TS1} encoding are available in a given font?}.
@@ -468,6 +469,8 @@ 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 when it in fact is.
+\fi
+\iffalse %%FMi but drop that
%%CCC Plus info:
%%FMi who is the ``we'' in this note? I'm not prepared to write that full explanation beyond what is there in lttextcomp
@@ -523,7 +526,8 @@ the approach very soon now.
%%FMi so I think your title focusses on the wrong topic
%%FMi (and which is why I didn't make any such split)
-\subsubsection[A note on the history of `text symbols']%
+\subsubsection
+ [A note on the history of `text symbols']%
{A note on the history of `text symbols' and
the \texttt{TS1} encoding}
@@ -549,13 +553,22 @@ 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.
+\iffalse %% FMi that got moved to the top, therefore also change next para
+
A couple of releases back the functionality of the \pkg{textcomp}
package got integrated into the core code of the \LaTeX{} kernel so
that its glyph definitions, e.g., \cs{textcopyright}, \cs{texteuro} or
\cs{textyen}, are now automatically available without the need to load
an additional package in the preamble.
-At the time this happened many new free fonts had appeared and
+\fi
+
+When we recently integrated the functionality of the \pkg{textcomp}
+into the \LaTeX{} kernel
+%
+%At the time this happened
+%
+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
@@ -569,7 +582,7 @@ 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 %%FMi fact.
+that the glyph is unavailable in that
font.
The mapping would ensure
that \LaTeX{} always errs on the side of caution, because it might
@@ -683,20 +696,26 @@ should now be robust in all circumstances.
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
\end{quote}
+\finalvspace*{-.3\baselineskip}
a \cs{\textbackslash} in the second column would have the definition
used within \cs{raggedright} and so it would not indicate the
-(premature) end of the \env{tabular}. Thus, for example,
+(premature) end of the \env{tabular}. Thus, for example,%
+\finalvspace*{-.3\baselineskip}
\begin{quote}
\verb=a & b1 \\ b2 & c \\=
\end{quote}
+\finalvspace*{-.3\baselineskip}
was interpreted as a single row of the \env{tabular} (as intended),
whereas
+\finalvspace*{-.3\baselineskip}
\begin{quote}
\verb=a & \\ b2 & c \\=
\end{quote}
+\finalvspace*{-.3\baselineskip}
resulted in two rows! This happened because the \cs{\textbackslash}
directly following the \verb=&= got interpreted while it still had the
\enquote{end the row} meaning and not yet the \enquote{start a new
More information about the latex3-commits
mailing list.