| 1 |
% \iffalse meta-comment |
| 2 |
% |
| 3 |
% Copyright (C) 2017-2025 |
| 4 |
% The LaTeX Project and any individual authors listed elsewhere |
| 5 |
% in this file. |
| 6 |
% |
| 7 |
% This file is part of the LaTeX base system. |
| 8 |
% ------------------------------------------- |
| 9 |
% |
| 10 |
% It may be distributed and/or modified under the |
| 11 |
% conditions of the LaTeX Project Public License, either version 1.3c |
| 12 |
% of this license or (at your option) any later version. |
| 13 |
% The latest version of this license is in |
| 14 |
% http://www.latex-project.org/lppl.txt |
| 15 |
% and version 1.3c or later is part of all distributions of LaTeX |
| 16 |
% version 2008 or later. |
| 17 |
% |
| 18 |
% This file has the LPPL maintenance status "maintained". |
| 19 |
% |
| 20 |
% The list of all files belonging to the LaTeX base distribution is |
| 21 |
% given in the file `manifest.txt'. See also `legal.txt' for additional |
| 22 |
% information. |
| 23 |
% |
| 24 |
% The list of derived (unpacked) files belonging to the distribution |
| 25 |
% and covered by LPPL is defined by the unpacking scripts (with |
| 26 |
% extension .ins) which are part of the distribution. |
| 27 |
% |
| 28 |
% \fi |
| 29 |
% Filename: ltnews26.tex |
| 30 |
% |
| 31 |
% This is issue 26 of LaTeX News. |
| 32 |
|
| 33 |
\documentclass{ltnews} |
| 34 |
\usepackage[T1]{fontenc} |
| 35 |
|
| 36 |
\usepackage{lmodern,url,hologo} |
| 37 |
|
| 38 |
\publicationmonth{January} |
| 39 |
\publicationyear{2017} |
| 40 |
|
| 41 |
\publicationissue{26} |
| 42 |
|
| 43 |
\providecommand\pkg[1]{\texttt{#1}} |
| 44 |
\providecommand\cls[1]{\texttt{#1}} |
| 45 |
\providecommand\option[1]{\texttt{#1}} |
| 46 |
\providecommand\env[1]{\texttt{#1}} |
| 47 |
\providecommand\file[1]{\texttt{#1}} |
| 48 |
|
| 49 |
\begin{document} |
| 50 |
|
| 51 |
\maketitle |
| 52 |
\tableofcontents |
| 53 |
|
| 54 |
\setlength\rightskip{0pt plus 3em} |
| 55 |
\section{\eTeX{}} |
| 56 |
|
| 57 |
In \LaTeX{} News~16 (December 2003) the team announced |
| 58 |
\begin{quotation} |
| 59 |
We expect that within the next two years, releases of \LaTeX{} will |
| 60 |
change modestly in order to run best under an extended \TeX{} engine |
| 61 |
that contains the \eTeX{} primitives, e.g., \eTeX{} or pdf\TeX{}. |
| 62 |
\end{quotation} |
| 63 |
and also said |
| 64 |
\begin{quotation} |
| 65 |
Although the current release does not \emph{require} \eTeX{} features, we |
| 66 |
certainly recommend using an extended \TeX{}, especially if you need to debug |
| 67 |
macros. |
| 68 |
\end{quotation} |
| 69 |
|
| 70 |
For many years the team have worked on the basis that users will have \eTeX{} |
| 71 |
available but had not revisited the above statements formally. As of the |
| 72 |
January 2017 release of \LaTeXe{}, \eTeX{} is \emph{required} to build the |
| 73 |
format, and attempting to build a format without the extensions will fail. |
| 74 |
|
| 75 |
Practically, modern \TeX{} distributions provide the extensions in all engines |
| 76 |
other than the ``pure'' Knuth \texttt{tex}, and indeed parts of the |
| 77 |
format-building process already require \eTeX{}, most notably some of the UTF-8 |
| 78 |
hyphenation patterns. As such, there should be no noticeable effect on users of |
| 79 |
this change. |
| 80 |
|
| 81 |
The team expect to make wider use of \eTeX{} within the kernel in future; |
| 82 |
details will be announced where they impact on end users in a visible way. |
| 83 |
|
| 84 |
\section{Default encodings in \hologo{XeLaTeX} and \hologo{LuaLaTeX}} |
| 85 |
The default encoding in \LaTeX\ has always been the original |
| 86 |
128-character encoding \texttt{OT1}. For Unicode based \TeX\ engines, this |
| 87 |
is not really suitable, and is especially problematic with |
| 88 |
\hologo{XeLaTeX} as in the major distributions this is built with |
| 89 |
Unicode based hyphenation patterns in the format. In practice this has |
| 90 |
not been a major problem as documents use the contributed |
| 91 |
\pkg{fontspec} package in order to switch to a |
| 92 |
Unicode encoded font. |
| 93 |
|
| 94 |
In this release we are adding \texttt{TU} as a new supported |
| 95 |
encoding in addition to the previously supported encodings such as \texttt{OT1} |
| 96 |
and \texttt{T1}. This denotes a Unicode based font encoding. It is essentially |
| 97 |
the same as the \texttt{TU} encoding that has been on trial with the |
| 98 |
experimental \option{tuenc} option to \pkg{fontspec} for the past |
| 99 |
year. |
| 100 |
|
| 101 |
The \hologo{XeLaTeX} and \hologo{LuaLaTeX} formats will now default |
| 102 |
to \texttt{TU} encoding and \texttt{lmr} (Latin Modern) family. In the |
| 103 |
case of \hologo{LuaLaTeX} the contributed \texttt{luaotfload} Lua |
| 104 |
module will be loaded at the start of each run to enable the loading |
| 105 |
of OpenType fonts. |
| 106 |
|
| 107 |
The \pkg{fontspec} package is being adjusted in a companion release |
| 108 |
to recognise the new encoding default arrangements. |
| 109 |
|
| 110 |
Note that in practice no font supports the full Unicode range, and so |
| 111 |
\texttt{TU} encoded fonts, unlike fonts specified for \texttt{T1}, may be |
| 112 |
expected to be incomplete in various ways. In the current release the file |
| 113 |
\file{tuenc.def} that implements the \texttt{TU} encoding-specific commands |
| 114 |
has made some basic assumptions for (for example) default handling of |
| 115 |
accent commands, and the set of command names is derived from the |
| 116 |
command names used for the UTF-8 support in the \pkg{inputenc} package, |
| 117 |
restricted roughly to the character ranges classically provided by |
| 118 |
the \texttt{T1} and \texttt{TS1} encodings, but is part of a longer term plan |
| 119 |
seen over recent releases to increase support for Unicode based \TeX\ engines |
| 120 |
into the core \LaTeX\ support. |
| 121 |
|
| 122 |
|
| 123 |
|
| 124 |
If for any reason you need to process a document with the previous |
| 125 |
default \texttt{OT1} encoding, you may switch encoding in the usual ways, for |
| 126 |
example |
| 127 |
\begin{verbatim} |
| 128 |
\usepackage[OT1]{fontenc} |
| 129 |
\end{verbatim} |
| 130 |
or you may roll back all the changes for this release by starting the |
| 131 |
document with |
| 132 |
\begin{verbatim} |
| 133 |
\RequirePackage[2016/12/31]{latexrelease} |
| 134 |
\end{verbatim} |
| 135 |
|
| 136 |
\section{\cs{showhyphens} in \hologo{XeLaTeX}} |
| 137 |
Due to the way \hologo{XeLaTeX} interfaces to font libraries, the |
| 138 |
standard definition of \cs{showhyphens} does not work. A variant |
| 139 |
definition has been available in the contributed \pkg{xltxtra} |
| 140 |
package, however a (slightly different) definition for \cs{showhyphens} |
| 141 |
is now included in \hologo{XeLaTeX} by default. As usual |
| 142 |
this change will be undone if an earlier |
| 143 |
release is specified using the \pkg{latexrelease} package. |
| 144 |
|
| 145 |
\section{The \pkg{fixltx2e} package} |
| 146 |
As described in \LaTeX{} News~22, the \pkg{fixltx2e} package has become |
| 147 |
obsolete with the new update policy. Since 2015 it has just made a |
| 148 |
warning and exited. In this release we have re-introduced all |
| 149 |
the code from the original fixes in the 2014 \LaTeX\ but guarded by |
| 150 |
\verb|\IncludeInRelease{2015/01/01}|. |
| 151 |
So for current releases \pkg{fixltx2e} still just displays a warning |
| 152 |
but for old releases, whether that is an old format, or a format with |
| 153 |
the version date reset via the \pkg{latexrelease} package, the |
| 154 |
fixes in the original \pkg{fixltx2e} will be applied. |
| 155 |
|
| 156 |
This improves the ability to run old documents in a way that is compatible |
| 157 |
with contemporary formats. If you have a 2014 document that used |
| 158 |
\verb|\usepackage{fixltx2e}| and you add |
| 159 |
\verb|\RequirePackage[2014/01/01]{latexrelease}| and process it with the |
| 160 |
current format then \pkg{latexrelease} will undo most changes made |
| 161 |
since 2014, but now when the document includes \pkg{fixltx2e} it |
| 162 |
will act like a 2014 version of the package and apply the code fixes, |
| 163 |
not just give a warning that the package is obsolete. |
| 164 |
|
| 165 |
\section{The \pkg{latexbug} package} |
| 166 |
|
| 167 |
As explained in more detail |
| 168 |
at the \LaTeX\ Project |
| 169 |
website\footnote{\url{https://www.latex-project.org/bugs/}} |
| 170 |
a new package, \pkg{latexbug}, has been produced to help produce |
| 171 |
test files to accompany bug reports on the core \LaTeX\ distribution. |
| 172 |
This is being published separately to CTAN at the same time as this |
| 173 |
release. By using the \pkg{latexbug} package you can easily check |
| 174 |
that the packages involved in the test are all part of the core |
| 175 |
release. The \LaTeX\ project cannot handle bug reports on contributed |
| 176 |
packages, which should be directed to the package maintainer as given |
| 177 |
in the package documentation. |
| 178 |
|
| 179 |
\section{Updates to \pkg{amsmath}} |
| 180 |
The \pkg{amsmath} package has two updates at this release. |
| 181 |
\begin{itemize} |
| 182 |
\item The spacing to the left of the \env{aligned} and |
| 183 |
\env{gathered} environments has been fixed: the spurious thin |
| 184 |
space is no longer added by default. Package options control this |
| 185 |
to revert to the original behaviour where required; see the |
| 186 |
\file{amsldoc} guide for further details. |
| 187 |
\item The large delimiters around generalised fractions (for example |
| 188 |
in the \cs{binom} construct) did not work in previous releases if |
| 189 |
using \hologo{LuaTeX} or \hologo{XeTeX} with OpenType math fonts. This is |
| 190 |
related to the lack of specific metrics for this use in the OpenType Math |
| 191 |
table. In principle \hologo{LuaTeX} has two additional named metrics |
| 192 |
to control the delimiters but these are not initialised by default, |
| 193 |
and in \hologo{XeTeX} it does not seem possible to make them work at all. |
| 194 |
So for Unicode \TeX\ systems, a new implementation of |
| 195 |
\cs{genfrac} is used at this release that uses \verb|\left\right| |
| 196 |
internally but parameterised to give spacing as close to the |
| 197 |
original as possible. The implementation in (pdf)\TeX\ is |
| 198 |
unaffected. |
| 199 |
\end{itemize} |
| 200 |
|
| 201 |
\section{Updates to \textsf{tools}} |
| 202 |
The \pkg{array} package has been updated to fix a longstanding but |
| 203 |
previously unreported issue with unwanted interactions between tables |
| 204 |
in the page head or foot and the body of the page, as reported in |
| 205 |
\href{http://www.latex-project.org/cgi-bin/ltxbugs2html?pr=tools/4488}{PR |
| 206 |
tools/4488}. |
| 207 |
There is also an update to the \hologo{LuaTeX} support in \pkg{bm}. |
| 208 |
|
| 209 |
\section{An addendum to the release changes in 2015: page breaks and vertical spacing} |
| 210 |
|
| 211 |
In 2015 we announced the introduction of the roll-back\slash |
| 212 |
roll-forward concept to manage bug fixes and additions to core |
| 213 |
\LaTeX{} in a manageable way. We also announced at that time |
| 214 |
that we now incorporate all fixes from \pkg{fixltx2e} into the |
| 215 |
kernel (as the old mechanism produced problems instead of improving |
| 216 |
the situation). Refer to |
| 217 |
\href{https://www.latex-project.org/news/latex2e-news/ltnews22.pdf}{\file{ltnews22.pdf}} |
| 218 |
for details. |
| 219 |
|
| 220 |
One of the fixes from \pkg{fixltx2e} was for a glaring bug in |
| 221 |
\cs{addvspace} that was originally detected in the mid-nineties and |
| 222 |
back then added to the \pkg{fixltx2e} support package. In certain |
| 223 |
situations \cs{addvspace} would result in a page/column break below |
| 224 |
the baseline of the last line. As a result documents using |
| 225 |
\cs{flushbottom} would show a clear misalignment (even more prominent |
| 226 |
when typesetting in two-column mode). |
| 227 |
|
| 228 |
Starting with release 2015/01/01 this is now finally corrected already |
| 229 |
in the kernel and not only in \pkg{fixltx2e}. In nearly all |
| 230 |
circumstances this will either make no difference to existing |
| 231 |
documents, or it will locally improve the visual appearance of that |
| 232 |
document without changing anything on other pages. However, by the |
| 233 |
nature of the change it is also possible that there are further |
| 234 |
non-local changes to the page breaks due to the different break |
| 235 |
positions introduced by the fix. |
| 236 |
|
| 237 |
Thus, for documents that have been written before 2015 and that should |
| 238 |
be preserved unchanged at all costs you may have to add |
| 239 |
\begin{verbatim} |
| 240 |
\RequirePackage[2014/01/01]{latexrelease} |
| 241 |
\end{verbatim} |
| 242 |
at the top of the document, to roll back the format to a date before |
| 243 |
the policy change. |
| 244 |
|
| 245 |
\end{document} |