[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: Many fixes and visual changes, plus draft news item (014d7b89)
Chris Rowley
car222222 at github.github.io
Tue May 18 09:01:01 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : ltnew33
Link : https://github.com/latex3/latex2e/commit/014d7b89a5a06f271328a162f457eb0dc7c66c8d
>---------------------------------------------------------------
commit 014d7b89a5a06f271328a162f457eb0dc7c66c8d
Author: Chris Rowley <car222222 at users.noreply.github.com>
Date: Tue May 18 14:01:01 2021 +0700
Many fixes and visual changes, plus draft news item
TS1 section almost entirely untouched
>---------------------------------------------------------------
014d7b89a5a06f271328a162f457eb0dc7c66c8d
base/doc/ltnews33.tex | 294 +++++++++++++++++++++-----------------------------
1 file changed, 122 insertions(+), 172 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index 725a41f5..5e69aec4 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -1,6 +1,5 @@
%% Temporary: quick draft identification --
-%% This is Draft 3f.
-%% It contains the original draft of the new TS1 Section.
+%% This is Draft 3g.
% \iffalse meta-comment
%
% Copyright 2019-2021
@@ -108,7 +107,7 @@
\tubcommand{\input{tubltmac}}
\publicationmonth{June}
-\publicationyear{2021 --- Draft Version 3f}
+\publicationyear{2021 --- Draft Version 3g}
\publicationissue{33}
@@ -174,7 +173,9 @@ as part of the full kernel documentation in \file{source2e.pdf}.
\section{Extending the hook concept to commands}
-Up to now, the hook management extensions covered hooks for only a few
+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
@@ -182,6 +183,7 @@ 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
@@ -232,9 +234,11 @@ 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 certain effects (such
+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
\section{Updates to the font selection scheme}
@@ -262,7 +266,6 @@ may otherwise happen due to the order of declarations.
\githubissue{444}
-%%CCC Changed %%FMi and corrected
\section{Improved handling of file names}
@@ -331,7 +334,7 @@ and uses \file{mychap.aux}.
The handling of file names has been modified so that \verb|\string| is
applied to normalize robust commands within the file name.
Previously, for example, \verb|\input{\sqrt{2}}| would cause
-\LaTeX\ to loop indefinitely whereas with %%FMi with
+\LaTeX\ to loop indefinitely whereas with
the new normalization
it looks for the file named \verb|sqrt {2}.tex|
(and therefore very likely reports ‘file not found’).
@@ -356,11 +359,11 @@ characters in its name. This has been fixed and now
\section{Glyphs, characters \& encodings}
-
-\subsection{Improved copy\,\&\,paste support for \pdfTeX{} documents}
+%%CCC Changed
+\subsection{Improved copy\,\&\,paste %%CCC support
+for \pdfTeX{} documents}
When compiling with \pdfTeX{}, additional information
-%%FMi add )
(from the file \texttt{glyphtounicode.tex}) is now added automatically
to the PDF file in order to improve copying from, and searching in,
text.
@@ -408,7 +411,8 @@ in addition to the more common
%
\texttt{"2013} (en-dash) and \texttt{"2014} (em-dash).
%
-In the past, these first three characters produced an error message
+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.
@@ -417,8 +421,9 @@ 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
-with the command names \cs{textnonbreakinghyphen}, \cs{textfiguredash}
+With all engines these characters can also now be accessed
+%%CCC with
+using the command names \cs{textnonbreakinghyphen}, \cs{textfiguredash}
and \cs{texthorizontalbar}, respectively.
%
\githubissue{404}
@@ -441,11 +446,88 @@ certainly better than no glyph showing up.
%
\githubissue{502}
+%%CCC Complete me!
+\subsection {The \pkg{textcomp} package is now in thevkernel}
+
+A couple of releases back, the functionality of the \pkg{textcomp}
+package was integrated into the \LaTeX{} kernel.
+Thus itbis no longer necessary
+to load this package in order to access glyphs such as
+ \cs{textcopyright}, \cs{texteuro} or \cs{textyen}.
+
+A full explanation of both the history and the current status of this
+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?
+
+
+%%CCC New TS1 subsection is back here now, as a section.
+%%CCC Together with a news item above (incomplete).
+%%CCC Fixed typos ex DCa (only)
+
+%%CCC This section Needs major editing for:
+%%CCC meaning, content, grammar and typos etc.
+\section{A note on the \texttt{TS1} encoding}
+
+The \enquote{text symbol encoding} (\texttt{TS1}) was originally
+designed at the Cork Conference as a companion to the \texttt{T1}
+encoding. In it various symbols that are not subject to hyphenation
+got assembled and the \pkg{textcomp} package was developed to make
+them accessible. Unfortunately the \TeX{} community was a bit too
+enthusiastic and included several symbols only available in a few
+\TeX{} fonts and some, such as the capital accents, not available at
+all but developed as part of the reference font implementation.
+
+In hindsight that was a very bad idea because it meant that other
+existing fonts (at the time) and later new fonts that got developed
+were unable to provide the full set of glyphs that made up the
+\texttt{TS1} encoding. For existing free PostScript fonts people
+%%CCC ex DCa to
+took the extra effort and produced virtual fonts that faked (some) of
+the missing glyphs. But this was and is a time consuming effort so it
+was done only for a few basic fonts. But even then, only some fonts
+included all glyphs from \texttt{TS1} so the \pkg{textcomp} already
+back then contained a long list, dividing fonts into 5 categories
+according to which glyphs were implemented and which were missing.
+
+A couple of releases back the functionality of the \pkg{textcomp}
+package got integrated into the core code of the \LaTeX{} kernel so
+that its glyph definitions, e.g., \cs{textcopyright}, \cs{texteuro} or
+\cs{textyen}, are now automatically available without the need to load
+an additional package in the preamble.
-%%CCC New TS1 subsection was here.
-%%CCC Moved to the end as a section (temporarily).
-%%FMi but please move back!
+At the time this happened many new free fonts had appeared and
+unfortunately the chaos around the question \enquote{which glyphs of
+ the \texttt{TS1} encoding are implemented by which font} had
+increased with it. Not only did one find many new holes it was next to
+impossible to order the set of fonts into a reasonable set of
+sub-encodings that are contained in each other in a single sequence.
+
+In the end we decided on nine or ten sub-encodings with a reasonable
+number of fonts %% ex DCa
+in each so that all font implemented all glyphs of the
+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 \LaTeX{} always errs on the side of caution, because it might
+claim a glyph is unavailable even though in fact it is.
+For example, the old \texttt{pcr} (PostScript Courier) font (as well
+as most other older PS fonts) is mapped to sub-encoding 5 and
+therefore claims that \cs{textasciigrave} is unavailable even though
+in fact for Courier this is not true. If one uses such a font and this
+becomes an issue then there are a couple (suboptimal) possibilities.
+For one, one can alter the mapping of Courier and pretend that belongs
+to a fuller sub-encoding, e.g.
+\begin{verbatim}
+ \DeclareEncodingSubset{TS1}{pcr}{2}
+\end{verbatim}
+The downside is, that \LaTeX{} then believes other glyphs that are in fact
+unavailable are also there, so that it is important to check that the
+final document doesn't have some missing glyphs.
\section{New or improved commands}
@@ -486,8 +568,9 @@ and shape, but leaves the series as a variable quantity, so that an
\githubissue{497}
-
-\subsection{Producing several footnote marks for one footnote}
+%%CCC Changed
+\subsection{Producing several %%CCC footnote
+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
@@ -505,10 +588,6 @@ using certain classes or the \pkg{footmisc} package.
\githubissue{482}
-
-
-
-
\subsection{Allow \cs{nocite} in the preamble}
A natural place for \verb=\nocite{*}= would be the preamble of the
@@ -559,14 +638,6 @@ We have restored consistency here: now both of the above lines
produce a single \env{tabular} row.
%
As before, you can
-%%CCC Unresolved: ask B&K?
-%%FMi no unnecessary quotes
-%%FMi put `\cs{raggedright} \cs{arraybackslash}'
-%%CCC But I thought that these quotes are necessary:
-%%CCC without them it was not clear to me that this was a single ‘code snippet’
-%%CCC to be added verbatim to the preamble.
-%%FMi you can remove the space between the two \cs and combine
-%%FMi the para with the one befor perhaps? DONE
put \cs{raggedright}\cs{arraybackslash} in the \env{tabular}'s
preamble for a column to ensure that \cs{\textbackslash} is always
interpreted as a tabular row separator when used in that column. And
@@ -607,13 +678,9 @@ a new primitive
\mbox{parameter}
%
\cs{tracingstacklevels} that, when both it and \cs{tracingmacros} are
-positive, will
-%%CCC print
-add to the tracing information for each macro a visual indication (using dots) of
-its nesting level in the macro expansion %FMi stsck.
-stack.
-%%FMi it adds ~.... in front of expansions with the number of dots indicating
-%% how deep down in the stack you are
+positive, will add to the tracing information for each
+macro a visual indication (using dots) of
+its nesting level in the macro expansion stack.
These changes have both now been added to \LaTeX's debugging macros
\cs{tracingall} and \cs{tracingnone}, so that these two new extensions
@@ -641,8 +708,9 @@ ended without an explicit \cs{par}.
%
\githubissue{489}
-
-\subsection{Ensure that \cs{AtEndDocument} is executed in vertical mode}
+%%CCC changed
+\subsection{Ensure that \cs{AtEndDocument} is %%CCC executed
+in vertical mode}
Until now \verb=\end{document}= executed the code from the
@@ -700,7 +768,7 @@ 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,
@@ -716,8 +784,8 @@ 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 the case of \pkg{lthooks})
-\cs{cs\_new:Npn}.
+with \cs{newcommand} or (as in %%CCC P ADJUST the case of
+\pkg{lthooks}) \cs{cs\_new:Npn}.
To solve such issues, we now provide \cs{NewModuleRelease}
so that completely
@@ -749,13 +817,13 @@ ends.
\section{Changes to packages in the \pkg{graphics} category}
-
-\subsection{Removed spurious warning when loading graphics files}
+%%CCC changed
+\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 %%FMi fnd
-find
+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
@@ -765,7 +833,8 @@ show up in that case.
\githubissue{516}
%%CCC Changed
-\subsection{Fixed loading of \texttt{gzip}ped PostScript graphics files}
+\subsection{Fixed loading of \texttt{gzip}ped %%CCC PostScript
+graphics files}
A previous release mistakenly changed the file searching mechanism so
that compressed graphics files would raise an error when being loaded
@@ -820,9 +889,10 @@ debugging possibilities.
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
-behaviour.
-
+handles both versions of this command and restores
+the original \mbox{behaviour}.
+%
+% %%CCC Removed BAD PARA BREAK ?
In addition, package options for guiding the use of \enquote{poor
man's bold} in fallback situations were added.
%
@@ -838,67 +908,9 @@ The fix for issue 548 was also applied in \pkg{amsmath}, see above.
-%%CCC Changed from subsection
-%%FMi why now twice in the file? one here and one after \end{document}
-
-\section{A note on the \texttt{TS1} encoding}
-
-The \enquote{text symbol encoding} (\texttt{TS1}) was originally
-designed at the Cork Conference as a companion to the \texttt{T1}
-encoding. In it various symbols that are not subject to hyphenation
-got assembled and the \pkg{textcomp} package was developed to make
-them accessible. Unfortunately the \TeX{} community was a bit too
-enthusiastic and included several symbols only available in a few
-\TeX{} fonts and some, such as the capital accents, not available at
-all but developed as part of the reference font implementation.
-
-In hindsight that was a very bad idea because it meant that other
-existing fonts (at the time) and later new fonts that got developed
-were unable to provide the full set of glyphs that made up the
-\texttt{TS1} encoding. For existing free PostScript fonts people to
-the extra effort and produced virtual fonts that faked (some) of
-the missing glyphs. But this was and is a time consuming effort so it
-was done only for a few basic fonts. But even then, only some fonts
-included all glyphs from \texttt{TS1} so the \pkg{textcomp} already
-back then contained a long list, dividing fonts into 5 categories
-according to which glyphs were implemented and which were missing.
-
-A couple of releases back the functionality of the \pkg{textcomp}
-package got integrated into the core code of the \LaTeX{} kernel so
-that its glyph definitions, e.g., \cs{textcopyright}, \cs{texteuro} or
-\cs{textyen}, are now automatically available without the need to load
-an additional package in the preamble.
-
-At the time this happened many new free fonts had appeared and
-unfortunately the chaos around the question \enquote{which glyphs of
- the \texttt{TS1} encoding are implemented by which font} had
-increased with it. Not only did one find many new holes it was next to
-impossible to order the set of fonts into a reasonable set of
-sub-encodings that are contained in each other in a single sequence.
-
-In the end we decided on nine or ten sub-encodings with a reasonable
-number of font in each so that all font implemented all glyphs of the
-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 \LaTeX{} always errs on the side of caution, because it might
-claim a glyph is unavailable even though in fact it is.
+%%CCC TS1 section moved back from here< also post-doc copy deleted
+%%CCC \section{A note on the \texttt{TS1} encoding}
-For example, the old \texttt{pcr} (PostScript Courier) font (as well
-as most other older PS fonts) is mapped to sub-encoding 5 and
-therefore claims that \cs{textasciigrave} is unavailable even though
-in fact for Courier this is not true. If one uses such a font and this
-becomes an issue then there are a couple (suboptimal) possibilities.
-For one, one can alter the mapping of Courier and pretend that belongs
-to a fuller sub-encoding, e.g.
-\begin{verbatim}
- \DeclareEncodingSubset{TS1}{pcr}{2}
-\end{verbatim}
-The downside is, that \LaTeX{} then believes other glyphs that are in fact
-unavailable are also there, so that it is important to check that the
-final document doesn't have some missing glyphs.
%\medskip
@@ -924,68 +936,6 @@ final document doesn't have some missing glyphs.
\end{document}
-\githubissue{502}
-
-
-\subsection{A note on the \texttt{TS1} encoding}
-
-The \enquote{text symbol encoding} (\texttt{TS1}) was originally
-designed at the Cork Conference as a companion to the \texttt{T1}
-encoding. In it various symbols that are not subject to hyphenation
-got assembled and the \pkg{textcomp} package was developed to make
-them accessible. Unfortunately the \TeX{} community was a bit too
-enthusiastic and included several symbols only available in a few
-\TeX{} fonts and some, such as the capital accents, not available at
-all but developed as part of the reference font implementation.
-
-In hindsight that was a very bad idea because it meant that other
-existing fonts (at the time) and later new fonts that got developed
-were unable to provide the full set of glyphs that made up the
-\texttt{TS1} encoding. For existing free PostScript fonts people to
-the extra effort and produced virtual fonts that faked (some) of
-the missing glyphs. But this was and is a time consuming effort so it
-was done only for a few basic fonts. But even then, only some fonts
-included all glyphs from \texttt{TS1} so the \pkg{textcomp} already
-back then contained a long list, dividing fonts into 5 categories
-according to which glyphs were implemented and which were missing.
-
-A couple of releases back the functionality of the \pkg{textcomp}
-package got integrated into the core code of the \LaTeX{} kernel so
-that its glyph definitions, e.g., \cs{textcopyright}, \cs{texteuro} or
-\cs{textyen}, are now automatically available without the need to load
-an additional package in the preamble.
-
-At the time this happened many new free fonts had appeared and
-unfortunately the chaos around the question \enquote{which glyphs of
- the \texttt{TS1} encoding are implemented by which font} had
-increased with it. Not only did one find many new holes it was next to
-impossible to order the set of fonts into a reasonable set of
-sub-encodings that are contained in each other in a single sequence.
-
-In the end we decided on nine or ten sub-encodings with a reasonable
-number of font in each so that all font implemented all glyphs of the
-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 \LaTeX{} always errs on the side of caution, because it might
-claim a glyph is unavailable even though in fact it is.
-
-For example, the old \texttt{pcr} (PostScript Courier) font (as well
-as most other older PS fonts) is mapped to sub-encoding 5 and
-therefore claims that \cs{textasciigrave} is unavailable even though
-in fact for Courier this is not true. If one uses such a font and this
-becomes an issue then there are a couple (suboptimal) possibilities.
-For one, one can alter the mapping of Courier and pretend that belongs
-to a fuller sub-encoding, e.g.
-\begin{verbatim}
- \DeclareEncodingSubset{TS1}{pcr}{2}
-\end{verbatim}
-The downside is, that \LaTeX{} then believes other glyphs that are in fact
-unavailable are also there, so that it is important to check that the
-final document doesn't have some missing glyphs.
-
\iffalse
%%CCC For Chris' local system
More information about the latex3-commits
mailing list.