| 1 |
% Copyright 2009 The LaTeX Project |
| 2 |
\documentclass{ltnews} |
| 3 |
\PassOptionsToPackage{colorlinks}{hyperref} |
| 4 |
|
| 5 |
\usepackage{metalogo,ragged2e} |
| 6 |
|
| 7 |
\AtBeginDocument{ |
| 8 |
\renewcommand{\LaTeXNews}{\LaTeX3~News} |
| 9 |
\RaggedRight |
| 10 |
} |
| 11 |
|
| 12 |
\publicationmonth{February} |
| 13 |
\publicationyear{2009} |
| 14 |
\publicationissue{1} |
| 15 |
|
| 16 |
\begin{document} |
| 17 |
\maketitle |
| 18 |
|
| 19 |
\section{Welcome to \LaTeX3} |
| 20 |
|
| 21 |
Momentum is again starting to build behind The \LaTeX{} Project. For the |
| 22 |
last few releases of \TeX~Live, the experimental programming foundation for |
| 23 |
\LaTeX3 has been available under the name \package{expl3}. Despite large |
| 24 |
warnings that the code would probably change in the future, we wanted to show |
| 25 |
that there was progress being made, no matter how slowly. Since then, some |
| 26 |
people have looked at the code, provided feedback, and~--- most |
| 27 |
importantly~--- actually tried using it. Although it is yet early days, we |
| 28 |
believe that the ideas behind the code are sound and there are only `cosmetic |
| 29 |
improvements' that need to be made before \package{expl3} is ready for the |
| 30 |
\LaTeX~package author masses. |
| 31 |
|
| 32 |
\section{What currently exists} |
| 33 |
|
| 34 |
The current \LaTeX3 code consists of two main branches: the |
| 35 |
\package{expl3} modules that define the underlying programming environment, |
| 36 |
and the `\package{xpackage}s', which are a suite of packages that are written |
| 37 |
with the \package{expl3} programming interface and provide some higher-level |
| 38 |
functionality for what will one day become \LaTeX3 proper. Both \package{expl3} and |
| 39 |
parts of the \package{xpackages} are designed to be used \emph{on top} of |
| 40 |
\LaTeXe, so new packages can take advantage of the new features while still |
| 41 |
allowing to be used alongside many of the vast number of \LaTeXe\ packages on |
| 42 |
\textsc{ctan}. |
| 43 |
|
| 44 |
\section{What's happening now} |
| 45 |
|
| 46 |
In preparation for a minor overhaul of the \package{expl3} code, we are |
| 47 |
writing a comprehensive test suite for each module. These tests allow us to |
| 48 |
make implementation changes and then test if the code still works as before. |
| 49 |
They are also highlighting any minor shortcomings or omissions in the code. |
| 50 |
As the tests are being written, our assumptions about what should be called |
| 51 |
what and the underlying naming conventions for the functions and datatypes are |
| 52 |
being questioned, challenged, and noted for further rumination. |
| 53 |
|
| 54 |
At the time of writing, we are approximately half-way through writing the test |
| 55 |
suite. Once this task is complete, which we plan for the first |
| 56 |
half of 2009, we will be ready to make changes without worrying about breaking |
| 57 |
anything. |
| 58 |
|
| 59 |
\section{What's happening soon} |
| 60 |
|
| 61 |
So what do we want to change? The current \package{expl3} codebase has |
| 62 |
portions that date to the pre-\LaTeXe\ days, while other modules have been |
| 63 |
more recently conceived. It is quite apparent when reading through the sources |
| 64 |
that some unification and tidying up would improve the simplicity and |
| 65 |
consistency of the code. In many cases, such changes will mean nothing more |
| 66 |
than a tweak or a rename. |
| 67 |
|
| 68 |
Beyond these minor changes, we are also re-thinking the exact notation behind |
| 69 |
the way functions are defined. There are currently a handful of different |
| 70 |
types of arguments that functions may be passed (from an untouched single |
| 71 |
token to a complete expansion of a token list) and we're not entirely happy |
| 72 |
with how the original choices have evolved now that the system has grown |
| 73 |
somewhat. We have received good feedback from several people on ways that we |
| 74 |
could improve the argument syntax, and as part of the upcoming changes to the |
| 75 |
\package{expl3} packages we hope to address the problems that we currently |
| 76 |
perceive in the present syntax. |
| 77 |
|
| 78 |
\section{What's happening later} |
| 79 |
|
| 80 |
After the changes discussed above are finished, we will begin freezing the core |
| 81 |
interface of the \package{expl3} modules, and we hope that more package |
| 82 |
authors will be interested in using the new ideas to write their own code. |
| 83 |
While the core functions will then remain unchanged, more features and new |
| 84 |
modules will be added as \LaTeX3 starts to grow. |
| 85 |
|
| 86 |
Some new and/or experimental packages will be changing to use the |
| 87 |
\package{expl3} programming interface, including \package{breqn}, |
| 88 |
\package{mathtools}, \package{empheq}, \package{fontspec}, and |
| 89 |
\package{unicode-math}. (Which is one reason for the lack of progress in |
| 90 |
these latter two in recent times.) There will also be a version of the |
| 91 |
\package{siunitx} package written in \package{expl3}, in parallel to the |
| 92 |
current \LaTeXe\ version. These developments will provide improvements to |
| 93 |
everyday \LaTeX\ users who haven't even heard of The \LaTeX{} Project. |
| 94 |
|
| 95 |
Looking towards the long term, \LaTeX3 as a document preparation system needs |
| 96 |
to be written almost from scratch. A high-level user syntax needs to be |
| 97 |
designed and scores of packages will be used as inspiration for the |
| 98 |
`out-of-the-box' default document templates. \LaTeXe\ has stood up to the test |
| 99 |
of time~--- some fifteen years and still going strong~--- and it is now time |
| 100 |
to write a successor that will survive another score. |
| 101 |
|
| 102 |
\end{document} |