Debian Codegraph @

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

raw
1 % \iffalse meta-comment
2 %
3 % Copyright (C) 1993-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: ltnews20.tex
30 %
31 % This is issue 20 of LaTeX News.
32
33 \documentclass{ltnews}
34
35 \usepackage[T1]{fontenc}
36
37 \usepackage{lmodern,url}
38
39 \publicationday{27}
40 \publicationmonth{June}
41 \publicationyear{2011}
42
43 \publicationissue{20}
44
45 \providecommand\pkg[1]{\texttt{#1}}
46 \providecommand\cls[1]{\texttt{#1}}
47 \providecommand\option[1]{\texttt{#1}}
48 \providecommand\env[1]{\texttt{#1}}
49 \providecommand\file[1]{\texttt{#1}}
50
51 \begin{document}
52
53 \maketitle
54
55 \section{Scheduled \LaTeX\ bug-fix release}
56
57 This issue of \LaTeX~News marks the first bug-fix release of
58 \LaTeXe\ since shifting to a new build system in 2009.
59 Provided sufficient changes are made each year, we expect to
60 repeat such releases once per year to stay in sync with \TeX\ Live.
61 Due to the excitement of \TeX's $2^5$-th birthday last year,
62 we missed our window of opportunity to do so for 2010.
63 This situation has been rectified this year!
64
65 \section{Continued development}
66
67 The \LaTeXe\ program is no longer being actively developed, as any
68 non-negligible changes now could have dramatic backwards compatibility
69 issues with old documents. Similarly, new features cannot be added to
70 the kernel since any new documents written now would then be
71 incompatible with legacy versions of \LaTeX.
72
73 The situation on the package level is quite different though. While
74 most of us have stopped developing packages for \LaTeXe{} there are
75 many contributing developers that continue to enrich \LaTeXe{} by
76 providing or extending add-on packages with new or better
77 functionality.
78
79 However, the \LaTeX\ team certainly recognises that there are
80 improvements to be made to the kernel code; over the last few years we
81 have been working on building, expanding, and solidifying the
82 \textsf{expl3} programming layer for future \LaTeX\ development. We
83 are using \textsf{expl3} to build new interfaces for package
84 development and tools for document design. Progress here is
85 continuing.
86
87 \section{Release notes}
88
89 In addition to a few small documentation fixes, the following changes
90 have been made to the \LaTeXe\ code; in accordance with the philosophy
91 of minimising forwards and backwards compatibility problems, most of
92 these will not be noticeable to the regular \LaTeX\ user.
93
94 \paragraph{Font subsets covered by Latin Modern and \TeX\ Gyre}
95
96 The Latin Modern and \TeX\ Gyre fonts are a modern suite of families based
97 on the well-known Computer Modern and `PostScript 16' families with many additional
98 characters for high-quality multilingual typesetting.%
99 \footnote{%
100 See their respective TUGboat articles for more information:\\
101 \url{http://www.tug.org/TUGboat/tb24-1/jackowski.pdf}\\
102 \url{http://www.tug.org/TUGboat/tb27-2/tb87hagen-gyre.pdf}%
103 }
104
105 Information about their symbol coverage in the \verb|TS1| encoding is now included
106 in \pkg{textcomp}'s default font definitions.
107
108
109 \paragraph{Redefinition of \cs{enddocument}}
110
111 Inside the definition of \verb=\end{document}= the \texttt{.aux} file
112 is read back in to resolve cross-references and build the table of
113 contents etc. From 2.09 days this was done using \verb=\input= without
114 any surrounding braces which could lead to some issues in boundary
115 cases, especially if \verb=\input= was redefined by some package. It
116 was therefore changed to use \LaTeXe{}'s internal name for this
117 function. As a result, packages that modify \verb=\enddocument= other
118 than through the officially provided hooks may need to get updated.
119
120 \paragraph{Small improvement with split footnotes in \pkg{ftnright}}
121
122 If in the first column there is more than a full column worth of
123 footnote material the material will be split resulting in footnotes
124 out of order. This issue is now at least detected and generates an
125 error but the algorithm used by the package is unable to gracefully
126 handle it in an automated fashion (some alternatives for resolving the
127 problem if it happens are given in the package documentation).
128
129 \paragraph{Improvement in \file{xspace} and font-switching}
130
131 The \file{xspace} package provides the command \verb|\xspace|
132 which attempts to be clever about inserting spaces automatically
133 after user-defined control sequences.
134 An important bug fix has been made to this command to correct its
135 behaviour when used in conjunction with font-switching commands
136 such as \verb|\emph| and \verb|\textbf|.
137 Previously, writing
138 \begin{verbatim}
139 \newcommand\foo{foo\xspace}
140 ... \emph{\foo} bar baz
141 ... \emph{\foo}, bar baz
142 \end{verbatim}
143 would result in an extraneous space being inserted after `foo' in
144 both cases; this has now been corrected.
145
146
147 \paragraph{RTL in \file{multicol}}
148
149 The 1.7 release of \file{multicol} adds support for languages that
150 are typeset right-to-left. For those languages the order of the
151 columns on the page also needs to be reversed---something that wasn't
152 possible in earlier releases.
153
154 The new feature is supported through the
155 commands \verb|\RLmulticolcolumns| (switching to right-to-left typesetting)
156 and \verb|\LRmulticolcolumns| (switching to left-to-right typesetting) the
157 latter being the default.
158
159 \paragraph{Improve French \file{babel} interaction with \file{varioref}}
160
161 Extracting and saving the page number turned out to be a source of
162 subtle bugs. Initially it was done through an \verb"\edef" with a
163 bunch of \verb"\expandafter" commands inside. This posed a problem if
164 the page number itself contained code which needed protection (e.g.,
165 pr/4080) so this got changed in the last release to use
166 \verb"\protected@edef". However, that in turn failed with Babel (bug
167 report/4093) if the label contained active characters, e.g., a ``:''
168 in French. So now we use (after one failed attempt pr/4159) even more
169 \verb"\expandafter" commands and \verb"\romannumeral" trickery to
170 avoid any expansion other than what is absolutely required---making
171 the code in that space absolutely unreadable.
172 \begin{verbatim}
173 \expandafter\def\expandafter#1\expandafter{%
174 \romannumeral
175 \expandafter\expandafter\expandafter
176 \z@
177 \expandafter \@cdr
178 \romannumeral
179 \expandafter\expandafter\expandafter
180 \z@
181 \csname r@#2\endcsname\@nil}%
182 \end{verbatim}
183 Code like this nicely demonstrates the limitations in the programming
184 layer of \LaTeXe{} and the advantages that \textsf{expl3} will offer
185 on this level.
186
187 \end{document}