Debian Codegraph @

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

raw
1 % \iffalse meta-comment
2 %
3 % Copyright (C) 2019-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: ltnews30.tex
30 %
31 % This is issue 30 of LaTeX News.
32
33 \documentclass{ltnews}
34 \usepackage[T1]{fontenc}
35
36 \usepackage{lmodern,url,hologo}
37
38 \usepackage{csquotes}
39
40 \providecommand\acro[1]{\textsc{#1}}
41 \providecommand\meta[1]{$\langle$\textit{#1}$\rangle$}
42 \providecommand\option[1]{\texttt{#1}}
43 \providecommand\env[1]{\texttt{#1}}
44
45
46 \providecommand\XeTeX{\hologo{XeTeX}}
47 \providecommand\LuaTeX{\hologo{LuaTeX}}
48 \providecommand\pdfTeX{\hologo{pdfTeX}}
49 \providecommand\MiKTeX{\hologo{MiKTeX}}
50 \providecommand\CTAN{\textsc{ctan}}
51 \providecommand\TL{\TeX\,Live}
52 \providecommand\githubissue[2][]{\ifhmode\unskip\fi
53 \quad\penalty500\strut\nobreak\hfill
54 \mbox{\small\slshape(%
55 \href{https://github.com/latex3/latex2e/issues/\getfirstgithubissue#2 \relax}%
56 {github issue#1 #2}%
57 )}%
58 \par\smallskip}
59
60 % simple solution right now (just link to the first issue if there are more)
61 \def\getfirstgithubissue#1 #2\relax{#1}
62
63 \providecommand\sxissue[1]{\ifhmode\unskip\fi
64 \quad\penalty500\strut\nobreak\hfill
65 \mbox{\small\slshape(\url{https://tex.stackexchange.com/#1})}\par}
66
67 \providecommand\gnatsissue[2]{\ifhmode\unskip\fi
68 \quad\penalty500\strut\nobreak\hfill
69 \mbox{\small\slshape(%
70 \href{https://www.latex-project.org/cgi-bin/ltxbugs2html?pr=#1\%2F#2}%
71 {gnats issue #1/#2}%
72 )}%
73 \par}
74
75 \let\cls\pkg
76 \providecommand\env[1]{\texttt{#1}}
77
78 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
79 \iffalse % only for TUB production
80 \usepackage{graphicx}
81 \makeatletter
82 % Xe\TeX{} requires reflecting the first E, hence we complain if the
83 % graphics package is not present. (For plain documents, this can be
84 % loaded via Eplain.) Also, at Barbara's suggestion, if the current
85 % font is slanted, we rotate by 180 instead of reflecting so there is at
86 % least a chance to look ok. (The magic values here seem more or less
87 % ok for \texttt{cmsl} and \texttt{cmti}.)
88 %
89 % \begin{macrocode}
90 \def\tubreflect#1{%
91 \@ifundefined{reflectbox}{%
92 \TBerror{A graphics package must be loaded for \string\XeTeX}%
93 }{%
94 \ifdim \fontdimen1\font>0pt
95 \raise 1.6ex \hbox{\kern.1em\rotatebox{180}{#1}}\kern-.1em
96 \else
97 \reflectbox{#1}%
98 \fi
99 }%
100 }
101 \def\tubhideheight#1{\setbox0=\hbox{#1}\ht0=0pt \dp0=0pt \box0 }
102 \def\XekernbeforeE{-.125em}
103 \def\XekernafterE{-.1667em}
104 \DeclareRobustCommand{\Xe}{\leavevmode
105 \tubhideheight{\hbox{X%
106 \setbox0=\hbox{\TeX}\setbox1=\hbox{E}%
107 \ifdim \fontdimen1\font>0pt \def\XekernbeforeE{0em}\fi
108 \lower\dp0\hbox{\raise\dp1\hbox{\kern\XekernbeforeE\tubreflect{E}}}%
109 \kern\XekernafterE}}}
110 \def\XeTeX{\Xe\TeX}
111 \def\XeLaTeX{\Xe{\kern.11em \LaTeX}}
112 \fi
113 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
114
115 \publicationmonth{October}
116 \publicationyear{2019}
117
118 \publicationissue{30}
119
120 \begin{document}
121
122 %\addtolength\textheight{4.2pc} % only for TUB
123
124 \maketitle
125 \tableofcontents
126
127 \setlength\rightskip{0pt plus 3em}
128
129 %\newpage
130
131 \medskip
132
133
134 %%CCC Does it need an intro?
135 %% \section{Introduction}
136
137 %% This document is under construction \ldots
138
139
140 \section{\LaTeX\texttt{-dev} formats now available}
141
142
143 We know that many of you, especially developers and maintainers of
144 important packages, have a strong interest in a stable \LaTeX{}
145 environment.
146
147 In order to keep \LaTeX{} very stable for users whilst allowing for
148 further development to continue, we now have a development branch of
149 \LaTeX{} on GitHub containing development code for the upcoming
150 release. When this code is ready for wider consumption and testing, we
151 generate a pre-release of \LaTeX{} from this development branch and make
152 it available on \CTAN.
153
154 For users of the \TL{} and \MiKTeX{} distributions it is therefore now
155 straightforward to test their documents and code against the upcoming
156 \LaTeX{} release with ease, simply by selecting a different program name
157 (when using the command line) or by selecting a menu entry (after
158 setting it up; see below).
159
160 If you do this then the latest version of the \LaTeX{} development format
161 will be used to process your document, allowing you to test the
162 upcoming release with your own documents and packages. For example, if
163 you run
164 \begin{verbatim}
165 pdflatex-dev myfile
166 \end{verbatim}
167 then you will be greeted on the screen with something like \texttt{LaTeX2e
168 <2019-10-01> pre-release-2} (identifying the pre-release format)
169 instead of the normal \texttt{LaTeX2e <2018-12-01>}. In this
170 pre-release you will find the latest new features that we have
171 developed.
172
173 \subsection{Our hopes}
174
175 We don’t expect everybody to start using the development formats to
176 participate in testing, but we hope that people with a strong interest
177 in a stable \LaTeX{} environment (especially developers and maintainers
178 of important packages) will use the new facilities and help us to
179 ensure that future public releases of \LaTeX{} do not (as has happened in
180 the past) require some immediate patches because of issues that were
181 not identified by our internal regression test suite or by other
182 testing
183 we do.
184
185 Any issue identified when using the development format should
186 preferably be logged as an issue on GitHub, following the procedure
187 outlined on our website at \url{https://www.latex-project.org/bugs/}
188 including the use of the \pkg{latexbug} package as described.
189
190 Our bug reporting process normally states that issues involving
191 third-party software are out of scope as we can’t correct external
192 packages; see~\cite{30:Mittelbach:TB39-1}. However, in the particular
193 case of the development format showing an incompatibility with a
194 third-party package, it is fine to open an issue with us (in addition,
195 please, to informing the maintainer of that package) so that we know
196 about the problem and can jointly work on resolving it.
197
198 \subsection{Details please \ldots}
199
200 More details and some background information about the concepts and
201 the process are available in an upcoming \textsl{TUGboat} article: \enquote{The
202 \LaTeX{} release workflow and the \LaTeX{} dev
203 formats}~\cite{devformat}.
204
205 \subsection{Setting up menu items}
206
207 While the command line call works out of the box if you have a recent
208 \TL{} or \MiKTeX{} installation, its use within an integrated
209 editing environment doesn’t at this point in time (maybe the
210 developers of these editors will include it in the future). However,
211 it is normally fairly simple to enable it as most (or even all?)\ of
212 them provide simple ways to call your own setup. How this works in
213 detail depends very much on the environment you use, so we can’t give
214 much help here.
215
216 But as an example: to provide an additional menu entry for
217 \texttt{XeLaTeX-dev} on a MacBook all that is necessary is to copy
218 the file \texttt{XeLaTeX.engine} to \texttt{XeLaTeX-dev.engine} and change the
219 call from \texttt{xelatex} to \texttt{xelatex-dev} inside.
220
221
222
223
224 \section{Improving Unicode handling in \pdfTeX{}}
225
226 Perhaps the most important improvement in this release is
227 even
228 better support for \acro{utf}-8 characters when using \pdfTeX{}.\footnote{The
229 Japanese engines e-p\TeX{} and e-up\TeX{} can't use these features
230 yet as they don't support the primitive \cs{ifincsname}. Work is
231 under way to resolve this in the engines.}
232
233 When using a \enquote{Unicode engine},
234 any Unicode character (that is not acting as a command,
235 i.e., is not \enquote{active})
236 can be used as part of the
237 \cs{label}/\cs{ref} mechanism or can be displayed in a message or
238 written to a file. In 8-bit engines, however, this was severely
239 restricted:
240 essentially you had to limit yourself to using
241 \acro{ascii} letters, digits and a few punctuation symbols. With the
242 new release, most of these restrictions have been removed and you now
243 can write labels such as
244 \begin{verbatim}
245 \label{eq:größer}
246 \end{verbatim}
247 or use accented characters, etc., as part of a \cs{typeout} message.
248 The only requirement remaining is that only those \acro{utf}-8 characters
249 that are also available for typesetting can be used, i.e., only those
250 characters for
251 which adequate font support is loaded. Otherwise you will get an
252 error message stating that
253 the
254 particular Unicode character is not set
255 up for use with \LaTeX{}.
256
257 Note, however, that the restrictions on what characters can be
258 used in the names of commands have not changed.
259
260 What is not possible when using
261 an 8-bit engine such as \pdfTeX{} is to use
262 characters other than \acro{ascii} letters as part of a command
263 name. This is due to the fact that all other characters in such
264 engines are not single character tokens, but in fact consist of a
265 sequence of bytes and this is not supported in command names.
266
267 \section{Improving file name handling in \pdfTeX{}}
268
269 A related change is that file names used as part of \cs{input},
270 \cs{includegraphics}, etc., commands
271 can now contain any
272 Unicode characters allowed by the file system in use,
273 including spaces.
274 In this case,
275 even characters that can't be typeset
276 (due to lack of font support) can be used.
277
278
279 \section{Improving the \env{filecontents} environment}
280
281 The \env{filecontents} environment now supports an optional argument
282 in which you can specify that it is allowed to \option{overwrite} an
283 already existing file;
284 by default nothing is written if a file with the given name
285 exists anywhere in the search tree. An alternative name for this
286 option is \option{force}.
287 Even then the environment will refuse to write
288 to \cs{jobname}\texttt{.tex} to avoid clobbering its own input
289 file. However, if you use a different extension on your input file you
290 could still overwrite it (there is no way to test for that).
291
292 There is also an
293 option
294 \option{nosearch},
295 which specifies that only the current directory is
296 examined for an existing file, not the whole \TeX{} inputs tree.
297 This is useful if you want to write a
298 local copy of a standard system file.
299 Finally, \option{noheader} prevents writing a preamble to the file
300 (this
301 is the same as using the star form of the environment).
302
303 Another change is that this
304 environment is
305 now allowed anywhere in the document,
306 which means
307 it provides everything (and more) of what the now obsolete
308 \pkg{filecontents} package provided.
309
310
311
312 \section{Making more user commands robust}
313
314 In the early days of \LaTeX{} many commands were fragile, i.e., they
315 needed \cs{protect} in front of them when used in places such as
316 section headings and other \enquote{moving arguments}, etc.
317 In \LaTeXe{} many of these commands were made robust,
318 but still a fairly large number remained unnecessarily fragile.
319
320 In this release of \LaTeX{} we have now
321 made a lot more commands robust.
322 There is a very small collection of commands that must stay fragile
323 because their expansion (maybe partially) at just the right time is critical.
324 Yet others are unlikely to ever be needed in a \enquote{moving argument}.
325
326 Doing this for \cs{begin} and \cs{end} was rather tricky as the
327 standard mechanism with \cs{DeclareRobustCommand} doesn't work here,
328 at least not for \cs{end} as that needs to expand during typesetting
329 without generating a \cs{relax} (from the \cs{protect}). Such a token
330 would start a new row in table environments, such as \env{tabular},
331 etc. Furthermore, some packages try to look into the definition of
332 \cs{end} by expanding it several times. Thus expansion with
333 \cs{expandafter} had to produce exactly the same result as before. But
334 in the end we overcame that hurdle too, so now environments are
335 automatically robust if used in places like headings or
336 \verb=\typeout= and so forth.
337
338 %%CCC do we need to say something about possible problems if other packages
339 %% or documents have redefined commands whose robustness has changed?
340
341 What hasn't been tackled yet is the redefinitions in \pkg{amsmath}:
342 this package
343 redefines a number of basic math constructs
344 that are now robust, so that
345 they become fragile again
346 once the package is loaded.
347 This area will be addressed in a followup release.
348 %
349 \githubissue{123}
350
351
352
353 \section{Other changes to the \LaTeX{} kernel}
354
355 \subsection{Guard against \cs{unskip} in tabular cells}
356
357 If a \env{tabular} or \env{array} cell started with a
358 command that started with an
359 \cs{unskip}
360 then centering the column broke
361 because the stretching glue
362 on the left got removed. The fix for this was to add
363 a minuscule, and hence unnoticeable, additional space after the stretching space:
364 removing this extra space causes no problems.
365
366 This change was also applied in the \pkg{array} package.
367
368 \githubissue{102}
369
370
371 \subsection{Fix Unicode table data}
372
373 \texttt{U+012F} which is \enquote{i with ogonek} produced a
374 \enquote{dotless i with ogonek} by mistake. This has been corrected.
375
376 \githubissue{122}
377
378 The Unicode slots \texttt{27E8} and \texttt{27E9} have been mapped to
379 \cs{textlangle} and \cs{textrangle} which is the recommended mapping.
380 In the past they raised a
381 \\
382 \LaTeX{} error.
383 %
384 \githubissue{110}
385
386 When doing cut-and-paste from other documents or websites, f-ligatures and others ligatures
387 might end up as
388 single Unicode characters in your file. In the past those got rejected by \LaTeX{}.
389 We
390 now define those Unicode slots and map them back to the sequence of
391 individual characters constituting the ligature.
392 If supported by the current font
393 (which is normally the case) they
394 are then reconstructed as ligatures and thus get typeset
395 as desired.
396 Otherwise they will come out as individual characters which
397 is still better than an error message.
398
399 \githubissue{154}
400
401
402 \subsection{Improve \cs{InputIfFileExists}'s handling of file names}
403
404 In rare circumstances it was possible that \cs{InputIfFileExists}
405 would work incorrectly, e.g., a construction such as
406 \begin{verbatim}
407 \InputIfFileExists{foo}{\input{bar}}{}
408 \end{verbatim}
409 would not load the files \file{foo.tex} and \file{bar.tex} but
410 would load \file{bar.tex} twice. This has been corrected.
411
412 \githubissue{109}
413
414
415 \subsection{Improve interface for cross-references}
416
417 %%CCC should be 'provide' as they still exist. FMi - no they no longer do that
418 The packages \pkg{fncylab} and \pkg{varioref} provided
419 a slightly
420 improved definition of \cs{refstepcounter} which allowed
421 the internal
422 \cs{p@..} commands to receive the counter value as an argument,
423 instead of
424 acting as a simple prefix. This supports
425 more complex
426 formatting of the value in the reference.
427
428
429 These packages also provided
430 the command \cs{labelformat} to help in the specification of
431 such formatting in an easy way. For
432 example, \verb=\labelformat{equation}{eq.~(#1)}= specifies that
433 references to equations
434 automatically come out as
435 \enquote{eq.~(5)} or similar. As such a \cs{labelformat} declaration
436 means a \cs{ref} command can no
437 longer be successfully used at the start of a sentence, the packages also
438 provided \cs{Ref} for such scenarios.
439
440 Both of these commands, \cs{labelformat} and \cs{Ref},
441 are now removed from the packages and instead made available in
442 the kernel so there is no
443 need to load additional packages.
444
445
446
447
448 \subsection{Improve wording of a warning message}
449
450 The kernel now says \enquote{Trying to load \ldots}
451 instead of \enquote{Try loading \ldots} in one of its informal
452 messages to match style of similar messages.
453 %
454 \githubissue{107}
455
456
457 \subsection{Avoid bad side-effects of \cs{DeclareErrorFont}}
458
459 As a side effect of setting up the error font for \acro{nfss}, this
460 declaration also changed the current font size back to 10pt.
461 In most
462 circumstances that doesn't matter, because that declaration was meant
463 to be used only during the format generation and not during
464 a \LaTeX{} run.
465 However, it has turned out to be
466 used by some developers in other places
467 (incorrectly in fact:
468 e.g., inside some \texttt{.fd} files) where
469 resetting the size causes
470 havoc
471 seemingly at random.
472 The command has now changed to not produce such side effects.
473
474 \gnatsissue{latex}{4399}
475
476
477
478 \subsection{\pkg{nfssfont}: Make font table generation the default action}
479
480 With the small file \file{nfssfont.tex} it is possible to produce
481 font tables and other font tests
482 in the style set up by Don Knuth.
483 In nearly all cases
484 a font table is wanted,
485 so this action has been made the default.
486 Now one can simply hit enter
487 instead of having to write \verb=\table\bye=.
488
489
490 \subsection{\pkg{trace}: Add package support in the kernel}
491
492 The \pkg{trace} package implements the commands \cs{traceon}
493 and \cs{traceoff} that work like
494 \cs{tracingall} but skip
495 certain code blocks that produce a lot of tracing output.
496 %%CCC being of no interest to anyone!! -- FMi I love your encouragement
497 This is useful when debugging, to suppress uninteresting tracing
498 from, for example, loading a font.
499 Code blocks that should not be traced
500 need to be surrounded by the commands
501 \cs{conditionally@traceoff} and \cs{conditionally@traceon}.
502
503 The \LaTeX{} kernel now provides dummy definitions for these two
504 commands so that package writers can use them in their packages
505 regardless of \pkg{trace} being loaded or not.
506
507
508
509
510 \section{Changes to packages in the \pkg{tools} category}
511
512 \subsection{\pkg{array}: Warn if primitive column specifiers are overwritten}
513
514 With \cs{newcolumntype} it is possible to define your own column
515 specifiers for a \env{tabular} preamble; it is also possible to
516 change existing ones. However, doing that for a primitive column
517 specifier, such as \texttt{c}, is seldom a good idea, since then its
518 functionality becomes unavailable.
519 The package was therefore supposed
520 to warn the user in this case, but due to a missing \cs{expandafter}
521 in the code it never did---now it does.
522 %
523 \githubissue{148}
524
525
526 \subsection{\pkg{multicol}: Introduce \texttt{minrows} counter for balancing}
527
528 When there are only a few lines of text on a page at the end of a
529 \env{multicols} environment,
530 balancing the columns often looks rather odd: such as
531 three columns each containing a single line. The balancing behavior
532 can now be controlled through the counter \texttt{minrows}
533 (default is~1) which specifies that,
534 after balancing, there must be at least that many lines in the first column.
535 Thus, if you set \texttt{minrows}
536 to \texttt{2} then you
537 would get a
538 distribution of \texttt{2+1+0} lines and if set
539 to three, the result
540 would be
541 \texttt{3+0+0} instead of the default \texttt{1+1+1}.
542
543 What is most appropriate really depends on the circumstances, but this
544 now gives you the tools to make local or global adjustments.
545
546
547 \subsection{\pkg{varioref}: Better support for \pkg{cleveref}}
548
549 The \pkg{varioref} package has been internally updated to provide
550 better interfaces for packages such as \pkg{hyperref} and
551 \pkg{cleveref}.
552
553 It also
554 has a new package option \option{nospace} that stops
555 \pkg{varioref} from meddling with space in front of
556 its commands. The
557 original behavior was always somewhat problematical and it is
558 suggested that
559 all new documents
560 use this option (which
561 should really have been the default).
562
563 Support was also added for the Arabic language through the option
564 \option{arabic}.
565
566
567
568
569 \subsection[\pkg{xr}: Support citations to bibliographies in\\ external documents]
570 {\pkg{xr}: Support citations to bibliographies in external documents}
571
572 The \pkg{xr} package can be used to cross-reference an external \LaTeX{}
573 document.
574 This means that even when a work is split over different documents (that
575 need to be processed separately), \cs{ref} or \cs{pageref} can use labels from
576 any document, creating links between them. This facility has now been extended
577 so that \cs{cite} commands and
578 their cousins can now also reference bibliographies in external
579 documents; this feature was first provided in the package
580 \pkg{xcite} by Enrico Gregorio.
581
582 Note that for technical reasons \pkg{xr} doesn't work with
583 \pkg{hyperref}. Use \pkg{xr-hyper} instead if you need the latter
584 package.
585
586
587 \section{Changes to packages in the \pkg{amsmath} category}
588
589 \subsection{\pkg{amsmath}: Introduce \cs{overunderset} command}
590
591 The \pkg{amsmath} package has always offered
592 the commands \cs{overset} and
593 \cs{underset} to produce binary operators with something set above or
594 below. But sometimes one needs to put something above and something below:
595 The newly added \cs{overunderset} makes this
596 easily possible.
597
598
599
600 \section{Documentation updates}
601
602 There are a number of
603 %small
604 documentation updates in files
605 on the documentation page of the project website~\cite{30:site-doc}.
606
607 \subsection{Highlighting the standard \texorpdfstring{\acro{nfss}}{NFSS} codes for series}
608
609 The \emph{Font Selection Guide}~\cite{fntguide} has been
610 updated to strongly recommend that the standard codes should be used
611 when providing font support. The reason for this recommendation is explained here.
612
613
614 The font selection scheme uses a number of standard codes for
615 \cs{fontseries} and \cs{fontshape} to ensure that different fonts are
616 comparable, e.g., that you get a \enquote{light} weight if you specify
617 \texttt{l} and \enquote{extra bold} when you write \texttt{eb},
618 etc. Over the years people came up with a number of other creative
619 short codes like \texttt{k}, \texttt{j}, \texttt{t} and others with
620 the result that changing a font family required different codes and
621 thus prevented users from easily mixing and matching different
622 families.
623 Some work has been undertaken to get back to a coherent scheme and
624 all the font families supported through the program \texttt{autoinst}
625 are now producing the standard codes again.
626
627
628 \subsection{\LaTeX{} \textsf{base} and \textsf{doc} distribution reunited}
629
630 For a long time the \LaTeX{} distribution available from \CTAN{} was
631 split into several parts to allow them to be uploaded or downloaded
632 separately. As this is these days more confusing than helpful we have
633 recombined the base part with the documentation part (as both are
634 anyway always updated together). Thus the package \textsf{latex-doc}
635 is no longer separately available from \CTAN{} but contained in the
636 \textsf{latex-base} distribution.
637
638
639 \begin{thebibliography}{9}
640
641 %\fontsize{9.3}{11.3}\selectfont
642
643 \bibitem{30:Mittelbach:TB39-1} Frank Mittelbach:
644 \emph{New rules for reporting bugs in the \LaTeX{} core software}.
645 In: TUGboat, 39\#1, 2018.
646 \url{https://latex-project.org/publications/}
647
648 \bibitem{devformat} Frank Mittelbach:
649 \emph{The
650 \LaTeX{} release workflow and the \LaTeX{} dev formats}.
651 In: TUGboat, 40\#2, 2019.
652 \url{https://latex-project.org/publications/}
653
654 \bibitem{fntguide} \LaTeX{} Project Team:
655 \emph{\LaTeXe{} font selection}.\\
656 \url{https://latex-project.org/documentation/}
657
658 \bibitem{30:site-doc}
659 \emph{\LaTeX{} documentation on the \LaTeX{} Project Website}.\\
660 \url{https://latex-project.org/documentation/}
661
662 %\bibitem{30:site-pub}
663 % \emph{\LaTeX{} Project publications on the \LaTeX{} Project Website}.\\
664 % \url{https://latex-project.org/publications/}
665
666 \end{thebibliography}
667
668 \end{document}