This is a PROOF OF CONCEPT demonstration of
DVI to HTML.
Obviously there is a lot of rough
positioning in this example; it should be possible to make everything align properly in a fully worked program.
teT
E
X
Manual
Thomas
Esser
January
2005
Abstract
teT
E
X
is
a
distribution
of
T
E
X
and
r
elated
pr
ograms:
pdfT
E
X,
e-T
E
X,
Omega,
Aleph,
L
A
T
E
X,
ConT
E
Xt,
MET
AF
ONT
,
MET
AP
OST
,
dvips
,
xdvi
,
dvipdfm
,
dvipng
,
B
i
b
T
E
X,
makeindex
etc.
teT
E
X
aims
to
make
using
and
maintaining
a
T
E
X
system
as
easy
as
possible.
The
pr
ograms
ar
e
built
ar
ound
the
W
eb2c
distribution
by
Karl
Berry
and
Olaf
W
eber
.
A
common
part
of
many
pr
ograms
is
kpathsea
,
a
library
that
pr
ovides
e
ffi
cient
access
by
name
to
fi
les
stor
ed
hierar
chically
.
This
document
describes
how
to
use
and
set
up
the
teT
E
X
system.
It
does
not
attempt
to
be
a
compr
ehensive
guide,
instead
it
tries
to
give
an
overview
about
what
softwar
e
and
documentation
is
contained
in
the
distribution.
1
Contents
1
The
Components
of
teT
E
X
3
1.1
W
eb2c
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
1.2
T
E
X
extensions:
pdfT
E
X,
e-T
E
X,
Omega,
Aleph,
encT
E
X
.
.
.
.
.
.
.
.
.
.
.
3
1.3
DVI
drivers:
dvips,
dvilj,
xdvi,
dvipdfm,
dvipng
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
1.4
Makeindex
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1.5
T
exinfo
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1.6
UNIX
Scripts
/
T
ools
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
2
Concepts
and
con
fi
guration
7
2.1
The
T
E
X
Dir
ectory
Str
uctur
e
(TDS)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
2.2
Overview
of
the
pr
ede
fi
ned
texmf
tr
ees
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
2.3
The
fi
le
name
database
(ls-R)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
2.4
Runtime
con
fi
guration
(texmf.cnf
fi
le)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
2.5
Using
Postscript
type
1
fonts
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
2.6
Con
fi
guration
fi
les
maintained
by
texcon
fi
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10
2.7
Automatic
font
generation
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12
2.8
TCX
fi
les
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12
2.9
Cr
eating
PDF
fi
les
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13
3
Release
notes
for
teT
E
X
2.0
14
4
Release
notes
for
teT
E
X
3.0
14
4.1
New
pr
ograms
/
font
support
/
macr
o
packages
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14
4.2
Changes
to
web2c
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14
4.3
Modi
fi
cations
to
the
dir
ectory
str
uctur
e
and
fi
le
sear
ching
.
.
.
.
.
.
.
.
.
15
4.4
Changes
to
texcon
fi
g
/
updmap
/
fmtutil
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
16
4.5
Changes
to
pdfT
E
X
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
4.6
pdfetex:
the
new
default
T
E
X
engine
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
4.7
Changes
to
xdvik
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
4.8
Changes
to
dvipsk
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18
4.9
Impr
oved
documentation
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18
5
Resources
18
5.1
Helpindex
fi
le
for
the
documentation
tr
ee
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
19
5.2
Internet
Newsgr
oups
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
19
5.3
T
E
X
User
Gr
oups
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
19
5.4
Mailing
Lists
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
19
5.5
Compr
ehensive
T
eX
Ar
chive
Network
(CT
AN)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
20
5.6
The
T
E
X
Catalogue
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
20
5.7
Fr
equently
Asked
Questions
(F
AQs)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
20
2
1
The
Components
of
teT
E
X
This
document
cannot
describe
all
the
pr
ograms
which
ar
e
part
of
teT
E
X
in
detail,
but
it
tries
to
give
you
an
overview
.
This
section
describes
the
packages
which
form
the
main
components
of
teT
E
X.
1.1
W
eb2c
W
eb2c
is
a
T
E
X
implementation,
originally
for
Unix,
but
also
r
unning
under
W
indows,
Macintosh,
DOS,
Amiga,
and
other
operating
systems.
It
includes
T
E
X
itself
and
the
following
pr
ograms:
•
MET
AF
ONT
:
a
font
compiler
intended
to
pr
oduce
typefaces
of
high
quality
[
1
].
•
MET
AP
OST
:
a
pr
ogram
similar
to
MET
AF
ONT
,
modi
fi
ed
to
output
Postscript
code
instead
of
bitmaps.
Documentation
for
MET
AP
OST
is
available
via
the
command:
texdoc
mpman
.
•
B
i
b
T
E
X:
a
pr
epr
ocessor
to
make
bibliographies
for
L
A
T
E
X.
For
documentation,
see
texdoc
btxdoc
and
Appendix
B
of
[
2
].
•
utilities
for
converting
between
di
ff
er
ent
font
metric
and
bitmap
formats:
gftopk
,
gftodvi
,
gftype
,
pktogf
,
pktype
,
pltotf
,
tftopl
,
vftovp
,
vptovf
.
•
DVI
utilities:
dvicopy,
dvitomp,
dvitype
.
•
other
tools:
patgen
,
pooltype
,
tangle
,
weave
,
ctangle
,
cweave
.
The
main
documentation
for
W
eb2c
is
the
“
W
eb2c
manual
”
and
the
“
kpathsea
man-
ual
”
.
These
can
be
accessed
via
texdoc
web2c
and
texdoc
kpathsea
r
espectively
.
1.2
T
E
X
extensions:
pdfT
E
X,
e-T
E
X,
Omega,
Aleph,
encT
E
X
Besides
the
standar
d
T
E
X
pr
ogram,
the
following
extensions
to
T
E
X
ar
e
included
in
teT
E
X:
pdfT
E
X
This
can
optionally
write
Acr
obat
PDF
format
instead
of
DVI.
The
user
manual
can
be
accessed
by
the
command
texdoc
pdftex-a
.
The
L
A
T
E
X
hyperr
ef
package
(
texdoc
manual
)
has
an
option
“
pdftex
”
,
which
turns
on
all
the
pr
ogram
featur
es.
In
DVI
mode,
pdfT
E
X
works
like
the
usual
T
E
X
with
the
exception
of
the
availabil-
ity
of
additional
typographic
featur
es.
In
PDF
mode,
pdfT
E
X
supports
graphics
inclusion
for
the
following
graphic
for
-
mats:
•
PNG
(portable
network
graphics)
•
PDF
(portable
document
format),
•
JPG
(jpeg)
3
•
MPS
(metapost
output)
It
does
not
support
EPS
(encapsulated
postscript),
but
if
you
have
r
ecent
versions
of
ghostscript
(version
5.10
or
later)
and
perl
(version
5
or
later)
installed,
you
can
use
the
tool
epstopdf
to
convert
EPS
graphics
into
PDF
.
When
including
a
PDF
fi
le,
pdfT
E
X
is
able
to
access
parts
of
a
multi-page
fi
le:
a
complete
page
or
a
clipped
part
of
a
page.
This
featur
e
extends
pdfT
E
X
beyond
its
typesetting
capa-
bilities
into
a
versatile
tool
for
handling
arbitrary
generated
PDF
fi
les.
e-T
E
X
adds
a
small
but
powerful
set
of
new
primitives,
and
an
extension
for
right
to
left
typesetting.
In
default
mode,
e-T
E
X
is
100
%
compatible
with
or
dinary
T
E
X.
See
texdoc
etex-man
for
details.
Omega
(
Ω
)
Omega
works
internally
with
16-bit
Unicode
characters;
this
allows
it
to
work
dir
ectly
with
almost
all
the
world’s
scripts
simultaneously
.
It
also
supports
dynamically
loaded
“
Ω
T
ranslation
Pr
ocesses
”
(OTPs),
which
allow
the
user
to
de
fi
ne
complex
transformations
to
be
performed
on
arbitrary
str
eams
of
input.
Documentation:
texdoc
doc-1.12
.
Aleph
is
a
T
E
X
engine
that
combines
the
good
featur
es
of
eT
E
X
and
Omega.
The
L
A
T
E
X
based
format
of
Aleph
is
called
Lamed.
1.3
DVI
drivers:
dvips,
dvilj,
xdvi,
dvipdfm,
dvipng
For
printing
and
pr
eviewing
DVI
fi
les,
you
need
to
use
one
of
the
DVI
drivers
that
ar
e
available:
dvips
This
driver
converts
DVI
fi
les
into
Postscript.
Postscript
is
a
page
description
language
that
many
laser
printers
dir
ectly
support.
W
ith
the
help
of
the
utility
ghostscript
,
it
is
possible
to
view
Postscript
documents
on
scr
een
and
to
print
Postscript
documents
on
non-Postscript
printers.
This
version
of
dvips
supports
hypertex
and
partial
font
downloading.
In
this
r
elease,
the
sear
ch
path
for
con
fi
g
fi
les
have
been
changed:
the
curr
ent
dir
ectory
is
no
longer
sear
ched
by
default.
Additionally
,
secur
e
mode
has
been
turned
on
by
default.
For
details,
consult
the
documentation:
texdoc
dvips
.
dvilj
This
is
a
family
of
drivers
to
support
HP
LaserJet
(and
compatible)
printers:
dvilj,
dvilj2p,
dvilj4,
dvilj4l,
dvilj6
.
These
drivers
ar
e
faster
than
the
dvips
+
ghostscript
alternative
(which
can
also
be
used
to
print
DVI
fi
les
on
HP
LaserJet
printers),
but
they
lack
a
few
featur
es
like
support
for
virtual
fonts,
r
otated
or
scaled
graphics,
etc.
xdvi
This
is
a
pr
eviewer
for
DVI
fi
les
under
the
X
W
indow
System.
It
has
support
for
Postscript
specials
thr
ough
Display
Postscript,
NeWS
and
ghostscript
.
Hy-
pertex
support
was
also
added
for
this
version
of
xdvi
.
A
link
can
be
followed
by
clicking
with
Button-1
or
Button-2
(open
link
in
a
new
window)
on
it.
W
ith
4
the
help
of
sour
ce
specials,
xdvi
can
interact
with
most
editors
in
some
way
.
For
details,
visit
the
pr
oject
page
.
dvipdfm
This
pr
ogram
can
convert
dvi
fi
les
into
pdf
format,
while
supporting
a
rich
set
of
featur
es
(via
T
eX’s
\special
scheme):
hyperlinks,
bookmarks,
thumbnails,
image
inclusion
etc.
For
details
consult
the
documentation
texdoc
dvipdfm
and
the
web
page
.
dvipng
makes
PNG
and/or
GIF
graphics
fr
om
DVI
fi
les
as
obtained
fr
om
T
eX
and
its
r
elatives.
For
details,
consult
the
documentation:
texdoc
dvipng
.
1.4
Makeindex
makeindex
is
a
general
purpose
hierar
chical
index
generator;
it
accepts
one
or
mor
e
input
fi
les
(often
pr
oduced
by
a
text
formatter
such
as
T
E
X
or
troff
),
sorts
the
entries,
and
pr
oduces
an
output
fi
le
which
can
be
formatted.
The
formats
of
the
input
and
output
fi
les
ar
e
speci
fi
ed
in
a
style
fi
le;
by
default,
input
is
assumed
to
be
an
idx
fi
le,
as
generated
by
L
A
T
E
X.
Documentation:
texdoc
makeindex
1.5
T
exinfo
texinfo
is
a
documentation
system.
It
pr
oduces
online
or
printed
output
fr
om
a
single
sour
ce.
It
uses
T
E
X
to
typeset
documents
for
printing
(
texdoc
texinfo
).
1.6
UNIX
Scripts
/
T
ools
If
you
ar
e
using
teT
E
X
under
UNIX,
you
can
use
the
following
scripts.
Mor
e
documenta-
tion
for
a
speci
fi
c
tool
can
either
be
obtained
fr
om
its
UNIX
manual
page
or
by
r
unning
the
pr
ogram
with
the
option
–
help
.
texdoc
allows
you
to
easily
access
documentation
included
with
teT
E
X.
Y
ou
only
have
to
r
emember
the
fi
le
name
of
the
document
that
you
want
to
access,
without
the
dir
ectory
part.
If
you
do
not
specify
a
fi
le
name
extension
(such
as
.dvi
)
texdoc
will
try
a
few
default
extensions.
After
sear
ching
the
fi
le,
texdoc
starts
an
appr
o-
priate
viewer
.
The
command
texdoc
–
help
gives
you
a
list
of
available
command
line
options.
While
texdoc
is
a
fast
and
e
ffi
cient
tool
if
you
exactly
know
what
you
ar
e
sear
ching
for
,
it
is
of
limited
use
if
you
don’t
know
the
exact
name
of
the
documentation
fi
le.
texdoctk
This
perl/tk
based
tool
allows
you
to
br
owse
thr
ough
the
available
docu-
mentation
by
some
topics
and
to
sear
ch
for
keywor
ds.
It
uses
a
simple
database
fi
le
for
its
con
fi
guration
(named
texdoctk.dat
),
which
you
can
customize
and
extend
easily
.
texcon
fi
g
allows
you
to
carry
out
the
most
common
con
fi
guration
tasks
in
teT
E
X.
The
pr
ogram
can
be
used
in
command
mode
or
in
interactive
mode.
For
the
interac-
tive
mode
(which
is
invoked
by
calling
texconfig
without
ar
guments),
a
curses
5
based
utility
is
used
for
user
interaction
(menus,
check
boxes,
.
.
.
).
The
command
texconfig
help
shows
you
a
list
of
available
command
line
options
(command
mode).
texconfig
can
be
used
to
set
up
T
E
X
format
fi
les
and
their
hyphenation
patterns,
to
set
up
printers
(for
dvips
)
and
for
a
few
other
things.
It
manipulates
con
fi
gu-
ration
fi
les
to
stor
e
the
con
fi
guration
changes.
If
the
use
of
texconfig
causes
a
change
in
some
con
fi
guration
fi
le,
texconfig
will
try
to
save
that
fi
le
into
the
texmf
tr
ee
that
is
speci
fi
ed
by
the
TEXMFCONFIG
vari-
able.
V
ariable
(cached)
r
untime
data
(such
as
format
fi
les
generated
by
fmtutil
,
map
fi
les
generated
by
updmap
)
will
be
stor
ed
in
the
texmf
tr
ee
speci
fi
ed
by
the
TEXMFVAR
variable.
updmap
Some
tools
in
teT
E
X
support
Postscript
T
ype
1
fonts:
dvips
,
pdfT
E
X
,
xdvi
,
dvipdfm
and
gsftopk
,
ps2pk
.
The
last
two
in
this
list
just
convert
outline
fonts
into
a
bitmap
format
which
is
helpful
for
applications
that
don’t
dir
ectly
support
outline
fonts.
In
an
ideal
world,
all
of
these
pr
ograms
would
shar
e
a
common
con
fi
guration
fi
le
to
set
up
their
outline
fonts.
The
r
eality
is
di
ff
er
ent,
however
,
and
each
tool
needs
its
own
con
fi
guration.
The
updmap
utility
was
developed
to
generate
these
con
fi
guration
fi
les
fr
om
a
central
r
epository
.
Adding
font
de
fi
ni-
tions
for
all
supported
applications
fr
om
a
map
fi
le
foo.map
can
be
as
easy
as
updmap
--enable
Map
foo.map
.
For
details,
please
consult
the
manual
page
of
updmap
.
dvired
This
script
can
be
used
to
print
documents
formatted
for
A4
paper
2-up
(i.e.
two
logical
pages
to
one
physical
page
of
paper)
by
scaling
the
pages
to
70.7
%
of
their
original
size.
dvired
can
just
be
used
in
the
same
way
as
dvips
(same
command
line
options).
dvi2fax
This
script
converts
DVI
fi
les
into
F
AX
G3
format.
It
uses
ghostscript
(see:
http://www.cs.wisc.edu/~ghost/
)
which
is
not
part
of
teT
E
X.
The
DVI
fi
le
is
fi
rst
converted
to
Postscript
(
204
×
196
dpi
or
204
×
98
dpi)
and
then
to
F
AX
G3
using
ghostscript
(
faxg3
device).
allcm,
allec,
allneeded
teT
E
X’s
DVI
drivers
generate
missing
bitmap
fonts
on
demand
(the
fi
rst
time
they
ar
e
needed).
If
you
start
with
a
fr
esh
installation,
you
don’t
have
any
bitmap
fonts
and
the
delay
caused
by
font
generation
might
be
too
an-
noying
for
you.
In
that
case,
the
thr
ee
scripts
allcm,
allec
and
allneeded
can
help
you.
allcm
and
allec
cr
eate
a
few
DVI
fi
les
(using
L
A
T
E
X)
which
use
lots
of
fonts
at
various
sizes
and
r
un
these
DVI
fi
les
thr
ough
dvips
.
This
triggers
the
generation
of
the
most
commonly
used
Computer
Modern
(
allcm
)
and
Eur
opean
Computer
Modern
(
allec
)
fonts
r
espectively
.
Y
ou
might
alr
eady
have
DVI
fi
les
and
want
to
generate
just
the
bitmap
fonts
needed
by
these
documents.
This
can
be
done
by
the
allneeded
script.
This
script
will
sear
ch
a
given
set
of
dir
ecto-
ries
for
DVI
fi
les
and
r
un
them
thr
ough
dvips
.
All
these
scripts
just
trigger
font
generation.
L
A
T
E
X
and
DVI
fi
les
generated
by
allcm
/
allec
ar
e
r
emoved
when
6
the
pr
ogram
terminates.
Postscript
output
that
is
generated
by
dvips
is
sent
to
/dev/null
.
These
pr
ograms
accept
the
command
line
option
“
-r
”
(must
be
the
fi
rst
option)
to
generate
fi
les
for
the
magni
fi
cation
707
/
1000
which
is
used
by
dvired
.
allneeded
passes
options
which
corr
espond
to
existing
fi
le
or
dir
ectory
names
to
find
(for
locating
DVI
fi
les).
All
other
options
given
to
any
of
these
thr
ee
utilities
ar
e
passed
to
dvips
.
So,
by
passing
-D
NNN
-mfmode
some-mode
or
-P
some-printer
,
you
can
generate
fonts
for
a
speci
fi
c
r
esolution
(
NNN
)
and
mode
(
some-mode
)
or
for
a
speci
fi
c
printer
(
printer
).
2
Concepts
and
con
fi
guration
2.1
The
T
E
X
Directory
Structure
(TDS)
teT
E
X’s
support
tr
ee
with
fonts,
macr
os,
documentation
and
other
fi
les
(fr
om
now
on
called
the
“
texmf
tr
ee
”
)
follows
a
certain
str
uctur
e:
the
T
E
X
Dir
ectory
Str
uctur
e
(TDS).
This
is
a
standar
d
developed
by
a
T
E
X
W
orking
Gr
oup
of
TUG.
The
TDS
is
de
fi
ned
in
a
way
so
that
can
be
used
by
di
ff
er
ent
implementations
of
T
E
X
on
di
ff
er
ent
platforms.
T
o-
day
,
several
T
E
X
distributions
follow
this
standar
d:
teT
E
X,
T
E
X
Live,
fpT
E
X
and
miktex,
only
to
mention
some.
Y
ou
need
to
understand
this
str
uctur
e
if
you
want
to
build
your
own
texmf
tr
ee
(e.g.,
with
all
your
local
additions)
or
add
fi
les
into
an
existing
texmf
tr
ee.
The
list
of
all
texmf
tr
ees
(optionally
using
some
notation
called
“
brace
expansion
”
and
!!
modi
fi
ers;
the
kpathsea
manual
explains
this
in
detail)
can
be
obtained
by:
kpsewhich
-expand-var=’$TEXMF’
T
able
1
gives
a
short
overview
of
the
TDS.
It
shows
the
pr
oper
location
inside
the
TDS
tr
ee
for
several
kind
of
fi
les.
The
complete
documentation
for
TDS
can
be
accessed
by
texdoc
tds
.
If
you
want
to
see
some
examples,
just
look
at
the
main
texmf
tr
ee
of
teT
E
X.
It
has
several
thousand
fi
les.
T
E
X
macr
os
tex/
‹
format
›
/
‹
package
›
/
font
fi
les
fonts/
‹
type
›
/
‹
supplier
›
/
‹
typeface
›
/
MET
AF
ONT
fi
les
metafont/
‹
package
›
/
documentation
doc/
‹
package
›
/
sour
ces
sour
ce/
‹
package
›
/
B
i
b
T
E
X
fi
les
bibtex/{bst,bib}/
‹
package
›
/
T
able
1:
TDS:
an
overview
The
r
eplaceable
parts
in
this
table
mean:
‹
format
›
The
name
of
the
T
E
X
format,
e.g.,
latex
or
amstex
.
‹
package
›
The
name
of
the
package
to
which
the
fi
le
belongs,
e.g.,
babel
or
seminar
.
7
‹
type
›
The
name
of
the
type
of
a
font
fi
le,
e.g.,
pk
(packed
bitmap),
tfm
(tex
font
metric),
afm
(adobe
font
metric),
vf
(virtual
font),
or
source
(
MET
AF
ONT
sour
ce).
‹
supplier
›
The
name
of
the
font
supplier
(to
whom
the
font
fi
le
belongs),
e.g.,
adobe
or
urw
.
‹
typeface
›
The
name
of
the
typeface
name
(for
this
font
fi
le),
e.g.,
times
or
cm
(for
Computer
Modern).
It
is
important
to
know
that
the
default
sear
ch
paths
in
teT
E
X
r
ely
on
this
dir
ectory
str
uctur
e.
So,
if
you
add
a
fi
le
to
the
wr
ong
dir
ectory
tr
ee,
e.g.,
a
T
eX
macr
o
somewher
e
in
the
fonts
subtr
ee,
that
fi
le
will
not
be
found
corr
ectly
.
2.2
Overview
of
the
prede
fi
ned
texmf
trees
As
described
in
the
pr
evious
section,
each
texmf
tr
ee
follows
a
well
de
fi
ned
dir
ectory
str
uctur
e.
This
section
lists
all
pr
ede
fi
ned
texmf
tr
ees
and
their
intended
purpose.
The
command
texconfig
conf
shows
you
the
values
of
the
variables
below
,
so
that
you
can
easily
fi
nd
out
how
they
map
to
dir
ectory
names
in
your
installation.
TEXMFCONFIG
The
tr
ee
speci
fi
ed
by
this
variable
will
be
used
by
teT
E
X’s
utilities
texconfig
,
updmap
and
fmtutil
to
stor
e
modi
fi
ed
con
fi
guration
data.
TEXMFV
AR
The
tr
ee
speci
fi
ed
by
this
variable
will
by
used
by
the
utilities
texconfig
,
updmap
and
fmtutil
to
stor
e
(cached)
r
untime
data
such
as
format
fi
les
and
gen-
erated
map
fi
les.
TEXMFHOME
The
expansion
of
this
variable
typically
depends
on
$HOME
,
so
this
dy-
namically
adjusts
for
each
user
to
an
individual
dir
ectory
.
The
idea
is
to
allow
users
to
stor
e
their
own
versions
of
macr
os,
fonts
etc.
in
this
tr
ee.
TEXMFSYSCONFIG
The
tr
ee
speci
fi
ed
by
this
variable
will
be
used
used
by
the
util-
ities
texconfig-sys
,
updmap-sys
and
fmtutil-sys
to
stor
e
modi
fi
ed
con
fi
gura-
tion
data.
TEXMSYSFV
AR
The
tr
ee
speci
fi
ed
by
this
variable
will
by
used
by
texconfig-sys
,
updmap-sys
and
fmtutil-sys
to
stor
e
(cached)
r
untime
data
such
as
format
fi
les
and
generated
map
fi
les.
TEXMFMAIN
This
variable
speci
fi
es
the
texmf
tr
ee
wher
e
some
vital
parts
of
the
sys-
tem
ar
e
installed,
such
as
helper
scripts
(e.g.
web2c/mktexdir
),
pool
fi
les
and
other
support
fi
les.
TEXMFLOCAL
This
variable
names
a
dir
ectory
tr
ee
which
should
be
used
for
system-
wide
installation
of
additional
or
updated
macr
o
packages,
fonts
etc.
TEXMFDIST
This
variable
names
the
dir
ectory
tr
ee
which
holds
the
macr
os,
fonts
etc.
as
originally
distributed.
8
2.3
The
fi
le
name
database
(ls-R)
texmf
tr
ees
can
get
very
lar
ge
and
to
speed
up
sear
ching
in
such
a
tr
ee,
a
fi
le
name
database
is
used.
A
fi
le
name
database
exists
in
the
r
oot
of
each
texmf
tr
ee
and
has
the
name
ls-R
.
It
should
list
each
fi
le
in
the
texmf
tr
ee.
The
command
texhash
can
be
used
to
build
an
up-to-date
fi
le
name
database
for
each
texmf
tr
ee.
It
should
be
used
after
fi
les
have
been
added
to
a
texmf
tr
ee.
However
,
you
don’t
need
to
r
un
texhash
for
fi
les
added
by
the
automatic
font
generation
or
the
texconfig
utility
.
2.4
Runtime
con
fi
guration
(texmf.cnf
fi
le)
Sear
ch
paths
and
other
de
fi
nitions
(e.g.,
the
static
sizes
of
some
arrays
in
T
E
X
or
other
pr
ograms)
can
be
set
up
in
con
fi
guration
fi
les
named
texmf.cnf
.
By
changing
the
de
fi
-
nitions
in
these
con
fi
guration
fi
les
(teT
E
X’s
main
texmf.cnf
is
web2c/texmf.cnf
in
the
main
texmf
tr
ee),
the
behavior
of
pr
ograms
can
be
changed
without
r
ecompiling
them.
Chapters
3
and
4
of
the
kpathsea
manual
(
texdoc
kpathsea
)
describe
the
path
sear
ch-
ing
con
fi
guration
in
detail.
Section
2.5
of
the
W
eb2c
manual
(
texdoc
web2c
)
describes
some
inter
esting
r
untime
parameters
that
you
might
want
to
change.
Some
changes
to
the
array
sizes
r
equir
e
you
to
r
ebuild
the
dump
fi
les
that
the
pr
o-
gram
uses.
Run
the
command
texconfig
init
to
r
ebuild
all
dump
fi
les
after
you
have
changed
one
of
the
array
sizes.
This
implementation
of
T
E
X
can
r
ead
and
write
fi
les
(as
can
every
implementation
of
T
E
X)
and
it
can
also
call
external
commands
(via
the
\write18
str
eam).
Some
variables
in
the
texmf.cnf
fi
le
contr
ol
access
to
these
featur
es.
The
possibility
to
call
external
commands
can
be
turned
on
or
o
ff
(default
is
o
ff
).
Access
to
fi
le
beginning
“
.
”
is
dis-
allowed
in
r
estricted
mode
(default
for
r
eading
fi
les).
In
paranoid
mode,
fi
le
access
is
even
mor
e
r
estricted
and
you
cannot
access
fi
les
outside
the
curr
ent
dir
ectory
tr
ee
(de-
fault
for
writing
fi
les).
If
the
fi
rst
line
of
a
document
starts
with
%&
,
it
can
be
used
to
pass
the
name
of
the
format
fi
le
and/or
a
TCX
fi
le.
Parsing
the
fi
rst
line,
is
an
extension
that
can
be
turned
on
or
o
ff
(default
is
o
ff
)
in
the
texmf.cnf
fi
le.
2.5
Using
Postscript
type
1
fonts
For
every
font
you
use
with
T
E
X,
a
TFM
(T
E
X
font
metric)
fi
le
is
needed.
T
ype
1
fonts
usually
do
not
have
the
same
encoding
that
is
used
by
T
E
X,
so
additional
metrics
that
do
some
r
e-encoding
(virtual
font
fi
les)
ar
e
often
needed.
For
a
lot
of
font
families,
these
font
metric
fi
les
and
additional
map
fi
les
that
you
need
(see
below)
can
be
found
on
CT
AN
servers
in
the
dir
ectory
fonts
.
If
support
for
your
fonts
cannot
be
found
ther
e,
you
can
use
the
fontinst
utility
(documentation:
texdoc
fontinst
)
to
cr
eate
these.
Postscript
type
1
fonts
can
be
used
by
dvips
,
dvipdfm
,
xdvi
,
gsftopk
,
ps2pk
and
pdfT
E
X.
All
of
these
pr
ograms
r
equir
e
that
you
set
up
map
fi
les
for
these
fonts.
T
o
ease
the
pr
ocess
of
adding
map
fi
le
entries
to
the
con
fi
guration
fi
les
that
ar
e
used
by
these
tools,
you
should
follow
the
following
steps:
9
•
if
your
fonts
alr
eady
come
with
a
map
fi
le,
put
that
fi
le
into
the
fonts/map/dvips/
misc
dir
ectory
in
the
main
texmf
tr
ee.
•
otherwise,
you
will
need
to
cr
eate
a
map
fi
le
yourself,
using
the
syntax
as
de-
scribed
in
the
dvips
manual
(
texdoc
dvips
);
make
sur
e
to
set
up
these
fonts
as
“
download
fonts
”
,
not
as
“
built
in
”
fonts.
•
r
un
the
command
texhash
and
then
make
the
map
fi
le
known
to
updmap
by
r
un-
ning
the
command
updmap
--enable
Map
file.map
(wher
e
file.map
denotes
the
fi
lename
of
your
map
fi
le)
The
pr
ograms
gsftopk
and
ps2pk
convert
Postscript
type
1
fonts
into
bitmap
fonts
and
make
these
fonts
accessible
to
DVI
drivers
that
do
not
dir
ectly
support
Postscript
type
1
fonts.
This
conversion
is
automatically
invoked
by
the
mktexpk
script.
That
script
calls
gsftopk
by
default.
If
you
do
not
have
installed
the
ghostscript
pr
ogram
(which
gsftopk
needs),
or
if
you
want
to
use
ps2pk
for
other
r
easons
(e.g.,
because
it
is
usually
faster)
you
just
need
to
de
fi
ne
the
variable
ps_to_pk
to
ps2pk
.
This
variable
can
be
set
in
your
envir
onment
or
in
the
mktex.cnf
fi
le
(see
below).
2.6
Con
fi
guration
fi
les
maintained
by
texcon
fi
g
The
texconfig
utility
is
a
user
interface
for
changing
the
con
fi
guration
of
the
teT
E
X
system.
The
con
fi
guration
is
stor
ed
in
several
individual
fi
les.
This
section
documents
the
names
of
these
fi
les,
their
location
in
the
texmf
tr
ee
and
their
content.
This
explains
how
texconfig
works
and
enables
you
to
manually
con
fi
gur
e
parameters
which
ar
e
not
supported
by
texconfig
.
•
dvips/config/config.ps
stor
es
con
fi
guration
information
for
dvips
.
The
de-
fault
values
ar
e:
600
dpi
r
esolution;
ljfour
MET
AF
ONT
mode;
A4
paper;
o
ff
set
for
printing:
0pt,0pt;
output
goes
to
lpr
command.
•
tex/generic/config/pdftexconfig.tex
This
fi
le
sets
some
defaults
for
pdfT
E
X,
e.g.
the
default
paper
size.
This
information
is
dumped
into
format
fi
les,
so
if
you
modify
this
fi
le
dir
ectly
(without
using
texcon
fi
g),
you
have
to
r
ebuild
the
format
fi
les
by
using
the
command
fmtutil
--all
.
•
xdvi/XDvi
This
fi
le
sets
some
defaults
(e.g.
media
size,
metafont
mode)
for
xdvi
.
It
is
r
ead
via
the
app-default
mechanism
of
X11.
Y
ou
can
override
these
app-
defaults
as
usual
(i.e.
via
a
fi
le
~/.Xdefaults
or
with
r
esour
ces
managed
by
xrdb
).
•
dvipdfm/config
de
fi
nes
the
defaults
for
dvipdfm
,
e.g.
the
default
paper
size,
the
command
to
convert
encapsulated
postscript
graphics
into
PDF
etc.
•
web2c/mktex.cnf
This
fi
le
sets
the
default
metafont
mode
used
for
automatically
generated
bitmap
fonts,
the
r
esolution
which
is
used
in
scripts
(e.g.
mktextfm
)
and
a
list
of
“
featur
es
”
used
for
automatic
font
generation.
The
most
important
“
featur
es
”
ar
e
described
below;
for
a
full
list,
see
section
2.2.9.1
of
the
kpathsea
manual
(
texdoc
kpathsea
).
10
appendonlydir
Set
the
sticky
bit
on
dir
ectories
that
have
to
be
cr
eated.
The
sticky
bit
has
the
e
ff
ect
that
a
fi
le
in
such
a
dir
ectory
can
only
be
r
emoved
by
the
owner
of
that
dir
ectory
or
by
the
owner
of
that
fi
le.
varfonts
When
this
option
is
enabled,
fonts
that
would
otherwise
be
written
to
some
texmf
tr
ee
go
below
the
VARTEXFONTS
dir
ectory
instead.
The
default
value
is
in
/var/tmp/texfonts
.
The
“
Linux
File
System
Standar
d
”
r
ecom-
mends
/var/tex/fonts
.
The
varfonts
setting
in
MT_FEATURES
is
overridden
by
the
envir
onment
variable
USE_VARTEXFONTS
:
if
set
to
1,
the
featur
e
is
en-
abled,
and
if
set
to
0,
the
featur
e
is
disabled.
texmfvar
For
ce
generated
fi
les
that
would
go
into
a
system
tr
ee
(as
de
fi
ned
by
SYSTEXMF
)
into
TEXMFVAR
.
The
varfonts
featur
e
takes
pr
ecedence
if
also
set.
A
user
can
override
this
setting
in
either
dir
ection
by
setting
USE_TEXMFVAR
to
1
or
0.
•
web2c/updmap.cfg
contr
ols
how
updmap
generates
map
fi
les
for
all
supported
tools.
Besides
some
general
parameters,
all
active
map
fi
les
ar
e
listed
her
e.
•
web2c/fmtutil.cnf
This
fi
le
de
fi
nes
which
format
fi
les
ar
e
built
(and
how)
and
which
fi
le
can
be
used
to
customize
the
hyphenation
patterns
that
ar
e
loaded
into
these
formats.
The
pr
ograms
fmtutil
and
texlinks
(which
ar
e
automatically
called
if
the
formats
ar
e
set
up
via
texconfig
)
operate
on
this
fi
le.
fmtutil
can
be
used
to
cr
eate
the
format
fi
les
accor
ding
to
the
“
r
ules
”
de
fi
ned
in
fmtutil.cnf
(for
a
brief
description,
just
call
fmtutil
--help
).
If
you
de
fi
ne
a
new
format
fi
le,
you
usually
also
need
a
symbolic
link
with
the
name
for
the
format
to
the
appr
opriate
T
E
X
engine
(e.g.,
latex
!
tex
).
T
o
cr
eate
these
links,
just
call
the
texlinks
script.
•
hyphenation
setup
fi
les
as
de
fi
ned
in
web2c/fmtutil.cnf
:
the
thir
d
fi
eld
of
the
fi
le
fmtutil.cnf
de
fi
nes
names
of
fi
les
which
can
be
edited
to
customize
hyphen-
ation
(for
the
format
which
is
named
in
the
fi
rst
fi
eld).
Since
fmtutil.cnf
itself
is
a
con
fi
guration
fi
le,
the
list
of
fi
les
in
the
thir
d
fi
eld
might
vary
.
T
able
2
shows
the
names
of
the
fi
les
used
in
the
default
con
fi
guration.
Additional
fi
les
(used
fi
le
name
used
by
format
tex/context/config/cont-usr.tex
cont-en
tex/generic/config/language.dat
latex,
pd
fl
atex
tex/lambda/config/language.dat
lambda,
lamed
tex/plain/config/language.def
etex,
pdfetex
T
able
2:
fi
les
for
setting
up
hyphenation
by
formats
that
ar
e
disabled
in
the
default
con
fi
guration)
ar
e:
platex/config/
language.dat
and
mex/config/mexconf.tex
.
11
2.7
Automatic
font
generation
By
setting
various
“
featur
es
”
(see
2.6
)
the
automatic
font
generation
can
be
customized
in
many
ways.
The
tool
texconfig
o
ff
ers
support
in
con
fi
guring
and
setting
up
the
dir
ectories
wher
e
automatically
generated
fonts
end
up.
In
the
default
con
fi
guration
of
teT
E
X,
all
automatically
generated
fonts
end
up
in
the
dir
ectory
tr
ee
which
is
speci
fi
ed
by
the
VARTEXFONTS
variable.
The
command
line
mode
of
texconfig
(
not
the
interactive
mode)
allows
you
to
manipulate
the
path
and
the
permissions
of
this
dir
ectory
tr
ee
and
also
adjusts
the
“
featur
es
”
for
automatic
font
generation
to
match
the
chosen
dir
ectory
permissions:
texcon
fi
g
font
vardir
DIR
This
changes
the
path
which
is
stor
ed
in
the
VARTEXFONTS
variable
to
DIR
.
Y
ou
must
have
write
permissions
to
the
main
texmf.cnf
fi
le,
be-
cause
the
variable
is
stor
ed
ther
e.
texcon
fi
g
font
rw
This
makes
the
VARTEXFONTS
dir
ectory
(and
subtr
ees
pk
,
tfm
,
source
)
world
writable
and
sets
the
“
featur
es
”
appendonlydir
and
varfonts
in
the
con
fi
g
fi
le
mktex.cnf
.
T
o
change
the
global
mktex.cnf
fi
le
(instead
of
modifying
an
individual
copy),
use
texconfig-sys
instead
of
texconfig
.
texcon
fi
g
font
ro
This
makes
the
VARTEXFONTS
dir
ectory
(and
subtr
ees
pk
,
tfm
,
source
)
writable
for
the
owner
only
and
sets
the
“
featur
es
”
texmfvar
in
the
con
fi
g
fi
le
mktex.cnf
.
T
o
change
the
global
mktex.cnf
fi
le
(instead
of
modifying
an
individ-
ual
copy),
use
texconfig-sys
instead
of
texconfig
.
The
assumption
behind
the
manipulations
of
texconfig
is
that
you
set
up
a
world-
writable
VARTEXFONTS
tr
ee
if
you
want
all
generated
fonts
(by
all
users)
to
be
stor
ed
ther
e.
If
you
set
the
global
VARTEXFONTS
tr
ee
to
r
ead-only
,
then
the
texmfvar
is
activated
which
r
esults
in
a
user
-speci
fi
c
default
destination
for
automatically
generated
fonts
(
$TEXMFVAR/fonts
).
2.8
TCX
fi
les
TCX
(T
E
X
character
translation)
fi
les
help
T
E
X
support
dir
ect
input
of
8-bit
international
characters
if
fonts
containing
those
characters
ar
e
being
used.
Speci
fi
cally
,
they
map
an
input
(keyboar
d)
character
code
to
the
internal
T
E
X
character
code
(a
superset
of
ASCII).
teT
E
X
has
the
TCX
fi
les
il1-t1.tcx
and
il2-t1.tcx
which
support
ISO
Latin
1
and
ISO
Latin
2,
r
espectively
,
with
Cork-encoded
fonts
(a.k.a.:
the
T1
encoding).
TCX
fi
les
for
Czech,
Polish,
and
Slovak
ar
e
also
pr
ovided.
All
TCX
fi
les
that
ar
e
distributed
as
part
of
teT
E
X
can
be
found
in
the
web2c
subdi-
r
ectory
of
the
main
texmf
tr
ee;
their
fi
le
name
extension
is
.tcx
.
Y
ou
can
specify
a
TCX
fi
le
to
be
used
for
a
particular
T
E
X
r
un
by
specifying
the
command-line
option
-translate-file=
tcxfile
or
(pr
eferably)
specifying
it
explic-
itly
in
the
fi
rst
line
of
the
main
document
%&
-translate-file=
tcxfile
.
Note,
how-
ever
,
that
parsing
the
fi
rst
line
of
an
input
fi
le
in
an
extension
that
is
disabled
by
de-
12
fault
and
has
to
be
turned
on
via
command
line
switch
(
-parse-first-line
)
or
in
the
texmf.cnf
fi
le
(see
section
2.4
).
When
pr
ocessing
a
document
using
a
TCX
fi
le,
you
usually
must
not
use
L
A
T
E
X’s
inputenc
package.
One
exception
to
this
r
ule
ar
e
TCX
fi
les
that
map
all
characters
to
their
original
position
such
as
cp8bit.tcx
,
cp227.tcx
and
natural.tcx
.
The
purpose
of
these
TCX
fi
les
is
to
manipulate
the
“
printability
”
attribute
in
T
E
X’s
internal
tables.
2.9
Creating
PDF
fi
les
If
you
want
to
cr
eate
PDF
documents
with
the
help
of
T
E
X,
ther
e
ar
e
at
least
thr
ee
dif-
fer
ent
ways
to
do
this
1.
translate
your
T
E
X
sour
ces
dir
ectly
into
PDF
by
using
pdfT
E
X.
2.
translate
DVI
fi
les
generated
by
T
E
X
into
PDF
by
using
the
dvipdfm
pr
ogram
(now
included
in
teT
E
X).
3.
translate
a
Postscript
fi
le
generated
by
T
E
X
and
dvips
into
PDF
by
using
Adobe
Acr
obat
or
the
ps2pdf
utility
included
in
ghostscript.
When
using
ps2pdf
,
you
should
make
sur
e
to
use
at
least
version
6.50
of
ghostscript.
Earlier
versions
ar
e
known
to
have
serious
r
estrictions
on
cr
eating
PDF
output.
No
matter
which
appr
oach
you
use,
ther
e
is
one
common
r
ule
when
cr
eating
quality
PDF
fi
les:
you
should
avoid
bitmap
fonts.
They
just
display
very
poorly
on
scr
een
when
used
in
PDF
documents
(which
is
caused
by
poor
bitmap
r
endering
of
Adobe
Acr
obat
Reader
in
all
versions
up
to
5.x).
Using
only
the
fonts
pr
ovided
by
teT
E
X,
you
have
mor
e
choices
for
which
fonts
to
use.
The
following
typeface
families
ar
e
included
in
Postscript
type
1
format:
•
Computer
Modern
and
the
AMS
fonts
(extended
versions
with
polish,
czech
and
slovak
and
r
ussian
letters
ar
e
available,
too);
a
special
extension
to
Computer
Modern
pr
oviding
lots
of
additional
characters
(most,
but
not
exclusively
accents)
ar
e
the
Latin
Modern
fonts
•
the
full
set
of
the
35
basic
“
LaserW
riter
fonts
”
(see
psnfss
documentation,
sup-
porting
other
fonts
ar
e
pazo,
tx/px
fonts)
•
Bitstr
eam
Charter
The
EC
fonts
ar
e
not
included
in
type
1
format
in
teT
E
X.
If
you
have
a
L
A
T
E
X
docu-
ment
that
uses
EC
fonts,
you
have
at
least
two
ways
to
get
ar
ound
this
pr
oblem.
The
fi
rst
is
to
stop
using
EC
fonts
—
which
can
in
most
cases
be
done
by
switching
to
the
Latin
Modern
fonts.
Usually
,
the
EC
fonts
ar
e
activated
by
\usepackage[T1]{fontenc}
or
\usepackage{t1enc}
and
you
just
have
to
add
\usepackage{lmodern}
.
The
second
is
to
use
the
CM-SUPER
T
ype
1
fonts,
not
included
in
teT
E
X,
but
available
on
CT
AN
servers
in
the
dir
ectory
fonts/ps-type1/cm-super
.
This
package
is
pr
etty
huge,
but
it
contains
all
EC
fonts
in
outline
format
and
much
mor
e.
13
If
the
Latin
Modern
solution
works
for
you,
this
is
the
r
ecommended
one
for
the
following
r
easons:
•
quality:
the
Latin
Modern
fonts
have
been
cr
eated
by
using
a
better
technology
and
they
have
been
car
efully
hand-optimized
(hinting,
kerning,
accent
position-
ing
etc.)
•
the
Latin
Modern
fonts
ar
e
alr
eady
included
in
teT
E
X
•
the
r
esulting
fi
les
ar
e
usually
much
smaller
3
Release
notes
for
teT
E
X
2.0
Some
default
settings
of
“
tex
,
the
W
eb2C
implementation
of
T
E
X
”
have
changed.
W
e
determined
that
some
extensions
wer
e
in
fact
in
con
fl
ict
with
the
strict
de
fi
nition
of
T
eX
as
laid
down
by
Knuth.
The
most
notable
change
is
that
parsing
of
%&
constr
ucts
in
the
fi
rst
line
of
an
input
fi
le
is
now
disabled
by
default
–
it
can
be
enabled
in
texmf.cnf
if
you
desir
e
this.
In
that
case,
tex
will
announce
itself
as
“
T
eXk
”
and
print
an
additional
banner
line
saying
that
%&
-line
parsing
is
enabled.
W
e
may
encounter
mor
e
places
wher
e
the
default
behaviour
is
not
what
it
should
be,
and
pr
oceed
to
make
this
optional
(and
by
default
o
ff
)
in
futur
e
versions
of
W
eb2C.
4
Release
notes
for
teT
E
X
3.0
This
section
brie
fl
y
describes
what
has
changed
since
the
last
major
r
elease.
4.1
New
programs
/
font
support
/
macro
packages
T
wo
pr
ograms
(see
section
1
)
have
been
added
with
this
r
elease:
Aleph
and
dvipng.
Many
macr
o
packages
have
been
added,
too.
The
lar
gest
additions
ar
e
the
packages
beamer
and
memoir
.
In
the
fonts
sections,
some
additions
and
updates
have
happened,
too.
The
lar
gest
change
in
this
ar
ea
is
the
addition
of
the
Latin
Modern
Fonts
(
lmodern
)
in
Postscript
T
ype
1
format.
These
fonts
ar
e
not
as
exhaustive
as
the
cmsuper
fonts,
but
they
ar
e
of
very
good
quality
and
su
ffi
cient
for
languages
which
use
Latin
characters.
Using
the
Latin
Modern
Fonts
is
in
most
cases
pr
eferable
over
using
the
ae
fonts
(e.g.
PDF
fi
les
with
accents
ar
e
sear
chable,
text
extraction
works
better).
4.2
Changes
to
web2c
•
T
E
X
now
uses
the
new
tex.web
(version
3.141592)
fr
om
December
2002
(
fi
xed
\xleaders
,
glueset,
weir
d
alignments).
14
•
encT
E
X
(see
texdoc
encdoc-e
)),
a
T
E
X
extension
by
Petr
Ol
k
for
input
r
eencod-
ing
is
now
available
(for
non
Omega
based
engines).
The
new
functionality
is
enabled
by
setting
the
-enc
switch
at
format
generation
time.
It
de
fi
nes
10
new
primitives
which
can
be
used
to
contr
ol
T
E
X’s
internal
character
translation
tables
and
pr
oper
multibyte
input
(e.g.
for
handling
UTF-8).
•
The
\input
primitive
in
tex
(and
mf
and
mpost
)
now
accepts
double
quotes
con-
taining
spaces
and
other
special
characters.
T
ypical
examples:
\input
"filename
with
spaces"
%
plain
\input{"filename
with
spaces"}
%
latex
See
the
W
eb2C
manual
for
mor
e:
texdoc
web2c
.
4.3
Modi
fi
cations
to
the
directory
structure
and
fi
le
searching
split
of
texmf
trees
The
instr
uction
of
installing
teT
E
X
fr
om
the
sour
ces
that
I
pr
ovide
have
been
changed.
The
unpacked
texmf
tarball
(
$prefix/share/texmf-dist
,
set
up
as
$TEXMFDIST
in
texmf.cnf
)
is
no
longer
mixed
with
the
fi
les
that
ar
e
installed
via
“
make
install
”
fr
om
building
and
installing
the
pr
ogram
sour
ces.
These
fi
les
(e.
g.
format
fi
les)
that
ar
e
mor
e
tied
up
with
the
pr
ograms
end
up
in
the
dir
ectory
$prefix/share/texmf
(
$TEXMFMAIN
).
So,
the
content
of
the
texmf
tarball
r
emains
completely
unchanged
in
$TEXMFDIST
and
can
easily
be
r
eplaced
with
a
new
version
without
loosing
other
r
untime
fi
les
that
ar
e
not
pr
ovided
elsewher
e.
changed
location
for
font
map
fi
les
Following
a
change
intr
oduced
with
version
1.1
of
the
T
E
X
Dir
ectory
Str
uctur
e
(see
texdoc
tds
),
font
map
fi
les
(
.map
)
ar
e
now
only
sear
ched
in
subdir
ectories
of
fonts/map
in
each
texmf
tr
ee.
The
subdir
ec-
tories
of
fontname
,
dvips
and
pdftex
ar
e
no
longer
sear
ched
for
these
fi
les.
The
texmf
tr
ees
fr
om
this
distribution
follows
this
convention,
but
you
might
need
to
r
earrange
some
fi
les
if
you
maintain
a
local
texmf
tr
ee.
W
ithin
the
fonts/map
tr
ee
the
fi
les
ar
e
or
ganized
by
syntax
and
package.
Known
map
fi
le
syntaxes
ar
e
dvips
(this
is
the
most
common
one),
pdftex
(a
superset
of
the
dvips
syntax,
e.
g.
the
psname
fi
eld
is
optional),
dvipdfm
and
vtex
.
If
some
fi
le
is
stor
ed
within
the
fonts/map/dvips
subtr
ee,
this
does
not
mean
that
dvips
is
the
only
pr
ogram
that
accesses
these
fi
les.
Other
pr
ograms
which
support
the
same
syntax
can
use
these
fi
les
as
well.
It’s
just
that
the
pr
ogram
dvips
has
given
its
name
for
this
syntax.
The
next
dir
ectory
level
speci
fi
es
the
package
that
the
map
fi
le
belongs
to.
Exam-
ple:
the
fi
le
charter.map
of
the
psnfss
package
follows
the
syntax
of
dvips
,
so
it
is
stor
ed
in
fonts/map/dvips/psnfss/charter.map
.
If
you
happen
to
see
that
some
application
cannot
fi
nd
a
map
fi
le
which
is
stor
ed
in
a
wr
ong
location,
you
have
to
move
that
fi
le
to
the
right
location.
T
ry
to
fi
nd
15
out
the
syntax
and
the
package
that
the
fi
le
belongs
to.
If
unsur
e,
you
can
al-
ways
choose
“
unknown
”
,
since
the
only
r
estriction
for
the
dir
ectory
tr
ee
below
fonts/map
is
that
all
fi
le
names
ar
e
unique.
The
pr
ecise
<syntax>/<package>
sub-
dir
ectory
does
not
a
ff
ect
sear
ching.
Do
not
for
get
to
update
the
fi
lename
database
(
ls-R
)
by
r
unning
the
command
mktexlsr
(r
esp.
texhash
which
is
the
same).
changed
search
path
for
map
fi
les
Map
fi
les
used
to
be
sear
ched
along
the
$TEXCONFIG
variable
(
“
dvips
con
fi
g
”
format
in
terms
of
kpathsea
internals).
This
has
been
changed
to
the
$TEXFONTMAPS
variable
(
“
map
”
format).
The
new
location
of
the
font
map
fi
les
is
included
in
the
new
default
setting
of
$TEXFONTMAPS
,
but
not
in
the
default
setting
of
$TEXCONFIG
.
The
r
esult
is
that
an
old
application
that
sear
ches
font
map
fi
les
along
the
“
dvips
con
fi
g
”
format
will
not
work.
For
the
“
C
”
API
of
kpathsea
this
change
means
that
map
fi
les
should
be
accessed
using
kpse_fontmap_format
instead
of
kpse_dvips_config_format
.
For
scripts
that
use
kpsewhich,
one
has
to
make
sur
e
that
--format=map
is
used
to
sear
ch
font
map
fi
les.
changed
location
for
font
encoding
fi
les
T
ogether
with
font
map
fi
les
(see
above),
the
font
encoding
fi
les
have
been
given
a
new
location,
too.
The
new
location
is
fonts/enc/<syntax>/<package>
.
So,
if
you
happen
to
see
some
application
to
fail
fi
nding
a
font
encoding
fi
le,
just
move
it
to
the
right
location
in
the
texmf
tr
ee
and
update
the
fi
lename
database.
omission
of
“
engine
”
directories
W
ithin
the
texmf
tr
ees,
the
dir
ectory
tr
ees
associated
with
the
names
of
T
E
X
engines
(e.
g.
etex
,
pdftex
,
omega
,
mltex
)
ar
e
no
longer
sear
ched
for
T
E
X
macr
o
packages.
This
means
that
the
$TEXINPUTS
sear
ch
path
now
lies
completely
within
the
tex
subtr
ee.
If
you
ar
e
using
the
above
mentioned
“
obsolete
”
locations
for
T
E
X
macr
o
pack-
ages,
you
have
to
move
them
into
the
tex
dir
ectory
tr
ee.
4.4
Changes
to
texcon
fi
g
/
updmap
/
fmtutil
Following
the
new
dir
ectory
layout,
it
is
desir
ed
not
to
modify
the
dir
ectory
tr
ee
speci-
fi
ed
by
the
$TEXMFDIST
variable
any
mor
e.
This
makes
it
necessary
to
r
edir
ect
generated
output
(e.g.
map
fi
les
cr
eated
by
updmap,
updated
con
fi
g
fi
les)
somewher
e
else.
A
new
appr
oach
was
taken
by
the
implementation
in
teT
E
X-3.0:
two
new
variables
have
been
intr
oduced
to
specify
wher
e
to
stor
e
this
data:
TEXMFCONFIG
con
fi
guration
data
TEXMFV
AR
variable
(cached)
r
untime
data
If
a
teT
E
X
installation
is
shar
ed
among
several
users,
each
of
them
can
now
use
teT
E
X’s
con
fi
guration
tools.
For
each
of
the
thr
ee
pr
ograms,
a
-sys
variant
exists.
Call-
ing
this
variant,
e.g.
texconfig-sys
,
is
the
same
as
calling
the
r
egular
variant,
except
16
that
the
variables
TEXMFCONFIG
and
TEXMFV
AR
ar
e
r
edir
ected
to
TEXMFSYSCON-
FIG
and
TEXMFSYSV
AR
r
espectively
.
This
means
that
the
output
tr
ees
for
these
com-
mands
will
be
TEXMFSYSCONFIG
and
TEXMFSYSV
AR.
The
idea
behind
this
is
as
follows:
in
the
default
settings
of
teT
E
X,
the
variables
TEXMFCONFIG
and
TEXMFV
AR
point
to
dir
ectories
within
the
user
’s
home
dir
ec-
tories.
This
means
that
each
user
can
have
his
own
con
fi
guration,
but
this
makes
it
di
ffi
cult
to
change
the
global
defaults.
That’s
wher
e
TEXMFSYSCONFIG
and
TEXMF-
SYSV
AR
come
into
play
.
These
global
tr
ees
ar
e
included
in
the
sear
ch
paths
of
all
users.
By
using
the
-sys
variant
of
the
tools
mentioned
above,
it
becomes
easy
to
adminis-
trate
the
global
defaults.
So,
if
for
example,
some
administrator
installs
a
font-package
that
comes
with
a
map
fi
le
in
a
system’s
tr
ee
(e.g.
TEXMFLOCAL),
then
he
should
use
updmap-sys
to
add
the
new
map
fi
le
to
the
global
con
fi
guration.
4.5
Changes
to
pdfT
E
X
•
All
parameters
pr
eviously
set
thr
ough
the
special
con
fi
guration
fi
le
pdftex.cfg
must
now
be
set
thr
ough
primitives;
pdftex.cfg
is
no
longer
supported.
Some
settings
(e.g.
the
default
papersize)
ar
e
loaded
via
pdftexconfig.tex
into
the
format
fi
les.
•
\pdfmapfile
and
\pdfmapline
pr
ovide
font
map
support
fr
om
within
a
docu-
ment.
•
Micr
otypographic
font
expansion
can
be
used
mor
e
easily
.
http://www.ntg.nl/pipermail/ntg-
pdftex/2004-
May/000504.html
•
See
the
pdfT
E
X
manual
for
mor
e:
texdoc
pdftex-a
.
4.6
pdfetex:
the
new
default
T
E
X
engine
teT
E
X
uses
pdfetex
for
all
formats
except
“
good-old
”
tex
.
So,
if
you
r
un
latex
,
the
underlying
engine
will
be
pdfetex
.
Some
(br
oken)
T
E
X
macr
os
assume
that
pdfT
E
X
is
r
unning
in
PDF
generation
mode
if
they
detect
primitives
that
pdfT
E
X
has
intr
oduced
(e.g.
\pdfoutput
).
This
is
wr
ong,
since
pdfT
E
X
can
also
be
used
(and
is
used)
to
gen-
erate
DVI
output.
A
r
eliable
way
of
detecting
PDF
output
mode
is
implemented
in
ifpdf.sty
which
works
for
plain
T
E
X
as
well
as
L
A
T
E
X.
4.7
Changes
to
xdvik
•
On
supported
platforms
the
default
toolkit
of
xdvi
is
now
Motif.
The
GUIs
for
both
toolkits
(Motif
and
Xaw)
have
been
updated:
Ther
e
is
a
page
list
for
easier
navigation
and
impr
oved
menus.
The
Motif
version
now
has
a
toolbar
and
a
‘Pr
efer
ences’
dialog
for
advanced
customizations.
User
pr
efer
ences
that
ar
e
set
via
this
dialog,
the
‘Options’
menu
and
other
dialogs
ar
e
now
saved
in
a
fi
le
~/.xdvirc
.
This
fi
le
overrides
other
X
defaults,
but
not
the
17
command-line
options.
(The
option
‘
-q
’
and
the
X
r
esour
ce
‘
.noInitFile
’
can
be
used
to
disable
this
featur
e).
•
The
new
GUI
elements
can
be
selectively
toggled
via
the
option
or
the
X
r
esour
ce
‘
-expertmode
’,
which
should
be
used
instead
of
‘
-expert
’/‘
-statusline
’.
•
The
functionality
of
oxdvi
has
been
mer
ged
into
xdvi
;
oxdvi
no
longer
exists
as
a
separate
binary
.
•
Xdvi
now
supports
string
sear
ch
and
text
selection
in
DVI
fi
les
(menu
‘Modes
!
T
ext
Selection’),
printing
DVI
fi
les
and
exporting
them
in
PDF
,
Postscript
and
plain
text
format.
Pages
can
be
marked
with
Mouse-2
in
the
page
list
to
select
them
for
printing/saving.
•
By
default,
xdvi
will
cr
eate
a
backup
copy
of
the
DVI
fi
le
so
that
viewing
and
navigating
still
works
when
the
DVI
fi
le
is
being
written
by
T
E
X.
•
Other
new
featur
es
include:
Support
for
color
specials
and
color
ed
hyperlinks
(customizable
via
the
‘
linkstyle
option
and
X
r
esour
ce),
a
‘
-watchfile
’
option,
a
‘
-unique
’
option
for
loading
new
fi
les
into
a
r
unning
instance
of
xdvi
,
support
for
hyperr
efs
‘hdvips’
specials,
and
a
history
of
r
ecently
viewed
fi
les
via
the
menu
‘File
!
Open
Recent’.
4.8
Changes
to
dvipsk
•
The
functionality
of
odvips
has
been
mer
ged
into
dvips
;
odvips
no
longer
exists
as
a
separate
binary
.
•
Fonts
used
in
included
graphics
fi
les
ar
e
no
longer
partially
downloaded.
4.9
Improved
documentation
•
The
fi
le
doc/index.html
in
the
distributed
texmf
tr
ee
pr
ovides
a
much
impr
oved
overview
of
the
included
documentation
and
also
pr
ovides
a
sear
ch
facility
for
various
T
E
X
r
elated
information
sour
ces.
This
fi
le
is
generated
by
a
PHP
script
which
is
included
in
teT
E
X
as
well.
•
The
PHP
script
doc/texdoc.php
is
able
to
o
ff
er
a
web
interface
to
the
information
pr
ovided
in
texdoctk
databases.
5
Resources
This
section
describes
wher
e
you
can
fi
nd
further
(or
mor
e
up-to-date)
material
and
support
in
the
world
of
T
E
X.
18
5.1
Helpindex
fi
le
for
the
documentation
tree
The
fi
le
index.html
in
the
r
oot
of
teT
E
X’s
documentation
tr
ee
is
a
guide
for
the
docu-
mentation
that
is
included
in
teT
E
X.
It
is
a
good
point
to
start
when
you
want
to
br
owse
thr
ough
the
documentation
or
sear
ch
for
the
solution
of
a
speci
fi
c
pr
oblem.
5.2
Internet
Newsgroups
If
you
encounter
a
pr
oblem
which
might
not
be
teT
E
X
speci
fi
c,
but
rather
a
general
pr
oblem
with
T
E
X
or
L
A
T
E
X
(e.g.,
“
How
can
I
format
a
section
heading
in
a
di
ff
er
ent
way?
”
),
you
should
not
raise
your
question
on
one
of
the
mailing
lists
for
teT
E
X.
In
the
following
newsgr
oups,
T
E
X-r
elated
matters
ar
e
discussed:
comp.text.tex
General
things
about
T
E
X.
news.answers
F
AQs
(also
T
E
X-r
elated
F
AQs).
comp.answers
F
AQs
(also
T
E
X-r
elated
F
AQs).
de.comp.text.tex
General
things
about
T
E
X
(German).
fr
.comp.text.tex
General
things
about
T
E
X
(Fr
ench).
comp.fonts
Font
matters.
comp.programming.literate
Literate
pr
ogramming.
5.3
T
E
X
User
Groups
If
you
enjoy
T
E
X,
you
can
join
a
T
E
X
user
gr
oup
to
get
support
and
softwar
e
and
help
the
T
E
X
community
by
your
membership.
The
web
site
of
the
T
E
X
User
Gr
oup
(TUG),
http://tug.org/
has
the
necessary
contact
information
for
several
T
E
X
user
gr
oups.
5.4
Mailing
Lists
All
teT
E
X
mailing
lists
ar
e
hosted
on
the
same
server
which
is
managed
by
Major
domo
softwar
e.
Administrative
r
equests,
e.g.,
to
(un)subscribe
or
to
get
an
ar
chive
of
a
list
ar
e
handled
by
the
addr
ess:
majordomo@dbs.uni-hannover.de
T
o
get
a
list
of
available
commands
that
the
Major
domo
server
understands,
just
send
the
message
“
help
”
to
the
server
(in
the
body
of
a
message,
not
in
the
header).
The
lists
ar
e:
tetex
General
discussions
+
bug
r
eports
about
teT
E
X.
General
T
E
X
matters
that
ar
e
not
teT
E
X-speci
fi
c
ar
e
not
discussed.
Especially
general
questions
about
T
E
X
should
not
be
dir
ected
to
this
list;
use
a
newsgr
oup
instead.
tetex-announce
This
(moderated,
low
tra
ffi
c)
list
is
used
for
important
announcements
about
teT
E
X,
such
as
new
r
eleases
or
important
updates.
19
tetex-pretest
This
is
used
to
discuss
beta
versions
of
teT
E
X
and
to
r
eport
bugs
in
these
versions.
Bug
r
eports
about
o
ffi
cial
(non-beta)
r
eleases
should
not
be
send
her
e,
but
to
the
tetex
list.
Some
of
the
packages
which
ar
e
contained
in
teT
E
X
(e.g.,
Omega
and
pdfT
E
X)
have
special
mailing
lists
or
web
r
esour
ces
on
their
own.
The
web
site
of
TUG,
http://tug.
org/
has
links
to
many
of
them.
5.5
Comprehensive
T
eX
Archive
Network
(CT
AN)
T
o
aid
the
ar
chiving
and
r
etrieval
of
T
E
X-r
elated
fi
les,
a
TUG
(T
eX
User
Gr
oup)
work-
ing
gr
oup
developed
the
Compr
ehensive
T
E
X
Ar
chive
Network
(CT
AN).
Each
CT
AN
site
has
identical
material,
and
maintains
authoritative
versions
of
its
material.
These
collections
ar
e
extensive;
in
particular
,
almost
everything
mentioned
in
this
article
is
ar
chived
at
the
CT
AN
sites,
even
if
its
location
isn’t
explicitly
stated.
The
CT
AN
sites
ar
e
curr
ently
dante.ctan.org
,
cam.ctan.org
and
tug.ctan.org
.
The
or
ganization
of
T
E
X
fi
les
on
all
these
sites
is
identical
and
starts
at
/tex-archive
.
T
o
r
educe
network
load,
please
use
the
CT
AN
site
or
mirr
or
closest
to
you.
A
complete
and
curr
ent
list
of
CT
AN
sites
and
known
mirr
ors
can
be
obtained
by
using
the
finger
utility
on
‘user
’
ctan@cam.ctan.org
(it
also
works
with
the
other
CT
AN
hosts);
it
is
also
available
as
fi
le
help/ctan/CTAN.sites
in
teT
E
X’s
documentation
tr
ee.
5.6
The
T
E
X
Catalogue
This
catalogue
lists
many
T
E
X,
L
A
T
E
X,
and
r
elated
packages
and
tools.
Most
ar
e
avail-
able
worldwide
online
fr
om
CT
AN,
the
Compr
ehensive
T
eX
Ar
chive
Network.
Links
ar
e
pr
ovided
in
this
catalogue
to
available
sour
ces
and
documentation.
The
teT
E
X
docu-
mentation
tr
ee
contains
a
version
of
this
catalogue
in
help/Catalogue
.
The
most
r
ecent
online
version
is
available
at
http://texcatalogue.sarovar.org/
5.7
Frequently
Asked
Questions
(F
AQs)
Documents
which
list
fr
equently
asked
questions
and
their
answers
(in
short:
F
AQs)
ar
e
collections
of
solutions
to
many
common
pr
oblems.
The
documentation
tr
ee
of
teT
E
X
contains
the
teT
E
X
F
AQ
in
the
dir
ectory
tetex
and
the
UKTUG
F
AQ
in
the
dir
ectory
help/faq/uktug-faq
.
The
teT
E
X
F
AQ
can
be
r
ead
by
the
command
texconfig
faq
.
References
[1]
Donald
E.
Knuth.
The
MET
AF
ONT
book
.
Addison-W
esley
,
1984.
[2]
Leslie
Lamport.
L
A
T
E
X:
A
Document
Pr
eparation
System
.
Addison-W
esley
,
2nd
edition,
1994.
20