[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: some adjustments by KB (045ba615)
Frank Mittelbach
frank.mittelbach at latex-project.org
Thu Jan 23 19:33:39 CET 2020
Repository : https://github.com/latex3/latex2e
On branch : develop
Link : https://github.com/latex3/latex2e/commit/045ba6152d89588846880e2a0f562e8864864b5a
>---------------------------------------------------------------
commit 045ba6152d89588846880e2a0f562e8864864b5a
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Thu Jan 23 19:33:39 2020 +0100
some adjustments by KB
>---------------------------------------------------------------
045ba6152d89588846880e2a0f562e8864864b5a
base/doc/ltnews31.tex | 50 ++++++++++++++++++++++++--------------------------
1 file changed, 24 insertions(+), 26 deletions(-)
diff --git a/base/doc/ltnews31.tex b/base/doc/ltnews31.tex
index 31ea9d03..a8948db4 100644
--- a/base/doc/ltnews31.tex
+++ b/base/doc/ltnews31.tex
@@ -123,11 +123,10 @@
%\addtolength\textheight{4.2pc} % only for TUB
\maketitle
-\tableofcontents
+{\hyphenpenalty=10000 \spaceskip=3.33pt \tableofcontents}
\setlength\rightskip{0pt plus 3em}
-%\newpage
\medskip
@@ -155,7 +154,7 @@ before they even appear!
\section{Concerning this release \ldots (Lua\LaTeX{} engine)}
-In \TeX{}Live 2020 the Lua\LaTeX{} format will use the new LuaHB\TeX{}
+In \TeX{}~Live 2020 the Lua\LaTeX{} format will use the new LuaHB\TeX{}
engine, which is Lua\TeX{} with an embedded HarfBuzz library.
HarfBuzz can be used by setting a suitable renderer in the font
declaration. A basic interface for that is provided by \pkg{fontspec}.
@@ -163,7 +162,7 @@ This additional font renderer will greatly improve the shaping of
various scripts when using Lua\LaTeX{}, many of which are currently handled correctly only by
\XeTeX{} which is always using HarfBuzz.
To simplify testing of the new engine, binaries have
-already been added to MiK\TeX{} and \TeX{}Live 2019 and both have already now changed
+already been added to MiK\TeX{} and \TeX{}~Live 2019 and both have already now changed
the Lua\LaTeX-dev format to use it.
@@ -194,7 +193,7 @@ eventually, it will be possible to omit
entirely but, to support older formats, this is still recommended at present.
-\section[Improvements to \LaTeX{}'s font selection\\ mechanism (NFSS)]
+\section[Improvements to \LaTeX{}'s font selection mechanism (NFSS)]
{Improvements to \LaTeX{}'s font selection\\ mechanism (NFSS)}
@@ -202,8 +201,7 @@ entirely but, to support older formats, this is still recommended at present.
Over time, more and more fonts have become available for use with
\LaTeX{}. Many such font families offer additional shapes such as small
-caps italic
-(\texttt{scit}), small caps slanted (\texttt{scsl}) or
+caps italic (\texttt{scit}), small caps slanted (\texttt{scsl}) or
swash (\texttt{sw}).
By using \cs{fontshape} those shapes can
be explicitly selected. For the swash shapes there is also
@@ -249,7 +247,7 @@ they are by now used in many font support packages.
\subsection{Extending the font series management in NFSS}
Many of the the newer font families also come provided with additional
-weights (thin, semi-bold, ultra-bold, etc.\@) or several running widths,
+weights (thin, semi-bold, ultra-bold, etc.)\ or several running widths,
such as condensed or extra-condensed. In some cases the number of
different values for series (weight plus width) is really impressive:
for example, Noto Sans
@@ -310,11 +308,12 @@ developers are documented in \texttt{source2e.pdf}.
\subsection{Font series defaults per document family}
-With additional weights and widths available now being available in many font families, it
-is more likely that somebody will want to match, say, a medium weight
-serif family with a semi-light sans serif family, or that with one
-family one wants to use the bold-extended face when \cs{textbf} is used,
-while with another it should be bold (not extended) or semibold, etc.
+With additional weights and widths available now being available in
+many font families, it is more likely that somebody will want to
+match, say, a medium weight serif family with a semi-light sans serif
+family, or that with one family one wants to use the bold-extended
+face when \cs{textbf} is used, while with another it should be bold
+(not extended) or semibold, etc.
In the past this kind of extension was provided by Bob Tennent's
\pkg{mweights} package, which has been used in many font
@@ -449,7 +448,7 @@ the transcript is suppressed (which is not really recommended).
\subsection{New \texttt{alias} size function for use in \texttt{.fd} files}
-% these are really called ``size functions'' in NFSS, a bit weird
+% these are really called ``size functions'' in NFSS, a bit weird I know
Most of the newer fonts supported in \TeX{} have been set up with the
@@ -462,7 +461,7 @@ then mapped by substitution to the standard NFSS series
got unnecessary substitution warnings such as \enquote{\texttt{Font
T1/abc/bold/n not found, using T1/abc/b/n instead}}.
-%FMi the message above is actually different
+%FMi the message above is actually different and longer but ...
We now provide a new NFSS \texttt{alias} size function that can and will be
used by \texttt{autoinst} in the future. It provides the same
@@ -508,7 +507,7 @@ As part of loading a package the command
\texttt{\textbackslash}\textit{package}\texttt{.sty-h@@k} gets
defined. However, attempting to load a package a second time resulted
in this hook to become undefined again. Now the hook remains defined
-and one or several loading attempts do not change the state of
+so that additional loading attempts do not change the state of
\LaTeX{} (relevant only to package developers).
%
\githubissue{198}
@@ -517,7 +516,7 @@ and one or several loading attempts do not change the state of
\subsection{Avoid spurious warning if \texttt{LY1} is made the default encoding}
Making \texttt{LY1} the default encoding, as is done by some font support
-packages, gave a spurious warning even if \cs{rmdefault} had first been changed.
+packages, gave a spurious warning even if \cs{rmdefault} was changed first.
This was corrected.
%
\githubissue{199}
@@ -643,6 +642,10 @@ the \LaTeX{} kernel from the start of 2021:
\item \cs{pdffilesize}
\item \cs{pdflastxpos}
\item \cs{pdflastypos}
+ \item \cs{pdfmdfivesum}
+ \item \cs{pdfnormaldeviate}
+ \item \cs{pdfpageheight}
+ \item \cs{pdfpagewidth}
\end{itemize}
\end{multicols}
%
@@ -651,10 +654,6 @@ the \LaTeX{} kernel from the start of 2021:
%
\begin{multicols}{2}
\begin{itemize}
- \item \cs{pdfmdfivesum}
- \item \cs{pdfnormaldeviate}
- \item \cs{pdfpageheight}
- \item \cs{pdfpagewidth}
\item \cs{pdfprimitive}
\item \cs{pdfrandomseed}
\item \cs{pdfresettimer}
@@ -673,7 +672,6 @@ was added for \TeX{}~Live 2019. Similarly, the full set of these utility primiti
have been available in \XeTeX{} from the 2019 \TeX{}~Live release, and has
always been available in \LuaTeX{} (some by Lua emulation). Whilst p\TeX{} and
up\TeX{} gained all of the above (except \cs{ifincsname}) for \TeX{}~Live
-% bnb changed from 'bar'
2019 and will both have that primitive also from the 2020 release.
At the same time, engines which are fully Unicode-capable must provide
@@ -693,11 +691,11 @@ Note that it has become standard practice to check for Unicode-aware engines
by using the existence of the \cs{Umathcode} primitive. As such, this is already
a requirement: engines lacking these primitives cannot access the Unicode features
of the \LaTeXe{} kernel or of \pkg{expl3}. Note that up\TeX{} has facilities for
-handling Unicode but it is not classed as a Unicode engine by the base LaTeX code.
+handling Unicode but it is not classed as a Unicode engine by the base \LaTeX\ code.
\begin{thebibliography}{9}
-%\fontsize{9.3}{11.3}\selectfont
+\fontsize{9.3}{11.3}\selectfont
\bibitem{31:devformat} Frank Mittelbach:
\emph{The
@@ -707,11 +705,11 @@ handling Unicode but it is not classed as a Unicode engine by the base LaTeX cod
\bibitem{31:fntguide} \LaTeX{} Project Team:
\emph{\LaTeXe{} font selection}.\\
- \url{https://latex-project.org/documentation/}
+ \url{https://latex-project.org/help/documentation/fntguide.pdf}
\bibitem{31:site-doc}
\emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
- \url{https://latex-project.org/documentation/}
+ \url{https://latex-project.org/help/documentation/}
\end{thebibliography}
More information about the latex3-commits
mailing list