| 1 |
% \iffalse meta-comment |
| 2 |
% |
| 3 |
% Copyright 2023 |
| 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 |
% https://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: ltnews38.tex |
| 30 |
% |
| 31 |
% This is issue 38 of LaTeX News. |
| 32 |
|
| 33 |
\NeedsTeXFormat{LaTeX2e}[2020-02-02] |
| 34 |
|
| 35 |
\documentclass{ltnews} |
| 36 |
|
| 37 |
%% Maybe needed only for Chris' inadequate system: |
| 38 |
\providecommand\Dash {\unskip \textemdash} |
| 39 |
|
| 40 |
%% NOTE: Chris' preferred hyphens! |
| 41 |
%%\showhyphens{parameters} |
| 42 |
%% \hyphenation{because parameters parameter} |
| 43 |
|
| 44 |
\usepackage[T1]{fontenc} |
| 45 |
|
| 46 |
\usepackage{lmodern,url,hologo} |
| 47 |
|
| 48 |
\usepackage{csquotes} |
| 49 |
\usepackage{multicol} |
| 50 |
\usepackage{color} |
| 51 |
|
| 52 |
\providecommand\hook[1]{\texttt{#1}} |
| 53 |
|
| 54 |
\providecommand\meta[1]{$\langle$\textrm{\itshape#1}$\rangle$} |
| 55 |
\providecommand\option[1]{\texttt{#1}} |
| 56 |
\providecommand\env[1]{\texttt{#1}} |
| 57 |
\providecommand\Arg[1]{\texttt\{\meta{#1}\texttt\}} |
| 58 |
|
| 59 |
|
| 60 |
\providecommand\eTeX{\hologo{eTeX}} |
| 61 |
\providecommand\XeTeX{\hologo{XeTeX}} |
| 62 |
\providecommand\LuaTeX{\hologo{LuaTeX}} |
| 63 |
\providecommand\pdfTeX{\hologo{pdfTeX}} |
| 64 |
\providecommand\MiKTeX{\hologo{MiKTeX}} |
| 65 |
\providecommand\CTAN{\textsc{ctan}} |
| 66 |
\providecommand\TL{\TeX\,Live} |
| 67 |
\providecommand\githubissue[2][]{\ifhmode\unskip\fi |
| 68 |
\quad\penalty500\strut\nobreak\hfill |
| 69 |
\mbox{\small\slshape(% |
| 70 |
\href{https://github.com/latex3/latex2e/issues/\getfirstgithubissue#2 \relax}% |
| 71 |
{github issue#1 #2}% |
| 72 |
)}% |
| 73 |
\par\smallskip} |
| 74 |
%% But Chris has to mostly disable \href for his TEXPAD app: |
| 75 |
%% \def\href #1{} % Only For Chris' deficient TeX engine |
| 76 |
|
| 77 |
% simple solution right now (just link to the first issue if there are more) |
| 78 |
\def\getfirstgithubissue#1 #2\relax{#1} |
| 79 |
|
| 80 |
\providecommand\sxissue[1]{\ifhmode\unskip |
| 81 |
\else |
| 82 |
% githubissue preceding |
| 83 |
\vskip-\smallskipamount |
| 84 |
\vskip-\parskip |
| 85 |
\fi |
| 86 |
\quad\penalty500\strut\nobreak\hfill |
| 87 |
\mbox{\small\slshape(\url{https://tex.stackexchange.com/#1})}\par} |
| 88 |
|
| 89 |
\providecommand\gnatsissue[2]{\ifhmode\unskip\fi |
| 90 |
\quad\penalty500\strut\nobreak\hfill |
| 91 |
\mbox{\small\slshape(% |
| 92 |
\href{https://www.latex-project.org/cgi-bin/ltxbugs2html?pr=#1\%2F\getfirstgithubissue#2 \relax}% |
| 93 |
{gnats issue #1/#2}% |
| 94 |
)}% |
| 95 |
\par} |
| 96 |
|
| 97 |
\let\cls\pkg |
| 98 |
\providecommand\env[1]{\texttt{#1}} |
| 99 |
\providecommand\acro[1]{\textsc{#1}} |
| 100 |
|
| 101 |
\vbadness=1400 % accept slightly empty columns |
| 102 |
|
| 103 |
|
| 104 |
\let\finalpagebreak\pagebreak % for TUB (if they use it) |
| 105 |
|
| 106 |
\makeatletter |
| 107 |
% maybe not the greatest design but normally we wouldn't have subsubsections |
| 108 |
\renewcommand{\subsubsection}{% |
| 109 |
\@startsection {subsubsection}{2}{0pt}{1.5ex \@plus 1ex \@minus .2ex}% |
| 110 |
{-1em}{\@subheadingfont\colonize}% |
| 111 |
} |
| 112 |
\providecommand\colonize[1]{#1:} |
| 113 |
\makeatother |
| 114 |
|
| 115 |
\let\finalvspace\vspace % for document layout fixes |
| 116 |
|
| 117 |
% Undo ltnews's \verbatim@font with active < and > |
| 118 |
\makeatletter |
| 119 |
\def\verbatim@font{% |
| 120 |
\normalsize\ttfamily} |
| 121 |
\makeatletter |
| 122 |
|
| 123 |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
| 124 |
\providecommand\tubcommand[1]{} |
| 125 |
\tubcommand{\input{tubltmac}} |
| 126 |
|
| 127 |
\publicationmonth{November} |
| 128 |
%\publicationyear{2023 --- DRAFT version for upcoming release} |
| 129 |
\publicationyear{2023} |
| 130 |
|
| 131 |
\publicationissue{38} |
| 132 |
|
| 133 |
\begin{document} |
| 134 |
|
| 135 |
\tubcommand{\addtolength\textheight{4.2pc}} % only for TUB |
| 136 |
|
| 137 |
\maketitle |
| 138 |
{\hyphenpenalty=10000 \exhyphenpenalty=10000 \spaceskip=3.33pt \hbadness=10000 |
| 139 |
\tableofcontents} |
| 140 |
|
| 141 |
\setlength\rightskip{0pt plus 3em} |
| 142 |
|
| 143 |
\medskip |
| 144 |
|
| 145 |
%\section{Introduction} |
| 146 |
|
| 147 |
|
| 148 |
\section{News from the \enquote{\LaTeX{} Tagged PDF} project} |
| 149 |
|
| 150 |
The multi-year project to automatically tag \LaTeX{} documents in |
| 151 |
order to make them accessible~\cite{38:blueprint} is progressing |
| 152 |
steadily (at this point in time mainly as experimental |
| 153 |
\texttt{latex-lab} code). |
| 154 |
|
| 155 |
Just recently we added support for automatic tagging of tabular |
| 156 |
structures including environments from \pkg{tabularx} and |
| 157 |
\pkg{longtable}. The code is still in its early stages and lacks |
| 158 |
configuration possibilities\Dash these will be added in the future. |
| 159 |
|
| 160 |
\subsection{Approaching an important milestone} |
| 161 |
|
| 162 |
Nevertheless, with this new addition we are more or less able to |
| 163 |
automatically tag any document that confines itself to the commands |
| 164 |
and environments described in Leslie Lamport's \emph{\LaTeX{} |
| 165 |
Manual}~\cite{38:Lamport} by simply adding a single configuration line |
| 166 |
at the top. |
| 167 |
|
| 168 |
In addition, a number of extension packages that go beyond Lamport are |
| 169 |
already supported, most importantly perhaps \pkg{amsmath} (providing |
| 170 |
extended math capabilities) and \pkg{hyperref} (enhancing \LaTeX{} |
| 171 |
with interactive hyperlinking features). |
| 172 |
\finalpagebreak |
| 173 |
Also already supported are |
| 174 |
some of the major bibliography support packages such as \pkg{natbib} |
| 175 |
and \pkg{biblatex}. |
| 176 |
|
| 177 |
For now activation is done through the line |
| 178 |
\begin{verbatim} |
| 179 |
\DocumentMetadata |
| 180 |
{testphase={phase-III,math,table}} |
| 181 |
\end{verbatim} |
| 182 |
The math and the tabular support are not yet incorporated into |
| 183 |
\texttt{phase-III} but need their own activation, so that we can |
| 184 |
better experiment with additions and code adjustments. |
| 185 |
|
| 186 |
The \texttt{latex-lab} bundle contains various (still untagged) |
| 187 |
documentation files about the new code that can be accessed with |
| 188 |
\verb|texdoc -l latex-lab|. |
| 189 |
|
| 190 |
\subsection{A GitHub repository dedicated to the project} |
| 191 |
|
| 192 |
We have also started a new GitHub repository mainly intended for |
| 193 |
reporting issues, and offering a platform for discussions. For |
| 194 |
example, there is one discussion on ways to extend the \LaTeX{} |
| 195 |
\env{tabular} syntax to allow describing the logical structure of |
| 196 |
tables (e.g., which cells are header cells, etc.). |
| 197 |
|
| 198 |
Having all issues and discussions related to the project in a single |
| 199 |
place instead of being spread across multiple repositories such as |
| 200 |
\pkg{latex2e}, \pkg{latex3}, \pkg{tagpdf}, \pkg{hyperref}, |
| 201 |
\pkg{pdfresources}, etc., helps people to find information easily |
| 202 |
and report any issue related to the project without needing to know in which |
| 203 |
code repository the problematic code resides. |
| 204 |
|
| 205 |
You find this repository at |
| 206 |
\url{https://github.com/latex3/tagging-project} and the mentioned |
| 207 |
discussion on \env{tabular} syntax at |
| 208 |
\url{https://github.com/latex3/tagging-project/discussions/1}. |
| 209 |
|
| 210 |
Your feedback is important and reporting what doesn't yet work is |
| 211 |
beneficial to all users, so we hope to see you there and thank you for |
| 212 |
any contribution, whether it is an issue or a post on a discussion |
| 213 |
thread. |
| 214 |
|
| 215 |
|
| 216 |
\section{Hooks, sockets and plugs} |
| 217 |
|
| 218 |
In previous releases of \LaTeX{} we introduced the general concept of |
| 219 |
hooks (both specific and generic ones). These are places in the |
| 220 |
code into which different packages (or the user in the document |
| 221 |
preamble) can safely add their own code to extend the functionality of |
| 222 |
existing commands and environments without the need to overwrite or |
| 223 |
patch them in incompatible ways. An important feature of such hooks is |
| 224 |
that the code chunks added by different packages can be ordered by |
| 225 |
rules, if necessary, |
| 226 |
\finalpagebreak |
| 227 |
thereby avoiding problems arising from |
| 228 |
differences in package loading order. See \LaTeX{} News issues |
| 229 |
32--34~\cite{38:ltnews} for more information. |
| 230 |
|
| 231 |
However, sometimes you need a kind of \enquote{hook} into which only a |
| 232 |
single chunk of code is placed at any time.\footnote{While this is in |
| 233 |
theory possible to model with the existing hook mechanism, it is |
| 234 |
inefficient and cumbersome.} For example, there is code that |
| 235 |
implements footnote placement in relation to bottom floats (above or |
| 236 |
below them). But at any time in the document only one such placement |
| 237 |
code can be in force. Or consider the extra code needed for making |
| 238 |
\LaTeX{} documents accessible (e.g., adding tags to the PDF |
| 239 |
output). Such code is either there (perhaps in alternative versions) |
| 240 |
or not at all, but it cannot have code from other packages added at |
| 241 |
the same point interfering with the algorithm. |
| 242 |
|
| 243 |
For these use cases we now introduce the concept of sockets and plugs. |
| 244 |
A socket is a place in the code into which one can put a plug (a |
| 245 |
chunk of code with a name) after which the socket is in use; to put in |
| 246 |
a different plug, the former one has to be taken out |
| 247 |
first.\footnote{Think of electric outlets and plugging something into |
| 248 |
them.} A socket may or may not have inputs that can then be used by |
| 249 |
the plugs. |
| 250 |
% |
| 251 |
While this is technically not much different to putting a command in |
| 252 |
the code and at some point alter its definition, the advantage is that |
| 253 |
this offers a consistent interface, allows for status information, |
| 254 |
supports tracing, etc. |
| 255 |
|
| 256 |
You declare a new socket and possibly some plugs for it with |
| 257 |
\begin{flushleft} |
| 258 |
\cs{NewSocket}\Arg{socket name}\Arg{\# of inputs} \\ |
| 259 |
\cs{NewSocketPlug}\Arg{socket name}\Arg{plug name}\Arg{code} |
| 260 |
\end{flushleft} |
| 261 |
For example, after the declaration \verb=\NewSocket{foo}{0}= you can |
| 262 |
immediately use this socket in your code with \verb=\UseSocket{foo}=. |
| 263 |
The \cs{NewSocket} declaration automatically defines a simple plug |
| 264 |
with the name \texttt{noop} for the socket and assigns it to the socket |
| 265 |
(plugs it in), thus your \cs{UseSocket} sits idle doing |
| 266 |
nothing\footnote{Sockets with one input also define an |
| 267 |
\texttt{identity} plug and initially assign that to the socket\Dash |
| 268 |
this means that their input is simply returned without processing.} |
| 269 |
until you assign it a different plug, which is done with |
| 270 |
\cs{AssignSocketPlug}. This takes the current plug out and puts the |
| 271 |
new one in. |
| 272 |
% |
| 273 |
All the declarations and commands are also available in the \LaTeX3 |
| 274 |
programming layer as \cs{socket\_new:nn}, \cs{socket\_new\_plug:nnn}, |
| 275 |
etc. |
| 276 |
|
| 277 |
With this concept we can, for example, add tagging support for the |
| 278 |
\enquote{\LaTeX{} Tagged PDF} project to various packages without |
| 279 |
altering their behavior if the tagging code is inactive. Activating |
| 280 |
one or the other form of tagging then just means to assign named plugs |
| 281 |
to the different sockets. |
| 282 |
|
| 283 |
This is just a brief introduction to the mechanism; for more detailed |
| 284 |
documentation see \texttt{texdoc ltsockets-doc}. |
| 285 |
|
| 286 |
|
| 287 |
\finalpagebreak |
| 288 |
|
| 289 |
\section{Document properties and cross-referencing} |
| 290 |
|
| 291 |
Traditional \LaTeX{} uses \cs{label}\Arg{key} to record the values of two |
| 292 |
\enquote{local} properties of the document: the textual |
| 293 |
representations of the \emph{current page number} and the |
| 294 |
\emph{current \textup{\cs{ref}} value} set by \cs{refstepcounter} |
| 295 |
declarations~\cite[p.~209]{38:Lamport}. (These declarations are |
| 296 |
issued, for example, by sectioning commands, by numbered environments |
| 297 |
like \env{equation}, and by \cs{item} in an \env{enumerate} or |
| 298 |
similar environment.) |
| 299 |
|
| 300 |
These two recorded values can then be accessed and typeset (from |
| 301 |
anywhere in the next run of the document) by use of the |
| 302 |
(non-expandable) commands \cs{ref} and \cs{pageref} using the |
| 303 |
\emph{key} that was specified as the argument to \cs{label} when |
| 304 |
recording these values. This supported basic cross-referencing |
| 305 |
(within a document), using these recorded values to provide both |
| 306 |
page-related and counter-related information (such as the page xvii or |
| 307 |
the subsection number 4.5.2).\footnote{In the Spring 2023 release of |
| 308 |
\LaTeX{}, the \cs{label} command was extended to record, in addition, |
| 309 |
both a title (such as the text used in a section head) and the |
| 310 |
\emph{logical name} used for an associated link target provided these |
| 311 |
have been set by packages such as \pkg{nameref} or \pkg{hyperref}.} |
| 312 |
|
| 313 |
|
| 314 |
Over the years \LaTeX{} packages have appeared that extend |
| 315 |
this basic \enquote{label-ref system} in various ways. |
| 316 |
% |
| 317 |
For example, the \pkg{refcount} package made a small but significant change |
| 318 |
to the functions used to access recorded values, by making them expandable. |
| 319 |
And the \pkg{smart-ref} package supports the storage of a larger |
| 320 |
collection of counter values so that, for example, a cross-reference |
| 321 |
can refer to the relevant chapter together with an equation tag. |
| 322 |
The \pkg{cleveref} package stores (by means of a second, internal |
| 323 |
\enquote{logical label}) extra information such as the name of the counter. |
| 324 |
The \pkg{hyperref} package adds the \cs{autoref} command, which |
| 325 |
tries to retrieve the name of a counter from the \emph{logical name} |
| 326 |
used for a link target. |
| 327 |
The \pkg{tikzmarks} library records information about |
| 328 |
\emph{labelled positions} on the page when using \pkg{tikz}. |
| 329 |
Finally, the \pkg{zref} package implements many related ideas, including a general |
| 330 |
idea of properties and lists of properties, with methods to record, and |
| 331 |
subsequently access, the value of any declared property. |
| 332 |
|
| 333 |
|
| 334 |
Starting with this release, the \LaTeX{} kernel provides handling of |
| 335 |
general document properties as a core functionality with standard |
| 336 |
interfaces. |
| 337 |
% |
| 338 |
This is based on concepts introduced by the \pkg{zref} package but |
| 339 |
with some differences in detail, particularly in the implementation. |
| 340 |
It supports the declaration of new properties, and the recording of |
| 341 |
the values of any list of properties. These values are retrieved |
| 342 |
expandably. |
| 343 |
|
| 344 |
To set up a new property that is the current chapter |
| 345 |
number, for example, here is the declaration to use. |
| 346 |
\begin{verbatim} |
| 347 |
\NewProperty{chapter}{now}{?}{\thechapter} |
| 348 |
\end{verbatim} |
| 349 |
\par\finalpagebreak\noindent |
| 350 |
The second argument means that the property value will be recorded |
| 351 |
immediately (\enquote{now}), and not \enquote{during the next |
| 352 |
\cs{shipout}}. The third argument sets a default to be used when, |
| 353 |
for example, an unknown label is supplied. |
| 354 |
% |
| 355 |
The final argument contains the code that will, as part of the |
| 356 |
recording process, be expanded to obtain the value to record for this |
| 357 |
property. |
| 358 |
|
| 359 |
Then, to record the value of this new property, |
| 360 |
together with others, use this command. |
| 361 |
\begin{verbatim} |
| 362 |
\RecordProperties{mylabel} |
| 363 |
{chapter,page,label} |
| 364 |
\end{verbatim} |
| 365 |
This records the current values for the properties \texttt{chapter}, |
| 366 |
\texttt{page}, and \texttt{label}, using \texttt{mylabel} as the |
| 367 |
label, or \emph{key}, for the record. |
| 368 |
|
| 369 |
To \emph{reference} (i.e., retrieve) this recorded value for use in a |
| 370 |
cross-reference to this chapter, use the \cs{RefProperty} command with |
| 371 |
two arguments: the label, or \emph{key}, and the property. |
| 372 |
\begin{verbatim} |
| 373 |
\RefProperty{mylabel}{chapter} |
| 374 |
\end{verbatim} |
| 375 |
|
| 376 |
The |
| 377 |
\LaTeX{} kernel itself contains |
| 378 |
declarations for some generally useful properties, |
| 379 |
including these: |
| 380 |
\begin{description} |
| 381 |
\item[\texttt{label}] the textual representation of the \emph{current |
| 382 |
\textup{\cs{ref}} value}, see above; |
| 383 |
|
| 384 |
\item[\texttt{page}] the textual representation of the page number for |
| 385 |
the page currently under construction; |
| 386 |
|
| 387 |
\item[\texttt{title}] the title, if set by, e.g.,~\pkg{nameref}; |
| 388 |
|
| 389 |
\item[\texttt{target}] the logical name of the associated link target, |
| 390 |
if set by, e.g.,~\pkg{hyperref}; |
| 391 |
|
| 392 |
\item[\texttt{pagetarget}] the logical name of the target added by |
| 393 |
\pkg{hyperref} at the origin of each shipped out page; |
| 394 |
|
| 395 |
\item[\texttt{pagenum}] the value of the \LaTeX{} counter |
| 396 |
\texttt{page} in Arabic numerals; |
| 397 |
|
| 398 |
\item[\texttt{abspage}] the absolute page number of the page under |
| 399 |
construction, i.e., one more than the number of pages shipped out so |
| 400 |
far (thus it starts at 1 and is increased by 1 whenever a page is |
| 401 |
shipped out); |
| 402 |
|
| 403 |
\item[\texttt{counter}] the name of the counter that produced the |
| 404 |
\emph{current \textup{\cs{ref}} value}, i.e., the counter that was |
| 405 |
stepped in the most recent \cs{refstepcounter} within the current |
| 406 |
scope; |
| 407 |
|
| 408 |
\item[\texttt{xpos}, \texttt{ypos}] the position on the shipped out |
| 409 |
page as set by the most recent \cs{pdfsavepos}: recording these |
| 410 |
properties should be done as soon as possible after saving the |
| 411 |
position. |
| 412 |
\end{description} |
| 413 |
|
| 414 |
Both \LaTeXe{} commands (using camel-case names) and |
| 415 |
\LaTeX3 programming layer commands are provided. |
| 416 |
% |
| 417 |
For a more complete documentation, see \texttt{texdoc ltproperties-doc}. |
| 418 |
|
| 419 |
|
| 420 |
|
| 421 |
\finalpagebreak |
| 422 |
|
| 423 |
\section{New or improved commands} |
| 424 |
|
| 425 |
\subsection{Testing for the \LaTeX3 programming layer version: \cs{IfExplAtLeastTF}} |
| 426 |
|
| 427 |
The integration of \pkg{expl3} (the \LaTeX3 programming layer) |
| 428 |
into the kernel means that programmers can use all of the features |
| 429 |
available without needing to load it explicitly. However, as \pkg{expl3} |
| 430 |
is upgraded separately from \LaTeXe{} and is not a separate package, its |
| 431 |
version is different from that of \LaTeXe{} and cannot be tested using |
| 432 |
\cs{IfPackageAtLeastTF}. To date, low-level methods have therefore |
| 433 |
been needed to check for the availability of features in |
| 434 |
\pkg{expl3}. We have now added \cs{IfExplAtLeastTF} as a test working |
| 435 |
in the same way as \cs{IfPackageAtLeastTF} but focused on the |
| 436 |
pre-loaded programming layer. Programmers can check the date of |
| 437 |
\pkg{expl3} they are using in the \texttt{.log}, as it appears both at |
| 438 |
the start and end in the format |
| 439 |
\begin{verbatim} |
| 440 |
L3 programming layer <YYYY-MM-DD> |
| 441 |
\end{verbatim} |
| 442 |
just after the line which identifies the format (\texttt{LaTeX2e}, etc.). |
| 443 |
% |
| 444 |
\githubissue{1004} |
| 445 |
|
| 446 |
|
| 447 |
\section{Code improvements} |
| 448 |
|
| 449 |
\subsection{Support for tabs in \cs{verb*} and \env{verbatim*}} |
| 450 |
|
| 451 |
\LaTeX{} converts a single tab to a single space, which is then treated like a |
| 452 |
\enquote{real} space in typesetting. The same has been true to date inside |
| 453 |
\cs{verb}, but was done in a way that meant that they remained as normal spaces |
| 454 |
even in \cs{verb*}, etc. We have now adjusted the code so that tabs are |
| 455 |
retained within the argument to \cs{verb} and \cs{verb*}, and the |
| 456 |
\env{verbatim} and \env{verbatim*} environments, independently from |
| 457 |
spaces, and are set up to print in the same way spaces do. This means that they |
| 458 |
now generate visible spaces inside \cs{verb*} and \env{verbatim*}, and their |
| 459 |
behavior can be adjusted if required to be different from that of spaces. |
| 460 |
% |
| 461 |
\githubissue{1085} |
| 462 |
|
| 463 |
|
| 464 |
\subsection{Improved argument checking for box commands} |
| 465 |
Previously if an alignment option had an unexpected value, such as |
| 466 |
\verb|\makebox[4cm][x]{text}|, |
| 467 |
no warning was given but the box content was silently discarded. |
| 468 |
This will now produce a warning and act like the default \texttt{c} alignment. |
| 469 |
\cs{framebox} and \cs{parbox} have a similar change. |
| 470 |
% |
| 471 |
\githubissue{1072} |
| 472 |
|
| 473 |
|
| 474 |
\subsection{Aligning status of tilde with other active characters} |
| 475 |
|
| 476 |
Some time ago we revised the definition of active characters in \pdfTeX{} to |
| 477 |
allow the full range of UTF-8 codepoints to be used in for example labels, |
| 478 |
file names, etc. However, \verb|~| was not changed at that point as it is active |
| 479 |
independent of the engine in use. This has now been corrected: the definition |
| 480 |
of \verb|~| is an engine-protected one which gives the string version of the |
| 481 |
character if used inside a csname. |
| 482 |
|
| 483 |
\finalpagebreak |
| 484 |
|
| 485 |
\subsection{In the programming layer} |
| 486 |
|
| 487 |
In the programming layer (\pkg{expl3}), we have revised the behavior of the |
| 488 |
titlecasing function to enable this to either titlecase only the first word of |
| 489 |
the input, or to titlecase every word. This should be transparent at the |
| 490 |
document level but will be useful for programmers. |
| 491 |
|
| 492 |
We have also added the ability to define variables and functions inside |
| 493 |
\cs{fpeval} (at the \pkg{expl3} level this is \cs{fp\_eval:n}). This allows |
| 494 |
programmers to create non-standard functions that can then be used inside |
| 495 |
\cs{fpeval}. For example, this could be used to create a new function |
| 496 |
\texttt{dinner}: |
| 497 |
\begin{verbatim} |
| 498 |
\ExplSyntaxOn |
| 499 |
\fp_new_variable:n{duck} |
| 500 |
\fp_new_function:n{dinner} |
| 501 |
\fp_set_function:nnn{dinner}{duck} |
| 502 |
{duck - 0.25 * duck} |
| 503 |
\fp_set_variable:nn{duck}{1} |
| 504 |
$\fp_eval:n{duck} |
| 505 |
>\fp_eval:n{dinner(duck)} |
| 506 |
\fp_set_variable:nn{duck}{dinner(duck)} |
| 507 |
>\fp_eval:n{dinner(duck)} |
| 508 |
\fp_set_variable:nn{duck}{dinner(duck)} |
| 509 |
>\fp_eval:n{dinner(duck)} |
| 510 |
\fp_set_variable:nn{duck}{dinner(duck)} |
| 511 |
>\fp_eval:n{dinner(duck)} |
| 512 |
$ |
| 513 |
\ExplSyntaxOff |
| 514 |
\end{verbatim} |
| 515 |
|
| 516 |
The computation above would then generate |
| 517 |
\begin{quote} |
| 518 |
\ExplSyntaxOn |
| 519 |
\fp_new_variable:n{duck} |
| 520 |
\fp_new_function:n{dinner} |
| 521 |
\fp_set_function:nnn{dinner}{duck} |
| 522 |
{duck - 0.25 * duck} |
| 523 |
\fp_set_variable:nn{duck}{1} |
| 524 |
$\fp_eval:n{duck} |
| 525 |
>\fp_eval:n{dinner(duck)} |
| 526 |
\fp_set_variable:nn{duck}{dinner(duck)} |
| 527 |
>\fp_eval:n{dinner(duck)} |
| 528 |
\fp_set_variable:nn{duck}{dinner(duck)} |
| 529 |
>\fp_eval:n{dinner(duck)} |
| 530 |
\fp_set_variable:nn{duck}{dinner(duck)} |
| 531 |
>\fp_eval:n{dinner(duck)} |
| 532 |
$ |
| 533 |
\ExplSyntaxOff |
| 534 |
\end{quote} |
| 535 |
|
| 536 |
Users will be able to access added functions without needing to use the |
| 537 |
\pkg{expl3} layer. It is possible that a future release of \LaTeX{} will |
| 538 |
add the ability to create and set floating point variables at the |
| 539 |
document level: this will be examined based on feedback on the |
| 540 |
utility of the programming layer change. |
| 541 |
|
| 542 |
|
| 543 |
\section{\emph{Removed} kernel commands} |
| 544 |
|
| 545 |
It is very rare that commands are removed from the \LaTeX{} kernel. However, in |
| 546 |
this release we have elected to remove \cs{GetDocumentCommandArgSpec}, |
| 547 |
\cs{GetDocumentEnvironmentArgSpec}, \cs{ShowDocumentCommandArgSpec} and |
| 548 |
\cs{ShowDocumentEnvironmentArgSpec} from the kernel. These commands have been |
| 549 |
moved back to the \enquote{stub} \pkg{xparse} provided in \pkg{l3packages}. The |
| 550 |
reason for this change is that the removed commands exposed implementation |
| 551 |
details. They were essentially debugging tools which with hindsight should |
| 552 |
not have been made available directly in the kernel. |
| 553 |
|
| 554 |
|
| 555 |
% \section{Bug fixes} |
| 556 |
|
| 557 |
\finalpagebreak |
| 558 |
|
| 559 |
\section{Changes to packages in the \pkg{tools} category} |
| 560 |
|
| 561 |
\subsection{\pkg{longtable}: correct p-column definition} |
| 562 |
|
| 563 |
In general the \pkg{longtable} implementation follows the \pkg{array} |
| 564 |
usage but the package didn't take over a change made 1992 in |
| 565 |
\pkg{array} which adjusted the handling of the strut inserted at the |
| 566 |
begin of p-columns. As a consequence there are a number of |
| 567 |
inconsistencies in the output of p-columns between \pkg{tabular} and |
| 568 |
\pkg{longtable}. This has been corrected; \pkg{longtable} now uses for |
| 569 |
the strut the same definition as \pkg{array}. |
| 570 |
% |
| 571 |
\githubissue{1128} |
| 572 |
|
| 573 |
\medskip |
| 574 |
\tubcommand{\newpage} |
| 575 |
|
| 576 |
\begin{thebibliography}{9} |
| 577 |
|
| 578 |
%\fontsize{9.3}{11.3}\selectfont |
| 579 |
|
| 580 |
|
| 581 |
\bibitem{38:Lamport} |
| 582 |
Leslie Lamport. |
| 583 |
\newblock \emph{{\LaTeX}: {A} Document Preparation System: User's Guide and Reference |
| 584 |
Manual}. |
| 585 |
\newblock \mbox{Addison}-Wesley, Reading, MA, USA, 2nd edition, 1994. |
| 586 |
\newblock ISBN 0-201-52983-1. |
| 587 |
\newblock Reprinted with corrections in 1996. |
| 588 |
|
| 589 |
|
| 590 |
\bibitem{38:ltnews} \LaTeX{} Project Team. |
| 591 |
\emph{\LaTeXe{} news 1--38}.\\ |
| 592 |
\url{https://latex-project.org/news/latex2e-news/ltnews.pdf} |
| 593 |
|
| 594 |
\bibitem{38:blueprint} Frank Mittelbach and Chris Rowley. |
| 595 |
\emph{\LaTeX{} Tagged PDF \Dash A blueprint for a large project}.\\ |
| 596 |
\url{https://latex-project.org/publications/indexbyyear/2020/} |
| 597 |
|
| 598 |
|
| 599 |
|
| 600 |
\end{thebibliography} |
| 601 |
|
| 602 |
\end{document} |