[latex3-commits] [git/LaTeX3-latex3-latex2e] copyedits-chris: draft for intro; some reordering and one clarification (f70d7ef5)
Frank Mittelbach
frank.mittelbach at latex-project.org
Mon Oct 25 13:03:50 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : copyedits-chris
Link : https://github.com/latex3/latex2e/commit/f70d7ef51f9197ca8eb9a1577d74c3fc477f0cee
>---------------------------------------------------------------
commit f70d7ef51f9197ca8eb9a1577d74c3fc477f0cee
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Mon Oct 25 13:03:50 2021 +0200
draft for intro; some reordering and one clarification
>---------------------------------------------------------------
f70d7ef51f9197ca8eb9a1577d74c3fc477f0cee
base/doc/ltnews34.tex | 172 ++++++++++++++++++++++++++------------------------
1 file changed, 88 insertions(+), 84 deletions(-)
diff --git a/base/doc/ltnews34.tex b/base/doc/ltnews34.tex
index c72c0bd8..d3cddc59 100644
--- a/base/doc/ltnews34.tex
+++ b/base/doc/ltnews34.tex
@@ -117,8 +117,7 @@
\tubcommand{\input{tubltmac}}
\publicationmonth{November}
-\publicationyear{2021 \Dash Third Draft Version,
- not quite complete, eg needs Intro?)} %% CCC
+\publicationyear{2021}
\publicationissue{34}
@@ -137,14 +136,12 @@
\section{Introduction}
-\emph{TO BE COMPOSED, PROBABLY}
-
-%%
-% \subsection{???}
-%
-% \emph{write} ??
-%%
+This release of \LaTeX{} does not contain any major new modules, but
+is focused around consolidation and improvements of functionality
+introduced in previous releases. In addition various smaller
+enhancements and bug fixes have been added to the kernel and the core
+packages.
\section{Hook business}
@@ -361,6 +358,88 @@ been fixed so that patching now works for those commands as well.
\section{New or improved commands}
+%FMi reorder subsections by importance
+
+\subsection{\cs{NewCommandCopy} and \cs{ShowCommand} extended}
+
+%FMi title and description was misleading. the commands have been there before but with limited functionality
+
+Since the 2020-10-01 release (see~\cite{34:ltnews32}), \LaTeX{}
+has provided \cs{NewCommandCopy} to copy robust commands,
+and \cs{ShowCommand} to show their definitions on the terminal.
+%
+In that same release, the \pkg{xparse} package was integrated
+into the kernel (as \pkg{ltcmd}) to offer \cs{NewDocumentCommand}, etc.
+%
+However, the extended support for \cs{NewCommandCopy} and
+\cs{ShowCommand} was not implemented in \pkg{ltcmd}. The present
+\LaTeX{} release implements this support, so now commands
+defined with \cs{NewDocumentCommand} and friends can also be copied, and their definitions
+can be easily shown on the terminal without the need for ``\cs{csname} gymnastics''.
+%
+\githubissue{569}
+
+
+\subsection{Undo math alphabet allocations if necessary}
+
+\TeX{}, or more exactly the 8-bit versions of \TeX, such as \pdfTeX{}
+have a hard limit of 16 on the number of different math font groups
+(\cs{fam} or \cs{mathgroup}) that can be used in a single formula. For each symbol font
+declared (by a package or in the preamble) an extra math group is allocated,
+and the same happens for each math alphabet, (such as \cs{mathbf})
+%FMi that
+once it
+gets used anywhere in the document. Up to now, these math
+alphabet allocations were permanent, even if they were
+used only once;
+the result was that in complex documents you
+could easily run out of available math font groups.
+The only remedy for this was to
+define your own math version, which is a complicated and cumbersome process.
+
+This situation has now been improved by the introduction of a new counter
+\texttt{localmathalphabets}: this counter governs how many of
+the math group slots are assigned only locally when a new math
+alphabet (and a new math group) is needed.
+%
+Once the current formula is finished, every such further (local)
+allocation is undone, giving you a fighting chance of being
+able to use different new math alphabets in the next formula.
+
+The default value of \texttt{localmathalphabets} is 2,
+but if you need more local alphabets because of the complexity of your
+document, you can set this to a higher value such as 4 or 5.
+Setting it even higher is possible, but this would seldom
+be useful because many group slots will be taken up by
+symbol fonts and such slots are always permanently allocated,
+whether used or not.
+%
+\githubissue{676}
+
+
+\subsection{New default value for \cs{tracinglostchars}}
+
+In 2021 all \TeX{} engines were enhanced so that \cs{tracinglostchars}
+supported the extra value \texttt{3}, that turns missing
+characters into errors and not just warnings.
+%
+This engine change made us
+realize that \LaTeX{} should set a better default value for this parameter
+(previously, the warning was written only to the transcript file).
+Using the now available value of \texttt{3} as the default
+would really be best, but for
+compatibility reasons we have only increased it to \texttt{2} in the kernel.
+%
+However, we recommend setting \cs{tracinglostchars}\texttt{=3},
+in either a package or the
+preamble of your documents: this is because having missing glyphs
+in the output is definitely an error and should therefore be
+flagged as such (to ensure that it gets proper attention).
+Further reasons, related especially to Unicode engines, for making
+this recommended change can be found later in this newsletter
+(in connection with the misuse of text accents in mathmode).
+
+
\subsection{\cs{PackageNote} and \cs{ClassNote} added}
@@ -445,59 +524,6 @@ For classes, similar commands (with \texttt{Package} replaced by
\githubissue{621}
-\subsection{\cs{NewCommandCopy}, \cs{ShowCommand} now in \pkg{ltcmd}}
-
-Since the 2020-10-01 release (see~\cite{34:ltnews32}), \LaTeX{}
-has provided \cs{NewCommandCopy} to copy robust commands,
-and \cs{ShowCommand} to show their definitions on the terminal.
-%
-In that same release, the \pkg{xparse} package was integrated
-into the kernel (as \pkg{ltcmd}).
-%
-However, the extended support for \cs{NewCommandCopy} and
-\cs{ShowCommand} was not implemented in \pkg{ltcmd}. The present
-\LaTeX{} release implements this support, so now commands
-defined with \pkg{xparse}/\pkg{ltcmd} can be copied, and their definitions
-can be easily shown on the terminal without the need for ``\cs{csname} gymnastics''.
-%
-\githubissue{569}
-
-
-\subsection{Undo math alphabet allocations if necessary}
-
-\TeX{}, or more exactly the 8-bit versions of \TeX, such as \pdfTeX{}
-have a hard limit of 16 on the number of different math font groups
-(\cs{fam} or \cs{mathgroup}) that can be used in a single formula. For each symbol font
-declared (by a package or in the preamble) an extra math group is allocated,
-and the same happens for each math alphabet, (such as \cs{mathbf}) that
-gets used anywhere in the document. Up to now, these math
-alphabet allocations were permanent, even if they were
-used only once;
-the result was that in complex documents you
-could easily run out of available math font groups.
-The only remedy for this was to
-define your own math version, which is a complicated and cumbersome process.
-
-This situation has now been improved by the introduction of a new counter
-\texttt{localmathalphabets}: this counter governs how many of
-the math group slots are assigned only locally when a new math
-alphabet (and a new math group) is needed.
-%
-Once the current formula is finished, every such further (local)
-allocation is undone, giving you a fighting chance of being
-able to use different new math alphabets in the next formula.
-
-The default value of \texttt{localmathalphabets} is 2,
-but if you need more local alphabets because of the complexity of your
-document, you can set this to a higher value such as 4 or 5.
-Setting it even higher is possible, but this would seldom
-be useful because many group slots will be taken up by
-symbol fonts and such slots are always permanently allocated,
-whether used or not.
-%
-\githubissue{676}
-
-
\subsection{Better handling for a misuse of \cs{include}}
The command \cs{include} is by now getting used quite often, but
@@ -514,28 +540,6 @@ file hooks from \cs{InputIfFileExists} are run).
\githubissue{645}
-\subsection{New default value for \cs{tracinglostchars}}
-
-In 2021 all \TeX{} engines were enhanced so that \cs{tracinglostchars}
-supported the extra value \texttt{3}, that turns missing
-characters into errors and not just warnings.
-%
-This engine change made us
-realize that \LaTeX{} should set a better default value for this parameter
-(previously, the warning was written only to the transcript file).
-Using the now available value of \texttt{3} as the default
-would really be best, but for
-compatibility reasons we have only increased it to \texttt{2} in the kernel.
-%
-However, we recommend setting \cs{tracinglostchars}\texttt{=3},
-in either a package or the
-preamble of your documents: this is because having missing glyphs
-in the output is definitely an error and should therefore be
-flagged as such (to ensure that it gets proper attention).
-Further reasons, related especially to Unicode engines, for making
-this recommended change can be found later in this newsletter
-(in connection with the misuse of text accents in mathmode).
-
\section{Code improvements}
More information about the latex3-commits
mailing list.