| 1 |
% \iffalse meta-comment |
| 2 |
% |
| 3 |
% Copyright (C) 2015-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: ltnews24.tex |
| 30 |
% |
| 31 |
% This is issue 24 of LaTeX News. |
| 32 |
|
| 33 |
\documentclass{ltnews} |
| 34 |
\usepackage[T1]{fontenc} |
| 35 |
|
| 36 |
\usepackage{lmodern,url,hologo} |
| 37 |
|
| 38 |
\makeatletter % -- provide command introduced in new release |
| 39 |
% so this typesets with an old format |
| 40 |
|
| 41 |
% Check we are not in the preamble of a composite document |
| 42 |
\def\@tempa{\@latex@error{Can be used only in preamble}\@eha} |
| 43 |
\ifx\DeclareTextCommandDefault\@tempa |
| 44 |
\else |
| 45 |
\DeclareTextCommandDefault\textcommabelow[1] |
| 46 |
{\hmode@bgroup\ooalign{\null#1\crcr\hidewidth\raise-.31ex |
| 47 |
\hbox{\check@mathfonts\fontsize\ssf@size\z@ |
| 48 |
\math@fontsfalse\selectfont,}\hidewidth}\egroup} |
| 49 |
\DeclareTextCommandDefault\textcommaabove[1]{% |
| 50 |
\hmode@bgroup |
| 51 |
\ooalign{% |
| 52 |
\hidewidth |
| 53 |
\raise.7ex\hbox{% |
| 54 |
\check@mathfonts\fontsize\ssf@size\z@\math@fontsfalse\selectfont`% |
| 55 |
}% |
| 56 |
\hidewidth\crcr |
| 57 |
\null#1\crcr |
| 58 |
}% |
| 59 |
\egroup |
| 60 |
} |
| 61 |
\fi |
| 62 |
|
| 63 |
\makeatother |
| 64 |
|
| 65 |
\publicationmonth{February} |
| 66 |
\publicationyear{2016} |
| 67 |
|
| 68 |
\publicationissue{24} |
| 69 |
|
| 70 |
\providecommand\pkg[1]{\texttt{#1}} |
| 71 |
\providecommand\cls[1]{\texttt{#1}} |
| 72 |
\providecommand\option[1]{\texttt{#1}} |
| 73 |
\providecommand\env[1]{\texttt{#1}} |
| 74 |
\providecommand\file[1]{\texttt{#1}} |
| 75 |
|
| 76 |
\begin{document} |
| 77 |
|
| 78 |
\maketitle |
| 79 |
|
| 80 |
\tableofcontents |
| 81 |
|
| 82 |
\section{\hologo{LuaTeX} support} |
| 83 |
|
| 84 |
This release refines the \hologo{LuaTeX} support introduced in the |
| 85 |
2015/10/01 release. A number of patches have been added to improve the |
| 86 |
behavior of \pkg{ltluatex} (thanks largely to code review by Philipp Gesang). |
| 87 |
The kernel code has been adjusted to |
| 88 |
allow for changes in \hologo{LuaTeX} v0.85--v0.88. Most notably, newer |
| 89 |
\hologo{LuaTeX} releases allow more than $16$ write streams and these are now |
| 90 |
enabled for use by \verb|\newwrite|, but also the experimental |
| 91 |
\texttt{newtoken} Lua library has been renamed back to \texttt{token} |
| 92 |
which required small adjustments in the \hologo{LuaTeX} setup. |
| 93 |
|
| 94 |
The biggest change in \hologo{LuaTeX} v0.85--v0.87 compared to previous |
| 95 |
versions is that all the primitives (originally defined in |
| 96 |
\hologo{pdfTeX}) dealing with the PDF ``back end'' |
| 97 |
are no longer defined, being replaced by a much smaller set of new primitives. |
| 98 |
This does not directly affect the core \LaTeX{} |
| 99 |
files in this release but has required major changes to the |
| 100 |
\texttt{.ini} files used by \TeX{} Live and similar distributions to |
| 101 |
set up the format files. These changes in the \hologo{LuaTeX} engine |
| 102 |
will affect any packages using these back end commands (packages such |
| 103 |
as \pkg{graphics}, \pkg{color}, \pkg{hyperref}, etc.). |
| 104 |
Until all contributed packages are updated to the new syntax users may |
| 105 |
need to add aliases for the old \hologo{pdfTeX} commands. A new |
| 106 |
\pkg{luapdftexalias} package has been contributed to CTAN (not part of the |
| 107 |
core \LaTeX\ release) that may be used for this purpose. |
| 108 |
|
| 109 |
See also the sections below for related changes in the |
| 110 |
\textsf{tools} and \textsf{graphics} bundles. |
| 111 |
|
| 112 |
|
| 113 |
\section{Unicode data} |
| 114 |
|
| 115 |
As noted in \LaTeX{} News~22, the 2015/01/01 release of \LaTeX{} introduced |
| 116 |
built-in support for extended \TeX{} systems. In particular, the kernel now |
| 117 |
loads appropriate data from the Unicode Consortium to set \verb|\lccode|, |
| 118 |
\verb|\uccode|, \verb|\catcode| and \verb|\sfcode| values in an automated |
| 119 |
fashion for the entire Unicode range. |
| 120 |
|
| 121 |
The initial approach taken by the team was to incorporate the existing model |
| 122 |
used by (plain) \hologo{XeTeX} and to pre-process the ``raw'' Unicode data into |
| 123 |
a ready-to-use form as \verb|unicode-letters.def|. However, the relationship |
| 124 |
between the Unicode Consortium files and \TeX{} data structures is non-trivial and still |
| 125 |
being explored. As such, it is preferable to directly parse the original |
| 126 |
(\verb|.txt|) files at point of use. The team has therefore ``spun-out'' both |
| 127 |
the data and the loading to a new generic package, \pkg{unicode-data}. This |
| 128 |
package makes the original Unicode Consortium data files available in the |
| 129 |
\verb|texmf| tree (in \verb|tex/generic/unicode-data|) and provides generic |
| 130 |
loaders suitable for reading this data into the plain, \LaTeXe{}, and other, |
| 131 |
formats. |
| 132 |
|
| 133 |
At present, the following data files are included in this new package: |
| 134 |
\begin{itemize}\parskip=0pt |
| 135 |
\item \verb|CaseFolding.txt| |
| 136 |
\item \verb|EastAsianWidth.txt| |
| 137 |
\item \verb|LineBreak.txt| |
| 138 |
\item \verb|MathClass.txt| |
| 139 |
\item \verb|SpecialCasing.txt| |
| 140 |
\item \verb|UnicodeData.txt| |
| 141 |
\end{itemize} |
| 142 |
These files are used either by \LaTeXe{} or by \textsf{expl3} |
| 143 |
(i.e.~they represent the set currently required by the team). The |
| 144 |
Unicode Consortium provides various other data files and we would be happy to add |
| 145 |
these to the generic package, as it is intended to provide a single place |
| 146 |
to collect this material in the \verb|texmf| tree. Such requests can be |
| 147 |
mailed to the team as~usual or logged at the package home page: |
| 148 |
\url{https://github.com/latex3/unicode-data}. |
| 149 |
|
| 150 |
The new approach extends use of Unicode data in setting \TeX{} information in |
| 151 |
two ways. First, the \verb|\sfcode| of all end-of-quotation/closing punctuation |
| 152 |
is now set to $0$ (transparent to \TeX{}). Second, \verb|\Umathcode| values are |
| 153 |
now set using \verb|MathClass.txt| rather than setting up only letters (which |
| 154 |
was done using an arbitrary plane~$0$/plane~$1$ separation). There are also |
| 155 |
minor refinements to the existing code setting, particularly splitting the |
| 156 |
concepts of case and letter/non-letter category codes. |
| 157 |
|
| 158 |
For \hologo{XeTeX}, users should note that \verb|\xtxHanGlue| and |
| 159 |
\verb|\xtxHanSpace| are \emph{no longer defined}, that no assignments are made |
| 160 |
to \verb|\XeTeXinterchartoks| and that no \verb|\XeTeXintercharclass| data is |
| 161 |
loaded into the format. The values which were previously inherited from |
| 162 |
the plain \hologo{XeTeX} setup files are \emph{not} suitable for properly |
| 163 |
typesetting East Asian text. There are third-party packages addressing this |
| 164 |
area well, notably those in the \textsf{CTeX} bundle. Third-party packages |
| 165 |
may need adjustment to load the data themselves; see the \pkg{unicode-data} |
| 166 |
package for one possible loader. |
| 167 |
|
| 168 |
\section{More support for east European accents} |
| 169 |
|
| 170 |
As noted in \LaTeX{} News~23, comma accent support was added for \texttt{s} and |
| 171 |
\texttt{t} in the 2015/10/01 release. In this release a matching |
| 172 |
\verb|\textcommaabove| accent has been added for U+0123 (\verb|\c{g}|, |
| 173 |
\textcommaabove{g}) which is the lower case of U+0122 (\verb|\c{G}|, |
| 174 |
\textcommabelow{G}). In the OT1 and T1 encodings the combinations are |
| 175 |
declared as composites with the \verb|\c| command, which matches the |
| 176 |
Unicode names ``\textsf{latin (capital|small) letter g with cedilla}'' and |
| 177 |
also allows \verb|\MakeUppercase{\c{g}}| to produce \verb|\c{G}|, as |
| 178 |
required. In T1 encoding, the composite of \verb|\c| with \texttt{k}, \texttt{l}, |
| 179 |
\texttt{n} and \texttt{r} are also |
| 180 |
declared to use the comma below accent rather than cedilla to match the |
| 181 |
conventional use of these letters. |
| 182 |
|
| 183 |
The UTF-8 \pkg{inputenc} option \option{utf8} has been extended to |
| 184 |
support all latin combinations that can be reasonably constructed with a |
| 185 |
(single) accent command an a base character for the T1 encoding so |
| 186 |
\textcommaabove{g}, \k{u} and similar characters may be directly input |
| 187 |
using UTF-8 encoding. |
| 188 |
|
| 189 |
\section{Changes in Graphics} |
| 190 |
|
| 191 |
The changes in \hologo{LuaTeX}~v0.87 mean that the \pkg{color} and |
| 192 |
\pkg{graphics} packages no longer share the \file{pdftex.def} file |
| 193 |
between \hologo{LuaTeX} and \hologo{pdfTeX}. A separate file |
| 194 |
\file{luatex.def} (distributed separately) has been produced, and |
| 195 |
distributions are encouraged to modify \file{graphics.cfg} and |
| 196 |
\file{color.cfg} configuration files to default to the \option{luatex} |
| 197 |
option if \hologo{LuaTeX}~v0.87 or later is being used. The team has |
| 198 |
contributed suitable \texttt{.cfg} files to CTAN to be used |
| 199 |
as models. |
| 200 |
|
| 201 |
Normally it is best to let the local \file{graphics.cfg} |
| 202 |
automatically supply the right option depending on the \TeX\ engine |
| 203 |
being used; however the \pkg{color} and \pkg{graphics} (and so |
| 204 |
\pkg{graphicx}) packages have been extended to have an explicit |
| 205 |
\option{luatex} option comparable to the existing \option{pdftex} and |
| 206 |
\option{xetex} options. |
| 207 |
|
| 208 |
The \pkg{trig} package has been updated so that pre-computed values |
| 209 |
such as $\sin(90)$ now expand to digits (\texttt{1} rather than the |
| 210 |
internal token \verb|\@one| in this case). This allows them to be used |
| 211 |
directly in PDF literal strings. |
| 212 |
|
| 213 |
\section{Changes in Tools} |
| 214 |
|
| 215 |
\hologo{LuaTeX} from version v0.87 no longer supports the |
| 216 |
\verb|\write18| syntax to access system commands. A new package |
| 217 |
\pkg{shellesc} has been added to \textsf{tools} that defines a new |
| 218 |
command \verb|\ShellEscape| that may be used in all \TeX\ variants to |
| 219 |
provide a consistent access to system commands. The package also |
| 220 |
defines \verb|\write18| in \hologo{LuaTeX} so that it continues to access |
| 221 |
system commands as before; see the package documentation for details. |
| 222 |
|
| 223 |
\section{Improving support for Unicode engines} |
| 224 |
|
| 225 |
\looseness=-1 |
| 226 |
Stability concerns are always paramount when considering any change to |
| 227 |
the \LaTeXe{} kernel. At the same time, it is important that the format |
| 228 |
remains usable and gives reliable results for users. For the Unicode |
| 229 |
\TeX{} engines \hologo{XeTeX} and \hologo{LuaTeX} there are important |
| 230 |
differences in behavior from classical ($8$-bit) \TeX{} engines which |
| 231 |
mean that identical default behaviors are not appropriate. Over the |
| 232 |
past 18 months the team has addressed the most pressing of these |
| 233 |
considerations (as detailed above and in \LaTeX{} News~22 and 23), |
| 234 |
primarily by integrating existing patches into the kernel. There are, |
| 235 |
though, important areas which still need consideration, and which |
| 236 |
\emph{may} result in refinements to kernel support in this area in |
| 237 |
future releases. |
| 238 |
|
| 239 |
The default font setup in \LaTeXe{} at present is to use the \texttt{OT1} |
| 240 |
encoding. This assumes that hyphenation patterns have been read using |
| 241 |
appropriate codes: the \texttt{T1} encoding is assumed. The commonly-used |
| 242 |
hyphenation patterns today, \texttt{hyph-utf8}, are set up in this |
| 243 |
way for $8$-bit engines (\hologo{pdfTeX}) but for Unicode engines use |
| 244 |
Unicode code points. This means that hyphenation will be incorrect |
| 245 |
with Unicode engines unless a Unicode font is loaded. This requires |
| 246 |
a concept of a Unicode font encoding, which is currently provided by |
| 247 |
the \pkg{fontspec} package in two versions, \texttt{EU1} and |
| 248 |
\texttt{EU2}. The team is working to fully understand what is meant |
| 249 |
by a ``Unicode font encoding'', as unlike a classical \TeX{} encoding |
| 250 |
it is essentially impossible to know what glyphs will be provided |
| 251 |
(though each slot is always defined with the same meaning). There |
| 252 |
is also an overlap between this area and ideas of language and writing |
| 253 |
system, most obviously in documents featuring mixed scripts (for example |
| 254 |
Latin and Cyrillic). |
| 255 |
|
| 256 |
As well as these font considerations, the team is also exploring |
| 257 |
to what extent it is possible to allow existing ($8$-bit) |
| 258 |
documents to compile directly with Unicode engines without requiring |
| 259 |
changes in the sources. Whether this is truly possible remains an open |
| 260 |
question. |
| 261 |
|
| 262 |
It is important to stress that changes will only be made in this area where |
| 263 |
they do \emph{not} affect documents processed with |
| 264 |
\hologo{eTeX}/\hologo{pdfTeX} (i.e.~documents which are written for |
| 265 |
``classical'' $8$-bit \TeX{} engines). Changes will also be made only where |
| 266 |
they clearly address deficiencies in the current setup for Unicode engines |
| 267 |
(i.e.~where current behaviors are wrong). |
| 268 |
|
| 269 |
\end{document} |