| 1 |
% Copyright 2012 The LaTeX3 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{2012} |
| 14 |
\publicationissue{7} |
| 15 |
|
| 16 |
\begin{document} |
| 17 |
\maketitle |
| 18 |
|
| 19 |
\section{After the `Big Bang'} |
| 20 |
|
| 21 |
The last \LaTeX3 News gave details of the `Big Bang', in which the team have |
| 22 |
revised the layout and coverage of the \LaTeX3 codebase. This process has |
| 23 |
made the status of different modules clearer, so that both the team themselves |
| 24 |
and everyone else know what is going on. |
| 25 |
|
| 26 |
The `Big Bang' changes were not shipped to \textsc{ctan} until after the \TeX{} |
| 27 |
Live 2011 freeze, as we did not want to end up with a \textsc{dvd} containing |
| 28 |
badly broken code. The update went to \textsc{ctan} soon after \TeX{} Live 2011 |
| 29 |
shipped, and has now propagated around the world. The new package naming |
| 30 |
(\pkg{l3kernel}, \pkg{l3packages} and \pkg{l3experimental}) has caused some |
| 31 |
surprises for a small number of users, but there have not been any major |
| 32 |
issues with the changes at the code level. |
| 33 |
|
| 34 |
The `Big Bang' has attracted attention from programmers outside of the |
| 35 |
\LaTeX3 team, with useful feedback arriving on the |
| 36 |
\texttt{LaTeX-L} list and TeX.sx, in particular. One area that this has |
| 37 |
highlighted is the need to document carefully when changes to the `stable' |
| 38 |
parts of the \LaTeX3 codebase occur. All changes to \pkg{l3kernel} now |
| 39 |
come with an explicit date for the change in the documentation, which means |
| 40 |
that programmers can check exactly when the features they want were introduced. |
| 41 |
|
| 42 |
Another key part of supporting \LaTeX3 use beyond the team is making it easy |
| 43 |
to check on the version of \LaTeX3 installed. To support that, the file date |
| 44 |
of the main \pkg{expl3} package is now set each time there is a release of the |
| 45 |
\LaTeX3 material to \textsc{ctan}. This means that the \LaTeXe{} |
| 46 |
\cs{@ifpackagelater} test can be used reliably to detect if the installed |
| 47 |
version of \LaTeX3 is going to supply the functions that a programmer is |
| 48 |
using. |
| 49 |
|
| 50 |
\section{Deforming boxes} |
| 51 |
|
| 52 |
Additions to both the \LaTeX3 stable material and more experimental modules |
| 53 |
continue. Joseph Wright has been working on adding `native' drivers for |
| 54 |
\LaTeX3 to support box transformations. These allow box rotation, clipping |
| 55 |
and scaling with the drivers \texttt{dvips}, \texttt{xdvipdfmx} and direct |
| 56 |
\textsc{pdf} output. |
| 57 |
|
| 58 |
The development of clipping support for the \texttt{xdvipdfmx} driver has also allowed |
| 59 |
us to suggest improvements to the \LaTeXe{} graphics drivers, enabling clipping |
| 60 |
with the \XeTeX{} engine. |
| 61 |
|
| 62 |
\section{A \TeX{}-based regex engine} |
| 63 |
|
| 64 |
Bruno Le Floch has been %working across the codebase, %% omitted to avoid page break |
| 65 |
improving the efficiency |
| 66 |
and robustness of a number of \LaTeX3 functions. Most notably, he has |
| 67 |
created a purely \TeX{}-based regular expression (regex) system for \LaTeX3. |
| 68 |
This is currently experimental, but is already proving useful and will |
| 69 |
hopefully stabilise over the coming months. |
| 70 |
|
| 71 |
Bruno's regex system works with all of the supported engines (pdf\TeX{}, |
| 72 |
\XeTeX{} and \LuaTeX{}). He has implemented the core ideas of standard |
| 73 |
regex systems, along with some \TeX{}-specifics to allow matching and |
| 74 |
replacing |
| 75 |
the content of token lists % correct? |
| 76 |
by category code. |
| 77 |
|
| 78 |
\section{\pkg{xparse} improves} |
| 79 |
|
| 80 |
The \pkg{xparse} module has been overhauled, making the internal code |
| 81 |
more efficient and adding additional argument types. This has also allowed |
| 82 |
us to deal with a number of internal bugs, meaning that argument grabbing |
| 83 |
is now more reliable. |
| 84 |
|
| 85 |
The argument grabbers themselves have been reworked so that in the event of an error, |
| 86 |
the user will normally get a meaningful message from \TeX{} rather than |
| 87 |
one pointing to \pkg{xparse} internal function names. This should help |
| 88 |
in tracking down erroneous input in real documents. |
| 89 |
|
| 90 |
\section{The galley} |
| 91 |
|
| 92 |
As detailed in the last issue, work on the galley module has been continuing. |
| 93 |
Discussion of Joseph's reimplementation of the galley concepts highlighted |
| 94 |
some important areas to work on, with the nature of the template concept |
| 95 |
being particularly significant. |
| 96 |
|
| 97 |
More work is still needed to finalise the galley concepts, but it is clear that |
| 98 |
some of this will require feedback from other areas. Joseph therefore hopes |
| 99 |
to finish work on the current round of galley improvements by the end of |
| 100 |
February, and to return to them once some other areas have been addressed. |
| 101 |
|
| 102 |
\section{Relationships between document items} |
| 103 |
|
| 104 |
The \textsc{tug}2011 meeting took place in October in India. Frank Mittelbach |
| 105 |
spoke there about ideas for describing the design relationship between document elements. |
| 106 |
% omit calling it "ldb" here because that name will likely change (last I heard?) |
| 107 |
These ideas allow a document designer to specify the design of a document element |
| 108 |
based on its context within a document, and progress in this area will likely |
| 109 |
lead to an extension in the \pkg{xtemplate} system. |
| 110 |
|
| 111 |
\end{document} |