Download The XE TEX Project

Transcript
Marie-Louise Chaix and Fabrice Popineau
and the packages relevant to TEX typesetting, and the
supplementary tools cited above. The goal of the project
is by no means to write lots of new programs, but rather
to put glue between existing programs and package the
result so that it is easy to use for anybody. Relying on
several large, complex products like TEX, XEmacs, ...,
we are forced to play safe with updates to these products.
That means we can’t patch them heavily to suit our needs,
except if we can make sure the patches will find their way
in the main distribution. That is why it is better to use
the glue strategy than the patch strategy.
For its TEX part, XETEX will be a proper subset of TEX Live: only the most commonly used packages, as few binaries as possible, nothing related to bitmap PK fonts. The other parts have already been named:
XEmacs for integrating everything, Ghostscript, ImageMagick and NetPBM.
The project has been split into several tasks which
are described below. The goal is to get progressively
closer to the final XETEX product.
Installer Lots of work has already been done in the TEX
Live project regarding installation, especially about specification of packages and writing so-called TPM files.
XETEX should be very simple to install, hence should
offer as few options as possible to the user, contrary to
TEX Live, which offers lots of options to the user.
TEX Live installers for Windows and for Unix are
very different: it is an application with a graphical user
interface under Windows and a shell script running in
text mode under Unix. It has been unclear for a long
time if a portable installer was feasible and desirable.
Given that the XETEX installer should not offer
many options, we may think of something much simpler
for both cases. However, it appears that those platforms
are really different in several system aspects — file associations, icons, menus and so on — so that it seems difficult to have only one installer. More precisely, each
platform offers services to install applications, and these
services are different. So the answer is that a native installer should be built on each platform. Given our targets, that means a Debian package will be built under Debian Linux, and a MSI (Microsoft Installer) package will
be built under Windows.
Editing text The starting point here is XEmacs and the
AUC-TEX and Preview-LATEX packages. As powerful as
XEmacs may be, some aspects of the user interaction
may seem a bit strange or uneasy to novice users — think
about dialog through the minibuffer, or complex key sequences for example. This is partly due to the fact that
emacsen have been used mainly by programmers that
understand this way of thinking, and partly by the fact
emacsen can run in console mode, and no effort has been
made to build a simplified user interaction mode. Emac-
418
sen are complex tools for complex jobs. But it would be a
shame if the most powerful text editor could not be tailored to suit the needs of less experienced people. So this
part of the project will tackle the problem of ergonomics
and definition of menus, toolbars and keymaps suitable
for our goal. Following the general philosophy, we won’t
rewrite big parts of existing stuff, but rather tailor and
wrap up the existing tools.
As an exception to this rule and as a specific subpart, an equation editor has been considered. Given our
targeted audience, it could be a fancy and useful tool to
provide people with. A first sketch has been written in
wxPython to be portable. If it appears that the result is
stable enough under both platforms, it will be integrated
into the XETEX product.
Apart from typing in TEX documents, the user will
have to handle other kinds of files: images and graphics.
The related tasks will also be identified, and the common
ones will be offered through menus and toolbars. For example, MetaPost is a nice tool to draw graphics and support should be provided for it inside XEmacs.
Viewing documents TEX is not a WYSIWYG tool, which is
a bit disturbing for people who don’t know it yet. Specific
attention will be paid to coupling the compiler and the
viewer. Up to now, DVI and PDF have been the output
formats considered. The DVI format has the advantage to
be fast to display on screen, but the drawback not to be
self-contained: fonts, images are stored externally. For
the PDF format, it is the opposite.
The status of viewers available on TEX Live is not
the same under Windows and under Unix. The XDvi
viewer for Unix is able to display Type 1 fonts and to
use source specials to map a location in the viewer to the
same place in the source file. Windvi available for Windows does not yet have those features.2 However, we can
wonder if the DVI format should be advertised as the format of choice for new users, especially if it were possible
to view with the PDF format and the same source specials
mechanism feature. Heiko Oberdiek has implemented
such a mechanism in his vpe package. What needs to be
investigated is: can it be reasonably used? Is it fast, is it
convenient? If yes, no doubt the PDF format should be
advertised over the DVI format.
What we want to avoid at any price is the use of
bitmap font files. The mechanism to build these fonts is
too complex, too error prone. Nowadays, with scalable
fonts, we can completely avoid using bitmap fonts, and
thus avoid installing METAFONTand all the programs
calling it, like mktexpk. In any case, the Windvi viewer
will eventually be brought up to the same level of features
as the XDvi viewer.
2. The source special mechanism is available, but not documented.
TUGboat, Volume 24 (2003), No. 3 — Proceedings of EuroTEX 2003