[latex3-commits] [git/LaTeX3-latex3-latex2e] ltnews35: intro for ltnews35 (1790d778)

[Frank Mittelbach]

Repository : https://github.com/latex3/latex2e
On branch  : ltnews35
Link       : https://github.com/latex3/latex2e/commit/1790d778cbf1ec6495a31c8c236e15e4402427c8

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

commit 1790d778cbf1ec6495a31c8c236e15e4402427c8
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Tue May 17 13:20:50 2022 +0200

    intro for ltnews35


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

1790d778cbf1ec6495a31c8c236e15e4402427c8
 base/doc/ltnews35.tex | 62 ++++++++++++++++++++++++++++++++++-----------------
 1 file changed, 42 insertions(+), 20 deletions(-)

diff --git a/base/doc/ltnews35.tex b/base/doc/ltnews35.tex
index 741542a2..99858c66 100644
--- a/base/doc/ltnews35.tex
+++ b/base/doc/ltnews35.tex
@@ -118,7 +118,7 @@
 \tubcommand{\input{tubltmac}}
 
 \publicationmonth{June}
-\publicationyear{2022  --- DRAFT version for upcoming release}
+\publicationyear{2022}
 
 \publicationissue{35}
 
@@ -137,6 +137,28 @@
 
 \section{Introduction}
 
+The 2022 June release of \LaTeX{} is again focussing on improvements
+made for our multi-year project to automatically offer tagged PDF
+output~\cite{35:blueprint}. These are the new document metadata
+interface, the new mark mechanism for \LaTeX{}, a standard key/value
+approach for options, and the introduction of the \texttt{latex-lab}
+area for temporary code that could be optionally loaded by a document
+(when \cs{DocumentMetadata} is used with certain test keys). These
+additions are described in the first sections.  Related to this effort
+there are updates to \pkg{hyperref} and \pkg{tagpdf} both of which
+have their own distributions.
+
+As usual, we also added a number of smaller improvements and bug
+fixes in various components of core \LaTeX{}. Perhaps the most
+interesting ones (for some users) are direct support for floating
+point arithmetic (via \cs{fpeval} see below) and the ability to
+properly color parts of math formulas without introducing spacing
+problems. For this we now offer the command \cs{mathcolor}; see the
+description near the end of the newsletter.  There is also a new major
+release of the \pkg{doc} package that supports more a fine-grained
+classification of code elements and properly supports \pkg{hyperref}.
+
+
 \section{Document metadata interface}
 
 Until recently there was no dedicated location to declare
@@ -197,7 +219,7 @@ Currently supported values are \texttt{phase-I} and \texttt{phase-II}
 that enable code of the tagged PDF project (phase-I is frozen and
 phase-II the phase we are currently working on).  With
 \begin{verbatim}
-\DocumentMetadata{testphase=phase-II}
+  \DocumentMetadata{testphase=phase-II}
 \end{verbatim}
 you currently enable tagging for paragraphs and footnotes, more
 document elements will follow soon.
@@ -207,7 +229,8 @@ For more detailed testing it is also possible to pass other values to
 design interface based on \pkg{l3keys} can be accessed through the
 value \texttt{prototype}, thus
 \begin{verbatim}
-\DocumentMetadata{testphase={phase-II,prototype}}
+  \DocumentMetadata
+             {testphase={phase-II,prototype}}
 \end{verbatim}
 will enable all of phase-II plus the draft template interface (which
 is not yet integrated in phase-II).
@@ -284,11 +307,7 @@ examples and further notes on the mechanism in the file
 \texttt{ltmarks-doc} to display it on your computer.
 
 
-
-
-\section{New or improved commands}
-
-\subsection{A keyval approach to option handling}
+\section{A key/value approach to option handling}
 
 The classical \LaTeXe{} method for handling options, using \cs{ProcessOptions},
 treats each entry in the list as a string. Many package authors have sought to
@@ -327,6 +346,11 @@ Package options defined in this way can also be set within a package using
 the new command \cs{SetKeys}, which again takes an optional argument
 to specify the \emph{family}, plus a mandatory one for the options themselves.
 
+
+
+\section{New or improved commands}
+
+
 \subsection{Floating point and integer calculations}
 
 The L3 programming layer offers expandable commands for calculating
@@ -339,9 +363,9 @@ document-level, the small package \pkg{xfp} defined \cs{fpeval} and
 
 An example of use could be the following:
 \begin{verbatim}
-\LaTeX{} can now compute:
-\[ \frac{\sin (3.5)}{2} + 2\cdot 10^{-3}
-    = \fpeval{sin(3.5)/2 + 2e-3}         \]
+  \LaTeX{} can now compute:
+  \[ \frac{\sin (3.5)}{2} + 2\cdot 10^{-3}
+      = \fpeval{sin(3.5)/2 + 2e-3}         \]
 \end{verbatim}
 which produces the following output:
 \begin{quote}
@@ -357,9 +381,9 @@ other three commands are essentially thin wrappers for \cs{numexpr},
 \cs{dimexpr}, and \cs{glueexpr} \Dash therefore inheriting some syntax
 peculiars and limitations in expressiveness.
 \begin{verbatim}
-\newcommand\calulateheight[1]{%
-  \setlength\textheight{\dimeval{\topskip
-        + \baselineskip * \inteval{#1-1}}}}
+  \newcommand\calulateheight[1]{%
+    \setlength\textheight{\dimeval{\topskip
+          + \baselineskip * \inteval{#1-1}}}}
 \end{verbatim}
 The above, for example, calculates the appropriate \cs{textheight} for
 a given number of text lines.
@@ -460,7 +484,7 @@ lua.get_functions_table()
 For a long time \pkg{hyperref} provides starred versions for the reference commands
 that don't create active links. This syntax extension required users and
 package authors to check if \pkg{hyperref} was loaded and adjust the coding
-accordingly or take the starrred forms out if text was copied to a document
+accordingly or take the starred forms out if text was copied to a document
 without \pkg{hyperref}. The commands have now been aligned with
 the \pkg{hyperref} usage and always allow an optional star. The \pkg{showkeys} package
 has been updated to handle the starred versions too, both with \pkg{hyperref} or \pkg{nameref}
@@ -658,15 +682,13 @@ was seen.
 
 \subsection{Input support for normalized angle brackets}
 
-Source files containing \textlangle\ or \textrangle\ directly written as Unicode
-codepoints U+2329 and U+232A no longer break when the source file gets normalized under Unicode normalization rules.
+Source files containing \textlangle\ or \textrangle\ directly written
+as Unicode codepoints U+2329 and U+232A no longer break when the
+source file gets normalized under Unicode normalization rules.
 %
 \githubissue{gh/714}
 
 
-\subsection{???}
-%
-\githubissue{???}
 
 
 \section{Bug fixes}