[latex3-commits] [git/LaTeX3-latex3-latex2e] lt4.15: Add ltnews entry for #548 and general cleanup of the doc (a7519f2f)
Frank Mittelbach
frank.mittelbach at latex-project.org
Thu Apr 22 15:37:08 CEST 2021
Repository : https://github.com/latex3/latex2e
On branch : lt4.15
Link : https://github.com/latex3/latex2e/commit/a7519f2f48242c2336fdc6f9f78216a1eebfcef7
>---------------------------------------------------------------
commit a7519f2f48242c2336fdc6f9f78216a1eebfcef7
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Thu Apr 22 15:37:08 2021 +0200
Add ltnews entry for #548 and general cleanup of the doc
>---------------------------------------------------------------
a7519f2f48242c2336fdc6f9f78216a1eebfcef7
base/doc/ltnews33.tex | 148 +++++++++++++++++++++++++++++++++-----------------
1 file changed, 98 insertions(+), 50 deletions(-)
diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index e72d34a7..04138c47 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -109,7 +109,14 @@
\section{Introduction}
-\emph{to be written}
+The focus of the June 2020 release is to provide further important
+building blocks for producing reliable tagged PDF output in the future
+(see \cite{33:blueprint}), they are discussed in the next two
+sections. In addition we included a number of smaller enhancement and
+fixes that are outlined on the next pages. As usual, more detail can
+on individual changes can be found in the \texttt{changes.txt} files
+in the distribution and, of course, in the documented
+sources~\cite{33:source2e}.
@@ -117,11 +124,11 @@
\section{Extending the hook concept to paragraphs}
Largely triggered by the need for better control of paragraph text
-processing, in particular when producing tagged PDF output (see
-\cite{33:blueprint}), we have extended the paragraph processing of
-\LaTeX{} so that the kernel gains control both at the start and the
-end of each paragraph. This is done in a manner that is (or should
-be) transparent to packages and user documents.
+processing, in particular when producing tagged PDF output, we have
+extended the paragraph processing of \LaTeX{} so that the kernel gains
+control both at the start and the end of each paragraph. This is done
+in a manner that is (or should be) transparent to packages and user
+documents.
Beside the internal control points for exclusive use of the \LaTeX{}
kernel we also implemented four public hooks that can be used by
@@ -267,8 +274,11 @@ the name. The coding has now been slightly altered to allow for this.
\githubissue{427}
-\subsection{Add a Lua callback to \pkg{ltshipout} to provide
- a uniform location for applying custom attributes}
+\subsection[Add a Lua callback to \pkg{ltshipout} to provide
+ a uniform location for applying custom attributes]
+ {Add a Lua callback to \pkg{ltshipout} to provide
+ a uniform
+ \mbox\quad location for applying custom attributes}
Just before shipping out a page, a new \LuaTeX{} callback
\texttt{pre\_shipout\_filter} is now called to allow final
@@ -279,7 +289,8 @@ elements at shipout. An example for this is the \pkg{luacolor}
package which could insert the color commands using this callback.
-\subsection{Improved copy\&paste support for \pdfTeX{} documents}
+
+\subsection{Improved copy\,\&\,paste support for \pdfTeX{} documents}
When compiling with \pdfTeX{}, additional information is added to the
PDF file to improve copying from and searching in text. This especially
@@ -345,8 +356,10 @@ With the new behavior it accesses \verb|sqrt {2}.tex|.
\githubissue{481}
-\subsection{Additional support for Unicode characters from the
- Latin Extended Additional block}
+\subsection[Additional support for Unicode characters from the
+ Latin Extended Additional block]
+ {Additional support for Unicode characters from the Latin\\
+ \mbox\quad Extended Additional block}
\LaTeX\ is quite capable of typesetting characters such as
\enquote{\d{m}}, but until now it lacked the Unicode mappings for some
@@ -358,6 +371,7 @@ entered directly instead of resorting to \verb=\d{m}= and so forth.
\githubissue{484}
+
\subsection{Always have color groups set up}
To use color in \LaTeX{} certain constructs, especially boxes, need an
@@ -405,8 +419,10 @@ the \pkg{footmisc} package.
-\subsection{Providing the raw option list of packages or documentclass
- to key/value handlers}
+\subsection[Providing the raw option list of packages or documentclass
+ to key/value handlers]
+ {Providing the raw option list of packages or documentclass\\
+ \mbox\quad to key/value handlers}
\LaTeXe{} has always normalized space in option lists so\\
\verb|\documentclass[ a4paper , 12pt ]{article}|\\
@@ -537,8 +553,11 @@ more careful not to leave \pkg{ExplSyntaxOn} after a package ends.
-\subsection{Add \cs{tracingstacklevels}
- and \cs{tracinglostchars}\texttt{=3} to \cs{tracingall}}
+\subsection[Add \cs{tracingstacklevels}
+ and \cs{tracinglostchars}\texttt{=3} to \cs{tracingall}]
+ {Add \cs{tracingstacklevels}
+ and \cs{tracinglostchars}\texttt{=3}\\
+ \mbox\quad to \cs{tracingall}}
In July 2020 David Jones suggested an extension to \TeX{} engines, that
added the possibility to set \cs{tracinglostchars}\texttt{=3} to have an
@@ -565,7 +584,40 @@ demonstrating these parameters is available in the linked GitHub issue.
\subsection{Make \cs{\textbackslash} generally robust}
-\emph{write}
+In 2018 most \LaTeX{} user-level commands were made robust including
+\cs{\textbackslash}. However, \cs{\textbackslash} is redefined in
+various environments and not all cases were caught, in particular its use as row
+delimiter in \env{tablular} structures. This has now been corrected and
+\cs{\textbackslash} should be robust in all standard
+circumstances. Doing that also fixed one anomaly present in the past:
+in a tabular preamble of the form
+\begin{quote}
+ \verb={l=\texttt{\string>}\verb={raggedright}p{10cm}r}= % stupid class
+\end{quote}
+a \cs{\textbackslash} in the second column would have the definition
+used by \cs{raggedright} and would not indicate the (premature) end of
+the \env{tabular}, e.g.,
+\begin{quote}
+ \verb=a & b1 \\ b2 & c \\=
+\end{quote}
+would be a single row in that \env{tabular}. However, writing
+\begin{quote}
+ \verb=a & \\ b2 & c \\=
+\end{quote}
+would give you two rows: due to the scanning process the
+\cs{\textbackslash} directly following the \verb=&= still had
+the \enquote{end the row} meaning and not the \enquote{start a new
+ line in the second column} meaning.
+
+With \cs{\textbackslash} now robust, the scanning after \verb=&= ends
+when the command is seen and the second column is started and so now
+both lines above consistently produce a single \env{tabular} row.
+
+As before, you can use \cs{raggedright}\cs{arraybackslash} in the
+\env{tabular} preamble to ensure that \cs{\textbackslash} is always
+interpreted as a row separator when used in the column or you could
+use \cs{tabularnewline} to explicitly ask for a new row even when
+\cs{\textbackslash} has a different meaning in the current column.
%
\githubissue{548}
@@ -606,6 +658,12 @@ language options.
\githubissue[s]{353 and 529}
+\subsection{\pkg{array} and \pkg{longtable}: Make \cs{\textbackslash} generally robust}
+
+The fix for this issue was also applied to these packages, see above.
+%
+\githubissue{548}
+
\subsection{\pkg{longtable}: General bug fix update}
Minor update to \pkg{longtable} to fix bugs reported. Notably the
@@ -618,13 +676,20 @@ existing documents, a rollback to \pkg{longtable 4.13}
\githubissue{133 183 464}
-\subsection{Add \cs{tracingstacklevels}
- and \cs{tracinglostchars}\texttt{=3} to \cs{traceon}}
+\subsection[\pkg{trace}: Add \cs{tracingstacklevels}
+ and \cs{tracinglostchars}\texttt{=3} to \cs{traceon}]
+ {\pkg{trace}: Add \cs{tracingstacklevels} and\\
+ \mbox\quad \cs{tracinglostchars}\texttt{=3} to \cs{traceon}}
+The enhancement mentioned earlier was also added to the \pkg{trace} package.
+%
+\iffalse
The \cs{tracingstacklevels} and \cs{tracinglostchars} extensions
-mentioned earlier for \cs{tracingall} were also added for \cs{traceon}
-in the \pkg{trace} package, so if you're using that you can also benefit
-from these new debugging tools.
+mentioned earlier for \cs{tracingall} were also added for
+\cs{traceon} in the \pkg{trace} package, so if you're using that you
+can also benefit from these new debugging tools.
+\fi
+%
%
\githubissue{524}
@@ -632,15 +697,17 @@ from these new debugging tools.
-%\section{Changes to packages in the \pkg{amsmath} category}
-%
-%\subsection{\ldots}
+\section{Changes to packages in the \pkg{amsmath} category}
+
+%\subsection{\pkg{amsmath}: Make \cs{\textbackslash} generally robust}
+
+The fix for issue 548 was also applied in \pkg{amsmath}, see above.
%
-%%
-%\githubissue{xxx}
+\githubissue{548}
-\medskip
+%\medskip
+
\begin{thebibliography}{9}
\fontsize{9.3}{11.3}\selectfont
@@ -649,6 +716,10 @@ from these new debugging tools.
\emph{\LaTeX{} Tagged PDF — A blueprint for a large project}.\\
\url{https://latex-project.org/publications/indexbyyear/2020/}
+\bibitem{33:source2e}
+ \emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
+ \url{https://latex-project.org/help/documentation/}
+
\bibitem{33:ltnews32} \LaTeX{} Project Team:
\emph{\LaTeXe{} news 32}.\\
\url{https://latex-project.org/news/latex2e-news/ltnews32.pdf}
@@ -658,26 +729,3 @@ from these new debugging tools.
\end{document}
-
-
-\endinput % needed for ltnews processing
-
-\bibitem{32:ltnews31} \LaTeX{} Project Team:
- \emph{\LaTeXe{} news 31}.\\
- \url{https://latex-project.org/news/latex2e-news/ltnews31.pdf}
-
-\bibitem{32:site-doc}
- \emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
- \url{https://latex-project.org/help/documentation/}
-
-\bibitem{32:issue-tracker}
- \emph{\LaTeX{} issue tracker}.
- \url{https://github.com/latex3/latex2e/issues/}
-
-\bibitem{32:babel}
- Javier Bezos and Johannes Braams.
- \emph{Babel---Localization and internationalization}.\\
- \url{https://www.ctan.org/pkg/babel}
-
-
-
More information about the latex3-commits
mailing list.