Debian Codegraph @

texmf-dist/doc/latex/base/ltnews36.tex

raw
1 % \iffalse meta-comment
2 %
3 % Copyright (C) 2021-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 % 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: ltnews36.tex
30 %
31 % This is issue 36 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 \makeatletter
105 % maybe not the greatest design but normally we wouldn't have subsubsections
106 \renewcommand{\subsubsection}{%
107 \@startsection {subsubsection}{2}{0pt}{1.5ex \@plus 1ex \@minus .2ex}%
108 {-1em}{\@subheadingfont\colonize}%
109 }
110 \providecommand\colonize[1]{#1:}
111 \makeatother
112
113 \let\finalvspace\vspace % for document layout fixes
114
115 % Undo ltnews's \verbatim@font with active < and >
116 \makeatletter
117 \def\verbatim@font{%
118 \normalsize\ttfamily}
119 \makeatletter
120
121 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
122 \providecommand\tubcommand[1]{}
123 \tubcommand{\input{tubltmac}}
124
125 \publicationmonth{November}
126 \publicationyear{2022} % --- DRAFT version for upcoming release}
127
128 \publicationissue{36}
129
130 \begin{document}
131
132 \tubcommand{\addtolength\textheight{4.2pc}} % only for TUB
133
134 \maketitle
135 {\hyphenpenalty=10000 \exhyphenpenalty=10000 \spaceskip=3.33pt \hbadness=10000
136 \tableofcontents}
137
138 \setlength\rightskip{0pt plus 3em}
139
140
141 \medskip
142
143
144 \section{Introduction}
145
146 The 2022-11 release of \LaTeX{} is largely a consolidation release
147 where we made a number of minor improvements to fix some bugs or
148 improve one or the other interface.
149
150 The only really important functionality that was added is described in
151 the next section: the ability to easily define document-level commands
152 and environments that accept a key/value list in one of its (usually
153 optional) arguments, including the ability to determine if the argument
154 does in fact contain such a key/value list or just a single
155 \enquote{classical} value.
156
157 For the \enquote{Tagged \LaTeX{} Project} this functionality is very
158 important because many document-level commands will need to accept
159 such key/value lists, for example, to specify alternative text or
160 overwrite default tagging if that becomes necessary in a document.
161
162
163 \section{Auto-detecting key/value arguments}
164
165 To allow extension of the core \LaTeX{} syntax, \pkg{ltcmd} now supports
166 a \texttt{={...}}\ modifier when grabbing arguments. This modifier instructs
167 \LaTeX{} that the argument should be passed to the underlying code as
168 a set of key/values. If the argument does not \enquote{look like} a set
169 of key/values, it will be converted into a single key/value pair, with
170 the argument to \texttt{=} specifying the name of that key. For
171 example, the \cs{caption} command could be defined as
172 \begin{verbatim}
173 \DeclareDocumentCommand\caption
174 {s ={short-text}+O{#3} +m}
175 {...}
176 \end{verbatim}
177 which would mean that if the optional argument does \emph{not}
178 contain key/value data, it will be converted to a single key/value
179 pair with the key name \texttt{short-text}.
180
181 Arguments which begin with \texttt{=,} are always interpreted as
182 key/values even if they do not contain further \texttt{=} signs.
183 Any \texttt{=} signs enclosed within \verb|$...$| or \verb|\(...\)|,
184 i.e.~in inline math mode, are ignored, meaning that
185 only \texttt{=} outside of math mode will generally cause
186 interpretation as key/value material.
187
188 In case the argument contains a \enquote{textual} \texttt{=} sign that
189 is mistaken as a key/value indicator you can hide it using a brace
190 group as you would do in other places, e.g.,
191 \begin{verbatim}
192 \caption[{Use of = signs}]
193 {Use of = signs in optional arguments}
194 \end{verbatim}
195 However, because \texttt{=} signs in math mode are already ignored, this
196 should seldom be necessary.
197
198
199 \section{A note for font package developers}
200
201 \subsection{Encoding subsets for \texttt{TS1} encoded fonts}
202
203 The text companion encoding \texttt{TS1} is unfortunately not very
204 faithfully supported in fonts that are not close cousins to the
205 Computer Modern fonts. It was therefore necessary to provide the
206 notion of \enquote{sub-encodings} on a per font basis. These
207 sub-encodings are declared for a font family with the help of a
208 \cs{DeclareEncodingSubset} declaration, see \cite{36:fntguide} for
209 details.
210
211 Maintainers of font bundles that include \texttt{TS1} encoded font
212 files should add an appropriate declaration into the corresponding
213 \texttt{ts1}\textit{family}\texttt{.fd} file, because otherwise the
214 default subencoding is assumed, which is probably disabling too many
215 glyphs that are actually available in the font.\footnote{The \LaTeX{}
216 format contains declarations for many font families already. This
217 was done in 2020 to quickstart the use of the symbols in the kernel,
218 but it is really the wrong place for such declarations. Thus, for
219 new fonts the declarations should be placed into the corresponding
220 \texttt{.fd} files.}
221 %
222 \githubissue{905}
223
224 \section{New or improved commands}
225
226 \subsection{Better language handling for case-changing commands}
227
228 The commands \cs{MakeUppercase}, \cs{MakeLowercase} and \cs{MakeTitlecase} now
229 automatically detect the locale currently in use when \pkg{babel} is loaded.
230 This allows automatic adjustment of letter mappings where appropriate. They
231 also accept a leading optional argument. This accepts a key--value list of
232 control settings. At present, there is one key available: \texttt{locale},
233 which can also be accessed via the alias \texttt{lang}. This is intended to
234 allow local setting of the language, which can be done using a BCP-47
235 descriptor. For example, this could be used to force Turkish case changing in
236 otherwise English input
237 \begin{verbatim}
238 \MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}
239 \end{verbatim}
240 yields
241 \MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}.
242 % RAGIP HULÛS\.I ÖZDEM. %TUB
243
244 \section{Code improvements}
245
246 \subsection{Support for slanted small caps in the EC fonts}
247 For some time \LaTeX{} has supported the combination of the shapes
248 small caps and italic/slanted. The EC fonts contain slanted small caps fonts
249 but using them required the loading of an external package. Suitable font definitions
250 have now been added to \pkg{t1cmd.fd} and so from now on
251 \begin{verbatim}
252 \usepackage[T1]{fontenc}
253 ...
254 \textsc{\textsl{Slanted Small Caps}};
255 \textsc{\textit{Italic Small Caps}};
256 \bfseries
257 \textsc{\textsl{Bold Slanted Small Caps}};
258 \textsc{\textit{Bold Italic Small Caps}}.
259 \end{verbatim}
260 will give the expected result: {\fontfamily{cmr}
261 \textsc{\textsl{Slanted Small Caps}}; \textsc{\textit{Italic Small Caps}};
262 \bfseries
263 \textsc{\textsl{Bold Slanted Small Caps}}; \textsc{\textit{Bold Italic Small Caps}}}.
264
265 Given that the Computer Modern fonts in \texttt{T1} do not have real
266 italic small caps but only slanted small caps, the latter is
267 substituted for the former. This is why both work in the above, but
268 there is no difference between the two (and you get a substitution
269 warning for the \cs{textit}\cs{textsc} shape combination).
270 %
271 \githubissue{782}
272
273
274 \subsection{EC sans serif at small sizes}
275
276 The EC (T1 encoded Computer Modern) sans serif fonts have errors at
277 small sizes: the medium weight is bolder and wider than the bold
278 extended. This makes them unusable at these small sizes. The default
279 \texttt{.fd} file has therefore been adjusted to use a scaled down 8pt
280 font instead.
281 %
282 \githubissue{879}
283
284
285
286 \subsection{Improve font series handling with incorrect \texttt{.fd} files}
287
288 By convention, the font series value is supposed to contain no
289 \texttt{m}, unless you refer to the \enquote{medium} series (which is
290 represented by a single \texttt{m}). For example, one should write
291 \texttt{c} for \enquote{medium weight, condensed width} and not
292 \texttt{mc}. This was one of the many space-conserving methods
293 necessary in the early days of \LaTeXe.
294
295 Some older \texttt{.fd} files
296 do not obey that convention but use \texttt{mc}, \texttt{bm}, etc., in
297 their declarations. As a result, some font selection scheme
298 functionality was not working when confronted with such \texttt{.fd}
299 files. We have therefore augmented \cs{DeclareSymbolFont} and
300 \cs{SetSymbolFont} to strip any surplus \texttt{m} from their series argument
301 so that they do not unnecessarily trigger font
302 substitutions. Regardless of this support such
303 \texttt{.fd} files should get fixed by their maintainers.
304 %
305 \githubissue{918}
306
307
308
309
310 \subsection{Detect nested \texttt{minipage} environments}
311
312 Nesting of \texttt{minipage} environments is only partially supported
313 in \LaTeX{} and can lead to incorrect output, such as overfull boxes
314 or footnotes appearing in the wrong place;
315 see~\cite[p.~106]{36:Lamport}. However, until now there was no warning
316 if that happened. This has been changed and the environment now
317 warns if you nest it in another \texttt{minipage} environment that
318 already contains footnotes.
319 %
320 \githubissue{168}
321
322
323 \subsection{Robust commands in package options}
324 With the standard key-based option handler added in the last release,
325 or with contributed packages offering similar features, users may
326 expect to be able to use a package option such as
327 \verb|[font=\bfseries]|.
328 Previously this failed with internal errors as the option list was
329 expanded via \verb|\edef|. This has now been changed to use the
330 existing command \verb|\protected@edef| so that any \LaTeX\ robust
331 command should be safe to pass to a key value option.
332 %
333 \githubissue{932}
334
335
336
337
338 \subsection{Improve \pkg{l3docstrip} integration into \pkg{docstrip}}
339
340 In 2020 we merged \pkg{l3docstrip.tex} into \pkg{docstrip.tex} to
341 support the \texttt{\%\string<@@=\meta{module}\string>} syntax of
342 \pkg{expl3}; see~\cite{36:ltnews32}. However, this support was
343 incomplete, because it didn't cover \pkg{docstrip} lines of the form
344 \texttt{\%<+...>} or \texttt{\%<-...>}. This was never noticed until
345 now, because usually \texttt{\%<*...>} blocks are used. Now all lines
346 in a \texttt{.dtx} file are subject to the \texttt{@@} replacement
347 approach.
348 %
349 \githubissue{903}
350
351
352
353 \subsection{\LuaTeX\ callback efficiency improvement}
354
355 The mechanism for providing the
356 \texttt{pre/post\_mlist\_to\_hlist\_filter} callbacks in \LuaTeX\ has
357 been improved to make it more reusable and to avoid overhead if these
358 callbacks are not used.
359 %
360 \githubissue{830}
361
362
363 \subsection{Rule-based ordering for \LuaTeX\ callback handlers}
364
365 In \hologo{LuaLaTeX} the callback handlers used to be called in the order
366 in which they were registered in, but this was often rather fragile.
367 It depends a lot on the load order and any attempts to enforce a
368 different order required unregistering and reregistering the handlers to
369 be reordered. Additionally, even if some ordering constraints where
370 enforced that way, another package loaded later could accidentally
371 overwrite it.
372
373 To improve this, we now order the callback handlers based on ordering
374 rules similar to the hook rules.
375
376 When registering a callback which should run before or after another
377 callback, \verb+luatexbase.declare_callback_rule+ can now be used to
378 record this ordering constraint.
379 For example
380 \begin{verbatim}
381 luatexbase.add_to_callback
382 ('pre_shaping_filter', my_handler, 'my_name')
383 luatexbase.declare_callback_rule
384 ('pre_shaping_filter',
385 'my_name', 'before', 'other_name')
386 \end{verbatim}
387 will ensure that \verb+my_handler+ will always be called before the
388 handler registered as \verb+other_name+.
389
390 This also means that the order in which callbacks are registered no
391 longer implicitly defines an order.
392 Code which relied on this implicit order should now define the order
393 rules explicitly.
394
395
396
397 \section{Bug fixes}
398
399 \subsection{Prevent \TeX{} from losing a \cs{smash}}
400
401 When \TeX{} is typesetting a fraction, it will rebox the material in
402 either the numerator or denominator, depending on which is wider. If
403 the repackaged part consists of a single box, that box gets new
404 dimensions and if it was built using a \cs{smash} that effect vanishes
405 (because a smash is nothing other than zeroing some box dimension,
406 which now got undone). For example, in the line
407 \begin{verbatim}
408 \frac{1}{2} = \frac{1}{\smash{2^X}}
409 \neq \frac{100}{\smash{2^X}}
410 \end{verbatim}
411 the $2$ in the denominators was not always at the same vertical position, because
412 the second \cs{smash} was ignored due to reboxing:
413 \vspace{-1.2\baselineskip}
414 \[
415 \makeatletter
416 \def\mathsm@sh#1#2{\setbox\z@\hbox{$\m@th#1{#2}$}\finsm@sh} % old definition
417 \makeatother
418 \newcommand*\drawbaseline{\rlap{\vrule width 60pt height 0.1pt depth 0pt }}
419 \qquad
420 \frac{1}{\drawbaseline2} = \frac{1}{\smash{2^X}} \neq
421 \frac{100}{\smash{2^X}}
422 \pagebreak % not TUB
423 \]
424 The differences are subtle but noticeable.
425 This is now corrected and the \cs{smash} is always
426 honored. Thus now you get this output:
427 \vspace{-1.2\baselineskip}
428 \[
429 \newcommand*\drawbaseline{\rlap{\vrule width 60pt height 0.1pt depth 0pt }}
430 \qquad
431 \frac{1}{\drawbaseline2} = \frac{1}{\smash{2^X}} \neq
432 \frac{100}{\smash{2^X}}
433 \]
434 \par
435 \vspace{-1.5\baselineskip}
436 %
437 \githubissue{517}
438
439
440 \subsection{Resolve an issue with \cs{mathchoice} and \texttt{localalphabets}}
441
442 The code for keeping a number of math alphabets local (introduced in
443 2021; see~\cite{36:ltnews34}) used \cs{aftergroup} to do some cleanup actions after a
444 formula had finished. Unfortunately, \cs{aftergroup} can't be used
445 inside the arguments of the \cs{mathchoice} primitive and as a result one
446 got low-level errors if the freezing happened in such a place. The
447 implementation was therefore revised to avoid the \cs{aftergroup}
448 approach altogether.
449 %
450 \githubissue{921}
451
452 \subsection{Reporting of unused global options when using key/value processing}
453
454 Using the new key/value option processor did not properly report any unused
455 global options when it was used in handling class options. This has now been
456 corrected.
457 %
458 \githubissue{938}
459
460
461 %\section{Changes to packages in the \pkg{amsmath} category}
462
463
464 %\newpage TUB?
465
466 \section{Changes to packages in the \pkg{graphics} category}
467
468 \subsection{Fix a \cs{mathcolor} bug}
469
470 The \cs{mathcolor} command introduced in \cite{36:ltnews35} needs to
471 scan for following sub- and superscripts, but if it did so at the end
472 of an alignment cell, e.g., in a \texttt{array} environment, the
473 \texttt{\&} was evaluated too early, causing some internal errors. This
474 is now properly guarded for.
475 %
476 \githubissue{901}
477
478
479
480 \section{Changes to packages in the \pkg{tools} category}
481
482 \subsection{\pkg{array}: Correctly identify single-line m-cells}
483
484 Cells in m-columns that contain only a single line are supposed to
485 behave like single-line p-cells and align at the same baseline. To
486 test for the condition, \pkg{array} used to compare the height of the cell to
487 the height of the strut used for the table rows. However, the height of that
488 strut depends on the setting of \cs{arraystretch} and if you made this
489 negative (or very large) the test came out wrong. Therefore, we now
490 test against the height of a normal strut to ensure that single-line
491 cells are correctly identified as such (unless their content is truly very
492 tall, in which case aligning is pointless anyway).
493 %
494 \githubissue{766}
495
496
497 %\medskip
498
499 \begin{thebibliography}{9}
500
501 \fontsize{9.3}{11.3}\selectfont
502
503 %\bibitem{36:blueprint} Frank Mittelbach and Chris Rowley:
504 % \emph{\LaTeX{} Tagged PDF \Dash A blueprint for a large project}.\\
505 % \url{https://latex-project.org/publications/indexbyyear/2020/}
506
507 %\bibitem{36:source2e}
508 % \emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
509 % \url{https://latex-project.org/help/documentation/}
510
511 \bibitem{36:Lamport}
512 Leslie Lamport.
513 \newblock {\LaTeX}: {A} Document Preparation System: User's Guide and Reference
514 Manual.
515 \newblock \mbox{Addison}-Wesley, Reading, MA, USA, 2nd edition, 1994.
516 \newblock ISBN 0-201-52983-1.
517 \newblock Reprinted with corrections in 1996.
518
519 \bibitem{36:ltnews32} \LaTeX{} Project Team:
520 \emph{\LaTeXe{} news 32}.\\
521 \url{https://latex-project.org/news/latex2e-news/ltnews32.pdf}
522
523 \bibitem{36:ltnews34} \LaTeX{} Project Team:
524 \emph{\LaTeXe{} news 34}.\\
525 \url{https://latex-project.org/news/latex2e-news/ltnews34.pdf}
526
527 \bibitem{36:ltnews35} \LaTeX{} Project Team:
528 \emph{\LaTeXe{} news 35}.\\
529 \url{https://latex-project.org/news/latex2e-news/ltnews35.pdf}
530
531 \bibitem{36:fntguide} \LaTeX{} Project Team:
532 \emph{\LaTeXe{} font selection}.\\
533 \url{https://latex-project.org/help/documentation/}
534
535 %\bibitem{36:ltfilehook-doc} Frank Mittelbach, Phelype Oleinik, \LaTeX{}~Project~Team:
536 % \emph{The \texttt{\upshape ltfilehook} documentation}.\\
537 % Run \texttt{texdoc} \texttt{ltfilehook-doc} to view.
538 \end{thebibliography}
539
540
541
542 \end{document}