| 1 |
% Copyright 2009,2010 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 |
\usepackage{url,hologo} |
| 13 |
|
| 14 |
\publicationmonth{July} |
| 15 |
\publicationyear{2010} |
| 16 |
\publicationissue{4} |
| 17 |
|
| 18 |
\begin{document} |
| 19 |
\maketitle |
| 20 |
|
| 21 |
\noindent |
| 22 |
Now that we're back from the \TeX\ Users Group conference in San |
| 23 |
Francisco, it's time to discuss what's been going on over the last six months. |
| 24 |
Due to some extra travel plans after the conference, this issue is slightly |
| 25 |
late in coming out. |
| 26 |
|
| 27 |
|
| 28 |
\section{\textsf{expl3} in practice} |
| 29 |
|
| 30 |
Joseph Wright and Will Robertson have both released significant new versions |
| 31 |
of their packages, resp., \textsf{siunitx} and \textsf{fontspec}. These have |
| 32 |
been re-written in the \LaTeX3 programming language \textsf{expl3}, which we |
| 33 |
have discussed here previously. Using \textsf{expl3} for production code has |
| 34 |
been very successful, both in demonstrating that the concepts are sound and |
| 35 |
highlighting areas that still need some attention. |
| 36 |
% The \textsf{expl3} |
| 37 |
% code will continue to evolve as more people use it for their work. |
| 38 |
|
| 39 |
In the case of \textsf{fontspec}, \textsf{expl3} programming is being used to |
| 40 |
target \LaTeX\ running on either \XeTeX\ and \hologo{LuaTeX}. In the latter |
| 41 |
case, the package is a mixture of Lua code and \pkg{expl3} code; Will |
| 42 |
presented the \pkg{unicode-math} package at TUG~2010, which is developed in |
| 43 |
the same style. |
| 44 |
|
| 45 |
|
| 46 |
\section{New \textsf{xpackages}} |
| 47 |
|
| 48 |
Frank Mittelbach has started to work on a new experimental \LaTeX3 package |
| 49 |
\textsf{xhead} that provides templates for one of the most complex areas of |
| 50 |
document design: section headings and document divisions. This |
| 51 |
is the beginning of an ambitious idea to map out the requirements for |
| 52 |
typesetting most documents currently processed with \LaTeX. |
| 53 |
|
| 54 |
One of the challenges here is providing a ``natural'' design language for |
| 55 |
describing the two-dimensional spatial relationships of objects participating |
| 56 |
in the design, e.g., the placement of a heading number in relation to the |
| 57 |
heading title, a possible sub-title, etc. In answer to this challenge Frank |
| 58 |
developed the \textsf{xcoffin} package, which he presented at TUG~2010. It is |
| 59 |
designed as a high-level interface for placing and aligning boxes on a page, |
| 60 |
allowing a `designer's approach' for indicating the positional relationship |
| 61 |
between boxes. (A `coffin' is a box with handles.) As an example, it is |
| 62 |
possible to represent ideas such as `align the lower-left corner of box A with |
| 63 |
the upper-right corner of box B after rotating it ninety degrees', without |
| 64 |
having to calculate the intermediate positions. |
| 65 |
|
| 66 |
We expect a future version of \textsf{xcoffin} (after some further work on its |
| 67 |
interface layer and its internal implementation) to play a major role in all |
| 68 |
packages providing layout templates for higher-level document objects, such as |
| 69 |
table of contents designs, floats, etc. |
| 70 |
|
| 71 |
Finally, |
| 72 |
Joseph Wright has begun work with the current `galley' packages, producing the |
| 73 |
new, minimal, \textsf{xgalley} based on \textsf{xfm-galley} as a testbed for |
| 74 |
what we need and what will work. |
| 75 |
|
| 76 |
|
| 77 |
\section{Developments with \textsf{expl3}} |
| 78 |
|
| 79 |
Meanwhile, Joseph's \emph{also} been writing a new floating-point calculation |
| 80 |
module, called \textsf{l3fp}, for \pkg{expl3}. This module allows manipulation |
| 81 |
and calculation of numbers with a much larger range than \TeX\ allows |
| 82 |
naturally. The \textsf{l3fp} module has already been utilised in the |
| 83 |
\pkg{xcoffin} code for calculatations such as coordinate rotations and |
| 84 |
intersection points of vectors. |
| 85 |
|
| 86 |
The modules \pkg{l3io} and \pkg{l3file} have been revised, rethinking the way |
| 87 |
that read and write streams are dealt with. \TeX\ has a hard limit of sixteen |
| 88 |
input and output streams open at any one time, and the new implementation for |
| 89 |
\pkg{expl3} provides more flexibility in how they are allocated; there's now |
| 90 |
much less chance of running into a `\verb|No room for a new \read|' (or |
| 91 |
\verb|\write|) error. |
| 92 |
|
| 93 |
Sometimes we discuss ideas for \textsf{expl3} that \emph{don't} end up making |
| 94 |
it into the final code. One example of this is the concept of having `local |
| 95 |
registers' for integers, boxes, and so on, that do not survive outside of the |
| 96 |
group they are defined in (in contrast to Plain \TeX\ and \LaTeX, where |
| 97 |
allocators such as \verb|\newcount| and \verb|\newbox| are always global). |
| 98 |
Despite the scope for some small benefit, we decided that the extra complexity |
| 99 |
that the additional functions required, in both syntax and documentation, was |
| 100 |
not justified. |
| 101 |
|
| 102 |
|
| 103 |
\section{TUG 2010 reflections} |
| 104 |
|
| 105 |
% added most of it back in: -fmi |
| 106 |
|
| 107 |
%% Most of the active \LaTeX3 Project team were able to attend the TUG~2010 |
| 108 |
%% conference and (for Will) meet everyone in person for the first time. |
| 109 |
|
| 110 |
Our interpretation of the broad themes discussed at the conference are that |
| 111 |
\TeX-based systems are still thriving and there are some big problems to solve |
| 112 |
with robust solutions to transform \LaTeX\ source, including mathematics, into |
| 113 |
a form such as HTML. While there are big pushes for standardising various aspects |
| 114 |
of the \LaTeX\ syntax, we also believe that it is \LaTeX's very |
| 115 |
flexibility---its inherently non-standardised markup---that has allowed it to |
| 116 |
survive for so many years. There is a delicate trade-off here between moving |
| 117 |
forward into more standards-based territory while also retaining the |
| 118 |
extensibility of the third-party package system. |
| 119 |
|
| 120 |
\end{document} |
| 121 |
|
| 122 |
|
| 123 |
|