[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: Getting there, slowly (585beac0)
Chris Rowley
car222222 at github.github.io
Tue May 18 16:46:39 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : ltnew33
Link : https://github.com/latex3/latex2e/commit/585beac0b07774052abd9a65e4ab1348ecdfcaf4
>---------------------------------------------------------------
commit 585beac0b07774052abd9a65e4ab1348ecdfcaf4
Author: Chris Rowley <car222222 at users.noreply.github.com>
Date: Tue May 18 21:46:39 2021 +0700
Getting there, slowly
Not much tinkering this time
>---------------------------------------------------------------
585beac0b07774052abd9a65e4ab1348ecdfcaf4
base/doc/ltnews33.tex | 98 ++++++++++++++++++++++++++-------------------------
1 file changed, 50 insertions(+), 48 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index 00fa7c32..14371e97 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -1,5 +1,5 @@
%% Temporary: quick draft identification --
-%% This is Draft 3h.
+%% This is Draft 3i.
% \iffalse meta-comment
%
% Copyright 2019-2021
@@ -107,7 +107,7 @@
\tubcommand{\input{tubltmac}}
\publicationmonth{June}
-\publicationyear{2021 --- Draft Version 3h}
+\publicationyear{2021 --- Draft Version 3i}
\publicationissue{33}
@@ -173,7 +173,7 @@ 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.
+(document-level) command—in theory at least.
In practice, these new generic \hook{cmd} hooks, especially the
@@ -186,7 +186,7 @@ However, given that these hooks are mainly meant for developers who
wish to provide better interoperability between different packages,
and between packages and the \LaTeX{} kernel, these restrictions are,
we hope, of minor importance. Indeed, for commands where this
-mechanism can't be applied, one is in the same situation as before;
+mechanism can’t be applied, one is in the same situation as before;
and for all others there will be a noticeable improvement.
These hooks will be especially important for our current project to
@@ -296,7 +296,7 @@ file \file{mychap.tex.tex} for inclusion and tried to
use the file \file{mychap.tex.aux} for internal (auxiliary) information. The reason was that
\cs{include} had to construct both
of these file names from the given
-argument and it didn't bother to do
+argument and it didn’t bother to do
anything special
with the supplied
extension \texttt{.tex}.
@@ -382,28 +382,28 @@ directly instead of using \verb=\d{m}=, etc.
-\subsection{More ``dashes'' in encodings \texttt{OT1},
+\subsection{More ``dashes’’ in encodings \texttt{OT1},
\texttt{T1} and \texttt{TU}}
When pasting in text from external sources, one can encounter these
three Unicode characters
%
-\texttt{"2011} (non-breaking hyphen),
-\texttt{"2012} (figure dash) and
-\texttt{"2015} (horizontal bar),
+\texttt{“2011} (non-breaking hyphen),
+\texttt{“2012} (figure dash) and
+\texttt{“2015} (horizontal bar),
%
in addition to the more common
%
-\texttt{"2013} (en-dash) and \texttt{"2014} (em-dash).
+\texttt{“2013} (en-dash) and \texttt{“2014} (em-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.
+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.
+``Missing character’’ warning in the log file.
With all engines these characters can also now be accessed using the
command names \cs{textnonbreakinghyphen}, \cs{textfiguredash} and
@@ -412,14 +412,14 @@ command names \cs{textnonbreakinghyphen}, \cs{textfiguredash} and
\githubissue{404}
-\subsection{Poor man's \cs{textasteriskcentered}}
+\subsection{Poor man’s \cs{textasteriskcentered}}
The \cs{textasteriskcentered} symbol, used as part of the set of
footnote symbols in \LaTeX{}, is assumed to be implemented by every
font with the \texttt{TS1} encoding (when \pdfTeX{} is used) or with
the \texttt{TU} encoding for the Unicode engines. That assumption is
unfortunately not correct for all fonts since, for example, the
-\texttt{stix2} fonts don't provide this glyph. A result is that one
+\texttt{stix2} fonts don’t provide this glyph. A result is that one
gets missing glyph messages when using \cs{thanks}, etc.
Therefore \cs{textasteriskcentered} now checks whether there is such a
@@ -445,13 +445,13 @@ 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 — 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 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 — For quite a while the ltnewsletters are more than minimal snippets
%%FMi referring to other places
@@ -461,8 +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
+%%FMi — I still think it should be just one subsection and the previous
+%%FMi dropped/incorporated
\section{A note on the \texttt{TS1} encoding}
The \enquote{text symbol encoding} (\texttt{TS1}) was originally
@@ -524,7 +524,7 @@ to a fuller sub-encoding, e.g.
\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.
+final document doesn’t have some missing glyphs.
\section{New or improved commands}
@@ -631,7 +631,7 @@ We have restored consistency here: now both of the above lines
produce a single \env{tabular} row.
%
As before, you can
-put \cs{raggedright}\cs{arraybackslash} in the \env{tabular}'s
+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
you can use \cs{tabularnewline} to explicitly ask for a new table row,
@@ -646,7 +646,7 @@ current column.
\subsection{Allow extra space between name and address in \pkg{letter} class}
The \cs{opening} command in the \pkg{letter} class expects the name
-and address to be separated by \verb=\\=, but it didn't allow the use
+and address to be separated by \verb=\\=, but it didn’t allow the use
of an optional argument to add some extra space after the name. The
code has now been slightly altered to allow this.
%
@@ -662,7 +662,7 @@ order to generate an error message in case some character is missing
from a font. In previous years, a warning about a missing character
was silently printed to the \texttt{.log} file (if
$\cs{tracinglostchars}>0$) and to the terminal (if ${}>1$). This
-extension was added for \TL{} and \MiKTeX{} (except in Knuth's \TeX,
+extension was added for \TL{} and \MiKTeX{} (except in Knuth’s \TeX,
of course), so that with $\cs{tracinglostchars}>2$ you now also get an
error message for each missing glyph.
@@ -675,7 +675,7 @@ 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
+These changes have both now been added to \LaTeX’s debugging macros
\cs{tracingall} and \cs{tracingnone}, so that these two new extensions
are activated/deactivated as appropriate, so long as the \TeX{} engine
supports them. An example document demonstrating these parameters is
@@ -700,15 +700,13 @@ ended without an explicit \cs{par}.
%
\githubissue{489}
-%%CCC changed
-%%FMi that is technically wrong --- it matter not at all in what
+%%FMi that is technically wrong — it matters 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}
+%%FMi — changed albeit longer
-\subsection{Execute \cs{AtEndDocument}'s code in vertical mode}
+%\subsection{Execute \cs{AtEndDocument}’s code in vertical mode}
+%%CCC What about this?
+\subsection{Execute \cs{AtEndDocument} hook in vertical mode}
Until now \verb=\end{document}= executed the code from the
@@ -728,7 +726,7 @@ statement. This was fixed and now \cs{enddocument} first issues a
The use of color in certain \LaTeX{} constructs, especially boxes,
needs an extra layer of grouping to ensure that the color setting does
-not \emph{escape} and continue outside the box when it shouldn't.
+not \emph{escape} and continue outside the box when it shouldn’t.
%
To support this, the \LaTeX{} kernel defines a number of commands,
e.g., \cs{color at begingroup} to be used in such places.
@@ -771,16 +769,16 @@ documented sources~\cite{33:source2e}.
\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
+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
+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
+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 \pkg{lthooks}) \cs{cs\_new:Npn}.
@@ -802,7 +800,7 @@ with \verb|texdoc latexrelease|).
Whereas the \pkg{latexrelease} package can usually emulate an older
\LaTeX{} kernel without much problem, rolling back to before the
-2020-02-02 release didn't work properly: this is because the
+2020-02-02 release didn’t work properly: this is because the
management of the \cs{ExplSyntaxOn/Off} status for packages (after an
\pkg{expl3}-based package is loaded) cannot be removed by the rollback
without messing up the catcodes. This has been fixed so that rollback
@@ -816,7 +814,8 @@ ends.
\section{Changes to packages in the \pkg{graphics} category}
%%CCC changed
-%%FMi -- why?
+%%FMi — why?
+%%CCC Length in TOC (as usual:-)
\subsection{Removed %%CCC spurious
warning when loading graphics files}
@@ -824,23 +823,23 @@ 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
+fact be correctly loaded. The warning now doesn’t show up in that
case.
%
\githubissue{516}
-%%CCC Changed
-%%FMi --- wrong in my opinion, only PS graphics (eps) can get gzipped not any odd graphic
+%%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 ...
+%%CCC Try this then, see changed body too.
\subsection{Fixed loading of \texttt{gzip}ped
- %%CCC PostScript
- PostScript %%FMi
-graphics files}
+ %%CCC PostScript graphics
+ PostScript files}
A previous release mistakenly changed the file searching mechanism so
-that compressed graphics files would raise an error when being loaded
+that compressed %%CCC
+PostScript graphics files would raise an error when being loaded
with \cs{includegraphics}. This has been fixed so that
\texttt{gzip}ped graphics files now load correctly.
%
@@ -890,7 +889,9 @@ debugging possibilities.
\subsection{\pkg{bm}: Better support for commands with optional arguments}
-Some uses of optional arguments that were supported by \cs{bm} stopped
+%%CCC Try again to fix para!
+Some uses of optional arguments in %%CCC 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
@@ -898,8 +899,9 @@ the original \mbox{behaviour}.
% %%CCC Removed BAD PARA BREAK ?
% %%FMi clarity before visual imho, so no
+% %%CCC Agreed: fixed otherwise, see above.
In addition, package options for guiding the use of \enquote{poor
- man's bold} in fallback situations were added.
+ man’s bold} in fallback situations were added.
%
\githubissue{554}
@@ -940,7 +942,7 @@ The fix for issue 548 was also applied in \pkg{amsmath}, see above.
\iffalse
-%%CCC For Chris' local system
+%%CCC For Chris’ local system
\usepackage[utf8]{inputenc}
\def\githubissue #1{\par\noindent{\small\sl
@@ -950,7 +952,7 @@ The fix for issue 548 was also applied in \pkg{amsmath}, see above.
%%FMi This is the subsubsection from the class (for reference) unchanged
\makeatletter
-% maybe not the greatest design but normally we wouldn't have subsubsections
+% maybe not the greatest design but normally we wouldn’t have subsubsections
\renewcommand{\subsubsection}{%
\@startsection
{subsubsection}{2}{\leftmargini}{-1.5ex \@plus -1ex \@minus -.2ex}%
More information about the latex3-commits
mailing list.