
FAQ
Here you can find some frequently asked questions – and
their answers.
 Is εχT_{E}X ready for use?
 εχT_{E}X is still under development. When version 0.1 is
released then you can consider it to be feature complete for the
T_{E}X compatibility mode. This means that DVI can be produced which
is comparable – but not necessarily identical – to the
DVI obtained from T_{E}X.
 Under which License is εχT_{E}X distributed?
 The core part of εχT_{E}X is distributed under the
LGPL.
Some libraries are used by εχT_{E}X which come with their own licences.
 How is εχT_{E}X pronounced?
 The first sylable is pronounced ex as in expandable. And you
know how to pronounce T_{E}X...
 How is εχT_{E}X typeset?

Here is the (L^{A}T_{E}X) definition of the logo for εχT_{E}X:
\def\ExTeX{\textrm{% Logo always with serifs
\ensuremath{\textstyle\varepsilon_{\kern0.15em\mathcal{X}}}%
\kern.15em\TeX
}}
 Which version of Java is required for εχT_{E}X?
 εχT_{E}X requires Java in version 5.0 or newer. Older versions
will not suffice.
 Does εχT_{E}X run under a "free" Java?
 εχT_{E}X is developed with the Sun JDK and the Eclipse system.
The last time we checked εχT_{E}X did not compile with GCJ.
If anyone is willing to work on a compatibility layer this
help is welcome.
 Can εχT_{E}X be used as Java component?
 εχT_{E}X has been designed with the application as library in
mind. Thus interaction with the user or the environemnt are
encapsulated and can be replaced. The command line interface is
one example how to do it. The test driver for JUnit is also
embedding εχT_{E}X directly.
For a real application as library a texmf tree has to be present.
An activity has been started in εχT_{E}X to provide a texmf tree in the
form of jar archives.

