[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: cleanup of the draft for copy-editing by bb and kb (06fe82e5)
Frank Mittelbach
frank.mittelbach at latex-project.org
Tue May 25 15:05:38 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : ltnew33
Link : https://github.com/latex3/latex2e/commit/06fe82e5887198ad4214d2abf66dffa742e98aae
>---------------------------------------------------------------
commit 06fe82e5887198ad4214d2abf66dffa742e98aae
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Tue May 25 15:05:38 2021 +0200
cleanup of the draft for copy-editing by bb and kb
>---------------------------------------------------------------
06fe82e5887198ad4214d2abf66dffa742e98aae
base/doc/ltnews33.tex | 164 ++++++++++++--------------------------------------
1 file changed, 39 insertions(+), 125 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index 8d0544b6..a58e6c43 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -1,5 +1,3 @@
-%% Temporary: quick draft identification --
-%% This is Draft 3p.
% \iffalse meta-comment
%
% Copyright 2019-2021
@@ -40,7 +38,6 @@
\providecommand\Dash {---}
-%%CCC Do we need a cite for source2e.pdf ?
%% NOTE: Chris' preferred hyphens!
%%\showhyphens{parameters}
@@ -116,7 +113,7 @@
\tubcommand{\input{tubltmac}}
\publicationmonth{June}
-\publicationyear{2021 --- Draft Version 3p}
+\publicationyear{2021} %% --- Draft Version 3p
\publicationissue{33}
@@ -437,44 +434,27 @@ certainly better than no glyph showing up.
%
\githubissue{502}
-%%CCC Still only a news item: new heading text
\subsection {The characters from \pkg{textcomp} are in the kernel}
A couple of releases back, the functionality of the \pkg{textcomp}
-package was integrated into the \LaTeX{} kernel.
-Thus it is no longer necessary
-to load this package in order to access glyphs such as
- \cs{textcopyright}, \cs{texteuro} or \cs{textyen}.
-
- %%CCC Extra news,summarised:
- %%FMi but not really correct :-( That approach was used already 10-15 years ago,
- %%FMi only back then with 5 classes now with 10 given that there are more fonts around nowadays.
- %%FMi
- %%FMi Bottom line, I really don't see that this is better than my original (give or take copy-editing),
- %%FMi the only thing is that is it now noticeably longer (while at the same time having lost 2 important
- %%FMi paragraphs at the end, which I have reintroduced) and as a result now runs over the 6 pages we had before.
-
- %%FMi if this block is dropped we are back to 6 pages
- %%FMi it reads nice, but as I said it is not correct really as that was always the case only less granular
-
- \iftrue %%FMi keep this (if if a bit incorrect)
-
- At this time the opportunity was also taken to bring some order to the
- chaos surrounding the question: \enquote{which glyphs from
- the \texttt{TS1} encoding are available in a given font?}.
-This was done using an approach based on font families and collections, with the differing
-glyph coverage of the \enquote*{text symbols} being indicated by assigning to a font family or collection
-a 'sub-encoding number' that indicates which glyphs from the \texttt{TS1} encoding are guaranteed to be available when using
-a font from that family or collection. This assignment ensures
-that \LaTeX{} always errs on the side of caution, possibly
-claiming that a glyph is not available even when it in fact is.
-
-\fi
-\iffalse %%FMi but drop that
+package was integrated into the \LaTeX{} kernel. Thus it is no longer
+necessary to load this package in order to access glyphs such as
+\cs{textcopyright}, \cs{texteuro} or \cs{textyen}.
+
+
+At this time the opportunity was also taken to bring some order to the
+chaos surrounding the question: \enquote{which glyphs from the
+ \texttt{TS1} encoding are available in a given font?}. This was
+done using an approach based on font families and collections, with
+the differing glyph coverage of the \enquote*{text symbols} being
+indicated by assigning to a font family or collection a 'sub-encoding
+number' that indicates which glyphs from the \texttt{TS1} encoding are
+guaranteed to be available when using a font from that family or
+collection. This assignment ensures that \LaTeX{} always errs on the
+side of caution, possibly claiming that a glyph is not available even
+when it in fact is.
-%%CCC Plus info:
-%%FMi who is the ``we'' in this note? I'm not prepared to write that full explanation beyond what is there in lttextcomp
-%%FMi in the forseeable future.
+\iffalse %%FMi but drop that
The documented code for this can be found now in the file
\file{lttextcomp.dtx} but we hope to publish a full explanation of
@@ -483,51 +463,9 @@ the approach very soon now.
\fi %% FMi potential drop
-%%CCC Removed:
-%% A full explanation of both the history and the current status of
-%% package and the \enquote{text symbol encoding} (\texttt{TS1}) encoding
-%% follows here.
-
-%%CCC Otherwise use this: 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 explanation in earlier ltnews or anywhere to
-%%FMi my knowledge which is why I added that note on TS1 into this onep
-%%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.
-%%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.
-%%FMi — I still think it should be just one subsection and the previous
-%%FMi dropped/incorporated
-
-%%CCC CHANGED to subsubsection, to fit with above changes.
-%%CCC BUT NO editing done yet, needs to be rewritten,
-%%CCC when I understand it!
-
-%%CCC Frank's original, without the subsection above:
-%% \subsection{A note on the \texttt{TS1} encoding}
-
-%%CCC Also changed wording:
-%% \subsubsection{A note on the \texttt{TS1} encoding}
-
-
-%%FMi the point is not the history, the point is what to do if
-%%FMi there is trouble and to understand that, a bit of history is needed
-%%FMi so I think your title focusses on the wrong topic
-%%FMi (and which is why I didn't make any such split)
\subsubsection
- [A note on the history of `text symbols']%
+ [A note on the history of `text symbols']
{A note on the history of `text symbols' and
the \texttt{TS1} encoding}
@@ -545,7 +483,6 @@ 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
@@ -553,21 +490,9 @@ 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.
-\iffalse %% FMi that got moved to the top, therefore also change next para
-
-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.
-
-\fi
When we recently integrated the functionality of the \pkg{textcomp}
into the \LaTeX{} kernel
-%
-%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
@@ -576,15 +501,12 @@ 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
+number of fonts 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
-font.
-The mapping would ensure
+that the glyph is unavailable in that 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.
@@ -602,9 +524,6 @@ 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.
-%%FMi: all that part got lost in moving stuff back and forth!
-%%FMi: and that is part of the advice why the whole section is there!
-
An alternative is to pretend that \cs{textasciigrave} can always be
taken from the \texttt{TS1} encoding (no questions asked):
\begin{verbatim}
@@ -848,15 +767,14 @@ been changed.
-%%DPC restore mention of unused option warning change
One
-aspect of this %%FMi added
+aspect of this
change does affect the standard \mbox{processing}: any tokens to the
-right of an \texttt{=} %% tt added
+right of an \texttt{=}
sign are \mbox{removed}
-from consideration %% from the
+from consideration
when constructing
-the \enquote{\mbox{unused} option list}. %% In
+the \enquote{\mbox{unused} option list}.
For example, in
this release \texttt{clip=true} and
\texttt{clip=false} both contribute \texttt{clip} to the list of
@@ -882,14 +800,13 @@ 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
-new modules can be defined using the facilities of
-\pkg{latexrelease} in such a way that,
-when rolling back or forward, the system will know whether the code of
-the new module has to be read or completely ignored. More details on
-this can be found in the \pkg{latexrelease} documentation (get this
-with \verb|texdoc latexrelease|).
+To solve such issues, we now provide \cs{NewModuleRelease} so that
+completely new modules can be defined using the facilities of
+\pkg{latexrelease} in such a way that, when rolling back or forward,
+the system will know whether the code of the new module has to be read
+or completely ignored. More details on this can be found in the
+\pkg{latexrelease} documentation (get this with
+\verb|texdoc latexrelease|).
%
\githubissue{479}
@@ -915,14 +832,12 @@ ends.
\subsection{Removed warning when loading graphics files}
A previous release sometimes mistakenly caused a (false) warning
-message to appear when \mbox{using} a generic graphics rule to find and load
-a graphics file with an unknown \mbox{extension}.
+message to appear when \mbox{using} a generic graphics rule to find
+and load a graphics file with an unknown \mbox{extension}.
%%CCC removing hyphenation here makes this one line longer.
-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.
+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}
@@ -931,9 +846,8 @@ The warning now doesn't show up in that case.
PostScript files}
A previous release mistakenly changed the file searching mechanism so
-that compressed
-PostScript graphics files would raise an error when being loaded
-with \cs{includegraphics}. This has been fixed so that
+that compressed 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.
%
\githubissue{519}
More information about the latex3-commits
mailing list.