[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnew33: Version 3n (56e9f8be)

[Chris Rowley]

Repository : https://github.com/latex3/latex2e
On branch  : ltnew33
Link       : https://github.com/latex3/latex2e/commit/56e9f8bed7677d30b51eb56d264cc6105955257e

>---------------------------------------------------------------

commit 56e9f8bed7677d30b51eb56d264cc6105955257e
Author: Chris Rowley <car222222 at users.noreply.github.com>
Date:   Mon May 24 15:42:20 2021 +0700

    Version 3n


>---------------------------------------------------------------

56e9f8bed7677d30b51eb56d264cc6105955257e
 base/doc/ltnews33.tex | 40 ++++++++++++++++++++++++++--------------
 1 file changed, 26 insertions(+), 14 deletions(-)

diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index ec070c6e..b34586d2 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -1,5 +1,5 @@
 %%  Temporary: quick draft identification --
-%%  This is Draft 3m.
+%%  This is Draft 3n.
 % \iffalse meta-comment
 %
 % Copyright 2019-2021
@@ -115,7 +115,7 @@
 \tubcommand{\input{tubltmac}}
 
 \publicationmonth{June}
-\publicationyear{2021 --- Draft Version 3m}
+\publicationyear{2021 --- Draft Version 3n}
 
 \publicationissue{33}
 
@@ -437,12 +437,8 @@ certainly better than no glyph showing up.
 %
 \githubissue{502}
 
-%%CCC  Complete me!
-%%FMi wrong title it is *not now!!!
-%%CCC  I tried again! 
-%%CCC \subsection {The \pkg{textcomp} package is now in the kernel}
-
-\subsection {The \texttt{TS1} characters from \pkg{textcomp} in the kernel}
+%%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.  
@@ -450,16 +446,32 @@ Thus it is 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 
-%#CCC possible new version for keeping it in here: 
-follows here.
+ %%CCC  Extra news,summarised:
+ At this time the opprtunity was also taken to bring some order to the 
+ chaos surrounding the question: \enquote{which glyphs from
+  the \texttt{TS1} encoding are aviailable 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: 
+The documented code for this can be found now in the file 
+\file{lttextcomp.dtx} but we hope to publish a full explanation of 
+the approach very soon now. 
+
+%%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 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      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