[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: Chris' latest version (c3557bb2)
Chris Rowley
21151379+car222222 at github.github.io
Mon Jan 27 08:51:38 CET 2020
Repository : https://github.com/latex3/latex2e
On branch : develop
Link : https://github.com/latex3/latex2e/commit/c3557bb28b72549445d0ce32de3047b38646b3d1
>---------------------------------------------------------------
commit c3557bb28b72549445d0ce32de3047b38646b3d1
Author: Chris Rowley <21151379+car222222 at users.noreply.github.com>
Date: Mon Jan 27 14:51:38 2020 +0700
Chris' latest version
>---------------------------------------------------------------
c3557bb28b72549445d0ce32de3047b38646b3d1
base/doc/ltnews31.tex | 101 ++++++++++++---------
.../fontloader-l-function 2.lua} | 0
2 files changed, 59 insertions(+), 42 deletions(-)
diff --git a/base/doc/ltnews31.tex b/base/doc/ltnews31.tex
index 55df0767..9caa2e0d 100644
--- a/base/doc/ltnews31.tex
+++ b/base/doc/ltnews31.tex
@@ -141,14 +141,18 @@
As reported in the previous \emph{\LaTeX{} News}, we have made a pre-release
version of the \LaTeX{} kernel available as \LaTeX\texttt{-dev}. Overall, the
approach of having an explicit testing release has been positive: it is now
-readily available in \TeX{} systems and is getting real use beyond the team.
+readily available in \TeX{} systems and is getting real use\\
+beyond the team.
The current
release has been tested by a number of people, and we have had valuable feedback
-on a range of new ideas. This has allowed us to fix issues in several of the
-new features described below. We thank the dedicated users who have been
-trying out the development formats, and encourage others to do so. Pre-testing
-in this way does mean that, for the vast majority of users problems are solved
+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
+in this way does mean that, for the vast majority of users, problems are solved
before they even appear!
@@ -166,7 +170,10 @@ already been added to MiK\TeX{} and \TeX{}~Live 2019 and both have already now c
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{}
-happens depends on the distribution (for \TeX{}~Live this will be with \TeX{}~Live 2020).
+happens
+%% CAR: bad style and difficult to read correctly, cannot think how to fix!
+depends on the distribution you use
+(for \TeX{}~Live this will be with \TeX{}~Live 2020).
@@ -175,7 +182,7 @@ happens depends on the distribution (for \TeX{}~Live this will be with \TeX{}~Li
The \LaTeX3 programming layer, \pkg{expl3}, has over the past decade moved from
being largely experimental to broadly stable. It is now used in a significant
-number of third-party packages, most notably \pkg{xparse} for defining
+number of third-party packages, most notably \pkg{xparse}, for defining
interfaces in cases where no \pkg{expl3} code is \enquote{visible}. In addition, most
\LaTeX{} documents compiled using \XeTeX{} or \LuaTeX{} load \pkg{fontspec},
which is written using \pkg{expl3}.
@@ -197,7 +204,8 @@ 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)]
+% 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)}
@@ -273,7 +281,7 @@ bring this unsatisfactory situation back under control; so today we are
happy to report that the internal font support files for more than a
hundred font families are all back to following the standard NFSS conventions.
Combining them is now again rather nice and easy, and from a technical
-perspective they can now easily matched; but, of course,
+perspective they can now be easily matched; but, of course,
there is still the task of choosing combinations that visually work
well together.
@@ -293,7 +301,7 @@ high-level command for selecting a condensed face, etc. However, using
the NFSS low-level interface it is now possible to ask for, say,
\verb=\fontseries{c}\selectfont= to get a condensed
face (suitable for a marginal note) and that would still allow
-the use \cs{textbf} inside the note, which would
+the use of \cs{textbf} inside the note, which would
select a bold-condensed face (and not a rather odd-looking
bold-extended face in the middle of condensed type).
@@ -302,7 +310,8 @@ class and package designers but, given that the low-level NFSS
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 when it comes to font usage.
+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
@@ -350,7 +359,7 @@ argument then gives the desired series value in NFSS nomenclature.
In previous releases of \LaTeX{}, nested \cs{emph} commands
automatically alternated between italics and upright. This mechanism
-has now been generalized so that you can now specify for arbitrary nesting
+has now been generalised so that you can now specify for arbitrary nesting
levels how emphasis should be handled.
The declaration \cs{DeclareEmphSequence} expects a comma separated
@@ -421,7 +430,8 @@ 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?
\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
@@ -454,24 +464,23 @@ the transcript is suppressed (which is not really recommended).
% 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
\texttt{autoinst} tool by Marc Penninga. In the past, this program
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 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}}.
+These face names were then mapped by substitution to
+to 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}}.
%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
-functionality as the \texttt{subst} function but is less vocal about
-its actions, so that only significant font substitutions show up as
-warnings.
+We now provide a new NFSS size function, \texttt{alias}, that can
+and will be used by \texttt{autoinst} in the future. It provides the
+same functionality as the \texttt{subst} function but is less vocal
+about its actions, so that only significant font substitutions show
+up as warnings.
\subsection{Suppress unnecessary font substitution warnings}
@@ -499,20 +508,24 @@ In 2018 we made UTF-8 the default input encoding for \LaTeX{} but we
overlooked the case of non-\acro{ascii} characters in the short
package descriptions used in declarations, e.g., in the optional argument to
\cs{ProvidesPackage}.
-They worked (sometimes) before, but after the switch to UTF-8 always
-generated an error. This has been corrected.
+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}
-\subsection{Fix inconsistent hook setting when loading packages}
-
-As part of loading a package the command
+%% 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
-in this hook to become undefined again. Now the hook remains defined
-so that additional loading attempts do not change the state of
+in this hook becoming undefined again. Now the hook remains defined
+so that extra loading attempts do not change the state of
\LaTeX{} (relevant only to package developers).
%
\githubissue{198}
@@ -531,9 +544,10 @@ This was corrected.
\subsection{Ensure that \cs{\textbackslash} remains robust}
In the last release we made most document-level commands robust, but
-\cs{\textbackslash} became fragile again whenever
-\cs{raggedright} or similar typesetting was used.
-This has been fixed.
+\cs{\textbackslash} became fragile again\\
+whenever \cs{raggedright} or similar typesetting\\
+%% CAR fixed bad breaks
+was used. This has been fixed.
%
\githubissue{203}
@@ -550,9 +564,11 @@ has been corrected. This also involved a correction to \pkg{amsmath}.
Most \TeX{} engines only support a maximum of sixteen concurrently
open write streams, and when those have been used up, then
-\texttt{filecontents} or any other code trying to open another one
-will fail. In \LuaTeX{} more write streams are available and those can
-also now be utilized.
+\texttt{filecontents} or any other code trying to open one
+will fail.
+In \LuaTeX{} more write streams are available and those can
+also now be utilised.
+%% CAR word removed for better breaks
%
\githubissue{238}
@@ -629,10 +645,11 @@ been incorporated into \XeTeX{} and (u)p-\TeX{}; they were already available in
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 primitive functionality (which in
-\LuaTeX{} may be achieved using Lua code)
-will therefore be \emph{required} by
-the \LaTeX{} kernel from the start of 2021:
+which uses \cs{ifincsname}. The following primitve
+functionality (which in \LuaTeX{} may be achieved using Lua code)
+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}
\begin{multicols}{2}
@@ -674,7 +691,7 @@ For ease of reference, these primitives will be referred to as the
`\pdfTeX{} utilities'. With the exception of \cs{expanded}, these have been
present in \pdfTeX{} since the release of version 1.40.0 in 2007; \cs{expanded}
was added for \TeX{}~Live 2019. Similarly, the full set of these utility primitives
-have been available in \XeTeX{} from the 2019 \TeX{}~Live release, and has
+has 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
2019 and will both have that primitive also from the 2020 release.
diff --git a/texmf/tex/luatex/lualibs/lualibs-function.lua b/texmf/tex/luatex/luaotfload/fontloader-l-function 2.lua
similarity index 100%
copy from texmf/tex/luatex/lualibs/lualibs-function.lua
copy to texmf/tex/luatex/luaotfload/fontloader-l-function 2.lua
More information about the latex3-commits
mailing list.