[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: bump to 3h ; cleanup and added comments (fe4f6545)
Frank Mittelbach
frank.mittelbach at latex-project.org
Tue May 18 12:14:39 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : ltnew33
Link : https://github.com/latex3/latex2e/commit/fe4f65450722599d4f1980e21743a26d5ac0bbb5
>---------------------------------------------------------------
commit fe4f65450722599d4f1980e21743a26d5ac0bbb5
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Tue May 18 12:14:39 2021 +0200
bump to 3h ; cleanup and added comments
>---------------------------------------------------------------
fe4f65450722599d4f1980e21743a26d5ac0bbb5
base/doc/ltnews33.tex | 174 +++++++++++++++++++++++++-------------------------
1 file changed, 88 insertions(+), 86 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index c6ddee42..00fa7c32 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -1,5 +1,5 @@
%% Temporary: quick draft identification --
-%% This is Draft 3g.
+%% This is Draft 3h.
% \iffalse meta-comment
%
% Copyright 2019-2021
@@ -107,7 +107,7 @@
\tubcommand{\input{tubltmac}}
\publicationmonth{June}
-\publicationyear{2021 --- Draft Version 3g}
+\publicationyear{2021 --- Draft Version 3h}
\publicationissue{33}
@@ -133,17 +133,10 @@ reliable tagged PDF output
are discussed in the next two
sections.
-%%CCC Changed for new structure.
-Subsequent sections describe
-%%CCC In addition we have included
-quite a number of recent %%CCC
-smaller enhancements and fixes.
-%%CCC that are outlined on the next pages.
-%%CCC Nothing here yet about the new TS1 note.
-As usual, more detail
-on individual changes can be found in the \texttt{changes.txt} files
-in the distribution and, of course, in the documented
-sources~\cite{33:source2e}.
+Subsequent sections describe quite a number of recent smaller
+enhancements and fixes. As usual, more detail on individual changes
+can be found in the \texttt{changes.txt} files in the distribution
+and, of course, in the documented sources~\cite{33:source2e}.
@@ -173,17 +166,15 @@ as part of the full kernel documentation in \file{source2e.pdf}.
\section{Extending the hook concept to commands}
-Up to now, %%CCC
-hook management %%CCC p adjust extensions
-covered hooks for only a few
-core areas, such as the hooks for the \cs{shipout} process or those in
-the \env{document} environment, as well as some \enquote {generic}
-hooks, both for file loading (helpful for patching such files) and for
+Up to now, hook management covered hooks for only a few core areas,
+such as the hooks for the \cs{shipout} process or those in the
+\env{document} environment, as well as some \enquote {generic} hooks,
+both for file loading (helpful for patching such files) and for
arbitrary environments (the hooks executed within \cs{begin} and
\cs{end}). This concept of \enquote{generic hooks} has now been
extended to provide \hook{/before} and \hook{/after} hooks for any
(document-level) command---in theory at least.
-%%CCC ADJUSTed PARA??
+
In practice, these new generic \hook{cmd} hooks, especially the
\hook{cmd/.../after}, hooks may fail with commands that are too
@@ -217,14 +208,12 @@ for example, the addition of background or foreground material
to some or all pages.
-We have now added a command,
-%%FMi currently %%CCC ??? To be discussed elsewhere, at length!
-called \cs{RawShipout}, which does not do any rebuilding of the page
-box and so does not run most of these hooks. When using this new
-command, essential internal book-keeping is still carried out, such as
-updating the \texttt{totalpages} counter and adding
-\texttt{shipout/firstpage} or \texttt{shipout/lastpage} material when
-appropriate.
+We have now added a command, called \cs{RawShipout}, which does not do
+any rebuilding of the page box and so does not run most of these
+hooks. When using this new command, essential internal book-keeping
+is still carried out, such as updating the \texttt{totalpages} counter
+and adding \texttt{shipout/firstpage} or \texttt{shipout/lastpage}
+material when appropriate.
\subsection{A new Lua callback in \pkg{ltshipout},
@@ -234,11 +223,9 @@ For use just before shipping out a page, there is now a \LuaTeX{}
callback \texttt{pre\_shipout\_filter} to contain final adjustments to
the box being shipped out. This is particularly useful for
Lua\TeX\ packages which flag (using, for example, attributes or
-properties) elements on a page in order to apply %%CCC P ADJUST certain
-effects (such
-as the insertion of \enquote{color commands}) to these elements at
-shipout.
-%%CCC ADJUSTED
+properties) elements on a page in order to apply effects (such as the
+insertion of \enquote{color commands}) to these elements at shipout.
+
\section{Updates to the font selection scheme}
@@ -359,9 +346,7 @@ characters in its name. This has been fixed and now
\section{Glyphs, characters \& encodings}
-%%CCC Changed
-\subsection{Improved copy\,\&\,paste %%CCC support
-for \pdfTeX{} documents}
+\subsection{Improved copy\,\&\,paste for \pdfTeX{} documents}
When compiling with \pdfTeX{}, additional information
(from the file \texttt{glyphtounicode.tex}) is now added automatically
@@ -411,20 +396,18 @@ in addition to the more common
%
\texttt{"2013} (en-dash) and \texttt{"2014} (em-dash).
%
-In the past, these first three %CCC P adjust characters
-produced an error message
-when used with \pdfTeX{} (since they are not available in \texttt{OT1}
-or \texttt{T1} encoded fonts). They now typeset an approximation to
-the glyph: e.g., the `figure dash' is approximated by an en-dash.
+In the past, these first three produced an error message when used
+with \pdfTeX{} (since they are not available in \texttt{OT1} or
+\texttt{T1} encoded fonts). They now typeset an approximation to the
+glyph: e.g., the `figure dash' is approximated by an en-dash.
With Unicode engines they either work (when the glyph is contained in
the selected Unicode font) or they typeset nothing, producing a
``Missing character'' warning in the log file.
-With all engines these characters can also now be accessed
-%%CCC with
-using the command names \cs{textnonbreakinghyphen}, \cs{textfiguredash}
-and \cs{texthorizontalbar}, respectively.
+With all engines these characters can also now be accessed using the
+command names \cs{textnonbreakinghyphen}, \cs{textfiguredash} and
+\cs{texthorizontalbar}, respectively.
%
\githubissue{404}
@@ -447,11 +430,13 @@ certainly better than no glyph showing up.
\githubissue{502}
%%CCC Complete me!
+%%FMi wrong title it is *not now!!!
+
\subsection {The \pkg{textcomp} package is now in the kernel}
A couple of releases back, the functionality of the \pkg{textcomp}
package was integrated into the \LaTeX{} kernel.
-Thus itbis no longer necessary
+Thus it is no longer necessary
to load this package in order to access glyphs such as
\cs{textcopyright}, \cs{texteuro} or \cs{textyen}.
@@ -460,6 +445,14 @@ package and the \enquote{text symbol encoding} (\texttt{TS1}) encoding
is (wiil be?) available as ??? %%CCC \cite ??
%%CCC This could be a ref to a section in an edition of ltnews,
%%CCC but should it be?
+%%FMi --- there is no such eplanation in earlier ltnews or anywhere to
+%%FMi my knowledge which is why I added that note on TS1 into this one
+%%FMi because it was forgotten to be described
+%%FMi --- and so you can only refer to the next section which I think is pointless
+%%FMi and this is why I think that should remain ass a single longer subsection
+%%FMi as it was before!
+%%FMi --- For quite a while the ltnewsletters are more than minimal snippets
+%%FMi referring to other places
%%CCC New TS1 subsection is back here now, as a section.
@@ -468,6 +461,8 @@ is (wiil be?) available as ??? %%CCC \cite ??
%%CCC This section Needs major editing for:
%%CCC meaning, content, grammar and typos etc.
+%%FMi --- I still think it should be just one subsection and the previous
+%%FMi dropped/incoporated
\section{A note on the \texttt{TS1} encoding}
The \enquote{text symbol encoding} (\texttt{TS1}) was originally
@@ -511,7 +506,9 @@ 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 fact. The mapping would ensure
+that the glyph is unavailable in that %%FMi fact.
+font.
+The mapping would ensure
that \LaTeX{} always errs on the side of caution, because it might
claim a glyph is unavailable even though in fact it is.
@@ -568,19 +565,15 @@ and shape, but leaves the series as a variable quantity, so that an
\githubissue{497}
-%%CCC Changed
-\subsection{Producing several %%CCC footnote
-marks for one footnote}
+\subsection{Producing several marks for one footnote}
It is sometimes necessary to reference the same footnote several
times: i.e., to produce several footnote marks using the same number
-or symbol. This is now easily
-possible by placing a \cs{label} within the referenced \cs{footnote}
-and referencing
-this label by using the new command \cs{footref}. This
-means that footnote marks can be generated
-to refer to arbitrary footnotes
-(including those in \texttt{minipage}s).
+or symbol. This is now easily possible by placing a \cs{label} within
+the referenced \cs{footnote} and referencing this label by using the
+new command \cs{footref}. This means that footnote marks can be
+generated to refer to arbitrary footnotes (including those in
+\texttt{minipage}s).
This \cs{footref} command has previously been available, but only when
using certain classes or the \pkg{footmisc} package.
@@ -695,7 +688,6 @@ in the linked GitHub issue.
\section{Code improvements}
-%%CCC Changed
\subsection{Execute \cs{par} at the end of \cs{marginpar}}
Previously, \LaTeX{} ended a \cs{marginpar} without ever explicitly
@@ -709,8 +701,14 @@ ended without an explicit \cs{par}.
\githubissue{489}
%%CCC changed
-\subsection{Ensure that \cs{AtEndDocument} is %%CCC executed
-in vertical mode}
+%%FMi that is technically wrong --- it matter not at all in what
+%%FMi mode AtEndDocument it matters in what mode its code finally gets executed
+%%FMi --- changed albeit longer
+
+%\subsection{Ensure that \cs{AtEndDocument} is %%CCC executed
+%in vertical mode}
+
+\subsection{Execute \cs{AtEndDocument}'s code in vertical mode}
Until now \verb=\end{document}= executed the code from the
@@ -768,24 +766,24 @@ documented sources~\cite{33:source2e}.
%
\githubissue{85}
-%%CCC Better spacing?
+
+
\subsection{New for \pkg{latexrelease}\,: \cs{NewModuleRelease}}
-To explain the need for this new feature,
-we shall consider the following example:
-in the 2020-10-01 release, \LaTeX's new hook management system was
-added to the kernel (see \cite{33:ltnews32}) and, as with all changes
-to the kernel, it was added to \pkg{latexrelease}; this made it
-possible to roll back to a date where this module didn't yet exist, or
-to roll forward from an older \LaTeX{} release to get the hook
-management system (by loading the \pkg{latexrelease} package).
+To explain the need for this new feature, we shall consider the
+following example: in the 2020-10-01 release, \LaTeX's new hook
+management system was added to the kernel (see \cite{33:ltnews32})
+and, as with all changes to the kernel, it was added to
+\pkg{latexrelease}; this made it possible to roll back to a date where
+this module didn't yet exist, or to roll forward from an older
+\LaTeX{} release to get the hook management system (by loading the
+\pkg{latexrelease} package).
%
However, this method of rolling back from a later release to the
2020-10-01 release didn't quite work because it would try to define
-all the commands from \pkg{lthooks} again; and this
-would of course result in the expected errors from commands defined
-with \cs{newcommand} or (as in %%CCC P ADJUST the case of
-\pkg{lthooks}) \cs{cs\_new:Npn}.
+all the commands from \pkg{lthooks} again; and this would of course
+result in the expected errors from commands defined with
+\cs{newcommand} or (as in \pkg{lthooks}) \cs{cs\_new:Npn}.
To solve such issues, we now provide \cs{NewModuleRelease}
so that completely
@@ -818,22 +816,27 @@ ends.
\section{Changes to packages in the \pkg{graphics} category}
%%CCC changed
+%%FMi -- why?
\subsection{Removed %%CCC spurious
warning when loading graphics files}
-A previous release sometimes mistakenly caused a
-(false) warning message
-to appear when using a generic graphics rule to find
-and load a graphics
-file with an unknown extension.
-This warning would incorrectly say that the file was not found, whereas
-the file would in fact be correctly loaded. The warning now doesn't
-show up in that case.
+A previous release sometimes mistakenly caused a (false) warning
+message to appear when using a generic graphics rule to find and load
+a graphics file with an unknown extension. This warning would
+incorrectly say that the file was not found, whereas the file would in
+fact be correctly loaded. The warning now doesn't show up in that
+case.
%
\githubissue{516}
%%CCC Changed
-\subsection{Fixed loading of \texttt{gzip}ped %%CCC PostScript
+%%FMi --- wrong in my opinion, only PS graphics (eps) can get gzipped not any odd graphic
+%%FMi nothing else was ever supported
+%%FMi yes it makes the TOC 2 lines, but ...
+
+\subsection{Fixed loading of \texttt{gzip}ped
+ %%CCC PostScript
+ PostScript %%FMi
graphics files}
A previous release mistakenly changed the file searching mechanism so
@@ -886,13 +889,15 @@ debugging possibilities.
\subsection{\pkg{bm}: Better support for commands with optional arguments}
+
Some uses of optional arguments that were supported by \cs{bm} stopped
being supported (in 2004) when \cs{kernel at ifnextchar} was used
internally by the format instead of \cs{@ifnextchar}. This update
handles both versions of this command and restores
the original \mbox{behaviour}.
-%
+
% %%CCC Removed BAD PARA BREAK ?
+% %%FMi clarity before visual imho, so no
In addition, package options for guiding the use of \enquote{poor
man's bold} in fallback situations were added.
%
@@ -908,9 +913,6 @@ The fix for issue 548 was also applied in \pkg{amsmath}, see above.
-%%CCC TS1 section moved back from here< also post-doc copy deleted
-%%CCC \section{A note on the \texttt{TS1} encoding}
-
%\medskip
More information about the latex3-commits
mailing list.