summaryrefslogtreecommitdiff
path: root/macros/latex-dev/base/ltnews16.tex
blob: 75ee38c8150541d152ad085e27da6e02bf290ece (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
% \iffalse meta-comment
%
% Copyright (C) 1993-2020
% The LaTeX3 Project and any individual authors listed elsewhere
% in this file.
%
% This file is part of the LaTeX base system.
% -------------------------------------------
%
% It may be distributed and/or modified under the
% conditions of the LaTeX Project Public License, either version 1.3c
% of this license or (at your option) any later version.
% The latest version of this license is in
%    http://www.latex-project.org/lppl.txt
% and version 1.3c or later is part of all distributions of LaTeX
% version 2008 or later.
%
% This file has the LPPL maintenance status "maintained".
%
% The list of all files belonging to the LaTeX base distribution is
% given in the file `manifest.txt'. See also `legal.txt' for additional
% information.
%
% The list of derived (unpacked) files belonging to the distribution
% and covered by LPPL is defined by the unpacking scripts (with
% extension .ins) which are part of the distribution.
%
% \fi
% Filename: ltnews16.tex
%
% This is issue 16 of LaTeX News.

\documentclass
%    [lw35fonts]     % uncomment this line to get Palatino
   {ltnews}[2004/02/28]

% \usepackage[T1]{fontenc}

\publicationmonth{December}
\publicationyear{2003}
\publicationissue{16}

\begin{document}

\maketitle

%\raisefirstsection

\section{Anniversary news}

This anniversary \textit{Issue~16} takes a brief look into the future work of
the \LaTeX3 Project Team, both short and longer range.  Please let
us know if you want %\newline
to get involved with us in any of this work (see below).

An overview of the 10th Anniversary Release, dated 2003/12/01, is
can be found in \textit{Issue~15}.


\section{TLC2: The \LaTeX{} Companion -- 2nd edition!}

Since you are reading this newsletter, there is a good chance that
you, or a friend, has already bought this encyclopedic volume: the
incomparable Second\newline
Edition of this work that is every \LaTeX{}ie's\newline
ultimate lucky charm.

If by some chance you have not yet purchased your own copy then get
into training, get shopping, and get flexing your muscles (both
physical---it's $1100+$~pages,\newline
and intellectual) by using it to discover
masses of invaluable `insider information' about:
\begin{itemize}
\item the latest release of Standard \LaTeX{};
\item over~200~extension packages;
\item plus related software and systems.
\end{itemize}
For more information on this all new (??\ldots OK,\newline
not \emph{all}, but over 90\%!!),
all accurate (we hope!)\newline
10th~Anniversary Edition, check out\newline
 \mbox{\url{http://www.awprofessional.com/titles/0201362996}}.


\section{Future maintenance}

We are currently exploring how best to support the very large and
rapidly growing community of individuals, organisations and
enterprises that depend on the robustness and availability of the
current standard \LaTeX{} distribution.  Although we remain firmly\newline
resolved not to make changes in the base distribution (the kernel) of
Standard \LaTeX{}, there is still much that needs doing to maintain
its reliability and utility and to keep up the necessary level of
communication with users and supporters.  Also, as with all advanced
software systems, bugs are still turning up occasionally so %\newline
some fixes are still essential.

One major impediment to providing adequate service levels in this area
is, of course, the difficulties inherent in obtaining the time and
commitment of skilled minds---hence the appeal above to anyone
interested %\newline
in getting involved.


\section{LPPL certification}

There are still some outstanding diplomatic tasks around the
\LaTeX{} Project Public Licence: these include
e.g.,~getting it `OSF certified' and ensuring that it gains
more support and wider use, even in the FSF world\newline
where it has long been tolerated.


\section{Use of \eTeX/pdf\TeX}

We expect that within the next two years, releases of \LaTeX{} will
change modestly in order to run best under an extended \TeX{} engine
that contains the \eTeX{} primitives, e.g., \eTeX{} or pdf\TeX{}.
The details of this possible upgrade need further work so we are not
making a definite announcement yet.

Although the current release does not \emph{require} \eTeX{} features,
we certainly recommend using an extended \TeX{}, especially if you
need to debug macros.


\section{End of `autoload' support}

As computer systems generally grow in capacity, requirements change
and so we believe that the \package{autoload} variant of \LaTeX{} is
no longer required.  Thus, although the code remains it is no longer
supported.  We hope this does not cause any problems.


\section{New models, new code}

In the period 1999--2001 we published many results of our work over
the previous decade on the development of new concepts and models
for automated typesetting based on \TeX{} as the underlying platform.
These can be found at \url{http://www.latex-project.org/papers/}
and
\mbox{\url{http://www.latex-project.org/code/experimental/}}.

Since then a very large proportion of The Team's efforts have been
diverted to provide the core author team for TLC2, which provides
over 1000 pages of carefully researched and tested documentation of
many aspects of the vast world of \LaTeX{} related software that
was developed over that same time period and that continues
to grow and improve prodigiously.

Completion of that task \ldots\ until TLC3!! \ldots\ presents the
possibility of getting back to this more exciting development work,
or even to more radical work on non-\TeX{}-based models and
implementations.

Of course, any such ideas are predicated on our ability to organise
(with you, we hope) an efficient\newline
but responsive maintenance and support system\newline
for Standard \LaTeX{}.

\end{document}