[latex3-commits] [git/LaTeX3-latex3-latex2e] master: updates after copyedits by kb and bb, also fixed #99 (692fbc5)
Frank Mittelbach
frank.mittelbach at latex-project.org
Mon Dec 17 16:55:21 CET 2018
Repository : https://github.com/latex3/latex2e
On branch : master
Link : https://github.com/latex3/latex2e/commit/692fbc5ba9ca90c54ea9bfd7ca77c9c08ae185c0
>---------------------------------------------------------------
commit 692fbc5ba9ca90c54ea9bfd7ca77c9c08ae185c0
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Mon Dec 17 16:55:21 2018 +0100
updates after copyedits by kb and bb, also fixed #99
>---------------------------------------------------------------
692fbc5ba9ca90c54ea9bfd7ca77c9c08ae185c0
doc/ltnews29.tex | 99 ++++++++++++++++++++++++++++++++------------
required/tools/changes.txt | 2 +-
2 files changed, 73 insertions(+), 28 deletions(-)
diff --git a/doc/ltnews29.tex b/doc/ltnews29.tex
index bd74b31..c1d0732 100644
--- a/doc/ltnews29.tex
+++ b/doc/ltnews29.tex
@@ -47,15 +47,56 @@
\newcommand\githubissue[2][]{\ifhmode\unskip\fi
\quad\penalty500\strut\nobreak\hfill
- \mbox{\small\itshape(github issue#1 #2)}\par}
+ \mbox{\small\itshape(%
+ \href{https://github.com/latex3/latex2e/issues/\getfirstgithubissue#2 \relax}%
+ {github issue#1 #2}%
+ )}%
+ \par}
+
+% simple solution right now (just link to the first issue if there are more)
+\def\getfirstgithubissue#1 #2\relax{#1}
\newcommand\sxissue[1]{\ifhmode\unskip\fi
\quad\penalty500\strut\nobreak\hfill
- \mbox{\small\itshape\url(#1)}\par}
+ \mbox{\small\itshape(\url{https://tex.stackexchange.com/#1})}\par}
\let\cls\pkg
\newcommand\env[1]{\texttt{#1}}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\usepackage{graphics}
+\makeatletter
+% Xe\TeX{} requires reflecting the first E, hence we complain if the
+% graphics package is not present. (For plain documents, this can be
+% loaded via Eplain.) Also, at Barbara's suggestion, if the current
+% font is slanted, we rotate by 180 instead of reflecting so there is at
+% least a chance to look ok. (The magic values here seem more or less
+% ok for \texttt{cmsl} and \texttt{cmti}.)
+%
+% \begin{macrocode}
+\def\tubreflect#1{%
+ \@ifundefined{reflectbox}{%
+ \TBerror{A graphics package must be loaded for \string\XeTeX}%
+ }{%
+ \ifdim \fontdimen1\font>0pt
+ \raise 1.6ex \hbox{\kern.1em\rotatebox{180}{#1}}\kern-.1em
+ \else
+ \reflectbox{#1}%
+ \fi
+ }%
+}
+\def\tubhideheight#1{\setbox0=\hbox{#1}\ht0=0pt \dp0=0pt \box0 }
+\def\XekernbeforeE{-.125em}
+\def\XekernafterE{-.1667em}
+\DeclareRobustCommand{\Xe}{\leavevmode
+ \tubhideheight{\hbox{X%
+ \setbox0=\hbox{\TeX}\setbox1=\hbox{E}%
+ \ifdim \fontdimen1\font>0pt \def\XekernbeforeE{0em}\fi
+ \lower\dp0\hbox{\raise\dp1\hbox{\kern\XekernbeforeE\tubreflect{E}}}%
+ \kern\XekernafterE}}}
+\def\XeTeX{\Xe\TeX}
+\def\XeLaTeX{\Xe{\kern.11em \LaTeX}}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\publicationmonth{December}
\publicationyear{2018}
@@ -64,6 +105,8 @@
\begin{document}
+%\addtolength\textheight{4.2pc} % only for TUB
+
\maketitle
\tableofcontents
@@ -80,8 +123,9 @@ newer, and they are mostly rather obscure.
\section[Bug reports for core \LaTeXe{} and packages]
{Bug reports for core \LaTeXe{} and packages maintained by the Project Team}
-In Spring 2018 we established a new issue tracking system (GitHub
-issues) for both the \LaTeX{} core and the packages maintained by the
+In Spring 2018 we established a new issue tracking system
+(Github issues at \url{https://github.com/latex3/latex2e/issues}) for both
+the \LaTeX{} core and the packages maintained by the
\LaTeX{} Project team, with an updated procedure for how to report a
bug or problem.
@@ -102,8 +146,8 @@ with further details and discussion in~\cite{Mittelbach:TB39-1}.
\subsection{UTF-8:\ updates to the default input encoding}
In the April 2018 release of \LaTeX{} we changed the default encoding
-from 7-bit \acro{ascii} to UTF-8 when using classic \TeX\ or
-\hologo{pdfTeX}, see \textit{\LaTeX{} News~28}~\cite{ltnews28} for
+from 7-bit \acro{ascii} to \acro{utf}-8 when using classic \TeX\ or
+\hologo{pdfTeX}; see \textit{\LaTeX{} News~28}~\cite{ltnews28} for
details.
Now, after half a year of experience with
@@ -113,7 +157,7 @@ made a small number of adjustments to further improve the user experience.
These include:
\begin{itemize}
\item
- Some improvements when displaying error messages about UTF-8
+ Some improvements when displaying error messages about \acro{utf}-8
characters that have not been set up for use with \LaTeX{},
or are invalid for some other reason;
%
@@ -135,24 +179,24 @@ These include:
\githubissue{65}
%
\item
- Added \cs{Hwithstroke} and \cs{hwithstroke} necessary for
- typesetting Maltese.
+ Added \cs{Hwithstroke} (\enquote{\Hwithstroke}) and \cs{hwithstroke}
+ (\enquote{\hwithstroke}) necessary for typesetting Maltese.
%
- \sxissue{https://tex.stackexchange.com/q/460110}
+ \sxissue{q/460110}
\end{itemize}
-\subsection{Fixed \cs{verb*} and friends in \XeTeX{} and \LuaTeX{}}
+\subsection{Fixed \cs{verb*} and friends in \texorpdfstring{\XeTeX}{XeTeX} and \LuaTeX{}}
The original \cs{verb*} and \texttt{verbatim*} in \LaTeX{} were coded
under the assumption that the position of the space character (i.e.,
-ASCII 32) in a Typewriter Font contains a visible space glyph
+\acro{ascii} 32) in a typewriter font contains a visible space glyph
``\verb*= =''. This is correct for \pdfTeX{} with the most used font
encodings \texttt{OT1} and \texttt{T1}. However, this unfortunately
does not work for Unicode engines using the \texttt{TU} encoding since
-the space character slot (ASCII 32) then usually contains a real
+the space character slot (\acro{ascii} 32) then usually contains a real
(normal) space, which has the effect that \cs{verb*} produces the same
results as \cs{verb}.
@@ -181,7 +225,7 @@ for example
\end{verbatim}
will select the 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
+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}
@@ -201,7 +245,7 @@ This is now fixed.
\subsection{Fixed fatal link error with \pkg{hyperref}}
-If a \cs{href} link text gets broken across pages \pdfTeX{} and
+If an \cs{href} link text gets broken across pages, \pdfTeX{} and
\LuaTeX{} will generate a fatal error unless both parts of the link
are internally at the same boxing level. In two-column mode that was
not the case if one of the pages had spanning top floats. This has now
@@ -232,7 +276,7 @@ input reading whilst in vertical mode and each line in the file
represents a single line (paragraph) in the table of contents. If,
however, this is done in horizontal mode, which is sometimes the case,
then these spaces will appear in the output. If you then omit some of
-the input lines (e.g., because you do not display TOC data below a
+the input lines (e.g., because you do not display \acro{toc} data below a
certain level), then these spaces accumulate in the typeset output and
you get surprising, and unwanted, gaps inside the text.
@@ -241,7 +285,7 @@ lines in the \texttt{.toc} file so that \TeX{} will not generate such
spaces that may survive to spoil the printed result. As some third
party packages have augmented or changed the core \LaTeX{}
functionality in that area (for example, by adding additional
-arguments to the commands in TOC files) the code uses a conservative
+arguments to the commands in \acro{toc} files) the code uses a conservative
approach and the \texttt{\%} signs are added only when certain
conditions are met. Therefore some packages might require updates if
they want to benefit from this correction, especially if they
@@ -262,7 +306,7 @@ the traditional sense.
In a few cases this has some surprising effects
that are not always
for the better. One example is
-standard TOC entries,
+standard \acro{toc} entries,
where you have
heading data followed by some dot leaders and a page
number at the right, produced, for example, from this:
@@ -271,7 +315,7 @@ number at the right, produced, for example, from this:
\end{quote}
The space reserved for the page number is of a fixed width, so that
the dots always end in the same place. Well, they did end in the same
-place until the event of protrusion support in the \TeX{} engines.
+place until the advent of protrusion support in the \TeX{} engines.
Now, with the \pkg{microtype} package loaded, it is possible that the
page number will protrude slightly into the margin (even though it’s
typeset inside a box) and as a result this page number box gets
@@ -282,7 +326,7 @@ question on StackExchange that triggered the correction.
\LaTeX{} now takes care that there will be no protrusion happening on
such lines, even if it is generally enabled for the whole document.
%
-\sxissue{https://tex.stackexchange.com/q/172785}
+\sxissue{q/172785}
@@ -322,9 +366,10 @@ The reason turned out to be a redefinition of the \LaTeX{} command
\cs{nobreakspace} (\verb=~=) inside the class \cls{ltugboat}, which
removed any preceding space (and thus unfortunately also removed the
dots on the continuation line). While one can argue that this is a
-questionable redefinition, it has been in the class so long that
-changing it would certainly break older documents. So instead we now
-guard against that removal of space.
+questionable redefinition (if only done by a single class and not generally),
+it has been in the class so long that changing it would
+certainly break older documents. So instead we now guard against that
+removal of space.
%
\githubissue[s]{25 and 75}
@@ -353,7 +398,7 @@ The \pkg{xr} package has been updated so that the code that reads the
\texttt{.aux} file has been made more robust. It now correctly
ignores conditionals (added by \pkg{hyperref} and other packages)
rather than generating low level parsing errors.
-\sxissue{https://tex.stackexchange.com/a/452321}
+\sxissue{a/452321}
\subsection{Column data for \env{multicols*} sometimes vanished}
@@ -368,7 +413,7 @@ explicitly reinserting that penalty if necessary.
\subsection{Extension to \cs{docolaction} in \pkg{multicol}}
-The \cs{docolaction} command can be used used to carry out actions
+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
@@ -400,7 +445,7 @@ expression. But in more complicated settings involving the \pkg{calc}
package it could break with a low-level error message. This has now
been corrected.
%
-\sxissue{https://tex.stackexchange.com/q/459285}
+\sxissue{q/459285}
@@ -437,7 +482,7 @@ These are:
\item
\LaTeXe{} for authors;
\item
- User's Guide for the \pkg{amsmath}~\cite{amsldoc}.
+ User's Guide for the \pkg{amsmath}~Package~\cite{amsldoc}.
\end{itemize}
They can be found on the website documentation page~\cite{site-doc}.
You will now also find there a typeset version of the full \LaTeXe{}
diff --git a/required/tools/changes.txt b/required/tools/changes.txt
index 532d648..7362854 100644
--- a/required/tools/changes.txt
+++ b/required/tools/changes.txt
@@ -46,7 +46,7 @@ are not part of the distribution.
2018-04-30 Frank Mittelbach <Frank.Mittelbach at latex-project.org>
- * array.dtx Explicity place the row strut inside \\ before
+ * array.dtx Explicitly place the row strut inside \\ before
hitting \cr in case the last cell is a multicolumn cell
(issue 42)
More information about the latex3-commits
mailing list