[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: dropped a few double words rewrote/split the para on luahbtex added a warning that this document needs 2020-02-02 for processing (357d256f)
Frank Mittelbach
frank.mittelbach at latex-project.org
Mon Jan 27 12:22:30 CET 2020
Repository : https://github.com/latex3/latex2e
On branch : develop
Link : https://github.com/latex3/latex2e/commit/357d256f770918bf0be21455e3e39598364b6314
>---------------------------------------------------------------
commit 357d256f770918bf0be21455e3e39598364b6314
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Mon Jan 27 12:22:30 2020 +0100
dropped a few double words
rewrote/split the para on luahbtex
added a warning that this document needs 2020-02-02 for processing
>---------------------------------------------------------------
357d256f770918bf0be21455e3e39598364b6314
base/doc/ltnews31.tex | 34 ++++++++++++++++++----------------
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/base/doc/ltnews31.tex b/base/doc/ltnews31.tex
index 9caa2e0d..95a6cddf 100644
--- a/base/doc/ltnews31.tex
+++ b/base/doc/ltnews31.tex
@@ -30,6 +30,8 @@
%
% This is issue 31 of LaTeX News.
+\NeedsTeXFormat{LaTeX2e}[2020-02-02]
+
\documentclass{ltnews}
\usepackage[T1]{fontenc}
@@ -148,7 +150,7 @@ The current
release has been tested by a number of people, and we have had valuable feedback
on a range of the new ideas. This has allowed us to fix issues in several of the
new features, as described below.
-%% CAR: new para and extra words for better breaks.
+
We wish to thank all the dedicated users who have been
trying out the development formats, and we encourage others to do so. Pre-testing
@@ -166,10 +168,11 @@ various scripts when using Lua\LaTeX{}, many of which are currently handled corr
\XeTeX{}, which always uses 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 distributions have already now changed
the Lua\LaTeX-dev format to use it.
+
Going forward, Lua\LaTeX\ (and Lua\LaTeX-dev) will both use the LuaHB\TeX{}
-engine. When the switch to the the LuaHB\TeX{} engine for Lua\LaTeX{}
+engine. When the switch to the LuaHB\TeX{} engine for the Lua\LaTeX{} format
happens
%% CAR: bad style and difficult to read correctly, cannot think how to fix!
depends on the distribution you use
@@ -204,7 +207,6 @@ eventually, it will be possible to omit
entirely but, to support older formats, this is still recommended at present.
-% CAR changed TOC to save a line:-). Could change both entries.
\section[Improvements to \LaTeX{} font selection: NFSS]
{Improvements to \LaTeX{}'s font selection\\ mechanism (NFSS)}
@@ -311,7 +313,6 @@ commands are usable on the document level and that they are not really
difficult to apply, there are probably also a number of users who will
enjoy using these new possibilities that bring \LaTeX{} back into the
premier league for font usage.
-%% CAR saved a line and a bad break.
The ways in which the different series values combine with each other is not
hardwired but is again customizable and extensible. The mappings are
@@ -430,8 +431,12 @@ substituted with default glyphs that are sans serif if you typeset in
past they were always taken from Computer Modern Roman if substitution
was necessary.
-%% CAR comment. This does not work without the new stuff. But should it?
-%% Or add an explanation of this?
+
+\typeout{^^J^^J***************************************}
+\typeout{** This example needs LaTeX 2020-02-02}
+\typeout{** to come out correctly !!}
+\typeout{***************************************^^J^^J}
+
\textsf{This is most noticeable with \cs{oldstylenums} which are now
taken from \texttt{TS1} so that you no longer get
\textrm{\oldstylenums{1234}} but \oldstylenums{1234} when typesetting
@@ -469,7 +474,7 @@ Most of the newer fonts supported in \TeX{} have been set up with the
set up each font using the face name chosen by that font's designer,
e.g., \enquote{\texttt{regular}}, \enquote{\texttt{bold}}, etc.
These face names were then mapped by substitution to
-to the standard NFSS series names, i.e., \enquote{\texttt{m}}
+the standard NFSS series names, i.e., \enquote{\texttt{m}}
or \enquote{\texttt{b}}.
As a result one got unnecessary substitution warnings such as
\enquote{\texttt{Font T1/abc/bold/n not found, using T1/abc/b/n instead}}.
@@ -511,16 +516,13 @@ package descriptions used in declarations, e.g., in the optional argument to
They worked (sometimes) before, but the switch to UTF-8 made them always
generate an error.\\
This has been corrected.
-%% CAR rewording, better break also.
%
\githubissue{52}
-%% CAR attempt to improve TOC.
\subsection[Fix inconsistent hook setting when\\ loading packages]%
{Fix inconsistent hook setting when loading packages}
-%% CAR: commas and corrected wording.
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
@@ -647,8 +649,8 @@ A number of these additional primitives are needed to support new or improved
functionality in \LaTeX{}. This is seen for example in the improved UTF-8 handling,
which uses \cs{ifincsname}. The following primitve
functionality (which in \LuaTeX{} may be achieved using Lua code)
+\pagebreak
will therefore be \emph{required} by the \LaTeX{} kernel and core\\
-%% CAR: some extra words to get better break
packages from the start of 2021:
%
\begingroup\setlength\columnsep{0pt}
@@ -668,14 +670,14 @@ packages from the start of 2021:
\item \cs{pdfnormaldeviate}
\item \cs{pdfpageheight}
\item \cs{pdfpagewidth}
-\end{itemize}
-\end{multicols}
+%\end{itemize}
+%\end{multicols}
%
% very manual! multicol needs update to detect that it is used
% inside twocolumn!
%
-\begin{multicols}{2}
-\begin{itemize}
+%\begin{multicols}{2}
+%\begin{itemize}
\item \cs{pdfprimitive}
\item \cs{pdfrandomseed}
\item \cs{pdfresettimer}
More information about the latex3-commits
mailing list.