summaryrefslogtreecommitdiff
path: root/macros/latex/base/ltnews29.tex
diff options
context:
space:
mode:
Diffstat (limited to 'macros/latex/base/ltnews29.tex')
-rw-r--r--macros/latex/base/ltnews29.tex47
1 files changed, 23 insertions, 24 deletions
diff --git a/macros/latex/base/ltnews29.tex b/macros/latex/base/ltnews29.tex
index 78a1b2e60f..c707c65342 100644
--- a/macros/latex/base/ltnews29.tex
+++ b/macros/latex/base/ltnews29.tex
@@ -1,6 +1,6 @@
% \iffalse meta-comment
%
-% Copyright (C) 2018-2019
+% Copyright (C) 2018-2020
% The LaTeX3 Project and any individual authors listed elsewhere
% in this file.
%
@@ -177,7 +177,7 @@ These include:
\enquote{\guillemotright} in all encoding files. These correct
names are in addition to the old (but wrong) Adobe names: Adobe
mistakenly called them Guillemot, which is a sea bird.
-%
+%
\githubissue{65}
%
\item
@@ -225,14 +225,14 @@ for example
\DeclareRobustCommand\verbvisiblespace
{\textvisiblespace}
\end{verbatim}
-will select the the ``official'' visible space character of the
+will select the ``official'' visible space character of the
current font. This may look like the natural default, but it wasn't
chosen as our default because many fonts just don't have that Unicode
character, or they have one with a strange shape.
%
\githubissue[s]{69 and 70}
-
+
\subsection{Error message corrected}
Trying to redefine an undefined command could in a few cases generate
an error message with a missing space, e.g.,
@@ -244,7 +244,7 @@ This is now fixed.
%
\githubissue{41}
-
+
\subsection{Fixed fatal link error with \pkg{hyperref}}
If an \cs{href} link text gets broken across pages, \pdfTeX{} and
@@ -304,7 +304,7 @@ major data structures. As a result,
many things are internally modeled
as paragraphs even if they are not conceptually
``text paragraphs'' in
-the traditional sense.
+the traditional sense.
In a few cases this has some surprising effects
that are not always
for the better. One example is
@@ -347,21 +347,21 @@ corrected, and a corresponding update has been made to the
\pkg{amsmath} package, in which these commands are also defined.
%
\githubissue[s]{49 and 50}
-
-
+
+
\subsection{Guarding \cs{pfill} in \pkg{doc}}
For presenting index entries pointing to
code fragments and the like,
the \pkg{doc} package has a \cs{pfill} command that
-generates within the index a line of dots leading from
+generates within the index a line of dots leading from
the command name to the page or code line numbers.
If necessary it would automatically split the entry
over two lines. That worked well enough for a quarter century, but we
-discovered recently that it is broken inside
+discovered recently that it is broken inside
the \cls{ltugboat} class,
-where it sometimes produces
+where it sometimes produces
bad spacing within continuation lines.
The reason turned out to be a redefinition of the \LaTeX{} command
@@ -375,10 +375,10 @@ removal of space.
%
\githubissue[s]{25 and 75}
-
-
+
+
\section{Changes to packages in the \pkg{tools} category}
\subsection{Sometimes the \pkg{trace} package turned off too much}
@@ -419,7 +419,7 @@ The \cs{docolaction} command can be used to carry out actions
depending on the column you are currently in, i.e., first, any inner
one (if more than two) or last. However, if the action generates text
then there is the question: is this text part of the current column or
-the one after? That is, on the next run, do we test before or after it,
+the one after? That is, on the next run, do we test before or after it,
to determine in which column we are?
This is now resolved as follows: if you use \cs{docolaction*} any
@@ -479,7 +479,7 @@ topics~\cite{29:site-pub}. Feel free to take a look.
Yukitoshi Fujimura has kindly translated
into Japanese two documents that are
distributed with standard \LaTeX{}.
-These are:
+These are:
\begin{itemize}
\item
\LaTeXe{} for authors;
@@ -491,30 +491,30 @@ You will now also find there a typeset version of the full \LaTeXe{}
source code (with index etc.\@) and a number of other goodies.
-
+
\begin{thebibliography}{9}
-
+
\bibitem{29:Mittelbach:TB39-1} Frank Mittelbach:
- \emph{New rules for reporting bugs in the \LaTeX{} core software}.
+ \emph{New rules for reporting bugs in the \LaTeX{} core software}.
In: TUGboat, 39\#1, 2018.
\url{https://latex-project.org/publications/}
\bibitem{29:ltnews28}
- \emph{\LaTeX{} News, Issue 28}.
+ \emph{\LaTeX{} News, Issue 28}.
In: TUGboat, 39\#1, 2018.\\
\rlap{\url{https://latex-project.org/news/latex2e-news/}}
-\bibitem{29:site-doc}
- \emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
+\bibitem{29:site-doc}
+ \emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
\url{https://latex-project.org/documentation/}
-\bibitem{29:site-pub}
+\bibitem{29:site-pub}
\emph{\LaTeX{} Project publications on the \LaTeX{} Project Website}.\\
\url{https://latex-project.org/publications/}
\bibitem{29:amsldoc} American Mathematical Society and The \LaTeX3 Project:
- \emph{User's Guide for the \texttt{amsmath} Package} (Version 2.1).
+ \emph{User's Guide for the \texttt{amsmath} Package} (Version 2.1).
April 2018.
Available from
\url{https://www.ctan.org}
@@ -523,4 +523,3 @@ source code (with index etc.\@) and a number of other goodies.
\end{thebibliography}
\end{document}
-