summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2007-08-20 00:53:31 +0000
committerKarl Berry <karl@freefriends.org>2007-08-20 00:53:31 +0000
commite167bf48b8287c1f5b69d1cfed9bf01db39a306e (patch)
tree2d68c7832cfaecb8822ddf5e09af9e69cd1618ca /Master/texmf-doc/doc/english
parentecba2fb228fa7ad92c06db0f761d203e1eba2f0d (diff)
rm make-tex-work
git-svn-id: svn://tug.org/texlive/trunk@4770 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-doc/doc/english')
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/README56
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-018
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-029
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-016
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-024
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-0312
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-0433
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-03-0122
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0132
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0225
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0325
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0427
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0542
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0638
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-077
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0817
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-0916
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-015
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-025
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-0348
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0112
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0243
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0314
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0425
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0591
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0646
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0759
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0881
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-0933
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-07-018
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-10-0138
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-11-0119
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-017
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-024
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-01568
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-02427
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-03215
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-04151
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-05174
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-06181
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-0764
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-08191
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/apa.html903
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/apb.html2557
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/apc.html1168
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/apd.html229
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ape.html639
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch01.html2103
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch02.html2438
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch03.html1894
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch04.html2206
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch05.html3711
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch06.html3381
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch07.html2409
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch08.html2376
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch09.html1550
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch10.html782
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch11.html1139
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch12.html1542
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch13.html2491
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch14.html866
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch15.html958
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/ch16.html1805
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/co01.html187
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/amspell.pngbin882 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/arab.pngbin10347 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/badfont.err24
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/bbox.pngbin2379 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/bezier.pngbin5523 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/caffeine.pngbin917 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/cover.pngbin31217 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/eepic.pngbin6072 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/eight.mf19
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/epic.pngbin5326 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/fi-ligs.pngbin729 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/frog.pngbin13845 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/g-h.pngbin1805 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.140
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.241
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/hebrew-sample.pngbin9662 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/jgenji.pngbin12192 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/lint.pngbin2001 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/lithium.pngbin1067 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.16
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.211
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.312
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.412
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.56
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.64
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/mozart.pngbin1827 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-amt.pngbin5943 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-inf.pngbin5176 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-lol.pngbin6278 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ltx.pngbin6092 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ptx.pngbin6674 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/pgenji.pngbin12107 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/pictex-example.pngbin4636 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/pictexex.pngbin4636 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/pmc-sample.pngbin6473 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/pmcs-sample.pngbin6608 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/pmj-sample.pngbin3616 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/sample.pngbin7502 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.03.pngbin2329 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.04.pngbin6935 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.05.pngbin4264 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.01.pngbin4741 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.02.pngbin4595 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.03.pngbin6594 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.04.pngbin3294 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.05.pngbin4580 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.06.pngbin4614 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.07.pngbin2422 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.08.pngbin6538 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.09.pngbin4862 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.10.pngbin2653 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.11.pngbin1089 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.04.04.pngbin3140 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.04.pngbin4305 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.06.pngbin5677 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.01.pngbin470 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.02.pngbin1195 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.03.pngbin11216 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.04.pngbin5465 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.05.pngbin4352 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.06.pngbin5032 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.07.pngbin6691 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.08.pngbin11017 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.09.pngbin13845 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.11.pngbin5007 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.12.pngbin3728 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.13.pngbin4591 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.14.pngbin3374 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.20.pngbin3356 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.07.01.pngbin4219 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.08.03.pngbin4381 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.01.pngbin5118 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.02.pngbin5739 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.03.pngbin5006 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.04.pngbin3095 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.05.pngbin3590 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.06.pngbin4793 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.07.pngbin6790 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.08.pngbin2702 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.09.pngbin2614 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.10.pngbin3577 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.11.pngbin2300 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.12.pngbin3187 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.13.pngbin3480 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.14.pngbin4393 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.15.pngbin4326 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.16.pngbin4968 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.17.pngbin2733 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.01.pngbin3430 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.02.pngbin2730 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.03.pngbin1832 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.01.pngbin3628 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.02.pngbin4121 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.03.pngbin2546 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.04.pngbin4813 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.05.pngbin3441 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.01.pngbin10589 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.02.pngbin5226 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.03.pngbin4713 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.04.pngbin3736 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.05.pngbin3106 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/troffvstex.pngbin2327 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/two-rs.pngbin2001 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/we-we.pngbin1310 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/figures/xypic-example.pngbin5041 -> 0 bytes
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/index.html1956
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/mtw.css150
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/mtwcpyright.html63
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/pr01.html130
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/pr02.html1296
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/pt01.html489
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/pt02.html733
-rw-r--r--Master/texmf-doc/doc/english/make-tex-work/html/pt03.html948
177 files changed, 0 insertions, 46162 deletions
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/README b/Master/texmf-doc/doc/english/make-tex-work/examples/README
deleted file mode 100644
index d6c07fe3d73..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/README
+++ /dev/null
@@ -1,56 +0,0 @@
-This file is README dated 18 Apr 1994.
-
-This directory contains the examples from _Making TeX Work_:
-
-Title : Making TeX Work
-Author : Norman Walsh
-Publisher : O'Reilly and Associates
-Date : April, 1994
-ISBN : 1-56592-051-1
-Pages : 518
-Price : US$29.95
-
-The examples are:
-
-ex-01-01: example 1-1: An Example of a TeX Document
-ex-01-02: example 1-2: A typical bibliography database entry
-ex-02-01: example 2-1: A Simple Driver File
-ex-02-02: example 2-2: Local Variables in an Emacs Buffer
-ex-02-03: example 2-3: A Contrived Error
-ex-02-04: example 2-4: Revision Control Macros for TeX Documents Using RCS
-ex-03-01: example 3-1: The Document BADFONT.TeX
-ex-04-01: example 4-1: Plain TeX Input
-ex-04-02: example 4-2: LaTeX2e Input
-ex-04-03: example 4-3: LaTeX Input File
-ex-04-04: example 4-4: AMS-TeX Input File
-ex-04-05: example 4-5: Lollipop Input File
-ex-04-06: example 4-6: TeXinfo Input
-ex-04-07: example 4-7: The ChemTeX Source for Caffeine
-ex-04-08: example 4-8: The ChemStruct Source for the Lithium Cation
-ex-04-09: example 4-9: The MusicTeX Source for Figure 4-7
-ex-05-01: example 5-1: Font-shape Declaration with NFSS2
-ex-05-02: example 5-2: Font-shape declaration with NFSS2 (simplified)
-ex-05-03: example 5-3: The PStoTeXfont script
-ex-06-01: example 6-1: The Input for the Plain TeX Diagram
-ex-06-02: example 6-2: The LaTeX Input for Figure 6-2
-ex-06-03: example 6-3: The epic Input for Figure 6-3
-ex-06-04: example 6-4: The Input for Figure 6-4
-ex-06-05: example 6-5: PiCTeX Input for Figure 6-5
-ex-06-06: example 6-6: The XY-pic Input for Figure 6-6
-ex-06-07: example 6-7: The DraTeX Input for Figure 6-7
-ex-06-08: example 6-8: Converting EPS to a Bitmap with Ghostview
-ex-06-09: example 6-9: Script for Inserting a Captured TeXt Screen
-ex-07-01: example 7-1: A Sample Multilingual Document Using English and French
-ex-10-01: example 10-1: TeXinfo Commands
-ex-11-01: example 11-1: The Code for the Figure Eight
-ex-12-01: example 12-1: A Sample BIBTeX entry
-ex-12-02: example 12-2: A Tib style database entry
-ex-D-01 : example D-1: MakeTeXPK.pl
-ex-D-02 : example D-2: MakeTeXTFM.pl
-ex-D-03 : example D-3: dvidxx.btm
-ex-D-04 : example D-4: makepk.btm
-ex-D-05 : example D-5: enc-afm.pl
-ex-D-06 : example D-6: TeXtoXfont
-ex-D-07 : example D-7: PStoXfont
-ex-D-08 : example D-8: txt2verb.pl
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-01
deleted file mode 100644
index acb17e7c033..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-01
+++ /dev/null
@@ -1,8 +0,0 @@
-\def\ora{O'Reilly \& Associates}
-\font\orafont=grlg10
-\parskip=\baselineskip
-\parindent=0pt
-\pageno=5
-This book is published by \ora\ in
-the \textit{Nutshell} series.
-\bye
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-02 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-02
deleted file mode 100644
index 8439f035edf..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-01-02
+++ /dev/null
@@ -1,9 +0,0 @@
-@Book{kn:texbook,
- author = "Donald E. Knuth",
- title = "The {\TeX}book",
- publisher = "Addison-Wesley",
- year = 1989,
- edition = "Fifteenth",
- isbn = "0-201-13447-0"
- note = "Paperback ISBN: 0-201-13448-9"
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-01
deleted file mode 100644
index 09e32f3cde3..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-01
+++ /dev/null
@@ -1,6 +0,0 @@
-\documentstyle[ora]{book}
-\begin{document}
- \input{intro}
- \input{chap1}
- \input{chap2}
-\end{document}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-02 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-02
deleted file mode 100644
index 45593e4c7dd..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-02
+++ /dev/null
@@ -1,4 +0,0 @@
-% Local Variables:
-% TeX-master: "driver.tex"
-% TeX-command-default: "LaTeX"
-% End:
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-03 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-03
deleted file mode 100644
index 4992587b605..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-03
+++ /dev/null
@@ -1,12 +0,0 @@
-This is TeX version 3.141...
-** (flintstone.tex
-some
-messages [1]
-(fred.tex [2]
-some more
-messages
-[3] ) (wilma.tex [4]
-! Undefined control sequence.
-the dog \dino
- tipped over the car.
-l.6 the dog \dino\ tipped over the car.
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-04 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-04
deleted file mode 100644
index a949b916902..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-02-04
+++ /dev/null
@@ -1,33 +0,0 @@
- Documents Using RCS}
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-% RCS definitions...
-%
-\newif\ifdraft
-\def\RCSID$#1${%
- \ifdraft{\tolerance=100000%
- \hbadness=100000%
- \raggedright%
- \marginpar{\tiny Draft #1}}%
- \typeout{Draft #1}%
- \else\typeout{Production run #1}\fi%
-}
-
-\def\RCSmargid$#1: #2 #3 #4 #5 #6 #7${%
-% #1 = ``Id''
-% #2 = filename
-% #3 = vers
-% #4 = date
-% #5 = time
-% #6 = author
-% #7 = state [locker]
- \ifdraft
- \setbox0=\hbox to 0pt{%
- \tolerance=100000%
- \hbadness=100000%
- \parbox{4in}{%
- \rm\tiny #2\\ #3\\ #4}%
- \hss}%
- \marginpar{\box0}%
- \typeout{Draft Id: #2 #3 #4 #5 #6 #7}%
- \fi
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-03-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-03-01
deleted file mode 100644
index 3905e43def2..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-03-01
+++ /dev/null
@@ -1,22 +0,0 @@
-\documentstyle{article}
-% The following definition changes the font that LaTeX
-% uses for the 'Large' font. I have introduced a typo
-% into the definition, ``\fontsiz'' should be ``\fontsize''.
-%
-% The first time a \Large font is requested, an error will occur.
-%
-\renewcommand{\Large}{\fontsiz{17}{20pt}\selectfont}
-\begin{document}
-
-This text precedes the first section header.
-
-% Note: LaTeX uses the \Large font in section
-% headers...this will fail in a confusing way
-% because the error is deep within the definition
-% of \section where \Large is used...
-%
-\section{First Section}
-
-This is the first and only sentence of the first section.
-
-\end{document}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-01
deleted file mode 100644
index 1b7d26d9380..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-01
+++ /dev/null
@@ -1,32 +0,0 @@
-% Format: Plain
-\font\chapfont=cmbx12 scaled 1728
-\font\titlefont=cmbx12 scaled 2073
-\font\secfont=cmbx12 scaled 1200
-
-\parskip=\baselineskip
-\parindent=0pt
-\hsize=5in
-\hoffset=.75in
-
-\leftline{\chapfont Chapter 1}
-\vskip36pt
-
-\leftline{\titlefont Unsolved Problems}
-\vskip36pt
-
-\leftline{\secfont 1.1\ \ Odd Perfect Numbers}
-\vskip12pt
-
-A number is said to be {\it perfect\/} if it
-is the sum of its divisors. For example, $6$ is
-perfect because $1+2+3 = 6$, and $1$, $2$, and $3$
-are the only numbers that divide evenly into $6$
-(apart from $6$ itself).
-
-It has been shown that all even perfect numbers
-have the form $$2^{p-1}(2^{p}-1)$$ where $p$
-and $2^{p}-1$ are both prime.
-
-The existence of {\it odd\/} perfect numbers is
-an open question.
-\bye
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-02 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-02
deleted file mode 100644
index fd640088e08..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-02
+++ /dev/null
@@ -1,25 +0,0 @@
-% Format: LaTeX2e
-\documentclass{report}
-
-\setlength{\parskip}{\baselineskip}
-\setlength{\parindent}{0pt}
-
-\begin{document}
-
-\chapter{Unsolved Problems}
-
-\section{Odd Perfect Numbers}
-
-A number is said to be \emph{perfect} if it
-is the sum of its divisors. For example, $6$ is
-perfect because \(1+2+3 = 6\), and $1$, $2$, and $3$
-are the only numbers that divide evenly into $6$
-(apart from 6 itself).
-
-It has been shown that all even perfect numbers
-have the form \[2^{p-1}(2^{p}-1)\] where $p$
-and \(2^{p}-1\) are both prime.
-
-The existence of \emph{odd} perfect numbers is
-an open question.
-\end{document}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-03 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-03
deleted file mode 100644
index 3119cf8bab4..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-03
+++ /dev/null
@@ -1,25 +0,0 @@
-% Format: LaTeX
-\documentstyle{report}
-
-\setlength{\parskip}{\baselineskip}
-\setlength{\parindent}{0pt}
-
-\begin{document}
-
-\chapter{Unsolved Problems}
-
-\section{Odd Perfect Numbers}
-
-A number is said to be {\em perfect\/} if it
-is the sum of its divisors. For example, $6$ is
-perfect because \(1+2+3 = 6\), and $1$, $2$, and $3$
-are the only numbers that divide evenly into $6$
-(apart from 6 itself).
-
-It has been shown that all even perfect numbers
-have the form \[2^{p-1}(2^{p}-1)\] where $p$
-and \(2^{p}-1\) are both prime.
-
-The existence of {\em odd\/} perfect numbers is
-an open question.
-\end{document}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-04 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-04
deleted file mode 100644
index f6ac1adcc9b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-04
+++ /dev/null
@@ -1,27 +0,0 @@
-% Format: AMSTeX
-\documentstyle{amsppt}
-
-\parindent=0pt
-\parskip=\baselineskip
-\hoffset=.75in
-
-\topmatter
-\title \chapter{1} Unsolved Problems\endtitle
-\endtopmatter
-
-\document
-\head{1.1} Odd Perfect Numbers\endhead
-
-A number is said to be {\it perfect\/} if it
-is the sum of its divisors. For example, $6$ is
-perfect because $1+2+3 = 6$, and $1$, $2$, and $3$
-are the only numbers that divide evenly into $6$
-(apart from $6$ itself).
-
-It has been shown that all even perfect numbers
-have the form $$2^{p-1}(2^{p}-1)$$ where $p$
-and $2^{p}-1$ are both prime.
-
-The existence of {\it odd\/} perfect numbers is
-an open question.
-\enddocument
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-05 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-05
deleted file mode 100644
index cccb0e95601..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-05
+++ /dev/null
@@ -1,42 +0,0 @@
-% Format: Lollipop
-\DefineHeading:Chapter
- breakbefore:yes whiteafter:12pt
- line:start PointSize:20 Style:bold
- literal:Chapter Spaces:1 ChapterCounter
- line:stop
- vwhite:36pt
- line:start PointSize:24 Style:bold title
- line:stop
- vwhite:24pt
- Stop
-\DefineHeading:Section
- whitebefore:{20pt plus 2pt} whiteafter:14pt
- line:start PointSize:14 Style:bold
- ChapterCounter . SectionCounter
- Spaces:1 title line:stop
- label:start ChapterCounter . SectionCounter
- label:stop
- Stop
-\GoverningCounter:Section=Chapter
-\AlwaysIndent:no
-\Distance:parskip=12pt
-\Distance:hoffset=.75in
-\Distance:voffset=.5in
-\Start
-\Chapter Unsolved Problems
-
-\Section Odd Perfect Numbers
-
-A number is said to be {\it perfect\/} if it
-is the sum of its divisors. For example, $6$ is
-perfect because $1+2+3 = 6$, and $1$, $2$, and $3$
-are the only numbers that divide evenly into $6$
-(apart from $6$ itself).
-
-It has been shown that all even perfect numbers
-have the form $$2^{p-1}(2^{p}-1)$$ where $p$
-and $2^{p}-1$ are both prime.
-
-The existence of {\it odd\/} perfect numbers is
-an open question.
-\Stop
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-06 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-06
deleted file mode 100644
index cc95fc65a9a..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-06
+++ /dev/null
@@ -1,38 +0,0 @@
-\input texinfo @c -*- TeXinfo -*-
-@setfilename perf-inf.inf
-@ifinfo
- @paragraphindent 0
-@end ifinfo
-@iftex
- @defaultparindent=0pt @parindent=0pt
-@end iftex
-
-@node Top, , (dir), (dir)
-@chapter Unsolved Problems
-@section Odd Perfect Numbers
-
-A number is said to be @i{perfect} if it is
-the sum of its divisors. For example, 6 is
-perfect because
-@tex $1+2+3 = 6$,
-@end tex
-@ifinfo
-1+2+3 = 6,
-@end ifinfo
-and 1, 2, and 3 are the only numbers that divide
-evenly into 6 (apart from 6 itself).
-
-It has been shown that all even perfect numbers
-have the form
-@tex $$2^{p-1}(2^{p}-1)$$ where $p$ and $2^{p}-1$
-@end tex
-@ifinfo
-@center 2^(p-1) (2^p - 1)
-
-where p and 2^p - 1
-@end ifinfo
-are both prime.
-
-The existence of @i{odd} perfect numbers is an
-open question.
-@bye
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-07 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-07
deleted file mode 100644
index 45d24e38c54..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-07
+++ /dev/null
@@ -1,7 +0,0 @@
-\initial
-\len=4
-\def\H{\hbox{\rm H}}
-\def\C{\hbox{\rm C}}
-\def\O{\hbox{\rm O}}
-
-\[ \purine{$\H_3\C$}{$\O$}{$\C\H_3$}{Q}{$\O$}{Q}{Q}{D}{$\C\H_3$} \]
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-08 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-08
deleted file mode 100644
index d8c9b953434..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-08
+++ /dev/null
@@ -1,17 +0,0 @@
-\structure{\atom{~~Li$^+$}
-\side{\nwbelow\atom{O}
-\side{\nsingle\atom{H}\nnwbelow\atom{O}\side{\wsingle\atom{H}}
-\nsingle\atom{H}}\swsingle\atom{H}\wnwbelow\atom{O}
-\side{\wsingle\atom{H}}\nsingle\atom{H}}
-\side{\nebelow\atom{O}
-\side{\nsingle\atom{H}\nnebelow\atom{O}\side{\esingle\atom{H}}
-\nsingle\atom{H}}\sesingle\atom{H}\enebelow\atom{O}
-\side{\esingle\atom{H}}\nsingle\atom{H}}
-\side{\swbelow\atom{O}
-\side{\ssingle\atom{H}\sswbelow\atom{O}\side{\wsingle\atom{H}}
-\ssingle\atom{H}}\nwsingle\atom{H}\wswbelow\atom{O}
-\side{\wsingle\atom{H}}\ssingle\atom{H}}
-\side{\sebelow\atom{O}
-\side{\ssingle\atom{H}\ssebelow\atom{O}\side{\esingle\atom{H}}
-\ssingle\atom{H}}\nesingle\atom{H}\esebelow\atom{O}
-\side{\esingle\atom{H}}\ssingle\atom{H}}}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-09 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-09
deleted file mode 100644
index c86290fcc83..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-04-09
+++ /dev/null
@@ -1,16 +0,0 @@
-\begin{music}
-\parindent 1cm
-\def\nbinstruments{1}\relax
-\def\instrumenti{Piano}%
-\nbporteesi=2\relax
-\generalmeter{\meterfrac{4}{4}}\relax
-\debutextrait
-\normal
-\temps\Notes\ibu0f0\qh0{cge}\tbu0\qh0g|\hl j\enotes
-\temps\Notes\ibu0f0\qh0{cge}\tbu0\qh0g|\ql l\sk\ql n\enotes
-\barre
-\Notes\ibu0f0\qh0{dgf}|\qlp i\enotes
-\notes\tbu0\qh0g|\ibbl1j3\qb1j\tbl1\qb1k\enotes
-\temps\Notes\ibu0f0\qh0{cge}\tbu0\qh0g|\hl j\enotes
-\finextrait
-\end{music}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-01
deleted file mode 100644
index 48a3a5809aa..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-01
+++ /dev/null
@@ -1,5 +0,0 @@
-\DeclareFontShape{OT1}{logo}{m}{n}{%
- <-8>sub * cmr/m/n%
- <8><9><10>gen * logo%
- <10.95>logo10 at 10.95pt%
- <12->logo10}{}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-02 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-02
deleted file mode 100644
index 29914979d03..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-02
+++ /dev/null
@@ -1,5 +0,0 @@
-\DeclareFontShape{OT1}{logo}{m}{n}{%
- <-8>sub * cmr/m/n%
- <8-9>logo8%
- <9-10>logo9%
- <10->logo10}{}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-03 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-03
deleted file mode 100644
index 89f65e1c984..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-05-03
+++ /dev/null
@@ -1,48 +0,0 @@
-#!/usr/local/bin/bash
-#
-# This script file makes a new TeX font from a PS outline.
-#
-# Parameters are:
-#
-# name dpi bdpi [mag mode destdir]
-#
-# `name' is the name of the font, such as `ptmr'. `dpi'
-# is the resolution the font is needed at. `bdpi' is
-# the base resolution.
-#
-# This script ignores the remaining parameters. They are
-# left here to document the fact that the caller may provide
-# them. They may be provided because the caller thinks
-# MetaFont is going to do the work...
-#
-# Of course, this needs to be set up for your site.
-#
-# TEMPDIR needs to be unique for each process because of the
-# possibility of simultaneous processes running this script.
-
-TEMPDIR=/tmp/temp-tex-PS.$$
-NAME=$1
-DPI=$2
-BDPI=$3
-
-LOCALDIR=/usr/local/lib/mf/fonts
-DESTDIR=$LOCALDIR/pk
-
-BASENAME=$NAME.$DPI
-PFADIR=/usr/local/lib/tex/ps/outlines
-
-# Clean up on normal or abnormal exit
-trap "cd /; rm -rf $TEMPDIR" 0 1 2 15
-
-mkdir $TEMPDIR
-cd $TEMPDIR
-
-# We proceed by making a 10pt font at the resolution
-# requested...
-echo Making ${DPI}dpi version of $NAME.
-ps2pk -X$DPI -P10 -a$PFADIR/$NAME.afm \
- $PFADIR/$NAME.pfa ${BASENAME}pk
-
-mv ${BASENAME}pk $DESTDIR
-
-exit 0
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-01
deleted file mode 100644
index 173cc3c3607..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-01
+++ /dev/null
@@ -1,12 +0,0 @@
-\newdimen\unitlength
-\unitlength=1cm
-
-\def\plot(#1,#2){%
- \rlap{\kern#1\unitlength\raise#2\unitlength%
- \hbox{$\scriptstyle\bullet\;(#1,#2)$}}}
-
-\centerline{%
- \hbox{\plot(0,0)
- \plot(1,1)
- \plot(-3,2)}%
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-02 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-02
deleted file mode 100644
index e1bf051272f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-02
+++ /dev/null
@@ -1,43 +0,0 @@
-\unitlength=1.00mm
-\special{em:linewidth 0.4pt}
-\linethickness{0.4pt}
-\begin{picture}(93.00,40.00)
-\put(0.00,10.00){\line(1,0){70.00}}
-\put(70.00,10.00){\line(2,3){20.00}}
-\put(90.00,40.00){\line(-1,0){70.00}}
-\put(20.00,40.00){\line(-2,-3){20.00}}
-\put(70.00,10.00){\line(1,0){1.00}}
-\put(72.00,10.00){\line(1,0){1.00}}
-\put(74.00,10.00){\line(1,0){1.00}}
-\put(76.00,10.00){\line(1,0){1.00}}
-\put(78.00,10.00){\line(1,0){1.00}}
-\put(80.00,10.00){\line(1,0){1.00}}
-\put(82.00,10.00){\line(1,0){1.00}}
-\put(84.00,10.00){\line(1,0){1.00}}
-\put(86.00,10.00){\line(1,0){1.00}}
-\put(88.00,10.00){\line(1,0){1.00}}
-\put(90.00,10.00){\line(0,1){1.00}}
-\put(90.00,12.00){\line(0,1){1.00}}
-\put(90.00,14.00){\line(0,1){1.00}}
-\put(90.00,16.00){\line(0,1){1.00}}
-\put(90.00,18.00){\line(0,1){1.00}}
-\put(90.00,20.00){\line(0,1){1.00}}
-\put(90.00,22.00){\line(0,1){1.00}}
-\put(90.00,24.00){\line(0,1){1.00}}
-\put(90.00,26.00){\line(0,1){1.00}}
-\put(90.00,28.00){\line(0,1){1.00}}
-\put(90.00,30.00){\line(0,1){1.00}}
-\put(90.00,32.00){\line(0,1){1.00}}
-\put(90.00,34.00){\line(0,1){1.00}}
-\put(90.00,36.00){\line(0,1){1.00}}
-\put(90.00,38.00){\line(0,1){1.00}}
-\put(87.00,10.00){\line(0,1){3.00}}
-\put(87.00,13.00){\line(1,0){3.00}}
-\put(93.00,20.00){\vector(0,-1){10.00}}
-\put(93.00,30.00){\vector(0,1){10.00}}
-\put(93.00,25.00){\makebox(0,0)[cc]{$h$}}
-\put(30.00,7.00){\vector(-1,0){30.00}}
-\put(40.00,7.00){\vector(1,0){30.00}}
-\put(35.00,7.00){\makebox(0,0)[cc]{$w$}}
-\put(45.00,25.00){\makebox(0,0)[cc]{$A=h\times w$}}
-\end{picture}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-03 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-03
deleted file mode 100644
index 3ab8143acaf..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-03
+++ /dev/null
@@ -1,14 +0,0 @@
-\unitlength = 1mm
-\begin{picture}(50,100)(0,0)
-\put(0,0){\tiny \grid(50,50)(5,5)[0,0]}
-\put(25,25){\circle{50}}
-\drawline(15,0)(20,5)(30,10)(50,35)
-\drawline[-50](10,5)(15,10)(25,15)(45,40)
-\thicklines
-\dottedline{1.4}(5,10)(10,15)(15,25)(40,45)
-\dashline{2}(0,15)(5,20)(10,30)(35,50)
-\thinlines
-\begin{drawjoin}
-\jputfile{epicdata}{\picsquare}
-\end{drawjoin}
-\end{picture}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-04 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-04
deleted file mode 100644
index 0aeedce2493..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-04
+++ /dev/null
@@ -1,25 +0,0 @@
-\unitlength = 1mm
-\begin{picture}(100,50)(0,0)
-\put(0,0){\tiny \grid(100,50)(10,10)[0,0]}
-\bezier{500}(0,0)(0,0)(100,50)
-\bezier{500}(0,0)(10,0)(100,50)
-\bezier{500}(0,0)(20,0)(100,50)
-\bezier{500}(0,0)(30,0)(100,50)
-\bezier{500}(0,0)(40,0)(100,50)
-\bezier{500}(0,0)(50,0)(100,50)
-\bezier{500}(0,0)(60,0)(100,50)
-\bezier{500}(0,0)(70,0)(100,50)
-\bezier{500}(0,0)(80,0)(100,50)
-\bezier{500}(0,0)(90,0)(100,50)
-\bezier{500}(0,0)(100,0)(100,50)
-
-\bezier{500}(0,0)(0,50)(100,50)
-\bezier{500}(0,0)(0,40)(100,50)
-\bezier{500}(0,0)(0,30)(100,50)
-\bezier{500}(0,0)(0,20)(100,50)
-\bezier{500}(0,0)(0,10)(100,50)
-\bezier{500}(0,0)(0,0)(100,50)
-
-\multiput(0,0)(10,0){11}{\circle*{1}}
-\multiput(0,0)(0,10){6}{\circle*{1}}
-\end{picture}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-05 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-05
deleted file mode 100644
index 6be82ab7523..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-05
+++ /dev/null
@@ -1,91 +0,0 @@
-\newdimen\unit \unit=1.375in
-\newdimen\shadeunit
-\newif \ifFirstPass
-\FirstPasstrue
-%\FirstPassfalse % uncomment this after you have the size you want
-%
-\def\DF{{\cal A}}%
-%
-%The following figure appears in the preface to the \PiCTeX\ manual
-%
-$$
-\beginpicture
- \ifFirstPass
- \savelinesandcurves on "pictex-Arcsine.tex"
- \else
- \replot "pictex-Arcsine.tex"
- \fi
-% \ninepoint % (See Appendix E of the TeXbook.)
- \normalgraphs
- % Density plot
- \setcoordinatesystem units <\unit,.4\unit> point at 0 0
- \setplotarea x from 0 to 1, y from 0 to 2.5
- \axis bottom invisible label {\lines {$t$\cr
- shaded area is $\DF(\beta) - \DF(\alpha)$\cr}} ticks
- numbered from 0.0 to 1.0 by 0.5
- unlabeled short quantity 11
- length <0pt> withvalues $\alpha$ $\beta$ / at .65 .85 / /
- \axis left invisible label {$a(t)$} ticks
- numbered from 0.0 to 2.0 by 1.0
- unlabeled short from 0.5 to 2.5 by 1.0 /
- \plotheading{\lineskiplimit=1pt \lines{%
- Density\cr
- $a(t) = 1\big/\bigl(\pi \sqrt{t(1-t)}\,\bigr)$\cr
- of the arc sine law\cr}}
- \grid 1 1
- \putrule from .65 0.0 to .65 .66736
- \putrule from .85 0.0 to .85 .89145
- \shadeunit=.2\unit \divide\shadeunit by 12
- \setshadegrid span <\shadeunit> point at .75 0
- \setquadratic
- \vshade .65 0 .66736 <,,,1pt> .75 0 .73511 .85 0 .89145 /
- % Move origin to (.5,0)
- % Left half}
- \ifFirstPass
- \setcoordinatesystem point at -.5 0
- \inboundscheckon
- \plot -.48429 2.55990 -.47553 2.06015 -.46489 1.72936 /
- \inboundscheckoff
- \plot -.46489 1.72936 -.43815 1.32146 -.40451 1.08308
- -.36448 .92999 -.31871 .82623 -.26791 .75400
- -.21289 .70358 -.12434 .65727 .0 .63662 /
- % Right half
- \inboundscheckon
- \plot .48429 2.55990 .47553 2.06015 .46489 1.72936 /
- \inboundscheckoff
- \plot .46489 1.72936 .43815 1.32146 .40451 1.08308
- .36448 .92999 .31871 .82623 .26791 .75400
- .21289 .70358 .12434 .65727 .0 .63662 /
- \fi
- % Distribution function
- % Set origin of new coordinate system 1.7*1.375in=2.34in
- % to the right of the original origin.
- \setcoordinatesystem units <\unit,\unit> point at -1.7 0
- \setplotarea x from 0 to 1, y from 0 to 1
- \axis bottom label {$x\vphantom{t}$} ticks
- numbered from 0.0 to 1.0 by 0.5 unlabeled short quantity 11 /
- \axis left label {$\DF(x)$} ticks
- numbered from 0.0 to 1.0 by 0.5 unlabeled short quantity 11 /
- \plotheading{\lines{%
- Distribution function\cr
- $\DF(x) = {2\over \raise1pt\hbox{\seveni ^^Y}}
- \arcsin(\sqrt{x}\,)$\cr
- of the arc sine law\cr}}
- \linethickness=.25pt \grid {20} {20}
- \linethickness=.4pt \grid 2 2
- % Left half
- % Now move origin of coordinate system up to (.5,.5)
- \ifFirstPass
- \setcoordinatesystem point at -2.2 -.5
- \plot -.50000 -.50 -.49901 -.48 -.49606 -.46
- -.49104 -.44 -.48439 -.42 -.47553 -.40 -.46489 -.38
- -.43815 -.34 -.40451 -.30 -.36448 -.26 -.31871 -.22
- -.26791 -.18 -.21289 -.14 -.12434 -.08 .0 .0 /
- % Right half
- \plot .50000 .50 .49901 .48 .49606 .46
- .49104 .44 .48439 .42 .47553 .40 .46489 .38
- .43815 .34 .40451 .30 .36448 .26 .31871 .22
- .26791 .18 .21289 .14 .12434 .08 .0 .0 /
- \fi
-\endpicture
-$$
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-06 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-06
deleted file mode 100644
index c589bdde904..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-06
+++ /dev/null
@@ -1,46 +0,0 @@
-% Graph representing BAWL term [1]++[2]. [XY-pic & -*-tex-*-]
-% by Kristoffer H. Rose <kris@diku.dk>
-%
-\def\n#1{\llap{{\sevenit#1\/}:\,}}
-\def\op#1{(\mskip-.5\thinmuskip{#1}\mskip-.5\thinmuskip)}
-\def\concat{\mathbin{\text{\rm+\kern-.5em+}}}
-%
-\def\du#1#2{%
- % #1: slidesign, #2: #rows to go down.
- \save\aftergo{\go="p",[0,0]!<#1\jot,0pt>%
- \xto`d[#2,0]+<-2.5pc,-.8pc>`"p" "p"\restore}}
-%
-\def\dul#1#2#3{%
-% #1: slidesign, #2: #rows to go down; #3: #columns to go left.
-\save\aftergo{\go="p",[0,0]!<#1\jot,0pt>%
-\xto`d[#2,0]+<-2.5pc,-.8pc>`[#2,-#3]+<-2.5pc,0pc> `"p" "p"\restore}}
-%
-\spreaddiagramrows{-1.4pc}
-\spreaddiagramcolumns{-1pc}
-%
-$$
-\displaylines{\quad
- \left\lceil\openup-\jot\eqalign{
- [1]\concat[2] \quad\text{where}\qquad
- [\,] \concat ys &= ys \cr
- (x:xs) \concat ys &= x:(xs \concat ys)}\right\rceil
-\hfill\cr\hfill
- =\qquad
- {\diagram&& & & &&\n1\@\dlto\xto[2,2]\\
- & & & & &\n2{!\@}\xto[3,-2]\drto\\
- & & & & &&\n3\op:\dlto\dto&&\n4\op:\dlto\dto\\
- & & & & &\n51&\n6[\,] &\n72&\n8[\,]\\
- & & &\n{10}\lor\dlto\drrto \go+<-3em,0em>="10"\\
- & &\n{11}\lambda \dlto\ddto&&&\n{12}\lambda \dlto\drto\\
- &\n{13}\@\dlto\drto&& &\n{14}\@\dlto\drto
- &&\n{15}\op:\du04[3,-2]\drrto\\
-\n{16}{!\@}\dul000"10"\drto&&\n{17}{?}&\n{18}{!\@} \dul023"10" \drto
- &&\n{19}{?}&&&\n{20}\@\ddlto\du00[0,-3]\\
- &\n{21}[\,]& & &\n{22}\op:\dto\drto&& & &\\
- & & & &\n{23}{?}&\n{24}{?}
- &&\n{25}\@ \dul-27"10"\du+3[0,-2]\\
- & & & & & & &\\
- & & & & & & &\\
- & & & & & & &\enddiagram}
-\quad\cr}
-$$
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-07 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-07
deleted file mode 100644
index e203af7fad7..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-07
+++ /dev/null
@@ -1,59 +0,0 @@
-\Draw \Ragged(4) %%%%%%%%% tree %%%%%%%%%%%
-
-\Define\DotsToLoc(1){ \MarkLoc(x)
- \CSeg\DoLine(x,#1)(5){
- \MoveF(-3)\LineF(1)} }
-\PictNode(3){ \IF \EqText(,#2) \THEN \Text(--#1--) \ELSE
- \ThreeDim(#1,#2,#3)
- \MarkPLoc(1) \Line(50,0,0) \MarkPLoc(2) \Line(0,50,0)
- \MarkPLoc(3) \Line(-50,0,0) \MarkPLoc(4) \Line(0,-50,0)
- \Move(0,0,50) \MarkPLoc(1')
- \Move(50,0,0) \MarkPLoc(2') {\Line(0,0,-50)}
- \Line(0,50,0) \MarkPLoc(3') {\Line(0,0,-50)}
- \Line(-50,0,0) \MarkPLoc(4') {\Line(0,0,-50)}
- \Do(1,4){ \Do(1,4){
- \MarkPLoc(p\Val\I) \I+1; \Move(0,0,-16.66666)
- } \Move(16.66666,0,66.66666) }
- \TwoDim
- \MoveToLL(3,4)(4',1') \DotsToLoc(1') \DotsToLoc(1)
- \MoveToLL(2,3)(1',2') \DotsToLoc(1')
- \PaintQuad(p0,p1,p5,p4) \PaintQuad(p2,p3,p7,p6)
- \PaintQuad(p5,p6,p10,p9) \PaintQuad(p8,p9,p13,p12)
- \PaintQuad(p10,p11,p15,p14)
- \MoveToLoc(1) \CSeg[0.5]\Move(1,2) \Move(0,-5)
- \EntryExit(0,1,0,0) \Text(--(#1,#2,#3)--)
- \EndTwoDim
- \EndThreeDim \FI }
-
-\Define\MyEdge(2){\EdgeTo(#1,#2,0,1)} \TreeAlign(V,0,-1)(0,0,0)
-\TreeSpec(o,\OvalNode&r,\RectNode)()(\MyEdge)
-\TreeSpace(C,10,15) \AdjTree(A,0..0,0,-201,201,0 )
-\Tree()(
- 3,o,perspective~~projections~~eye~at~{(x,y,z)},, //
- 2,r,125,100,-100 & 0,r,75,75,-100 & 0,r,125,75,-100 //
- 0,r,125,125,-200 & 0,r,75,75,-200 //)
-
-%%%%%%%%% graph %%%%%%%%%%%
-
-\MoveToNode(2..1,2.5,-1) \MarkLoc(1)
-\MoveToNode(1..2,1,-1.5) \MarkLoc(2)
-\CSeg\Scale(1,2) \Scale(0.16666,0.14286)
-
-\Axis(1,2)(E3,&&&&&&&)
-\Axis(1,2)(S3,0&1&2&3&4&5&6)
- \MoveToLoc(1)
-\Table\x{ -1,2 & 0,5 & 4,-3 & -1,-4 & -2,0 }
- \PenSize(1.5pt) \Move(1,0) \x(0,99){\Line}
-\Table\x{ 3,3 & 1,-5 & -1,-2 & -3,4 }
- \Move(1,4) \x(0,99){\Line}
-
-%%%%%%%%% DraTeX+AlDraTeX logos %%%%%%%%%%%
-
-\it \TextNode(1){\Text(--#1--)}
-\MoveToNode(0..0,0,1) \Units(1pt,1pt) \Move(-60,0)
-\EntryExit(1,1,0,0) \Node(d)(--Dra\TeX--)
-\MoveToNode(2..0,-1,1) \Move(0,40) \EntryExit(-1,-1,0,0)
-\Node(a)(--Al~~Dra~~\TeX--) \PenSize(0.75pt)
-\ArrowHeads(2) \CurvedEdgeAt(d,-1,-1,a,0,1)(225,1.1,70,1.3)
-
-\EndDraw
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-08 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-08
deleted file mode 100644
index 9cbd15ae66d..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-08
+++ /dev/null
@@ -1,81 +0,0 @@
-#! perl
-#
-# Usage: gs-eps epsfile <outputfile> <resolution> <device>
-#
-# Where: epsfile is the encapsulated postscript file
-# outputfile is the output file (the default name
-# is <basename epsfile>.<device>)
-# resolution is the output resolution (default=300)
-# device is the GS driver to use (default=pbm)
-
-($epsfile,$outputfile,$res,$device) = @ARGV;
-
-if (! $epsfile) {
- printf "Usage: gs-eps epsfile <outputfile> <resolution>";
- printf " <gsdriver>\n";
- printf "Note: parameters are positional. To specify a";
- printf " driver, you\n";
- printf "must also specify an outputfile and resolution.\n";
- exit 1;
- }
-
-$epsfile =~ tr/\\/\//; # translate \foo\bar -> /foo/bar
-
-if (! -r $epsfile) {
- printf "Cannot read file: $epsfile\n";
- exit 1;
- }
-
-if (! $res) { $res = 300 }
-if (! $device) { $device = "pbm" }
-
-if (! $outputfile ) {
- @pathname = split(/\//,$epsfile);
- $outputfile = $pathname[$#pathname];
- $outputfile =~ s/.eps$//;
- $outputfile = join(".", $outputfile, $device);
- }
-
-printf "Converting $epsfile to $outputfile at ${res}dpi...\n";
-
-open (EPSFILE,$epsfile);
-
-undef $bbox;
-undef $showpg;
-while (<EPSFILE>) {
- $bbox = $_ if /\%\%\s*BoundingBox:\s*\d+\s+\d+\s+\d+\s+\d+/;
- $showpage = $_ if /showpage/;
- last if ($bbox && $showpage);
- }
-
-if (! $bbox) {
- printf "Cannot find a bounding box in $epsfile";
- exit 1;
- }
-
-$bbox =~ s/\D*//; # remove everything preceding the digits
-
-($llx,$lly,$urx,$ury) = split(/\s/,$bbox);
-
-$xsize = sprintf("%d", (($urx - $llx) * $res / 72) + 0.5);
-$ysize = sprintf("%d", (($ury - $lly) * $res / 72) + 0.5);
-
-printf "$llx neg $lly neg translate .gt. gs-eps-a.$$\n";
-printf "quit .gt. gs-eps-b.$$\n";
-
-if (! $showpg) {
- printf "showpage .gt. gs-eps-b.$$\n";
- printf "quit .gtgt. gs-eps-b.$$\n";
- }
-
-# join sillyness to keep the length of lines in the
-# script small enough to print in the book.
-$gscmd = join(" ", "gs -sDEVICE=$device",
- "-q -sOutputFile=$outputfile",
- "-g${xsize}x${ysize} -r$res",
- "gs-eps-a.$$ $epsfile -",
- ".lt. gs-eps-b.$$");
-
-printf "$gscmd\n";
-
-printf "rm -f gs-eps-a.$$ gs-eps-b.$$\n";
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-09 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-09
deleted file mode 100644
index 0852abdb0c9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-06-09
+++ /dev/null
@@ -1,33 +0,0 @@
-% use any IBM OEM encoded fixed width font!
-\font\screenfont=ncrr-ibm at 7pt
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-% These macros are derived from The TeXbook pg 380-381
-\def\uncatcodespecials{\def\do##1{\catcode`##1=12 }\dospecials}
-\def\setupverbatim{\screenfont%
- \def\par{\leavevmode\endgraf\relax}%
- \obeylines\uncatcodespecials%
- \catcode`\\=0\catcode`\{=1\catcode`\}=2\obeyspaces}
-{\obeyspaces\global\let =\ } % let active space be a control space
-\def\screenlisting#1{\par\begingroup%
- \def\c##1{\char##1}\setupverbatim\input{#1}%
- \endgroup}
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\def\screenbox#1{%
- \vbox{\offinterlineskip%
- \parskip=0pt\parindent=0pt%
- \screenlisting{#1}}}
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-% Input converted file '#1' and set it inside a box with '#2' padding
-% space around the image.
-\def\screendump#1#2{%
- \hbox{\vrule%
- \vbox{\hrule%
- \hbox{\hskip#2%
- \vbox{\vskip#2%
- \def\twentyxs{xxxxxxxxxxxxxxxxxxxx}%
- \setbox0=\hbox{\screenfont\twentyxs\twentyxs\twentyxs\twentyxs}%
- \hbox to \wd0{\screenbox{#1}\hss}%
- \vskip#2}%
- \hskip#2}%
- \hrule}%
- \vrule\hss}}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-07-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-07-01
deleted file mode 100644
index fa87ff6c02a..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-07-01
+++ /dev/null
@@ -1,8 +0,0 @@
- Using English and French}
-\documentstyle[english,francais]{article}
-\begin{document}
-This is a document which uses both English and
-French. \selectlanguage{french} Mais, Je ne parle plus
-la francais. \selectlanguage{english} So I won't try
-to make this example very long.
-\end{document}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-10-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-10-01
deleted file mode 100644
index cc95fc65a9a..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-10-01
+++ /dev/null
@@ -1,38 +0,0 @@
-\input texinfo @c -*- TeXinfo -*-
-@setfilename perf-inf.inf
-@ifinfo
- @paragraphindent 0
-@end ifinfo
-@iftex
- @defaultparindent=0pt @parindent=0pt
-@end iftex
-
-@node Top, , (dir), (dir)
-@chapter Unsolved Problems
-@section Odd Perfect Numbers
-
-A number is said to be @i{perfect} if it is
-the sum of its divisors. For example, 6 is
-perfect because
-@tex $1+2+3 = 6$,
-@end tex
-@ifinfo
-1+2+3 = 6,
-@end ifinfo
-and 1, 2, and 3 are the only numbers that divide
-evenly into 6 (apart from 6 itself).
-
-It has been shown that all even perfect numbers
-have the form
-@tex $$2^{p-1}(2^{p}-1)$$ where $p$ and $2^{p}-1$
-@end tex
-@ifinfo
-@center 2^(p-1) (2^p - 1)
-
-where p and 2^p - 1
-@end ifinfo
-are both prime.
-
-The existence of @i{odd} perfect numbers is an
-open question.
-@bye
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-11-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-11-01
deleted file mode 100644
index ea60ed245c5..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-11-01
+++ /dev/null
@@ -1,19 +0,0 @@
-mode_setup;
-u# := 2mm#;
-define_pixels(u);
-
-beginchar("A", 8u#, 9u#, 5u#);
- z1 = ( 0u, 0u);
- z2 = ( 8u, 0u);
- z3 = ( 1u, 8u);
- z4 = ( 7u, 8u);
- pickup pencircle scaled 1u#;
- draw z4 .. z1 .. z2 .. z3 .. cycle;
- pickup pencircle scaled 3u#;
- drawdot z1;
- drawdot z2;
- drawdot z3;
- drawdot z4;
-endchar;
-
-\end
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-01
deleted file mode 100644
index 0f0ccfadbbf..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-01
+++ /dev/null
@@ -1,7 +0,0 @@
-@book{kn:texbook,
- author = "Donald E. Knuth",
- title = "The {\TeX}book",
- publisher = "Addison-Wesley",
- year = 1989,
- edition = "Fifteenth",
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-02 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-02
deleted file mode 100644
index 36100d1df00..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-12-02
+++ /dev/null
@@ -1,4 +0,0 @@
-%A Donald E. Knuth
-%T The \TeX{}book
-%I Addison-Wesley
-%D 1989
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-01 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-01
deleted file mode 100644
index 391127e360e..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-01
+++ /dev/null
@@ -1,568 +0,0 @@
-#!/usr/local/bin/perl
-#
-# MakeTeXPK.pl version 1.0, Copyright (C) 1993,94 by Norman Walsh.
-# NO WARRANTY. Distribute freely under the GNU GPL.
-#
-# This script attempts to make a new TeX PK font, because one wasn't
-# found. Parameters are:
-#
-# name dpi bdpi [[[magnification] mode] subdir]
-#
-# `name' is the name of the font, such as `cmr10' (*NOT* cmr10.mf).
-# `dpi' is the resolution the font is needed at.
-# `bdpi' is the base resolution, useful for figuring out the mode to
-# make the font in.
-# `magnification' is a string to pass to MF as the magnification.
-# `mode' if supplied, is the mode to use.
-#
-# This script was designed with two goals in mind: to support recursive
-# subdirectory searching for fonts and to provide support for PK files
-# built from both MF fonts and PS fonts. It also supports the Sauter
-# and DC fonts which can be built at any design size.
-#
-# This script was designed and tested with the following directory structure
-# in mind: each typeface is stored in its own directory with appropriate
-# subdirectories for font sources, metrics, and glyphs. The script may not
-# work exactly right if you use a different directory structure (the font
-# installation, in particular, will probably be incorrect). However,
-# several other versions of MakeTeXPK exist which will handle simpler
-# directory structures, so you need not feel compelled to use the one
-# described here.
-#
-# For MF fonts: (... is usually something like /usr/local/lib/tex/fonts)
-#
-# .../typeface/src holds the sources
-# /tfm holds the TFM files
-# /glyphs root for glyphs
-# /glyphs/mode holds the PK files for "mode".
-#
-# For PS fonts: (... is usually something like /usr/local/lib/tex/fonts)
-#
-# .../typeface/afm holds the AFM files
-# /tfm holds the TFM files
-# /vf holds the VF files
-# /vpl holds the VPL files
-# /glyphs root for glyphs
-# /glyphs/pk/999dpi holds the PK files at 999 dpi created by ps2pk
-# /glpyhs/type1 holds the type1 PFA/PFB sources for the fonts
-#
-
-require "getopts.pl";
-$rc = &Getopts ('v'); # Get options from the user...
-
-$USE_MODE_IN_DEST = 1; # Does the destination directory name include
- # the name of the mode?
-
-$VERBOSE = $opt_v || $ENV{"DEBUG_MAKETEXPK"}; # Verbose?
-
-chop($CWD = `pwd`); # Where are we?
-$TEMPDIR = "/tmp/mkPK.$$"; # Where do temp files go?
-$MFBASE = "&plain"; # What MF base do we use by default?
-
-# Where are fonts stored?
-$TEXFONTS = $ENV{"TEXFONTS"} || ".:/usr/local/lib/fonts//";
-
-# Define modes that should be used for base resolutions...
-$DPI_MODES{300} = "laserwriter";
-$DPI_MODES{200} = "FAX";
-$DPI_MODES{360} = "lqhires";
-$DPI_MODES{400} = "nexthi";
-$DPI_MODES{600} = "QMSmoa";
-$DPI_MODES{100} = "nextscreen";
-
-$DPI_MODES{100} = "videodisplayi";
-$DPI_MODES{110} = "videodisplayii";
-$DPI_MODES{118} = "videodisplayiii";
-$DPI_MODES{120} = "videodisplayiv";
-$DPI_MODES{124} = "videodisplayv";
-$DPI_MODES{130} = "videodisplayvi";
-$DPI_MODES{140} = "videodisplayvii";
-$DPI_MODES{150} = "videodisplayviii";
-
-$DPI_MODES{72} = "MacTrueSize";
-$DPI_MODES{635} = "linolo";
-$DPI_MODES{1270} = "linohi";
-$DPI_MODES{2540} = "linosuper";
-
-# Where are the DC fonts stored and what base names can be used?
-$DCR_DIR = '/usr/local/lib/fonts/free/dc/src';
-@DCR_GEN = ('dcb','dcbom','dcbx','dcbxsl','dcbxti','dccsc','dcdunh','dcff',
- 'dcfi','dcfib','dcitt','dcr','dcsl','dcsltt','dcss','dcssbx',
- 'dcssi','dctcsc','dcti','dctt','dcu','dcvtt' );
-
-# Where are the Sauter fonts stored and what base names can be used?
-$SAUTER_DIR = '/usr/local/lib/fonts/free/sauter/src';
-@SAUTER_GEN = ('cmb','cmbizx','cmbozx','cmbsy','cmbszx','cmbx','cmbxsl',
- 'cmbxti', 'cmbz', 'cmbzx', 'cmcsc', 'cmdszc', 'cmdunh',
- 'cmex', 'cmff', 'cmfi', 'cmfib', 'cminch', 'cmitt', 'cmmi',
- 'cmmib', 'cmr', 'cmrcz', 'cmrisz', 'cmritz', 'cmriz',
- 'cmrotz', 'cmroz', 'cmrsz', 'cmrtz', 'cmruz', 'cmrz',
- 'cmsl', 'cmsltt', 'cmss', 'cmssbx', 'cmssdc', 'cmssi',
- 'cmssq', 'cmssqi', 'cmsy', 'cmtcsc', 'cmtex', 'cmti',
- 'cmtt', 'cmu', 'cmvtt', 'czinch', 'czssq', 'czssqi',
- 'lasy', 'lasyb');
-
-$SAUTER_ROUNDING{11} = '10.954451';
-$SAUTER_ROUNDING{14} = '14.4';
-$SAUTER_ROUNDING{17} = '17.28';
-$SAUTER_ROUNDING{20} = '20.736';
-$SAUTER_ROUNDING{25} = '24.8832';
-$SAUTER_ROUNDING{30} = '29.8685984';
-
-# Get the command line arguments...
-($NAME, $DPI, $BDPI, $MAG, $MODE, $FORCEDEST, $EXTRA) = @ARGV;
-
-open (TTY, ">/dev/tty"); # Open the TTY (so we can print messages
-select (TTY); $| = 1; select(STDOUT); # even if STDERR and STDOUT are both
- # redirected)
-
-if ($VERBOSE) {
- print TTY "$0: font name: $NAME\n";
- print TTY "$0: dpi: $DPI\n";
- print TTY "$0: base dpi: $BDPI\n";
- print TTY "$0: magnification: $MAG\n" if $MAG;
- print TTY "$0: mode: $MODE\n" if $MODE;
- print TTY "$0: force destination directory: $FORCEDEST\n" if $FORCEDEST;
- print TTY "$0: extra: $EXTRA\n" if $EXTRA;
-}
-
-# Make sure we got enough arguments, but not too many...
-die "$0: Invalid arguments.\n" if ($BDPI eq "" || $EXTRA ne "");
-
-# Calculate the magnification from the requested resolutions if no
-# magnification string was provided.
-if (!$MAG) {
- $MAG = "$DPI/$BDPI";
- print TTY "$0: magnification: $MAG\n" if $VERBOSE;
-}
-
-# Calculate the mode if the mode was not given. Die if we don't know
-# what mode to use for the requested base resolution.
-if ($MODE eq "") {
- $MODE = $DPI_MODES{$BDPI};
- die "$0: No mode for ${BDPI}dpi base resolution.\n" if $MODE eq "";
- print TTY "$0: mode: $MODE\n" if $VERBOSE;
-}
-
-########################################################################
-
-# Really start the work...
-print TTY "Attempting to build PK file for: $NAME at ${DPI}dpi.\n";
-
-$mfFile = $NAME;
-$mfFile =~ /^(.*[^0-9])(\d+)$/;
-$mfBase = $1;
-$mfSize = $2;
-
-# Presumably, we got here because the PK file doesn't exist. Let's look
-# for the MF file or the PFA or PFB file...
-
-# ... it's more complicated than that...
-
-# If the font is from a PFA/B file, it may have the name "rxxx" or
-# "xxx0" because virtual fonts extract glyphs from the "raw" font.
-# We need to find the PFA/B file and install the font with the right name.
-# I'm not sure what the best solution would really be, but this will work.
-# Luckily, it gets installed with the right name 'cause we already
-# figured that out...
-#
-# A better solution on Unix machines might be to make "xxx0.pfa" or
-# "rxxx.pfa" a symbolic link to "xxx.pfa". But that won't work for other
-# architectures...
-
-$t1source = "";
-$t1source = $1 if $mfFile =~ /^r(.*)$/;
-$t1source = $1 if $mfFile =~ /^(.*)0$/ && ($t1source eq "");
-
-if ($t1source) {
- $fontSource = &find_fonts($TEXFONTS,
- ("$mfFile.mf", "$mfFile.pfa", "$mfFile.pfb",
- "$t1source.pfa", "$t1source.pfb"));
-} else {
- $fontSource = &find_fonts($TEXFONTS,
- ("$mfFile.mf", "$mfFile.pfa", "$mfFile.pfb"));
-}
-
-if ($fontSource) {
- if ($fontSource =~ /\.pfa$/ || $fontSource =~ /\.pfb$/) {
- print TTY "Building PK file from PostScript source.\n";
- &make_and_cd_tempdir();
- &make_from_ps($fontSource);
- } elsif ($fontSource =~ /\.mf$/) {
- local($fpath, $fname);
- print TTY "Building PK file from MF source.\n";
- &make_and_cd_tempdir();
-
- if ($fontSource =~ /^(.*)\/([^\/]*)$/) {
- $fpath = $1;
- $fname = $2;
-
- $fpath = $CWD if $fpath eq ".";
- $fpath = "$CWD/.." if $fpath eq "..";
- } else {
- $fpath = "";
- $fname = $fontSource;
- }
-
- &make_from_mf($fpath, $fname);
- } else {
- print TTY "$0: Cannot build PK font for $NAME.\n";
- print TTY " " x length($0), " Unprepared for $fontSource.\n";
- die "\n";
- }
-} else {
- if (grep(/^$mfBase$/, @DCR_GEN)) {
-
- print TTY "Building PK file from DC source.\n";
-
- &make_and_cd_tempdir();
-
- $MFBASE = "&dxbase";
- open (MFFILE, ">$mfFile.mf");
- print MFFILE "gensize:=$mfSize; generate $mfBase;\n";
- close (MFFILE);
-
- &make_from_mf("$DCR_DIR","$mfFile.mf");
-
- } elsif (grep(/^$mfBase$/, @SAUTER_GEN)) {
-
- print TTY "Building PK file from Sauter source.\n";
-
- &make_and_cd_tempdir();
-
- if (defined($SAUTER_ROUNDING{$mfSize})) {
- $designSize = $SAUTER_ROUNDING{$mfSize};
- } else {
- $designSize = $mfSize;
- }
-
- open (MFFILE, ">$mfFile.mf");
- print MFFILE "design_size := $designSize;\n";
- print MFFILE "input b-$mfBase;\n";
- close (MFFILE);
-
- &make_from_mf("$SAUTER_DIR","$mfFile.mf");
-
- } else {
- print TTY "$0: Cannot build PK file. Can't find source.\n";
- die "\n";
- }
-}
-
-&cleanup();
-
-exit 0;
-
-########################################################################
-
-sub run {
- local(@cmd) = @_;
- local($rc);
-
- open (SAVEOUT, ">&STDOUT");
- open (SAVEERR, ">&STDERR");
- close (STDOUT);
- open (STDOUT, ">&TTY");
- close (STDERR);
- open (STDERR, ">&TTY");
-
- # Chdir seems to return a funny exit code. So do it internally...
- # (this is a hack)
- if (@cmd[0] eq "chdir") {
- $rc = chdir(@cmd[1]);
- $rc = !$rc;
- } else {
- $rc = system(@cmd);
- }
-
- close (STDOUT);
- open (STDOUT, ">&SAVEOUT");
- close (SAVEOUT);
-
- close (STDERR);
- open (STDERR, ">&SAVEERR");
- close (SAVEERR);
-
- if ($rc) {
- printf TTY "%s\n", "*" x 72;
- print TTY "$0 error : system return code: $rc\n";
- print TTY "$0 failed: @cmd\n";
- printf TTY "%s\n", "*" x 72;
- }
-
- $rc;
-}
-
-sub make_and_cd_tempdir {
- &run ("mkdir", "$TEMPDIR");
- &run ("chdir", "$TEMPDIR");
-}
-
-sub cleanup {
- &run ("chdir", "$CWD");
- &run ("rm", "-rf", "$TEMPDIR");
-}
-
-sub install_font {
- local($source_path, $font, $subdir, $mode) = @_;
- local($pkdirs, @paths, $ptarget);
- local($target) = "";
-
- if ($VERBOSE) {
- print "Install: source_path: $source_path\n";
- print "Install: font : $font\n";
- print "Install: subdir : $subdir\n";
- print "Install: mode : $mode\n";
- }
-
- $pkdirs = $ENV{"TEXPKS"} || $ENV{"PKFONTS"} || "";
- @paths = split(/:|;/,$pkdirs);
-
- # Need to find an installable target for the PK files. Try
- # ../glyphs/$subdir and ../$subdir then give up and use the best $pkdirs
- # path...
-
- if (!$target) {
- ($ptarget = $source_path) =~ s#/[^/]*$##;
- $target = "$ptarget/glyphs/$subdir"
- if -d "$ptarget/glyphs/$subdir"
- || (-d "$ptarget/glyphs"
- && -w "$ptarget/glyphs"
- && ! -f "$ptarget/glyphs/$subdir");
- }
-
- if (!$target) {
- ($ptarget = $source_path) =~ s#/[^/]*$##;
- $target = "$ptarget/$subdir"
- if -d "$ptarget/$subdir"
- || (-d $ptarget && -w $ptarget && ! -f "$ptarget/$subdir");
-
- # what a minute, suppose we just made a font in the current
- # directory...let's put the PK file there too...
- if (! -d "$target" && ($source_path eq $CWD)) {
- $target = $source_path;
- $USE_MODE_IN_DEST = 0;
- }
- }
-
- while (!$target && ($ptarget = shift @paths)) {
- $target = $ptarget if ($ptarget ne "." && $ptarget ne ".."
- && -d $ptarget && -w $ptarget);
- }
-
- if ($target) {
- if (! -d $target) {
- &run ("mkdir", "$target");
- &run ("chmod", "777", "$target");
- }
-
- if ($USE_MODE_IN_DEST) {
- $target .= "/$mode";
- if (! -d $target) {
- &run ("mkdir", "$target");
- &run ("chmod", "777", "$target");
- }
- }
-
- print TTY "Installing $font in $target.\n";
- &run ("cp", "$font", "$target/fonttmp.$$");
- &run ("chdir", "$target");
- &run ("mv", "fonttmp.$$", "$font");
- &run ("chmod", "a+r", "$font");
- &run ("chdir", "$TEMPDIR");
- print STDOUT "$target/$font\n";
- } else {
- print TTY "$0: Install failed: no where to put $font.\n";
- }
-}
-
-sub make_from_mf {
- local ($source_path, $source_file) = @_;
- local ($mfsource, $mfinputs, $cmd);
- local ($gfname, $pkname, $realdpi, $testdpi);
- local ($cmpath);
-
- print "source_path: $source_path\n" if $VERBOSE;
- print "source_file: $source_file\n" if $VERBOSE;
-
- &run ("chdir", "$TEMPDIR");
-
- if (!$source_file) {
- $mfsource = $source_path;
- ($source_path = $mfsource) =~ s#/[^/]*$##;
- ($source_file = $mfsource) =~ s#^.*/([^/]*)$#$1#;
- }
-
- $mfinputs = $ENV{"MFINPUTS"};
- $mfinputs =~ s/^:*(.*):*$/$1/ if $mfinputs;
- $ENV{"MFINPUTS"} = ".:$source_path";
- $ENV{"MFINPUTS"} .= ":$mfinputs" if $mfinputs;
-
- print "MFINPUTS: $ENV{MFINPUTS}\n" if $VERBOSE;
-
- $cmpath = "/usr/local/lib/fonts/free/cm/src";
- if (-d $cmpath && $ENV{"MFINPUTS"} !~ /$cmpath/) {
- $ENV{"MFINPUTS"} .= ":$cmpath";
- }
-
- $cmd = "$MFBASE \\mode:=$MODE; mag:=$MAG; scrollmode; " .
- "\\input $source_file";
- print TTY "virmf $cmd\n";
-
- $saveTERM = $ENV{"TERM"};
- $saveDISPLAY = $ENV{"DISPLAY"};
- delete $ENV{"DISPLAY"};
- $ENV{"TERM"} = "vt100";
-
- $rc = &run ("virmf", "$cmd");
-
- $ENV{"DISPLAY"} = $saveDISPLAY;
- $ENV{"TERM"} = $saveTERM;
-
- $realdpi = $DPI;
- $gfname = "./$mfFile.${realdpi}gf";
-
- for ($testdpi = $realdpi-2; $testdpi < $realdpi+3; $testdpi++) {
- $gfname = "./$mfFile.${testdpi}gf", $realdpi = $testdpi
- if ! -f $gfname && -f "./$mfFile.${testdpi}gf";
- }
-
- $gfname = "./$mfFile.${realdpi}gf";
- $pkname = "./$mfFile.${realdpi}pk";
-
- $rc = &run ("gftopk", "$gfname", "$pkname");
-
- &install_font($source_path, "$mfFile.${realdpi}pk", 'pk', "$MODE");
-}
-
-sub make_from_ps {
- local ($source_path, $source_file) = @_;
- local ($pssource, @cmd);
- local ($basename, $afmFile, $afmtest, $part);
-
- &run ("chdir", "$TEMPDIR");
-
- if (!$source_file) {
- $pssource = $source_path;
- ($source_path = $pssource) =~ s#/[^/]*$##;
- ($source_file = $pssource) =~ s#^.*/([^/]*)$#$1#;
- }
-
- # Need to find the AFM file...
- $afmFile = "";
- ($basename = $source_file) =~ s/\.pf[ab]$//;
- # First, look in ../afm:
- ($afmtest = $source_path) =~ s#/[^/]*$##;
- $afmtest .= "/afm/$basename.afm";
- $afmFile = $afmtest if -r $afmtest;
-
- # Then, look in ../../afm:
- ($afmtest = $source_path) =~ s#/[^/]*$##;
- $afmtest =~ s#/[^/]*$##;
- $afmtest .= "/afm/$basename.afm";
- $afmFile = $afmtest if !$afmFile && -r $afmtest;
-
- die "$0: Cannot find AFM file for $source_file.\n" if !$afmFile;
-
- @cmd = ('ps2pk', "-a$afmFile", "-X$DPI",
- "$source_path/$source_file", "./$mfFile.${DPI}pk");
-
- foreach $part (@cmd) {
- print TTY "$part ";
- }
- print TTY "\n";
-
- $rc = &run (@cmd);
-
- &install_font($source_path, "$mfFile.${DPI}pk", 'pk', "${DPI}dpi");
-}
-
-sub find_fonts {
-# This subroutine searches for font sources. It looks in all the directories
-# in the path specified. Recursive searches are preformed on directories
-# that end in //, !, or !!. The emTeX directive "!", which should search
-# only one level deep, is treated exactly like "!!".
-#
- local($path, @fonts) = @_;
- local(@dirs, $dir, $font);
- local(@matches) = ();
- local(@recursive_matches);
-
- $path =~ s/!!/\/\//g;
- $path =~ s/!/\/\//g;
- $path =~ s/\\/\//g;
-
- print TTY "CWD: ", `pwd` if $VERBOSE;
- print TTY "Find: @fonts\n" if $VERBOSE;
- print TTY "Path: $path\n" if $VERBOSE;
-
- @dirs = split(/:|;/, $path);
- while (@dirs) {
- $dir = shift @dirs;
- next if !$dir;
-
- if ($dir =~ /\/\//) {
- @recursive_matches = &recursive_search($dir, @fonts);
- push (@matches, @recursive_matches)
- if @recursive_matches;
- } else {
- $dir =~ s/\/*$//; # remove trailing /, if present
- foreach $font (@fonts) {
- push (@matches, "$dir/$font")
- if -f "$dir/$font";
- }
- }
- }
-
- $font = shift @matches;
-
- if (@matches) {
- print TTY "$0: Found more than one match.\n";
- print TTY " " x length($0), " Using: $font\n";
- }
-
- $font;
-}
-
-sub recursive_search {
- local($dir, @fonts) = @_;
- local(@matches) = ();
- local(@dirstack, $rootdir, $font, $fontmask);
-
- $dir =~ /^(.*)\/\/(.*)$/;
- $rootdir = $1;
- $fontmask = $2;
-
- $rootdir =~ s/\/*$//; # remove trailing /'s
-
- # Note: this perl script has to scan them all, the mask is meaningless.
- # Especially since I'm looking for the font *source* not the TFM or
- # PK file...
-
- $fontmask =~ s/\$MAKETEX_BASE_DPI/$BDPI/g;
- $fontmask =~ s/\$MAKETEX_MAG/$MAG/g;
- $fontmask =~ s/\$MAKETEX_MODE/$MODE/g;
-
- print TTY "Search root=$rootdir\n" if $VERBOSE;
- print TTY "Search mask=$fontmask (ignored by $0)\n" if $VERBOSE;
-
- @dirstack = ($rootdir);
-
- while ($rootdir = shift @dirstack) {
- opendir (SEARCHDIR, "$rootdir");
- while ($dir = scalar(readdir(SEARCHDIR))) {
- if ($dir ne "." && $dir ne ".." && -d "$rootdir/$dir") {
- push(@dirstack, "$rootdir/$dir");
- foreach $font (@fonts) {
- if (-f "$rootdir/$dir/$font") {
- print TTY "Matched: $rootdir/$dir/$font\n" if $VERBOSE;
- push(@matches, "$rootdir/$dir/$font");
- }
- }
- }
- }
- closedir (SEARCHDIR);
- }
-
- @matches;
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-02 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-02
deleted file mode 100644
index 7283ee9459e..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-02
+++ /dev/null
@@ -1,427 +0,0 @@
-#!/usr/local/bin/perl
-#
-# MakeTeXTFM.pl version 1.0, Copyright (C) 1993,94 by Norman Walsh.
-# NO WARRANTY. Distribute freely under the GNU GPL.
-#
-# This script attempts to make a new TeX TFM file, because one wasn't
-# found. The only argument is the name of the TFM file, such as
-# `cmr10.tfm' (*NOT* just `cmr10').
-#
-# This script was designed with two goals in mind: to support recursive
-# subdirectory searching for fonts and to provide support for PK files
-# built from both MF fonts and PS fonts. It also supports the Sauter
-# and DC fonts which can be built at any design size.
-#
-# This script was designed and tested with the following directory structure
-# in mind: each typeface is stored in its own directory with appropriate
-# subdirectories for font sources, metrics, and glyphs. The script may not
-# work exactly right if you use a different directory structure (the font
-# installation, in particular, will probably be incorrect). However,
-# several other versions of MakeTeXPK exist which will handle simpler
-# directory structures, so you need not feel compelled to use the one
-# described here.
-#
-# For MF fonts: (... is usually something like /usr/local/lib/tex/fonts)
-#
-# .../typeface/src holds the sources
-# /tfm holds the TFM files
-# /glyphs root for glyphs
-# /glyphs/mode holds the PK files for "mode".
-#
-# For PS fonts: (... is usually something like /usr/local/lib/tex/fonts)
-#
-# .../typeface/afm holds the AFM files
-# /tfm holds the TFM files
-# /vf holds the VF files
-# /vpl holds the VPL files
-# /glyphs root for glyphs
-# /glyphs/pk/999dpi holds the PK files at 999 dpi created by ps2pk
-# /glpyhs/type1 holds the type1 PFA/PFB sources for the fonts
-#
-# The TFM files constructed for PostScript fonts are mapped to the Old TeX
-# encoding.
-#
-
-require "getopts.pl";
-$rc = &Getopts ('v'); # Get options from the user...
-
-$VERBOSE = $opt_v || $ENV{"DEBUG_MAKETEXPK"}; # Verbose?
-
-chop($CWD = `pwd`); # Where are we?
-$TEMPDIR = "/tmp/mkPK.$$"; # Where do temp files go?
-$MFBASE = "&plain"; # What MF base do we use by default?
-
-# Where are fonts stored?
-$TEXFONTS = $ENV{"TEXFONTS"} || ".:/usr/local/lib/fonts//";
-
-# Define modes that should be used for base resolutions...
-$DPI_MODES{300} = "laserwriter";
-$DPI_MODES{200} = "FAX";
-$DPI_MODES{360} = "lqhires";
-$DPI_MODES{400} = "nexthi";
-$DPI_MODES{600} = "QMSmoa";
-$DPI_MODES{100} = "nextscreen";
-
-$DPI_MODES{100} = "videodisplayi";
-$DPI_MODES{110} = "videodisplayii";
-$DPI_MODES{118} = "videodisplayiii";
-$DPI_MODES{120} = "videodisplayiv";
-$DPI_MODES{124} = "videodisplayv";
-$DPI_MODES{130} = "videodisplayvi";
-$DPI_MODES{140} = "videodisplayvii";
-$DPI_MODES{150} = "videodisplayviii";
-
-$DPI_MODES{72} = "MacTrueSize";
-$DPI_MODES{635} = "linolo";
-$DPI_MODES{1270} = "linohi";
-$DPI_MODES{2540} = "linosuper";
-
-# Where are the DC fonts stored and what base names can be used?
-$DCR_DIR = '/usr/local/lib/fonts/free/dc/src';
-@DCR_GEN = ('dcb','dcbom','dcbx','dcbxsl','dcbxti','dccsc','dcdunh','dcff',
- 'dcfi','dcfib','dcitt','dcr','dcsl','dcsltt','dcss','dcssbx',
- 'dcssi','dctcsc','dcti','dctt','dcu','dcvtt' );
-
-# Where are the Sauter fonts stored and what base names can be used?
-$SAUTER_DIR = '/usr/local/lib/fonts/free/sauter/src';
-@SAUTER_GEN = ('cmb','cmbizx','cmbozx','cmbsy','cmbszx','cmbx','cmbxsl',
- 'cmbxti', 'cmbz', 'cmbzx', 'cmcsc', 'cmdszc', 'cmdunh',
- 'cmex', 'cmff', 'cmfi', 'cmfib', 'cminch', 'cmitt', 'cmmi',
- 'cmmib', 'cmr', 'cmrcz', 'cmrisz', 'cmritz', 'cmriz',
- 'cmrotz', 'cmroz', 'cmrsz', 'cmrtz', 'cmruz', 'cmrz',
- 'cmsl', 'cmsltt', 'cmss', 'cmssbx', 'cmssdc', 'cmssi',
- 'cmssq', 'cmssqi', 'cmsy', 'cmtcsc', 'cmtex', 'cmti',
- 'cmtt', 'cmu', 'cmvtt', 'czinch', 'czssq', 'czssqi',
- 'lasy', 'lasyb');
-
-$SAUTER_ROUNDING{11} = '10.954451';
-$SAUTER_ROUNDING{14} = '14.4';
-$SAUTER_ROUNDING{17} = '17.28';
-$SAUTER_ROUNDING{20} = '20.736';
-$SAUTER_ROUNDING{25} = '24.8832';
-$SAUTER_ROUNDING{30} = '29.8685984';
-
-open (TTY, ">/dev/tty");
-select (TTY); $| = 1; select(STDOUT);
-
-$tfmFile = @ARGV[0];
-if (!$tfmFile) {
- print TTY "$0 error: No TFM file specified.\n";
- die "\n";
-}
-
-print TTY "\nAttempting to build TFM file: $tfmFile.\n";
-
-# This is the *wierdest* bug I've ever seen. When this script is called
-# by virtex to build a TFM file, the argument (as interpreted by Perl)
-# has (at least one) ASCII 16 attached to the end of the argument. This
-# loop removes all control characters from the $tfmFile name string...
-$tfmFile =~ /(.)$/;
-$char = ord ($1);
-while ($char <= 32) {
- $tfmFile = $`;
- $tfmFile =~ /(.)$/;
- $char = ord ($1);
-}
-
-# Now we know the name of the TFM file. Next, get the name of the MF file
-# and the base name and size of the MF file.
-
-($mfFile = $tfmFile) =~ s/\.tfm$//;
-$mfFile =~ /^(.*[^0-9])(\d+)$/;
-$mfBase = $1;
-$mfSize = $2;
-
-# Presumably, we got here because the TFM file doesn't exist. Let's look
-# for the MF file or the AFM file...
-
-$tfmSource = &find_fonts($TEXFONTS, ("$mfFile.mf", "$mfFile.afm"));
-
-if ($tfmSource) {
- if ($tfmSource =~ /\.afm$/) {
- print TTY "Building $tfmFile from AFM source.\n";
- &make_and_cd_tempdir();
- &make_from_afm($tfmSource);
- } elsif ($tfmSource =~ /\.mf$/) {
- local($fpath, $fname);
- print TTY "Building $tfmFile from MF source.\n";
- &make_and_cd_tempdir();
-
- if ($tfmSource =~ /^(.*)\/([^\/]*)$/) {
- $fpath = $1;
- $fname = $2;
-
- $fpath = $CWD if $fpath eq ".";
- $fpath = "$CWD/.." if $fpath eq "..";
- } else {
- $fpath = "";
- $fname = $tfmSource;
- }
-
- &make_from_mf($fpath, $fname);
- } else {
- print TTY "$0: Cannot build $tfmFile.\n";
- print TTY " " x length($0), " Unprepared for $tfmSource.\n";
- die "\n";
- }
-} else {
- if (grep(/^$mfBase$/, @DCR_GEN)) {
-
- print TTY "Building $tfmFile from DC source.\n";
-
- &make_and_cd_tempdir();
-
- $MFBASE = "&dxbase";
- open (MFFILE, ">$mfFile.mf");
- print MFFILE "gensize:=$mfSize; generate $mfBase;\n";
- close (MFFILE);
-
- &make_from_mf("$DCR_DIR","$mfFile.mf");
-
- } elsif (grep(/^$mfBase$/, @SAUTER_GEN)) {
-
- print TTY "Building $tfmFile from Sauter source.\n";
-
- &make_and_cd_tempdir();
-
- if (defined($SAUTER_ROUNDING{$mfSize})) {
- $designSize = $SAUTER_ROUNDING{$mfSize};
- } else {
- $designSize = $mfSize;
- }
-
- open (MFFILE, ">$mfFile.mf");
- print MFFILE "design_size := $designSize;\n";
- print MFFILE "input b-$mfBase;\n";
- close (MFFILE);
-
- &make_from_mf("$SAUTER_DIR","$mfFile.mf");
-
- } else {
- print TTY "$0: Cannot build $tfmFile. Can't find source.\n";
- die "\n";
- }
-}
-
-&cleanup();
-
-exit 0;
-
-sub run {
- local(@cmd) = @_;
- local($rc);
-
- open (SAVEOUT, ">&STDOUT");
- open (SAVEERR, ">&STDERR");
- close (STDOUT);
- open (STDOUT, ">&TTY");
- close (STDERR);
- open (STDERR, ">&TTY");
-
- # Chdir seems to return a funny exit code. So do it internally...
- # (this is a hack)
- if (@cmd[0] eq "chdir") {
- $rc = chdir(@cmd[1]);
- $rc = !$rc;
- } else {
- $rc = system(@cmd);
- }
-
- close (STDOUT);
- open (STDOUT, ">&SAVEOUT");
- close (SAVEOUT);
-
- close (STDERR);
- open (STDERR, ">&SAVEERR");
- close (SAVEERR);
-
- if ($rc) {
- printf TTY "%s\n", "*" x 72;
- print TTY "MakeTeXTFM error : system return code: $rc\n";
- print TTY "MakeTeXTFM failed: @cmd\n";
- printf TTY "%s\n", "*" x 72;
- }
-
- $rc;
-}
-
-sub make_and_cd_tempdir {
- &run ("mkdir", "$TEMPDIR");
- &run ("chdir", "$TEMPDIR");
-}
-
-sub cleanup {
- &run ("chdir", "$CWD");
- &run ("rm", "-rf", "$TEMPDIR");
-}
-
-sub install_font {
- local($source_path, $font, $subdir) = @_;
- local(@paths) = split(/:|;/,$ENV{"TEXFONTS"});
- local($target) = "";
- local($ptarget);
-
- if (!$target && $source_path =~ /\/src$/) {
- $ptarget = $source_path;
- $ptarget =~ s/(.*)\/src$/$1/;
- $ptarget .= "/$subdir";
- $target = $ptarget if (-d $ptarget && -w $ptarget);
- }
-
- if (!$target && $source_path =~ /\/afm$/) {
- $ptarget = $source_path;
- $ptarget =~ s/(.*)\/afm$/$1/;
- $ptarget .= "/$subdir";
- $target = $ptarget if (-d $ptarget && -w $ptarget);
- }
-
- if (!$target && ($source_path eq $CWD)) {
- $target = $source_path;
- }
-
- while (!$target && ($ptarget = shift @paths)) {
- $target = $ptarget if ($ptarget ne "." && $ptarget ne ".."
- && -d $ptarget && -w $ptarget);
- }
-
- if ($target) {
- print TTY "Installing $font in $target.\n";
- &run ("cp", "$font", "$target/fonttmp.$$");
- &run ("chdir", "$target");
- &run ("mv", "fonttmp.$$", "$font");
- &run ("chmod", "a+r", "$font");
- &run ("chdir", "$TEMPDIR");
- print STDOUT "$target/$font\n";
- } else {
- print TTY "$0: Install failed: no where to put $font.\n";
- }
-}
-
-sub make_from_mf {
- local ($source_path, $source_file) = @_;
- local ($mfsource, $mfinputs, $cmd);
-
- &run ("chdir", "$TEMPDIR");
-
- if (!$source_file) {
- $mfsource = $source_path;
- ($source_path = $mfsource) =~ s#/[^/]*$##;
- ($source_file = $mfsource) =~ s#^.*/([^/]*)$#$1#;
- }
-
- $mfinputs = $ENV{"MFINPUTS"};
- $mfinputs =~ s/^:*(.*):*$/$1/ if $mfinputs;
- $ENV{"MFINPUTS"} = ".:$source_path";
- $ENV{"MFINPUTS"} .= ":$mfinputs" if $mfinputs;
-
- print "MFINPUTS: $ENV{MFINPUTS}\n" if $VERBOSE;
-
- $cmd = "$MFBASE \\mode:=laserwriter; scrollmode; \\input $source_file";
- print TTY "virmf $cmd\n";
-
- $saveTERM = $ENV{"TERM"};
- $saveDISPLAY = $ENV{"DISPLAY"};
- delete $ENV{"DISPLAY"};
- $ENV{"TERM"} = "vt100";
-
- $rc = &run ("virmf", "$cmd");
-
- $ENV{"DISPLAY"} = $saveDISPLAY;
- $ENV{"TERM"} = $saveTERM;
-
- &install_font($source_path, $tfmFile, 'tfm');
-}
-
-sub make_from_afm {
- local ($afmFile) = @_;
- local ($source_path);
-
- print TTY "afm2tfm $afmFile -v $mfFile ${mfFile}0\n";
- $rc = &run ("afm2tfm", "$afmFile", "-v", "$mfFile", "${mfFile}0");
-
- print TTY "vptovf $mfFile.vpl $mfFile.vf $mfFile.tfm\n";
- $rc = &run ("vptovf", "$mfFile.vpl", "$mfFile.vf", "$mfFile.tfm");
-
- ($source_path = $afmFile) =~ s#/[^/]*$##;
- &install_font($source_path, "$mfFile.tfm", 'tfm');
- &install_font($source_path, "${mfFile}0.tfm", 'tfm');
- &install_font($source_path, "$mfFile.vpl", 'vpl');
- &install_font($source_path, "$mfFile.vf", 'vf');
-}
-
-sub find_fonts {
- local($path, @fonts) = @_;
- local(@dirs, $dir, $font);
- local(@matches) = ();
- local(@recursive_matches);
-
- print "Find fonts on path: $path\n" if $VERBOSE;
-
- @dirs = split(/:|;/, $path);
- while ($dir = shift @dirs) {
- print "Search: $dir\n" if $VERBOSE;
- if ($dir =~ /\/\//) {
- @recursive_matches = &recursive_search($dir, @fonts);
- push (@matches, @recursive_matches)
- if @recursive_matches;
- } else {
- $dir =~ s/\/*$//; # remove trailing /, if present
- foreach $font (@fonts) {
- push (@matches, "$dir/$font")
- if -f "$dir/$font";
- }
- }
- }
-
- $font = shift @matches;
-
- if (@matches) {
- print TTY "$0: Found more than one match.\n";
- print TTY " " x length($0), " Using: $font\n";
- }
-
- $font;
-}
-
-sub recursive_search {
- local($dir, @fonts) = @_;
- local(@matches) = ();
- local(@dirstack, $rootdir, $font, $fontmask);
-
- $dir =~ /^(.*)\/\/(.*)$/;
- $rootdir = $1;
- $fontmask = $2;
-
- $rootdir =~ s/\/*$//; # remove trailing /'s
-
- # Note: this perl script has to scan them all, the mask is meaningless.
- # Especially since I'm looking for the font *source* not the TFM or
- # PK file...
-
- $fontmask =~ s/\$MAKETEX_BASE_DPI/$BDPI/g;
- $fontmask =~ s/\$MAKETEX_MAG/$MAG/g;
- $fontmask =~ s/\$MAKETEX_MODE/$MODE/g;
-
- print "Search root=$rootdir\n" if $VERBOSE;
- print "Search mask=$fontmask (ignored by $0)\n" if $VERBOSE;
-
- @dirstack = ($rootdir);
-
- while ($rootdir = shift @dirstack) {
- opendir (SEARCHDIR, "$rootdir");
- while ($dir = scalar(readdir(SEARCHDIR))) {
- if ($dir ne "." && $dir ne ".." && -d "$rootdir/$dir") {
- push(@dirstack, "$rootdir/$dir");
- foreach $font (@fonts) {
- if (-f "$rootdir/$dir/$font") {
- print "Matched: $rootdir/$dir/$font\n" if $VERBOSE;
- push(@matches, "$rootdir/$dir/$font");
- }
- }
- }
- }
- closedir (SEARCHDIR);
- }
-
- @matches;
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-03 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-03
deleted file mode 100644
index 7a1158292a7..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-03
+++ /dev/null
@@ -1,215 +0,0 @@
-@echo off
-: -----------------------------------------------------------------------
-: DVIDXX Copyright (C) 1992,94 by Norman Walsh
-:
-: This file is free. You can do anything you like with it with one
-: exception: if you change this file, you MUST rename it!
-:
-: Requirements: 4DOS, emTeX drivers 1.4s or higher, MAKEPK.BTM
-:
-: Usage: DVIDXX emtexDriver driverOptions
-:
-: Note: DVIDXX requires a fair amount of free environment space in order
-: to function properly.
-:
-: Norman Walsh
-: <norm@ora.com>
-:
-: 12/09/1992: - Vers 0.5
-: - This is a first attempt. It works, but it doesn't have
-: any bells and whistles. It would be nice, for example,
-: if it noticed that PS2PK failed for a particular font...
-: -----------------------------------------------------------------------
-:
-: This batch file is a replacement for emTeX's dvidrv program. It offers
-: one additional feature. In addition to using MFjob to build fonts that
-: don't exist, DVIDXX can use PS2PK to build PK files for PostScript fonts.
-: Note: You must have the AFM and PFA/B files for the PS fonts in question.
-:
-: Why did you write this as a 4DOS BTM file? For two reasons. First, I
-: wanted it to be interpreted rather than compiled so that it would be
-: easy to change, modify, and extend. Second, I did it in 4DOS BTM language
-: because DOS's batch language is too primitive. Yes, maybe I _could_ have
-: done it with a plain BAT file, but I had no desire to try.
-:
-: -----------------------------------------------------------------------
-:
-: This file relies on MAKEPK.BTM to actually build the fonts with PS2PK.
-:
-: Both MAKEPK and DVIDXX are somewhat dependant on the layout of your
-: hard disk. Well, on the layout of mine, actually ;-)
-:
-: Here's how my HD is organized:
-:
-: C:\PSFONTS\ Root of my PostScript fonts directory.
-: This is stored in the %[PSFONTS] env. variable
-: %[PSFONTS]\PFB Where .PFB files are kept
-: %[PSFONTS]\AFM Where .AFM files are kept
-: %[PSFONTS]\UTIL Where MAKEPK is kept
-:
-: -----------------------------------------------------------------------
-: Make sure this is 4DOS...
-if "%@eval[2+2]" == "4" goto start
-echo Sorry, this batch file can only be run with 4Dos.
-goto end
-: -----------------------------------------------------------------------
-: Call the driver (maybe we won't have to do anything else)
-: In a network environment, you may have to make the mfjob-file unique
-: for each user in some way...
-: -----------------------------------------------------------------------
-:start
-if not "%_dos" == "DOS" goto os2ok
-iff %_env lt 128 then
- echo Sorry, this batch file requires at least 128 bytes of free environment
- echo space. Consult your 4DOS manual for information about increasing it.
- goto end
-endiff
-:os2ok
-setlocal
-set MFJOBFN=dvidxx.mfj
-
-%1 %2$ +mfjob-file:%MFJOBFN +batch-mode
-iff not errorlevel == 8 then
- endlocal
- goto end
-endiff
-: -----------------------------------------------------------------------
-: Ok, we have to build some fonts...
-:
-: NEWJOB = name of the MFjob file that will actually be used
-: PSJOB = name of the batch file that will build fonts with PS2PK
-: PSCNT = number of PS fonts to build
-: MFCNT = number of MF fonts to build
-: MFJOBLEN = number of lines in the original MFjob file
-: LNUM = current line number (in original MFjob file)
-: LINE = text of the current line
-: FONT = name of font
-: SIZE = ptsize of current font (assumes designsize of 10pt)
-: PSFNT = 0/1 flag determines if the %FONT in question is PS or not
-: -----------------------------------------------------------------------
-echo Looking at MFJob file...
-set NEWJOB=%@unique[%@path[%MFJOBFN]]
-set PSJOB=%@unique[%@path[%MFJOBFN]]
-ren %NEWJOB %NEWJOB.mfj /q
-ren %PSJOB %PSJOB.btm /q
-set NEWJOB=%NEWJOB.mfj
-set PSJOB=%PSJOB.btm
-set PSCNT=0
-set MFCNT=0
-set MFJOBLEN=%@lines[%MFJOBFN]
-set LNUM=0
-
-: Create the batch file and the new MFjob file...
-echo %% > %NEWJOB
-echo pushd %PSFONTS > %PSJOB
-
-: -----------------------------------------------------------------------
-: Loop through the entire MFjob file. Lines that begin "{font=" are
-: analyzed further to determine what kind of font it is. All other lines
-: are simply copied to the new MFjob file.
-: -----------------------------------------------------------------------
-
-:looptop
-
-if %LNUM gt %MFJOBLEN goto loopover
-
-: Deleting this percent stuff will save a small amount of time, but
-: since reading from the MFjob file is pretty slow, I find it reassuring...
-set PERC=%@eval[%LNUM / %MFJOBLEN * 100]
-set p=%@index[%PERC,.]
-if %p gt 0 set PERC=%@substr[%PERC,0,%p]
-echos %@CHAR[13]Working:
-echos %[PERC]%%
-
-set LINE=%@line[%MFJOBFN,%LNUM]
-:
-: We employ a convoluted compound test because %@substr["%foo",1,5] fails
-: with a "no closing quote" error if the %@len["%foo"] < 5...
-:
-set FOUND=0
-iff %@len["%LINE"] gt 5 then
- if (%@substr["%LINE",1,5]) == ({font) set FOUND=1
-endiff
-
-: If we found a font, %FOUND will be 1
-iff %FOUND == 1 then
- Rem Extract the font name and the size
- set p=%@index["%LINE",;]
- set FONT=%@substr["%LINE",7,%@eval[%p - 7]]
- set p=%@index["%LINE",mag=]
- set q=%@index["%LINE",}]
- set SIZE=%@substr["%LINE",%@eval[%p+4],%@eval[%q-%p-5]]
- set SIZE=%@eval[%SIZE*10]
-
- Rem This is where we test to see if it is a PS font. I've got a really
- Rem simple test below. Basically, I keep all my PFB files for PS fonts
- Rem in a single directory. If the font in question isn't in that directory,
- Rem I assume it is an MF font.
- set PSFNT=0
- gosub ispsfont
- iff %PSFNT == 1 then
- Echo %FONT at %[SIZE]pt will be built by PS2PK
- Rem I keep MAKEPK in C:\PSFONTS\UTIL so that's what I write to the batch
- Rem file. If you keep it somewhere else, you'll have to change this.
- echo call %[psfonts]\util\makepk %FONT %SIZE >> %PSJOB
- set PSCNT=%@eval[%PSCNT + 1]
- else
- Echo %FONT at %[SIZE]pt will be built by MFjob
- echo %LINE >> %NEWJOB
- set MFCNT=%@eval[%MFCNT + 1]
- endiff
-else
- echo %LINE >> %NEWJOB
-endiff
-
-set LNUM=%@eval[%LNUM + 1]
-goto looptop
-:loopover
-
-: -----------------------------------------------------------------------
-
-: Finish up the PSJOB file and clean up the messages on the screen
-echo popd >> %PSJOB
-echos %@CHAR[13] %@CHAR[13]
-
-: -----------------------------------------------------------------------
-
-: Go for it!
-iff %MFCNT gt 0 then
- echo Attempting to build %MFCNT fonts with MFjob
- mfjob %NEWJOB
-endiff
-del %NEWJOB /q
-
-: Get back the environment space that we (may) need in MAKEPK...
-unset MFJOBLEN LNUM LINE FONT SIZE PSFNT MFCNT NEWJOB
-
-iff %PSCNT gt 0 then
- echo Attempting to build %PSCNT fonts with PS2PK
- call %PSJOB
-endiff
-del %PSJOB /q
-
-: -----------------------------------------------------------------------
-: Try to run the driver again...this time it should succeed!
-
-del %MFJOBFN /q
-%1 %2$ +mfjob-file:%MFJOBFN +batch-mode
-iff errorlevel == 8 then
- echo Font building must have failed for at least one font. Look in
- echo the %MFJOBFN file to see which font(s) failed.
-endiff
-
-endlocal
-goto end
-
-: -----------------------------------------------------------------------
-: This really simple subroutine is how I look for PS fonts. This routine
-: should set PSFNT=1 iff the %FONT variable names a PostScript font.
-:
-:ispsfont
-if exist %[psfonts]\pfb\%FONT.pfb set PSFNT=1
-return
-
-: -----------------------------------------------------------------------
-:end
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-04 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-04
deleted file mode 100644
index 7f096b4ca5d..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-04
+++ /dev/null
@@ -1,151 +0,0 @@
-@echo off
-: -----------------------------------------------------------------------
-: MAKEPK Copyright (C) 1992,94 by Norman Walsh
-:
-: This file is free. You can do anything you like with it with one
-: exception: if you change this file, you MUST rename it!
-:
-: Requirements: 4DOS, ps2pk, afm2tfm, pfm2afm, pkbbox
-:
-: Usage: MAKEPK fontfn ptsize [pkfn] [-opts]
-:
-: Norman Walsh
-: <norm@ora.com>
-:
-: 12/09/1992: - Vers 0.5
-:--------------------------------------------------------------------------
-: See usage info below
-:
-: This batch file relies on the following directory structure:
-:
-: C:\PSFONTS\ Root of the PostScript fonts directory.
-: This is stored in the %[PSFONTS] env. variable
-: %[PSFONTS]\PFB Where .PFB files are kept
-: %[PSFONTS]\AFM Where .AFM files are kept
-: %[PSFONTS]\PFM Where .PFM files are kept (only required if the
-: AFM file does not exist)
-: %[PSFONTS]\TFM Where _all_ TFM files are kept for PS fonts
-: C:\BIN\PS2PK Where all the PS2PK utils are kept
-:--------------------------------------------------------------------------
-: Make sure the parameters are ok...
-iff %# lt 1 then
- echo Usage: %0 fontfn ptsize [pkfn] [-opts]
- echo.
- echo MAKEPK rasterizes 'fontfn' at 'ptsize' and stores it in 'pkfn'. The
- echo default 'pkfn' is the name of the 'fontfn'. All fonts are stored in
- echo the %[psfonts]\@Rrdpi\ directory. If -opts are supplied, they are
- echo passed to PS2PK.
- quit 1
-endiff
-
-: Setup local environment
-setlocal
-pushd %[psfonts]
-
-: Parse the command line
-set pfbfn=%@name[%1]
-set ptsz=%2
-set pkfn=%@name[%3]
-shift 2
-:toshift
-iff ³%@substr[%1,0,1]³ == ³-³ then
- set pkopts=%pkopts %1
-else
- set pkfn=%@name[%1]
-endiff
-shift
-if %# gt 0 goto toshift
-: -----------------------------------------------------------------------
-: Figure out the name of the appropriate PK directory. Create it if it
-: doesn't exist. Abort if a filename exists with that name...
-:
-: TeX seems to underestimate the font size by a very small amount. We
-: compensate (in the calculation of the directory) by adding the small
-: amount 0.0005 to the point size before truncating to integer...
-:
-set pkres=%@int[%@eval[(%@eval[%ptsz+0.0005] * 300) / 10]]
-set pkdir=%[pkres]dpi
-if isdir %pkdir goto okdir
-iff not exist %pkdir then
- md %pkdir
- goto okdir
-endiff
-echo MakePK: Cannot create directory: %pkdir
-quit 1
-:okdir
-: -----------------------------------------------------------------------
-: Setup the %PKFN if it wasn't set by a parameter
-if "%pkfn" == "" set pkfn=%@name[%pfbfn]
-
-: If the font and TFM alread exist, don't bother making them
-iff exist %[pkdir]\%[pkfn].pk .and. .\tfm\%@filesize[%[pkfn].tfm] gt 0 then
- popd
- quit 0
-endiff
-
-: Check to see if an AFM file exists (and has a reasonable size)...
-iff %@filesize[.\afm\%[pfbfn].afm] gt 0 then
- set afmok=1
-else
- set afmok=0
-endiff
-: -----------------------------------------------------------------------
-: Make sure we have everything we need...a PFB and an AFM or PFM...
-set ok=1
-iff not exist .\pfb\%[pfbfn].pfb then
- echo Cannot find PFB file: .\pfb\%[pfbfn].pfb
- set ok=0
-endiff
-iff not exist .\pfm\%[pfbfn].pfm .and. %afmok == 0 then
- echo Cannot find PFM file (.\pfm\%[pfbfn].pfm) and
- echo cannot find AFM file (.\afm\%[pfbfn].afm)
- set ok=0
-endiff
-if "%ok" == "0" quit 1
-set ok=
-: -----------------------------------------------------------------------
-: If we didn't find an AFM file, make one...
-iff %afmok == 0 then
- echo PFMtoAFM...
- \bin\ps2pk\pfm2afm .\pfm\%[pfbfn].pfm .\afm\%[pfbfn].afm
-endiff
-
-: -----------------------------------------------------------------------
-: Build the font...
-echo Rasterizing...
-::: The lines marked *** MERGE *** should be joined onto the end of the
-::: preceding line. They were broken only to fit within the margins of
-::: this book.
-echo ps2pk -P10 -X%[pkres] -a.\afm\%[pfbfn].afm %pkopts
-*** MERGE *** .\pfb\%[pfbfn].pfb %[pkdir]\%[pkfn].pk
-ps2pk -V -P10 -X%[pkres] -a.\afm\%[pfbfn].afm %pkopts
-*** MERGE *** .\pfb\%[pfbfn].pfb %[pkdir]\%[pkfn].pk
-
-: If we didn't get a descent AFM then we built it with AFM2PFM.
-: Unfortunately, the bounding boxes are missing if we did that.
-: So add the bounding boxes with the UGLY HACKISH PKbbox program...
-iff %afmok == 0 then
- echo PKbbox to make bounding boxes...
- set tempafm=%@unique[.]
- c:\tex\util\pkbbox %pkdir\%pkfn.pk .\afm\%[pfbfn].afm > %tempafm
- move %tempafm .\afm\%[pfbfn].afm
-endiff
-
-: If there's no TFM, build it...
-iff not exist .\tfm\%[pkfn].tfm then
- echo AFMtoTFM...
- afm2tfm .\afm\%[pfbfn].afm .\tfm\%[pkfn].tfm
-endiff
-
-::: If we didn't build a 10pt font, scale it appropriately
-::iff not "%ptsz" == "10" then
-:: c:\tex\util\pkscale %[pkdir]\%[pkfn].pk .\tfm\%[pkfn].tfm /designsize:10
-:: del %[pkdir]\%[pkfn].bak /q
-::endiff
-
-:
-: -----------------------------------------------------------------------
-: We're all done...
-popd
-endlocal
-quit 0
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-05 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-05
deleted file mode 100644
index bb8e67689b3..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-05
+++ /dev/null
@@ -1,174 +0,0 @@
-#! /usr/local/bin/perl
-#
-# Usage: enc-afm afm-file enc-file > encoded-afm-file
-#
-# Where: afm-file is the original AFM file with an arbitrary
-# encoding enc-file is the encoding file (in PS
-# format, a la dvips .enc files) encoded-afm-file is
-# the new AFM file with 'enc-file' encoding.
-#
-
-# what about .notdef?
-
-$afmfile = @ARGV[0];
-$encfile = @ARGV[1];
-
-print STDERR "Reading encoding file: $encfile\n";
-&read_encfile($encfile);
-print STDERR "Reading AFM file: $afmfile\n";
-&read_afmfile($afmfile);
-
-# Assign the correct encoding position to each char
-$missing = 0;
-for ($count = 0; $count < $vectorlen; $count++) {
- $missing_glyphs{@encoding[$count]} = 1, $missing = 1
- if !defined($vectorplace{@encoding[$count]})
- && @encoding[$count] ne ".notdef";
- $vectorplace{@encoding[$count]} = $count;
-}
-
-&print_long_list("Note: the following glyphs are missing "
- . "from the AFM file: ",
- sort (keys %missing_glyphs))
- if $missing;
-
-# Construct the CharMetrics lines
-@output_encoding = ();
-foreach $name (keys %metrics) {
- push (@output_encoding,
- sprintf("C %3d ; %s",
- $vectorplace{$name}, $metrics{$name}));
-}
-
-# Sort the CharMetrics lines
-@sorted_encoding = sort (@output_encoding);
-
-# Move the unused characters to the end of the list
-@output_encoding = grep(/^C\s+\d+/, @sorted_encoding);
-@minusone_encoding = grep(/C\s+-1/, @sorted_encoding);
-push(@output_encoding, @minusone_encoding);
-
-# Print the new AFM file
-print $line, "\n" while ($line = shift @preamble);
-
-print "Comment Encoded with enc-afm from $encfile.\n";
-print "EncodingScheme $encname\n";
-printf "StartCharMetrics %d\n", $#output_encoding+1;
-print $line, "\n" while ($line = shift @output_encoding);
-print "EndCharMetrics\n";
-
-print $line, "\n" while ($line = shift @postamble);
-
-exit 0;
-
-sub read_afmfile {
- local ($afmfile) = @_;
- local ($inpreamble, $inmetrics, $inpostamble) = (1,0);
- local ($width, $name, $bbox, $prname);
-
- @preamble = ();
- %metrics = ();
- %vectorplace = ();
- @postamble = ();
-
- open (AFM, $afmfile)
- || die "Can't open afm file: $afmfile\n";
-
- while (<AFM>) {
- chop;
-
- push(@postamble, $_) if $inpostamble;
- push(@preamble, $_)
- if $inpreamble && ! /^EncodingScheme\s/i;
-
- if (/^EndCharMetrics/) {
- $inmetrics = 0;
- $inpostamble = 1;
- }
-
- if ($inmetrics) {
- $width = $1 if /[;\s]+WX\s+([0-9]+)[;\s]+/;
- $name = $1 if /[;\s]+N\s+(\w+)[;\s]+/;
- $bbox = $1 if /[;\s]+B\s+([^;]+)[;\s]+/;
- die "Invalid line in AFM file: $_\n"
- if ($name eq "");
- $metrics{$name} = sprintf("WX %4d ; N %s ; B %s ;",
- $width, $name, $bbox);
- $vectorplace{$name} = -1;
- }
-
- if (/^StartCharMetrics/) {
- $inpreamble = 0;
- $inmetrics = 1;
- }
- }
-}
-
-sub read_encfile {
- local ($encfile) = @_;
- local ($place, $line);
-
- open (ENC, $encfile)
- || die "Can't open encoding file: $encfile\n";
-
- $encname = "";
- @encoding = ();
- $#encoding = 256; # set the array length
- $vectorlen = 0;
- $done = 0;
- while (<ENC>) {
- chop;
- next if /^\s*%/;
-
- $line = $_;
- if ($encname eq "") {
- die "Invalid line in encoding file: $_\n"
- if ! /\s*\/(.*)\s*\[(.*)$/;
- $encname = $1;
- $line = $2;
- }
-
- $place = index($line, "%");
- $line = substr($line,$[,$place-1) if $place >= $[;
-
- $place = index($line, "]");
- if ($place >= $[) {
- $line = substr($line,$[,$place-1);
- $done = 1;
- }
-
- while ($line =~ /^\s*\/(\S*)\s*(.*)$/) {
- @encoding[$vectorlen++] = $1;
- $line = $2;
- }
-
- last if $done;
- }
-}
-
-############################################################
-# This routine prints a message followed by a potentially
-# long list of items, seperated by spaces. It will never
-# allow "word wrap" to occur in the middle of a word. There
-# has to be a better way, using Perl's report generation to
-# do this, but I haven't looked yet.
-#
-sub print_long_list {
- local ($message,@thelist) = @_;
- local ($line) = $message;
- local ($item, $displaystring) = ("", "");
-
- foreach $item (@thelist) {
- if (length($line . $item) < 73) {
- $line .= $item . ", ";
- } else {
- $displaystring .= $line . "\n";
- $line = $item . ", ";
- }
- }
-
- $line =~ s/(.*),\s*$/$1/; # remove the last ", "...
- $displaystring .= $line . "\n";
-
- print STDERR $displaystring;
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-06 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-06
deleted file mode 100644
index b7fb42f1853..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-06
+++ /dev/null
@@ -1,181 +0,0 @@
-#!/usr/local/bin/bash
-#
-# This script file makes a new X/TeX screen font, because one wasn't
-# found. Parameters are:
-#
-# name dpi bdpi magnification destdir
-#
-# `name' is the name of the font, such as `cmr10'. `dpi' is
-# the resolution the font is needed at. `bdpi' is the base
-# resolution, useful for figuring out the mode to make the font
-# in. `magnification' is a string to pass to MF as the
-# magnification. 'destdir' is the directory in which to cache the new
-# font.
-#
-# Note that this file must execute Metafont, mftobdf, and then bdftosnf,
-# and place the result in the correct location for X
-# to find it subsequently.
-#
-# Of course, it needs to be set up for your site.
-#
-# TEMPDIR needs to be unique for each process because of the possibility
-# of simultaneous processes running this script.
-TEMPDIR=/tmp/bdf-snf.$$
-NAME=$1
-DPI=$2
-BDPI=$3
-MAG=$4
-MODE=$5
-DESTDIR=$6
-umask 0
-
-#declare -i cmfound=0
-#MFDIRS=`echo $MFINPUTS | gawk -F: '{ for (i=1; i<=NF; i++) print $i }'`
-#for f in $MFDIRS
-#do
-# if [ -r $f/$NAME.mf ]; then
-# declare -i cmfound=1
-# fi
-#done
-
-if [ -r /usr/local/lib/tex/fonts/ps-outlines/$NAME.pfa ]
-then
- echo Building X-font from PostScript outline
- PStoXfont $1 $2 $3 $4 $5 $6
- exit 0
-else
- echo Building X-font from MetaFont outline
-fi
-
-# Something like the following is useful at some sites.
-GFNAME=$NAME.$DPI'gf'
-BDFNAME=$NAME.$DPI.'bdf'
-SNFNAME=$NAME.$DPI.pcf
-
-COMPRESS=1
-
-# check if we're not running with MIT server after all
-if xdpyinfo|grep -s 'vendor string: *.*MIT.*'; then
-# DESTDIR=/usr/lib/X11/fonts/xtex
-# SNFNAME=$NAME.$DPI.'snf'
- COMPRESS=0
- MITSERVER=1
-fi
-
-if test "$COMPRESS" = "1"
-then
- SNFZNAME=${SNFNAME}'.Z'
-else
- SNFZNAME=${SNFNAME}
-fi
-
-# Clean up on normal or abnormal exit
-trap "cd /; rm -rf $TEMPDIR $DESTDIR/bdftmp.$$ $DESTDIR/snftmp.$$" 0 1 2 15
-
-mkdir $TEMPDIR
-cd $TEMPDIR
-
-if test -r $DESTDIR/$BDFNAME
-then
- echo "$DESTDIR/$BDFNAME already exists!"
- exit 0
-fi
-
-if test -r $DESTDIR/$SNFNAME
-then
- echo "$DESTDIR/$SNFNAME already exists!"
- exit 0
-fi
-
-if test -r $DESTDIR/$SNFZNAME
-then
- echo "$DESTDIR/$SNZFNAME already exists!"
- exit 0
-fi
-
-
-##
-# First try mftobdf, maybe it exists...
-##
-
-echo "1st mftobdf -dpi" $DPI $NAME
-mftobdf -dpi $DPI $NAME
-if test ! -r $BDFNAME
-then
- pwd
- echo mf "\mode:=$MODE; mag:=$MAG/1000; scrollmode; input $NAME </dev/null"
- mf "\mode:=$MODE; mag:=$MAG/1000; scrollmode; input $NAME" </dev/null
- if test ! -r $GFNAME
- then
-#
-# My local metafont gives bogus names occasionally. Don't know why.
-#
- echo "Unable to find $GFNAME in directory "`pwd`
- OLDDPI=$DPI
- NEWDPI=`expr $DPI - 1`
- if [ -r $NAME.$NEWDPI'gf' ] ; then
- DPI=$NEWDPI
- fi
- NEWDPI=`expr $DPI + 1`
- if [ -r $NAME.$NEWDPI'gf' ] ; then
- DPI=$NEWDPI
- fi
- if [ -r $NAME.$DPI'gf' ] ; then
- GFNAME=$NAME.$DPI'gf'
- BDFNAME=$NAME.$DPI.'bdf'
- SNFNAME=$NAME.$DPI.pcf
- echo "Metafont built $GFNAME instead of $NAME.${OLDDPI}gf, \
-but that's ok..."
- gftopk $GFNAME
- else
- echo "Metafont failed for some reason on $GFNAME, \
-but continuing anyway"
- fi
- else
- gftopk $GFNAME
- fi
-
- echo "mftobdf -dpi" $DPI $NAME
- mftobdf -dpi $DPI $NAME
- if test ! -r $BDFNAME
- then
- echo "Mftobdf failed for some reason on $BDFNAME"
- exit 1
- fi
-fi
-
-echo "$FONTCOMPILER"
-if [ $MITSERVER ]; then
- bdftopcf $BDFNAME > $SNFNAME
-else
- /usr/bin/dxfc $BDFNAME > $SNFNAME
-fi
-if test ! -r $SNFNAME
-then
- echo "Font compiler failed for some reason on $SNFNAME"
- exit 1
-fi
-
-# Install the BDF and SNF files carefully, since others may be doing
-# the same as us simultaneously.
-
-#cp $BDFNAME $DESTDIR/bdftmp.$$
-cp $SNFNAME $DESTDIR/snftmp.$$
-cd $DESTDIR
-#mv bdftmp.$$ $BDFNAME
-mv snftmp.$$ $SNFNAME
-
-if test "$COMPRESS" = "1"
-then
- compress -f $SNFNAME
-fi
-
-if [ $MITSERVER ]; then
- mkfontdir $DESTDIR
-else
- /usr/bin/dxmkfontdir $DESTDIR
-fi
-xset +fp $DESTDIR
-xset fp rehash
-
-exit 0
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-07 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-07
deleted file mode 100644
index 5ae9a0e61c2..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-07
+++ /dev/null
@@ -1,64 +0,0 @@
-#!/usr/local/bin/bash
-#
-# This script file makes a new X/TeX screen font, because one wasn't
-# found. Parameters are:
-#
-# name dpi bdpi mag mode destdir
-#
-# `name' is the name of the font, such as `cmr10'. `dpi' is
-# the resolution the font is needed at. `bdpi' is the base
-# resolution, useful for figuring out the mode to make the font
-# in. `magnification' is a string to pass to MF as the
-# magnification. 'destdir' is the directory in which to cache the new
-# font.
-#
-# Note that this file must execute Metafont, mftobdf, and then bdftosnf,
-# and place the result in the correct location for X
-# to find it subsequently.
-#
-# Of course, it needs to be set up for your site.
-#
-# TEMPDIR needs to be unique for each process because of the possibility
-# of simultaneous processes running this script.
-#
-# This temp directory has to be under /users/oos/bin (or somewhere globally
-# accessible) because this script runs PS2PK on ibis even if it is started
-# elsewhere (e.g. on a Sparc). To do so, it uses the "ibis [cmd]" shortcut
-# and passes the temp directory. If the TEMPDIR was /tmp/whatever then,
-# it would fail because /tmp on a Sparc isn't /tmp on ibis.
-TEMPDIR=/users/oos/bin/PStemp/temp-X-PS.$$
-
-NAME=$1
-DPI=$2
-BDPI=$3
-MAG=$4
-MODE=$5
-DESTDIR=$6
-
-BASENAME=$NAME.$MAG.$BDPI
-PTSIZE=`echo "2 k $MAG 100 / p q" | dc`
-PFADIR=/usr/local/lib/tex/fonts/ps-outlines/
-
-# Clean up on normal or abnormal exit
-trap "cd /; rm -rf $TEMPDIR" 0 1 2 15
-
-mkdir $TEMPDIR
-cd $TEMPDIR
-
-echo Making ${PTSIZE}pt ${BDPI}dpi version of $NAME.
-ps2pk -v -X$BDPI -P$PTSIZE -a$PFADIR/$NAME.afm \
- $PFADIR/$NAME.pfa $BASENAME.pk
-
-pktobdf $BASENAME.pk | gawk -vname=$NAME.$DPI -f \
- /usr/local/lib/tex/ps/PStoXfont.awk > $BASENAME.bdf
-bdftopcf $BASENAME.bdf > $BASENAME.pcf
-mv $BASENAME.pcf $DESTDIR
-
-mkfontdir $DESTDIR
-xset +fp $DESTDIR
-xset fp rehash
-
-exit 0
-
-
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-08 b/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-08
deleted file mode 100644
index 7e860797a8e..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/examples/ex-D-08
+++ /dev/null
@@ -1,191 +0,0 @@
-#!/usr/local/bin/perl
-#
-# txt2verb Copyright (C) 1993 by Norm Walsh <norm@ora.com>
-# Distribute freely under the terms of the GNU Copyleft.
-#
-# Converts a text "screen" into a form suitable for \inputing into TeX
-# and printing as a screen dump. The original form is assumed to be
-# a series of 80-byte lines with any character in the range 0-255 present
-# (including CR and LF in the middle of a line).
-#
-# The output form is a series of lines of varying length. There is
-# one output line for each input line. TeX special characters and all
-# characters in the ranges 0-31 and 127-255 are replaced by control
-# sequences.
-#
-# Usage:
-#
-# txt2verb screenfile <texfile>
-#
-# If texfile is not specified, stdout is assumed.
-#
-# Options:
-#
-# -l File of lines. Input file contains lines of varying length,
-# but no imbedded CR or LF chars.
-# -v Verbose: print each input line as it's read.
-# -q Quiet: no messages.
-# -L # Set line length to '#' characters.
-#
-# To incorporate the resulting screen dump in your Plain TeX or LaTeX
-# document, insert the following macro definitions before the first
-# screen dump:
-#
-# \font\screenfont=cr-pc8 at 8pt % use any IBM OEM encoded fixed width font!
-#
-# %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-# % These macros are derived from The TeXbook pg 380-381
-# \def\uncatcodespecials{\def\do##1{\catcode`##1=12 }\dospecials}
-# \def\setupverbatim{\screenfont%
-# \def\par{\leavevmode\endgraf\relax}%
-# \obeylines\uncatcodespecials%
-# \catcode`\\=0\catcode`\{=1\catcode`\}=2\obeyspaces}
-# {\obeyspaces\global\let =\ } % let active space be a control space
-# \def\screenlisting#1{\par\begingroup%
-# \def\c##1{\char##1}\setupverbatim\input{#1}%
-# \endgroup}
-# %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-# \def\screenbox#1{%
-# \vbox{\offinterlineskip%
-# \parskip=0pt\parindent=0pt%
-# \screenlisting{#1}}}
-# %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-# % Input converted file '#1' and set it inside a box with '#2' padding
-# % space around the image.
-# \def\screendump#1#2{%
-# \hbox{\vrule%
-# \vbox{\hrule%
-# \hbox{\hskip#2%
-# \vbox{\vskip#2%
-# \def\twentyxs{xxxxxxxxxxxxxxxxxxxx}%
-# \setbox0=\hbox{\screenfont\twentyxs\twentyxs\twentyxs\twentyxs}%
-# \hbox to \wd0{\screenbox{#1}\hss}%
-# \vskip#2}%
-# \hskip#2}%
-# \hrule}%
-# \vrule\hss}}
-# %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-#
-# To include the converted image 'screen.tex' in your document with 2pt
-# of padding around the image, use:
-#
-# \screendump{screen}{2pt}
-#
-# in your document. Note: since this is set as an 'hbox', you may need
-# to use \leavevmode\screendump{screen}{2pt}
-#
-##########################################################################
-
-require 'getopts.pl';
-do Getopts('lvqL:');
-
-die "$0: options make no sense: -l and -L $opt_L.\n" if $opt_l && $opt_L;
-
-$FILEOFLINES = $opt_l;
-$VERBOSE = $opt_v;
-$QUIET = $opt_q;
-$LINELENGTH = $opt_L || 80;
-
-$capturefile = @ARGV[0] || die "Usage: $0 capturefile <texfile>";
-$texfile = @ARGV[1] || "-";
-
-select(STDERR); $| = 1; select(STDOUT); # no buffering of stderr
-
-%badchars = (); # These characters are illegal on input
-
-# anything in the control character range
-for ($byte = 0; $byte < 32; $byte++) {
- $char = sprintf("%c", $byte);
- $badchars{$char} = "\\c{$byte}";
-}
-
-# and anything over 126
-for ($byte = 127; $byte < 256; $byte++) {
- $char = sprintf("%c", $byte);
- $badchars{$char} = "\\c{$byte}";
-}
-
-$badchars{"\%"} = '\%';
-$badchars{"\$"} = '\$';
-$badchars{"\&"} = '\&';
-$badchars{"\#"} = '\#';
-$badchars{"\{"} = '\c{123}';
-$badchars{"\}"} = '\c{125}';
-$badchars{"\\"} = '\c{92}';
-$badchars{"\_"} = '\c{95}';
-$badchars{"\^"} = '\c{94}';
-
-open (CAPTFILE, $capturefile)
- || die "Can't open capture file: $capturefile\n";
-open (TEXFILE, ">$texfile")
- || die "Can't open TeX file: $texfile\n";
-while ($line = &get_line()) {
- print STDERR "." if $texfile ne "-" && !$VERBOSE && !$QUIET;
- print STDERR "$line\n" if $VERBOSE;
-
- $outputbuf = "";
- while (length($line) > 0) {
- $char = substr($line,0,1);
- $line = substr($line,1);
-
- if (defined($badchars{$char})) {
- $outputbuf .= $badchars{$char};
- } else {
- $outputbuf .= $char;
- }
- }
- print TEXFILE "$outputbuf\n";
-}
-
-close(CAPTFILE);
-close(TEXFILE);
-
-exit 0;
-
-sub get_text_line {
- local($line);
-
- if ($line = scalar(<CAPTFILE>)) {
- chop($line);
- }
-
- $line;
-}
-
-sub get_data_line {
- local($datalen, $line);
-
- if ($datalen = read(CAPTFILE, $line, $LINELENGTH)) {
- # if we got a complete line, look to see if the next
- # characters in the file are CR, CR/LF, or LF. If so, remove
- # them (assume the are line breaks in the file)
- if ($datalen = $LINELENGTH) {
- $place = tell(CAPTFILE);
- $datalen = read(CAPTFILE, $line, 1);
- if ($line eq "\015") {
- $place++;
- $datalen = read(CAPTFILE, $line, 1);
- if ($line ne "\012") {
- seek(CAPTFILE, $place, 0);
- }
- } elsif ($line ne "\012") {
- seek(CAPTFILE, $place, 0);
- }
- }
- } else {
- return undef;
- }
-
- $line;
-}
-
-sub get_line {
- local($line);
- if ($FILEOFLINES) {
- $line = &get_text_line();
- } else {
- $line = &get_data_line();
- }
-
- $line;
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/apa.html b/Master/texmf-doc/doc/english/make-tex-work/html/apa.html
deleted file mode 100644
index 5ac16b87c4b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/apa.html
+++ /dev/null
@@ -1,903 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Appendix&#160;A.&#160;Filename Extension Summary</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="ch16.html"
- title="Chapter&#160;16.&#160;TeX Utilities" />
- <link rel="next" href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;16.&#160;TeX Utilities"
- href="ch16.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Appendix&#160;B.&#160;Font Samples"
- href="apb.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="appendix">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.fileext"
- name="chap.fileext"></a>Appendix&#160;A.&#160;Filename
- Extension Summary</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- </div>
-
- <p>This chapter summarizes many common filename extensions.
- The extensions are listed in alphabetical order. All
- extensions can be shortened to three letters for consistency
- with operating systems that do not allow longer file
- extensions. On other file systems, they may be slightly
- different. For example, <tt>EPS</tt> files are sometimes
- called <tt>EPSF</tt> files on unix systems, which allow
- longer filenames.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">abf</span></dt>
-
- <dd>
- <p>An Adobe binary screen font file contains a binary
- encoding of a BDF (bitmap distribution format) file.
- Binary encoding makes the files smaller, but it also
- makes them less portable and unintelligible to humans.
- The binary format is described in Adobe's ABF Format
- Specification&#160;[<a
- href="bi01.html#abffiles">abffiles</a>]. BDF files are
- described below.</p>
- </dd>
-
- <dt><span class="term">afm</span></dt>
-
- <dd>
- <p>Adobe font metrics files are ASCII files distributed
- with \ps Type&#160;1 fonts. Type&#160;1 fonts are the
- linearly scalable fonts that \ps printer users are most
- familiar with. Bounding boxes, an encoding vector (what
- characters go where), kerning, and ligature information
- are among the things described in this file. The AFM
- file format is described completely in Adobe's AFM
- Format Specification&#160;[<a
- href="bi01.html#afmfiles">afmfiles</a>].</p>
-
- <p>\ps fonts (available through commercial vendors or
- from the Internet) are supplied with AFM files.
- Generally, the only occasion that you would have to
- modify an AFM file would be to change the encoding
- vector.</p>
- </dd>
-
- <dt><span class="term">aux</span></dt>
-
- <dd>
- <p>Auxiliary files are built by LaTeX each time it
- formats a document. LaTeX writes information about
- cross references, citations, etc., to the auxiliary
- file for post-processing by other tools, or for TeX
- processing the next time this document is
- formatted.</p>
- </dd>
-
- <dt><span class="term">bbl</span></dt>
-
- <dd>
- <p>Bibliography files are created by BibTeX from the
- citations in your document, the bibliography databases
- (BIB) that you specify, and the bibliography style
- (BST) you use. BibTeX writes the resulting bibliography
- to the BBL file, which is automatically included in
- your LaTeX document at the place where you define the
- bibliography.</p>
- </dd>
-
- <dt><span class="term">bdf</span></dt>
-
- <dd>
- <p>Bitmap distribution format files are ASCII files
- that describe a bitmap font. They are frequently used
- to distribute bitmap versions of scalable fonts in
- screen resolution at common sizes. They are resolution
- specific, but they are portable from one architecture
- to another. The BDF file format is described completely
- in Adobe's BDF Format Specification&#160;[<a
- href="bi01.html#bdffiles">bdffiles</a>].</p>
-
- <p>Some fonts packages are distributed with BDF files.
- Other BDF files are created as part of the conversion
- process from native format to X11 format. It is
- unlikely that you would ever create one purely by
- hand.</p>
- </dd>
-
- <dt><span class="term">bib</span></dt>
-
- <dd>
- <p>Bibliography databases contain bibliographic
- information. These are generally handwritten and may
- contain bibliographic information for all of the
- sources that you are (ever) likely to cite. The BibTeX
- program reads information about each work that you
- FIXME: from the BIB file. Consult the documentation for
- BibTeX for more information about the format of BIB
- files.</p>
- </dd>
-
- <dt><span class="term">blg</span></dt>
-
- <dd>
- <p>BibTeX log files record the status of the last run
- of BibTeX.</p>
- </dd>
-
- <dt><span class="term">bst</span></dt>
-
- <dd>
- <p>Bibliography style files are used by BibTeX to
- define the layout of the citations. BibTeX produces
- LaTeX commands in the BBL file that define the
- citations in the format specified by the BST file.</p>
-
- <p>You may eventually write or modify a bibliography
- style file, but it is less common than modifying LaTeX
- style files because bibliographies have a more rigidly
- defined format. Consult the documentation for BibTeX
- for more information about the format of BST files.</p>
- </dd>
-
- <dt><span class="term">bzr</span></dt>
-
- <dd>
- <p>The GNU fontutils define the BZR format to hold
- generic scalable font data. The file actually contains
- the specification for a series of bezier curves. The
- BZR file format is defined in the TeXinfo pages that
- accompany the GNU fontutils. The GNU fontutils create
- BZR files.</p>
- </dd>
-
- <dt><span class="term">dvi</span></dt>
-
- <dd>
- <p>TeX produces device-independent output in the DVI
- file. This file describes the TeXed document in a
- simple stack language that can be rendered on any
- device. The format of DVI files is described in the
- \web documentation for <b>DVItype</b>, or in <span
- class="emphasis"><em>The DVI Drivers
- Standard</em></span>&#160;[<a
- href="bi01.html#dvi:standard">dvi:standard</a>].</p>
-
- <p>TeX (and some <b>MFware</b> utilities) produces DVI
- files.</p>
-
- <p>\hyphenation{encap-sulated}</p>
- </dd>
-
- <dt><span class="term">epsf</span></dt>
-
- <dd>
- <p>Encapsulated \ps files contain scalable \ps images
- and extra information (such as the size of the image's
- bounding box) that is necessary to scale the image
- appropriately for printing, unlike generic \ps. Using
- encapsulated \ps images in your TeX document requires a
- DVI driver that understands \ps \specials. How to
- include pictures and figures via encapsulated
- PostScript is described in detail in Chapter&#160;<a
- href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a>,
- <span class="emphasis"><em><a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a></em></span>.</p>
-
- <p>You are unlikely to create encapsulated \ps files by
- hand, but many drawing and drafting programs can create
- them for you.</p>
- </dd>
-
- <dt><span class="term">fig</span></dt>
-
- <dd>
- <p>FIG files are created by the <b>XFig</b> program
- (and possibly other programs). The scalable
- representation of a collection of graphics objects is
- stored in ASCII form in FIG files. The <b>transfig</b>
- program can translate FIG files into a number of other
- formats including EPSF, HPGL, and a variety of LaTeX
- environments.</p>
- </dd>
-
- <dt><span class="term">fli</span></dt>
-
- <dd>
- <p>Font libraries are distributed with emTeX. They
- contain a collection of PK files. Font libraries have
- several advantages over a directory full of PK files:
- they are easier to maintain (because you don't have to
- deal with hundreds of files); they are faster to search
- (because they are indexed more efficiently than a
- directory); they are smaller (because <span
- class="emphasis"><em>each</em></span> PK file wastes an
- average of half a cluster of disk space); and the name
- of each font is not limited to eight characters as it
- is under MS-DOS file naming conventions.</p>
-
- <p>Note: <b>dvips</b> can also use emTeX FLI files.</p>
- </dd>
-
- <dt><span class="term">gf</span></dt>
-
- <dd>
- <p>Generic font files contain bitmap data for the
- characters of a font. The GF format is very simple, and
- many TeX related programs that create fonts produce GF
- files. The disadvantage of GF files is that they are
- very large (because no compression is performed). The
- format of GF files is described in the \web
- documentation for <b>GFtoPK</b> (or any of the
- GF-related <b>MFware</b> programs).</p>
-
- <p>MetaFont is the primary source for GF files. Some
- other programs (some of the GNU fontutils, for example)
- also produce GF files.</p>
- </dd>
-
- <dt><span class="term">gif</span></dt>
-
- <dd>
- <p>Graphics interchange format is a CompuServe bitmap
- graphics standard. GIF files are very popular, and a
- number of converters (e.g., <b>BM2FONT</b>) can
- translate GIF files into a format usable by TeX.</p>
- </dd>
-
- <dt><span class="term">glo</span></dt>
-
- <dd>
- <p>Glossary files are produced by the LaTeX \glossary
- command. They are analogous to the IDX files produced
- by the \index commands. The glossary is inserted in
- your document wherever the \makeglossary command
- occurs.</p>
- </dd>
-
- <dt><span class="term">gsf</span></dt>
-
- <dd>
- <p>Ghostscript fonts are scalable fonts very similar to
- \ps Type&#160;1 fonts. Theoretically,
- <b>Ghostscript</b> can use \ps Type&#160;1 fonts
- directly, although I have never tried. Several GSF
- fonts are distributed with <b>Ghostscript</b>.</p>
- </dd>
-
- <dt><span class="term">hpgl</span></dt>
-
- <dd>
- <p>Hewlett-Packard GL is a plotter language. Many
- programs can produce vector graphics in HPGL
- format.</p>
- </dd>
-
- <dt><span class="term">hptfm</span></dt>
-
- <dd>
- <p>Hewlett-Packard tagged font metric files are a lot
- like TeX TFM files. It is unfortunate that both files
- have the extension TFM because they are completely
- incompatible. You can generate TeX TFM files from
- HPTFMs with the <b>HPTFM2PL</b> program.</p>
- </dd>
-
- <dt><span class="term">idx</span></dt>
-
- <dd>
- <p>Index files are produced automatically when you use
- the \index commands in LaTeX. The IDX file contains raw
- indexing data that will be used by the <b>MakeIndex</b>
- program to build an index for your document. You must
- include the <tt>makeidx</tt> style in your
- <tt>documentstyle</tt> command, and you must turn on
- indexing with \makeindex in the preamble of your
- document if you wish to (re)build the index. See the
- entry for IND files below for more information.</p>
- </dd>
-
- <dt><span class="term">ilg</span></dt>
-
- <dd>
- <p><b>MakeIndex</b> log files record the status of the
- last run of <b>MakeIndex</b>.</p>
- </dd>
-
- <dt><span class="term">img</span></dt>
-
- <dd>
- <p>The IMG format is a particular bitmapped image
- format used by the GEM Window System (a PC-based
- windowed desktop interface product). The GNU fontutils
- read IMG files as their default format. The
- <b>PBMplus</b> utilities<sup>[<a id="id2942243"
- name="id2942243" href="#ftn.id2942243">129</a>]</sup>
- can convert between many graphics file formats,
- including IMG.</p>
-
- <p>Some scanning software produces IMG files directly.
- Other IMG files are distributed by the Free Software
- Foundation as part of an ongoing project to produce
- high-quality, free typefaces.</p>
- </dd>
-
- <dt><span class="term">ind</span></dt>
-
- <dd>
- <p>Index files are produced by the <b>MakeIndex</b> and
- automatically get included into your LaTeX document
- wherever you put the \printindex command. The \index
- commands in your LaTeX document write raw indexing data
- to the IDX file. <b>MakeIndex</b> reads the IDX file,
- sorts and formats the index according to the IST file,
- and produces an IND file for your document.</p>
- </dd>
-
- <dt><span class="term">ist</span></dt>
-
- <dd>
- <p>Index specification files are used by
- <b>MakeIndex</b> to format the index file. Consult the
- documentation for <b>MakeIndex</b> for more
- information.</p>
- </dd>
-
- <dt><span class="term">jpeg</span></dt>
-
- <dd>
- <p>JPEG files are compressed bitmap images. Because
- JPEG files use a &#8220;lossy&#8221; compression
- algorithm, they are frequently much smaller than other
- formats.</p>
- </dd>
-
- <dt><span class="term">lof</span></dt>
-
- <dd>
- <p>List of figures files are produced by the
- \listoffigures command in LaTeX. After seeing
- \listoffigures, LaTeX writes figure captions to the LOF
- file. The next time the document is formatted, LaTeX
- will insert the LOF file at the point where you issue
- the \listoffigures command.</p>
- </dd>
-
- <dt><span class="term">log</span></dt>
-
- <dd>
- <p>Log files are always produced by TeX and MetaFont.
- The LOG file is generally uninteresting. Status and
- warning messages deemed too trivial (or too detailed)
- for the display are written to the log file (all
- messages written to the display are also written to the
- log).</p>
- </dd>
-
- <dt><span class="term">lot</span></dt>
-
- <dd>
- <p>List of tables files are exactly analogous to LOF
- files.</p>
- </dd>
-
- <dt><span class="term">mf</span></dt>
-
- <dd>
- <p>Just as TeX reads TEX files, which are plain ASCII
- descriptions of a typeset document, MetaFont reads MF
- files, which are plain ASCII descriptions of a
- typeface. MetaFont and MF files are the topic of
- Knuth's \MFbook&#160;[<a
- href="bi01.html#kn:mfbook">kn:mfbook</a>]. Unlike \ps
- fonts, MetaFont fonts are not linearly scaled.<sup>[<a
- id="id2942471" name="id2942471"
- href="#ftn.id2942471">130</a>]</sup></p>
-
- <p>The standard TeX distribution contains the MF files
- for the Computer Modern fonts. Knuth has produced
- several more MF files to demonstrate MetaFont. The
- American Mathematical Society has extended Computer
- Modern with several more. The <b>MFpic</b> macro
- package produces MF files from a picture-like
- environment in TeX. \TheMFbook describes how to create
- your own fonts with MetaFont.</p>
-
- <p>The <span class="emphasis"><em>List of
- MetaFonts</em></span>&#160;[<a
- href="bi01.html#lreq:metafonts">lreq:metafonts</a>] is
- posted occasionally to the newsgroups
- \path|comp.text.tex| and \path|comp.fonts|.</p>
-
- <p>Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>,
- <span class="emphasis"><em><a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a></em></span>,
- describes MetaFont in more detail. The TeX fonts
- available in MetaFont format are listed in
- Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.</p>
- </dd>
-
- <dt><span class="term">mfj</span></dt>
-
- <dd>
- <p>MFjob files are plain ASCII files that contain
- instructions for <b>MFjob</b>, an emTeX program that
- builds groups of MetaFont fonts. MFJ files can be
- created by hand to automate the process of building a
- set of fonts. They are also created by the emTeX DVI
- drivers if automatic font generation is being used.</p>
- </dd>
-
- <dt><span class="term">msp</span></dt>
-
- <dd>
- <p>Microsoft Paint files contain bitmapped graphic
- images. They can be included in a TeX document with
- \special commands recognized by the emTeX DVI
- drivers.</p>
- </dd>
-
- <dt><span class="term">pbm</span></dt>
-
- <dd>
- <p>The portable bitmap format is a flexible bitmap
- representation introduced by the <b>PBMplus</b>
- package. The <b>PBMplus</b> utilities allow for the
- conversion of PBM format files to and from almost
- anything else. The PBM format (and all the utilities)
- are described in the manpages that accompany the
- <b>PBMplus</b> toolkit distribution.</p>
-
- <p>The PBM toolkit and many other X11 graphics
- utilities can read and write PBM files (e.g. XV).</p>
- </dd>
-
- <dt><span class="term">pcf</span></dt>
-
- <dd>
- <p>The PCF format is one of several X11 bitmap font
- formats. Architecture-specific versions of X11 use PCF
- files. Other architectures use one of a number of other
- architecture-specific formats (e.g., SNF). PCF files
- are used by at least the DEC versions of the X11
- server. The X11 distribution for your architecture
- includes a program that will convert BDF files to the
- standard adopted for your architecture.</p>
-
- <p>PCF files are almost invariably created from some
- other source. It is unlikely that you will ever create
- one by hand.</p>
- </dd>
-
- <dt><span class="term">pcl</span></dt>
-
- <dd>
- <p>PCL files contain printer commands for HP LaserJet
- printers. DVI drivers for HP LaserJet printers create
- PCL files. It is possible to get information out of
- some PCL files with <b>pcltomsp</b>.</p>
- </dd>
-
- <dt><span class="term">pcx</span></dt>
-
- <dd>
- <p>PCX files contain bitmapped graphic images. They can
- be included in a TeX document with \special commands
- recognized by the emTeX DVI drivers.</p>
- </dd>
-
- <dt><span class="term">pfa</span></dt>
-
- <dd>
- <p>Printer font ASCII files contain scalable outline
- data that describes each character in a Type&#160;1
- font. A large portion of this file is encrypted, so it
- is an ASCII file only in the sense that the binary
- portion is represented as a string of hexadecimal ASCII
- digits. This is traditional \ps because it is pure
- ASCII. See PFB below.</p>
-
- <p>Type&#160;1 outline fonts are created by special
- font editing programs or conversion tools (e.g. the GNU
- fontutils).</p>
- </dd>
-
- <dt><span class="term">pfb</span></dt>
-
- <dd>
- <p>Printer font binary files, like PFA files, contain
- the outline data for \ps Type&#160;1 fonts. The binary
- format was adopted to save space (they are generally
- about half the size of their PFA counterparts).<sup>[<a
- id="id2942788" name="id2942788"
- href="#ftn.id2942788">131</a>]</sup> Because they are
- binary files, it is more difficult to transfer them
- from one architecture to another (endian-ness, binary
- transmission, etc.). \ps purists are apt to disparage
- them.</p>
- </dd>
-
- <dt><span class="term">pfm</span></dt>
-
- <dd>
- <p>Printer font metric files are a Microsoft Windows
- standard. They are encountered frequently in archives
- that contain Type&#160;1 fonts. Unfortunately, these
- archives occasionally fail to include AFM files, which
- are more standard outside of the Windows community.
- Even more unfortunately, PFM files do not contain all
- of the information that is in an AFM file. However, the
- <b>PFM2AFM</b> program can construct a partial AFM
- file. I believe that the PFM file format is described
- in a Microsoft technical note; however, I have never
- seen it.</p>
-
- <p>Unless you use Microsoft Windows, PFM files are
- likely to be useless. If you need PFM files, the MS-DOS
- program <b>Refont</b> can create them from AFM
- files.</p>
- </dd>
-
- <dt><span class="term">pk</span></dt>
-
- <dd>
- <p>Most TeX DVI conversion programs read packed bitmap
- font files. The PK font format defines a clever scheme
- that allows bitmap fonts to be compressed
- significantly. The format of PK files is described in
- the \web documentation for <b>PKtype</b> (or any of the
- PK-related <b>MFware</b> programs).</p>
-
- <p>You are unlikely to create PK files by hand, per se,
- but there are a number of utility programs that
- ultimately create PK files (e.g., <b>GFtoPK</b>,
- MetaFont, <b>MFpic</b>, <b>PS2PK</b>).</p>
- </dd>
-
- <dt><span class="term">pl</span></dt>
-
- <dd>
- <p>A property list file contains an ASCII
- representation of a binary file. The property list
- format was created during TeX development to allow
- binary files (specifically TFM files) to be hand-coded.
- Most users have no reason to create PL files; however,
- some programs create PL files that must be converted
- into TFM files with the TeXware program <b>PLtoTF</b>.
- The PL format is described in the \web documentation
- for <b>PLtoTF</b>.</p>
-
- <p>If you need to edit TeX font metric information for
- a particular font, you will almost certainly do so by
- editing the PL file. You can create a PL file from a
- TFM file with the <b>TFtoPL</b> utility.</p>
- </dd>
-
- <dt><span class="term">ps</span></dt>
-
- <dd>
- <p>\ps is a page description language. The \ps language
- is described in a series of volumes from Adobe Systems.
- PS is a common extension for \ps files.</p>
-
- <p>Unless you are inclined to enter the Obfuscated \ps
- Contest, you are unlikely to create \ps files by hand.
- \ps files are created by many common tools.</p>
- </dd>
-
- <dt><span class="term">pxl</span></dt>
-
- <dd>
- <p>This format is obsolete. It has been completely
- superseded by the PK format. If you still have PXL
- files, you can convert them to PK format with the
- <b>PXtoPK</b> program. If you are still using a DVI
- driver that needs PXL files, you need an upgrade.</p>
- </dd>
-
- <dt><span class="term">sfl</span></dt>
-
- <dd>
- <p>These files contain HP LaserJet softfonts in
- landscape orientation. LaserJet softfonts are device
- specific bitmap representations of a typeface. The
- bitmap versions are described thoroughly in the <span
- class="emphasis"><em>LaserJet Technical Reference
- Manual</em></span>&#160;[<a
- href="bi01.html#pcl5:techref">pcl5:techref</a>] for
- each of the HP LaserJet printers. Newer laser printers
- can perform automatic rotation of fonts (in 90 degree
- increments, at least), so the distinction between
- landscape and portrait font files is disappearing.</p>
- </dd>
-
- <dt><span class="term">sfp</span></dt>
-
- <dd>
- <p>These files contain HP LaserJet softfonts in
- portrait orientation. See the entry for SFL files,
- above.</p>
- </dd>
-
- <dt><span class="term">sfs</span></dt>
-
- <dd>
- <p>Scalable softfonts are HP LaserJet softfonts for the
- new (HPLJ III and higher) LaserJet printers. These are
- really in AGFA IntelliFont Scalable format&#160;[<a
- href="bi01.html#intellifont">intellifont</a>].</p>
- </dd>
-
- <dt><span class="term">snf</span></dt>
-
- <dd>
- <p>Server native format fonts are another version of
- X11 bitmap font. See the entry for PCF files, above,
- for more information.</p>
- </dd>
-
- <dt><span class="term">sty</span></dt>
-
- <dd>
- <p>Style files are used by LaTeX to define the layout
- of a LaTeX document (by redefining the meaning of
- commands like \section, for example). They are also
- used commonly to extend LaTeX. See the LaTeX
- manual&#160;[<a
- href="bi01.html#ll:latexbook">ll:latexbook</a>] for
- more information.</p>
-
- <p>Style files are really just TeX files that perform
- specific tasks. You will eventually write or modify a
- style file, but it isn't something you are likely to do
- every day.</p>
- </dd>
-
- <dt><span class="term">tex</span></dt>
-
- <dd>
- <p>TEX files describe the layout of a typeset document
- in the TeX programming language,<sup>[<a id="id2943178"
- name="id2943178" href="#ftn.id2943178">132</a>]</sup>
- as defined by <span class="emphasis"><em>The
- TeXbook</em></span>&#160;[<a
- href="bi01.html#kn:texbook">kn:texbook</a>]. Most
- people use some form of macro package on top of TeX to
- make the language easier to swallow. If a TeX file
- begins with \documentstyle{} or has \begin{document}
- somewhere near the top, it is probably a LaTeX
- document. Otherwise, look for the \input commands to
- see what macro packages are being included.</p>
-
- <p>Documents that do not appear to be LaTeX documents
- and do not appear to \input special macro packages may
- be using a special <span
- class="emphasis"><em>format</em></span>. Formats are
- fast-loading precompiled macro packages. If you know
- the name of the format file, you can tell TeX to use it
- by typing &amp;<span
- class="emphasis"><em>format-name</em></span> as a
- parameter to TeX.</p>
- </dd>
-
- <dt><span class="term">tiff</span></dt>
-
- <dd>
- <p>TIFF files contain bitmapped or vector graphic
- images in a very flexible form. The &#8220;T&#8221; in
- TIFF stands for &#8220;tagged.&#8221; All of the
- different kinds of information (regarding number of
- colors, compression, etc.) that might appear in a TIFF
- file are given unique tags that allow a TIFF file
- reader to skip over information that it does not
- understand.</p>
- </dd>
-
- <dt><span class="term">tfm</span></dt>
-
- <dd>
- <p>TeX font metric files contain information about
- fonts. TeX doesn't know anything about the intrinsic
- shape of the characters that it lays down on the page.
- TeX deals entirely with boxes. Every character is
- described by the rectangular box that (usually)
- surrounds it. The TFM file for a font describes the
- size of each character's box, as well as ligature and
- kerning information for the font. A human-readable
- version of a TFM file can be produced with the
- <b>TFtoPL</b> program. The format of TFM files is
- described thoroughly in the \web documentation for
- <b>TFtoPL</b>.</p>
-
- <p>If you have reason to modify a TFM file, you will
- almost certainly do so by converting it to PL format
- first. You can convert it back into a TFM file with the
- <b>PLtoTF</b> utility.</p>
-
- <p>See also HPTFM files.</p>
- </dd>
-
- <dt><span class="term">toc</span></dt>
-
- <dd>
- <p>Table of contents files are produced by the
- \tableofcontents command in LaTeX. After seeing
- \tableofcontents, LaTeX writes chapter, section,
- subsection, etc., names to the TOC file. The next time
- the document is formatted, LaTeX will insert the TOC
- file at the point where you issue the \tableofcontents
- command.</p>
- </dd>
-
- <dt><span class="term">txt</span></dt>
-
- <dd>
- <p>Generic ASCII text.</p>
- </dd>
-
- <dt><span class="term">vf</span></dt>
-
- <dd>
- <p>Virtual font files. They are described in more
- detail in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.
- In short, a virtual font maps a character to an
- arbitrary sequence of <tt>DVI</tt> file commands. This
- may be another character in a different font, a
- different character in the same font, or something else
- entirely.</p>
- </dd>
-
- <dt><span class="term">vpl</span></dt>
-
- <dd>
- <p>The virtual property list is a property list file
- for virtual fonts (as opposed to being some sort of
- property list file that was itself virtual ;-). VPL
- files serve the same purpose for VF files that PL files
- serve for TFM files. The VPL format is defined in the
- \web documentation for <b>VPtoVF</b>.</p>
- </dd>
-
- <dt><span class="term">xbm</span></dt>
-
- <dd>
- <p>X11 bitmap files contain a bitmapped image. X11
- icons are frequently stored in XBM files. They also
- occur in <tt>.icon</tt> files and files without
- extensions (e.g., in
- <tt>/usr/include/X11/bitmaps</tt>). I mention them here
- only because I like to use icons on my X11 desktop, and
- I have used <b>PKtoBM</b> to create several nice ones
- from TeX PK files.</p>
-
- <p>X11 bitmap files are used for all bitmap displays in
- the X11 server (not just icons). Because they are ASCII
- and not binary, they are architecture independent,
- which makes them very portable.\par</p>
- </dd>
- </dl>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2942243" name="ftn.id2942243"
- href="#id2942243">129</a>]</sup> {The <b>PBMplus</b>
- utilities are a collection of programs that allow
- conversion between different graphic formats by using the
- PBM format as a transition step.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2942471" name="ftn.id2942471"
- href="#id2942471">130</a>]</sup> {Linear versus
- non-linear scaling is a typographic issue better
- discussed elsewhere. I mention it here just for
- completeness.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2942788" name="ftn.id2942788"
- href="#id2942788">131</a>]</sup> {The proof is left as an
- exercise to the reader (I always wanted to say
- that).}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2943178" name="ftn.id2943178"
- href="#id2943178">132</a>]</sup> You already knew this,
- didn't you?</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;16.&#160;TeX Utilities"
- href="ch16.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Appendix&#160;B.&#160;Font Samples"
- href="apb.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Chapter&#160;16.&#160;TeX
- Utilities&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Appendix&#160;B.&#160;Font Samples</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/apb.html b/Master/texmf-doc/doc/english/make-tex-work/html/apb.html
deleted file mode 100644
index 87dccbe0fb9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/apb.html
+++ /dev/null
@@ -1,2557 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Appendix&#160;B.&#160;Font Samples</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="apa.html"
- title="Appendix&#160;A.&#160;Filename Extension Summary" />
- <link rel="next" href="apc.html"
- title="Appendix&#160;C.&#160;Resources" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Appendix&#160;A.&#160;Filename Extension Summary"
- href="apa.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Appendix&#160;C.&#160;Resources"
- href="apc.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="appendix">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="app.fonts"
- name="app.fonts"></a>Appendix&#160;B.&#160;Font
- Samples</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- </div>
-
- <p>This appendix showcases a number of MetaFont fonts. First,
- several examples of encoding vectors are presented and then
- samples of many fonts from the CTAN archives are
- provided.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2941555"
- name="id2941555"></a>Font Encodings</h2>
- </div>
- </div>
-
- <p>Font encoding vectors are described in Chapter&#160;<a
- href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.
- Table&#160;<a href="apb.html#tab.cmrencode"
- title="Table&#160;B.1.&#160;The Computer Modern Roman Font Encoding">
- Table&#160;B.1</a> shows the Computer Modern Text encoding,
- Table&#160;<a href="apb.html#tab.cmmiencode"
- title="Table&#160;B.2.&#160;The Computer Modern Math Italic Font Encoding">
- Table&#160;B.2</a> shows the Computer Modern Math Italic
- encoding, Table&#160;<a
- href="apb.html#tab.font.corkencoding"
- title="Table&#160;B.3.&#160;The Cork Font Encoding">Table&#160;B.3</a>
- shows the Cork encoding, and Table&#160;<a
- href="apb.html#tab.adbstdencode"
- title="Table&#160;B.4.&#160;The Adobe Standard Font Encoding">
- Table&#160;B.4</a> shows the Adobe Standard encoding.</p>
-
- <p>\font\dcr=cmr12 \typeout{Setting CMR Encoding table}</p>
-
- <div class="table">
- <a id="tab.cmrencode" name="tab.cmrencode"></a>
-
- <p class="title"><b>Table&#160;B.1.&#160;The Computer
- Modern Roman Font Encoding</b></p>
-
- <table summary="The Computer Modern Roman Font Encoding"
- border="1">
- <colgroup>
- <col align="right" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="right">\colcount=0</th>
-
- <th align="center">\bf 0</th>
-
- <th align="center">\bf 1</th>
-
- <th align="center">\bf 2</th>
-
- <th align="center">\bf 3</th>
-
- <th align="center">\bf 4</th>
-
- <th align="center">\bf 5</th>
-
- <th align="center">\bf 6</th>
-
- <th align="center">\bf 7\strut</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="right">\colnum{0}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{1}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{2}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{3}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{4}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{5}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{6}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{7}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">&#160;</td>
-
- <td align="center">\bf 8</td>
-
- <td align="center">\bf 9</td>
-
- <td align="center">\bf A</td>
-
- <td align="center">\bf B</td>
-
- <td align="center">\bf C</td>
-
- <td align="center">\bf D</td>
-
- <td align="center">\bf E</td>
-
- <td align="center">\bf F\strut</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>\font\dcr=cmmi12 \typeout{Setting CMIT Encoding
- table}</p>
-
- <div class="table">
- <a id="tab.cmmiencode" name="tab.cmmiencode"></a>
-
- <p class="title"><b>Table&#160;B.2.&#160;The Computer
- Modern Math Italic Font Encoding</b></p>
-
- <table
- summary="The Computer Modern Math Italic Font Encoding"
- border="1">
- <colgroup>
- <col align="right" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="right">\colcount=0</th>
-
- <th align="center">\bf 0</th>
-
- <th align="center">\bf 1</th>
-
- <th align="center">\bf 2</th>
-
- <th align="center">\bf 3</th>
-
- <th align="center">\bf 4</th>
-
- <th align="center">\bf 5</th>
-
- <th align="center">\bf 6</th>
-
- <th align="center">\bf 7\strut</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="right">\colnum{0}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{1}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{2}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{3}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{4}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{5}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{6}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{7}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">&#160;</td>
-
- <td align="center">\bf 8</td>
-
- <td align="center">\bf 9</td>
-
- <td align="center">\bf A</td>
-
- <td align="center">\bf B</td>
-
- <td align="center">\bf C</td>
-
- <td align="center">\bf D</td>
-
- <td align="center">\bf E</td>
-
- <td align="center">\bf F\strut</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>\typeout{Setting Cork Encoding table}</p>
-
- <div class="table">
- <a id="tab.font.corkencoding"
- name="tab.font.corkencoding"></a>
-
- <p class="title"><b>Table&#160;B.3.&#160;The Cork Font
- Encoding</b></p>
-
- <table summary="The Cork Font Encoding" border="1">
- <colgroup>
- <col align="right" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="right">&#160;</th>
-
- <th align="center">\bf 0</th>
-
- <th align="center">\bf 1</th>
-
- <th align="center">\bf 2</th>
-
- <th align="center">\bf 3</th>
-
- <th align="center">\bf 4</th>
-
- <th align="center">\bf 5</th>
-
- <th align="center">\bf 6</th>
-
- <th align="center">\bf 7\strut</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="right">&#160;</td>
-
- <td align="center">\bf 8</td>
-
- <td align="center">\bf 9</td>
-
- <td align="center">\bf A</td>
-
- <td align="center">\bf B</td>
-
- <td align="center">\bf C</td>
-
- <td align="center">\bf D</td>
-
- <td align="center">\bf E</td>
-
- <td align="center">\bf F\strut</td>
- </tr>
-
- <tr>
- <td align="right">\endfoot \colnum{0}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{1}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{2}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{3}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{4}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{5}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{6}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{7}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{8}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{A}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{B}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{C}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{D}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{E}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{F}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>\font\dcr=grlg at 12pt \typeout{Setting Adobe Standard
- Encoding table}</p>
-
- <div class="table">
- <a id="tab.adbstdencode" name="tab.adbstdencode"></a>
-
- <p class="title"><b>Table&#160;B.4.&#160;The Adobe
- Standard Font Encoding</b></p>
-
- <table summary="The Adobe Standard Font Encoding"
- border="1">
- <colgroup>
- <col align="right" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- <col align="center" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="right">&#160;</th>
-
- <th align="center">\bf 0</th>
-
- <th align="center">\bf 1</th>
-
- <th align="center">\bf 2</th>
-
- <th align="center">\bf 3</th>
-
- <th align="center">\bf 4</th>
-
- <th align="center">\bf 5</th>
-
- <th align="center">\bf 6</th>
-
- <th align="center">\bf 7\strut</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="right">&#160;</td>
-
- <td align="center">\bf 8</td>
-
- <td align="center">\bf 9</td>
-
- <td align="center">\bf A</td>
-
- <td align="center">\bf B</td>
-
- <td align="center">\bf C</td>
-
- <td align="center">\bf D</td>
-
- <td align="center">\bf E</td>
-
- <td align="center">\bf F\strut</td>
- </tr>
-
- <tr>
- <td align="right">\endfoot \colnum{0}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{1}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{2}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{3}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{4}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{5}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{6}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{7}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{8}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{A}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{B}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{C}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{D}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{E}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\colnum{F}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="right">\cline{2-9}</td>
-
- <td align="center">\row</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2945478"
- name="id2945478"></a>Font Samples</h2>
- </div>
- </div>
-
- <p>MetaFont, like TeX, has been widely ported and many
- people have developed fonts using it. The remainder of this
- appendix shows examples of many of the fonts available in
- the CTAN archives in February, 1994.</p>
-
- <p>\fontdir{fonts/ams/amsfonts/cyrillic}
- \fontsample{wncyb10} \fontsample{wncyi10}
- \fontsample{wncyr10} \fontsample{wncysc10}
- \fontsample{wncyss10}</p>
-
- <p>\fontdir{fonts/ams/amsfonts/euler} \fontsample{euex10}
- \fontsample{eufb10} \fontsample{eufm10} \fontsample{eurb10}
- \fontsample{eurm10} \fontsample{eusb10}
- \fontsample{eusm10}</p>
-
- <p>\fontdir{fonts/ams/amsfonts/extracm} \fontsample{cmbsy9}
- \fontsample{cmcsc9} \fontsample{cmex9}
- \fontsample{cmmib9}</p>
-
- <p>\fontdir{fonts/ams/amsfonts/symbols} \fontsample{msam10}
- \fontsample[-52pt]{msbm10}</p>
-
- <p>\fontdir{fonts/apl} \fontsample{cmapl10}</p>
-
- <p>\fontdir{fonts/astro} \fontsample{astrosym}</p>
-
- <p>\fontdir{fonts/bard} \fontsample{bard}</p>
-
- <p>\fontdir{fonts/bashkirian} \fontsample{jkbash10}
- \fontsample{jkcyr10}</p>
-
- <p>\fontdir{fonts/bbding} \fontsample{bbding10}</p>
-
- <p>\fontdir{fonts/bbold} \fontsample{bbold10}
- \fontsample{cspex10}</p>
-
- <p>\fontdir{fonts/blackletter} \fontsample{blackletter}</p>
-
- <p>\fontdir{fonts/calligra} \fontsample{callig15}</p>
-
- <p>\fontdir{fonts/chess} \fontsample{chess10}
- \fontsample{chessf10}</p>
-
- <p>\fontdir{fonts/cirth} \fontsample{cirbf}
- \fontsample{cirsl} \fontsample{cirss}
- \fontsample{cirth}</p>
-
- <p>\fontdir{fonts/cm} \fontsample{cmb10}
- \fontsample{cmbsy10} \fontsample{cmbx10}
- \fontsample{cmbxsl10} \fontsample{cmbxti10}
- \fontsample{cmcsc10} \fontsample{cmdunh10}
- \fontsample{cmex10} \fontsample{cmff10} \fontsample{cmfi10}
- \fontsample{cmfib8} \fontsample{cmitt10}
- \fontsample{cmmi10} \fontsample{cmmib10} \fontsample{cmr10}
- \fontsample{cmsl10} \fontsample{cmsltt10}
- \fontsample{cmss10} \fontsample{cmssbx10}
- \fontsample{cmssdc10} \fontsample{cmssi10}
- \fontsample{cmssq8} \fontsample{cmssqi8}
- \fontsample{cmsy10} \fontsample{cmtcsc10}
- \fontsample{cmtex10} \fontsample{cmti10}
- \fontsample{cmtt10} \fontsample{cmu10}
- \fontsample{cmvtt10}</p>
-
- <p>\fontdir{fonts/cm/utility} \fontsample{grdov5}
- \fontsample{logo10} \fontsample{logo10}
- \fontsample{logobf10} \fontsample{logobf10}
- \fontsample{logosl10} \fontsample{logosl10}
- \fontsample{slaps4} \fontsample{sldov6}</p>
-
- <p>\fontdir{fonts/cmastro} \fontsample{cmastro10}</p>
-
- <p>\fontdir{fonts/cmcyr} \fontsample{cmcbx10}
- \fontsample{cmcbxsl10} \fontsample{cmcbxti10}
- \fontsample{cmcitt10} \fontsample{cmcsl10}
- \fontsample{cmcss10} \fontsample{cmcssdc10}
- \fontsample{cmcti10} \fontsample{cmctt10}
- \fontsample{cmcyr10}</p>
-
- <p>\fontdir{fonts/cmoefont} \fontsample{cmoebx10}
- \fontsample{cmoer10} \fontsample{cmoesc10}
- \fontsample{cmoesl10} \fontsample{cmoeti10}
- \fontsample{cmoett10}</p>
-
- <p>\fontdir{fonts/cmpica} \fontsample{cmpicab}
- \fontsample{cmpicati} \fontsample{cmpica}</p>
-
- <p>\fontdir{fonts/concrete} \fontsample{cccsc10}
- \fontsample{ccmi10} \fontsample{ccr10} \fontsample{ccsl10}
- \fontsample{ccslc9} \fontsample{ccti10}</p>
-
- <p>\fontdir{fonts/duerer} \fontsample{cdb10}
- \fontsample{cdi10} \fontsample{cdr10} \fontsample{cdsl10}
- \fontsample{cdss10} \fontsample{cdtt10}</p>
-
- <p>\fontdir{fonts/eiad} \fontsample{eiad10}
- \fontsample{eiadbf10}</p>
-
- <p>\fontdir{fonts/elvish} \fontsample{teng10}</p>
-
- <p>\fontdir{fonts/engwar} \fontsample{engwar}</p>
-
- <p>\fontdir{fonts/fc} \fontsample{b-fcbx10}
- \fontsample{b-fcbxi10} \fontsample{b-fcbxsl10}
- \fontsample{b-fcbxu10} \fontsample{b-fccsc10}
- \fontsample{b-fci10} \fontsample{b-fcitt10}
- \fontsample{b-fcr10} \fontsample{b-fcsibx10}
- \fontsample{b-fcsitt10} \fontsample{b-fcsl10}
- \fontsample{b-fcss10} \fontsample{b-fcssbx10}
- \fontsample{b-fcssi10} \fontsample{b-fcsstt10}
- \fontsample{b-fctt10} \fontsample{b-fcu10}</p>
-
- <p>\fontdir{fonts/futhark} \fontsample{futhol10}</p>
-
- <p>\fontdir{fonts/georgian} \fontsample{georgian}
- \fontsample{mxed10} \fontsample{mxedbf10}</p>
-
- <p>\fontdir{fonts/go} \fontsample{go10}
- \fontsample{go1bla10} \fontsample{go1whi10}
- \fontsample{go2bla10} \fontsample{go2whi10}</p>
-
- <p>\fontdir{fonts/gothic} \fontsample{yfrak}
- \fontsample{ygoth} \fontsample{yinit}
- \fontsample{yswab}</p>
-
- <p>\fontdir{fonts/greek/kd} \fontsample{kdbf10}
- \fontsample{kdgr10} \fontsample{kdsl10} \fontsample{kdti10}
- \fontsample{kdtt10}</p>
-
- <p>\fontdir{fonts/greek/kelly} \fontsample{cmg10}
- \fontsample{cmgb10} \fontsample{cmgi10}
- \fontsample{cmgtt10}</p>
-
- <p>\fontdir{fonts/greek/moschovakis} \fontsample{gecmbx10}
- \fontsample{gecmml10} \fontsample{gecmr10}
- \fontsample{gecmsc10} \fontsample{gecmsl10}
- \fontsample{gecmss10} \fontsample{gecmti10}
- \fontsample{gecmtt10}</p>
-
- <p>\fontdir{fonts/greek/yannis} \fontsample{mrgrbf10}
- \fontsample{mrgrrg10} \fontsample{mrgrsl10}
- \fontsample{mrgrti10} \fontsample{rgrbf10}
- \fontsample{rgrrg10} \fontsample{rgrsl10}
- \fontsample{rgrti10}</p>
-
- <p>\fontdir{fonts/halftone} \fontsample{halftone}</p>
-
- <p>\fontdir{fonts/hge} \fontsample{hge}</p>
-
- <p>\fontdir{fonts/hieroglyph} \fontsample{diacr10}</p>
-
- <p>\fontdir{fonts/karta} \fontsample{karta15}</p>
-
- <p>\fontdir{fonts/klinz} \fontsample{klinz}</p>
-
- <p>\fontdir{fonts/knot} \fontsample{knot1}
- \fontsample{knot2} \fontsample{knot3} \fontsample{knot4}
- \fontsample{knot5} \fontsample{knot6}
- \fontsample{knot7}</p>
-
- <p>\fontdir{fonts/levy} \fontsample{grbld10}
- \fontsample{grreg10} \fontsample{grtt10}</p>
-
- <p>\fontdir{fonts/malvern} \fontsample{fmvX10}
- \fontsample{fmvb10} \fontsample{fmvi10}
- \fontsample{fmvr10}</p>
-
- <p>\fontdir{fonts/ocr-a} \fontsample{ocr10}</p>
-
- <p>\fontdir{fonts/ocr-b} \fontsample{ocrb10}</p>
-
- <p>\fontdir{fonts/pandora} \fontsample{pnb10}
- \fontsample{pnr10} \fontsample[-8pt]{pnsl10}
- \fontsample{pnss10} \fontsample{pnssb10}
- \fontsample[-8pt]{pnssi10} \fontsample{pntt9}</p>
-
- <p>\fontdir{fonts/phonetic} \fontsample{cmph10}
- \fontsample{cmphb10} \fontsample{cmphi10}</p>
-
- <p>\fontdir{fonts/punk} \fontsample{punk10}
- \fontsample{punkbx20} \fontsample{punksl20}</p>
-
- <p>\fontdir{fonts/redis} \fontsample{redis10}
- \fontsample{redisbx10} \fontsample{rediss10}</p>
-
- <p>\fontdir{fonts/rsfs} \fontsample{rsfs10}</p>
-
- <p>\fontdir{fonts/rune} \fontsample{rune}
- \fontsample{srune}</p>
-
- <p>\fontdir{fonts/srune} \fontsample{srune}</p>
-
- <p>\fontdir{fonts/stmary} \fontsample{stmary10}</p>
-
- <p>\fontdir{fonts/tengwar} \fontsample{tengwar}</p>
-
- <p>\fontdir{fonts/tsipa} \fontsample{tsipa10}</p>
-
- <p>\fontdir{fonts/twcal} \fontsample{twcal14}</p>
-
- <p>\fontdir{fonts/va} \fontsample{va14}
- \fontsample{vacal14}</p>
-
- <p>\fontdir{fonts/wasy} \fontsample{wasy10}</p>
-
- <p>\fontdir{fonts/wasy2} \fontsample{wasy10}
- \fontsample{wasyb10}</p>
-
- <p>\fontdir{fonts/wsuipa} \fontsample{wbxipa10}
- \fontsample{wslipa10} \fontsample{wsuipa10}</p>
-
- <p>\fontdir{macros/latex/distribs/latex/fonts}
- \fontsample{lasy10} \fontsample{lasyb10}
- \fontsample{lcircle10} \fontsample{lcirclew10}
- \fontsample{lcmss8} \fontsample{lcmssb8}
- \fontsample{lcmssi8} \fontsample{line10}
- \fontsample{linew10}</p>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Appendix&#160;A.&#160;Filename Extension Summary"
- href="apa.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Appendix&#160;C.&#160;Resources"
- href="apc.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Appendix&#160;A.&#160;Filename Extension
- Summary&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Appendix&#160;C.&#160;Resources</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/apc.html b/Master/texmf-doc/doc/english/make-tex-work/html/apc.html
deleted file mode 100644
index d43d0de1651..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/apc.html
+++ /dev/null
@@ -1,1168 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Appendix&#160;C.&#160;Resources</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples" />
- <link rel="next" href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Appendix&#160;B.&#160;Font Samples"
- href="apb.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Appendix&#160;D.&#160;Long Examples"
- href="apd.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="appendix">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="app.resources"
- name="app.resources"></a>Appendix&#160;C.&#160;Resources</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- </div>
-
- <p>This appendix lists the resources described in this book.
- Each of the tools (with the exception of tools mentioned only
- in Chapter&#160;<a href="ch16.html"
- title="Chapter&#160;16.&#160;TeX Utilities">Chapter&#160;16</a>,
- <span class="emphasis"><em><a href="ch16.html"
- title="Chapter&#160;16.&#160;TeX Utilities">Chapter&#160;16</a></em></span>,
- which are already listed in a similar format) described in
- the book is presented here. Each entry credits the author and
- provides information about where the software can be
- obtained.</p>
-
- <p>Most of the resources in this appendix are availble from
- the CTAN archives. Where other sites are listed (for example,
- <tt>oak.oakland.edu</tt> for MS-DOS software), the addresses
- are only one possibility. Most of these archives are mirrored
- around the world. When possible, use an FTP site that is
- geographically nearby. If you are connected to the Internet,
- the <tt>archie</tt> service can help you locate nearby
- sites.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2943524"
- name="id2943524"></a>TUG: The TeX Users Group</h2>
- </div>
- </div>
-
- <p>The TeX Users Group <span class="smallcaps">TUG</span>,
- begun in 1980, is the international group for TeX users.
- Their mission is to encourage and expand the use of TeX,
- MetaFont, and related systems; to ensure the integrity and
- portability of these systems; and to foster innovation in
- high-quality electronic document preparation.</p>
-
- <p>Membership includes the quarterly <i>TUGboat</i>, the
- newsletter TTN (also a quarterly), and a membership
- directory; as well, <span class="smallcaps">TUG</span>
- publishes an occasional series called TeXniques, for
- special topics (e.g., PiCTeX, <tt>edmac.sty</tt>).</p>
-
- <p><span class="smallcaps">TUG</span> annual meetings are
- held in various locations, currently in North America and
- Europe, in a regular rotation; proceedings are published in
- <i>TUGboat</i>. Most of the publications now available on
- TeX, MetaFont, and related systems are available from the
- <span class="smallcaps">TUG</span> office, which also
- distributes the main public domain TeX implementations.</p>
-
- <p>In addition to its publications, <span
- class="smallcaps">TUG</span> promotes active development
- work via the Technical Council and its Technical Working
- Groups. \pagebreak Efforts here include the CTAN archive
- work, multilingual TeX, TeX for the disabled, and the
- intersection of TeX with SGML and with Acrobat.</p>
-
- <p>Information about joining <span
- class="smallcaps">TUG</span>, receiving <i>TUGboat</i>, and
- attending the annual meetings is available from:</p>
-
- <p>TeX Users Group \\ P.O. Box 869 \\ Santa Barbara,
- California \\ 93102 USA</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2946099"
- name="id2946099"></a>Other User Groups</h3>
- </div>
- </div>
-
- <p>There are also many other user groups, often based on
- language or geography: German-speaking users ({\sc
- DANTE}), French-speaking users ({\sc
- GUT}enberg\hskip.25pt), Dutch-speaking users ({\sc NTG}),
- users in the Nordic countries (the Nordic group), users
- in the UK ({\sc UK} TeX Users Group). There are active
- groups in existence in Japan, in Russia (Cyr<span
- class="smallcaps">TUG</span>), in Estonia, in Poland
- ({\sc GUST}), and in the Czech Republic (Cs<span
- class="smallcaps">TUG</span>), to name but a few.</p>
-
- <p>Contact <span class="smallcaps">TUG</span> for details
- on how to get in touch with these or other TeX user
- groups.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2946152"
- name="id2946152"></a>TeX Software</h2>
- </div>
- </div>
-
- <p>\package{\cmactex} \author{Thomas R. Kiffe}
- \ftp{CTAN:systems/mac/cmactex} \print</p>
-
- <p>\package{\directex} \author{Wilfried Ricken}
- \ftp{CTAN:systems/mac/directtex} \print</p>
-
- <p>\package{\emTeX} <a id="ap03.emtex"
- name="ap03.emtex"></a> \author{Eberhard Mattes}
- \ftp{CTAN:systems/msdos/emtex} \print</p>
-
- <p>\package{\gTeX} \author{Young U. Ryu}
- \ftp{CTAN:systems/msdos/gtex} \print</p>
-
- <p>\package{\oztex} <a id="ap03.oztex"
- name="ap03.oztex"></a> \author{Andrew Trevorrow}
- \files{$\Sigma$Edit} \ftp{CTAN:systems/mac/oztex}</p>
-
- <p>\package{\PCTeX} <a id="ap03.pctex"
- name="ap03.pctex"></a> \author{Personal \TeX, Inc.}
- \address{12 Madrona Avenue\\Mill Valley, CA 94941\\USA}
- \phone{(415) 388--8853 / (413) 388--8865 FAX} \print</p>
-
- <p>\package{\sbTeX} <a id="ap03.sbtex"
- name="ap03.sbtex"></a> \author{Wayne G. Sullivan}
- \ftp{CTAN:systems/msdos/sbtex} \print</p>
-
- <p>\package{\TeX} <a id="ap03.tex" name="ap03.tex"></a>
- \author{Donald Knuth} \ftp{CTAN:systems/web2c} \comment{The
- \Web sources and the \Web2C programs are both available
- here.} \print</p>
-
- <p>\package{texas} \author{Shih-Ping Chan}
- \ftp{CTAN:systems/msdos/texas} \print</p>
-
- <p>\package{Textures} <a id="ap03.textures"
- name="ap03.textures"></a> \author{Blue Sky Research}
- \address{534 SW Third Avenue\\Portland, OR 97204\\USA}
- \phone{(800) 622--8398 or (503) 222--9571 / (503) 222--1643
- FAX} \files{dvitool} \print</p>
-
- <p>\package{\TurboTeX} <a id="ap03.turbotex"
- name="ap03.turbotex"></a> \author{Kinch Computer Company}
- \address{501 Meadow Street\\Ithaca, NY 14850\\USA}
- \phone{(607) 273--0222 / (607) 273--0484 FAX} \print</p>
-
- <p>\package{\utex} <a id="ap03.utex" name="ap03.utex"></a>
- \author{ArborText} \address{1000 Victors Way\\Ann Arbor, MI
- 48108\\USA} \phone{(313) 996--3566 / (313) 996--3573 FAX}
- \print</p>
-
- <p>\package{\yyTeX} \author{\YY, Inc.} \address{106 Indian
- Hill\\Carlisle, MA 01741\\USA} \phone{(508) 371--3286 /
- (508) 371--2004 FAX} <a id="ap03.yytex"
- name="ap03.yytex"></a> \print</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2946301"
- name="id2946301"></a>TeX Shells</h2>
- </div>
- </div>
-
- <p>\vskip2pt</p>
-
- <p>\package{\fourTeX} \author{Wietse Dol, Erik Frambach,
- Arjen Merckens, and Maarten van der Vlerk}
- \ftp{CTAN:systems/msdos/4tex} \print</p>
-
- <p>\package{\PMTeX} \author{Guillaume Schiltz}
- \ftp{CTAN:systems/os2/pmtex} \print</p>
-
- <p>\package{\TeXPert} \author{Johannes Martin}
- \ftp{CTAN:systems/msdos/texpert} \print</p>
-
- <p>\package{\TeXShell} \author{J\"urgen Schlegelmilch}
- \ftp{CTAN:systems/msdos/texshell} \print</p>
-
- <p>\package{X\TeX{}Shell} \author{Michael Hofmann}
- \ftp{tsx-11.mit.edu:pub/linux/packages/TeX} \print</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2946342"
- name="id2946342"></a>Editors</h2>
- </div>
- </div>
-
- <p>\vskip2pt</p>
-
- <p>\package{$\Sigma$Edit} \xref{\oztex}{ap03:oztex}
- \print</p>
-
- <p>\package{Alpha} \author{Pete Keheler}
- \ftp{CTAN:systems/mac} \print</p>
-
- <p>\package{BBEdit} \author{Rich Siegel}
- \ftp{mac.archive.umich.edu:/mac/util/text} \print</p>
-
- <p>\package{Brief} \author{Borland International, Inc.}
- \address{1800 Green Hills Road\\P.O. Box 660001\\Scotts
- Valley, CA 95067--0001} \phone{(408) 438--8400} \print</p>
-
- <p>\package{demacs} \author{Manabu Higashida and Hirano
- Satoshi} \ftp{oak.oakland.edu:/pub/msdos/demacs} \print</p>
-
- <p>\package{Doc} \xref{idraw}{ap03:idraw} \print</p>
-
- <p>\package{emacs} \xref{GNU emacs}{ap03:emacs} \print</p>
-
- <p>\package{epm} \author{International Business Machines}
- \ftp{ftp.cdrom.com:/pub/os2/ibm/epm} \print</p>
-
- <p>\package{GNU emacs} <a id="ap03.emacs"
- name="ap03.emacs"></a> \author{Free Software Foundation}
- \address{675 Massachusetts Avenue\\Cambridge, MA
- 02139\\USA} \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{Jove} \author{Jonathan Payne}
- \ftp{oak.oakland.edu:/pub/msdos/editor} \print</p>
-
- <p>\package{MathPad} \author{Roland Backhouse, Richard
- Verhoeven, and Olaf Weber} \ftp{CTAN:support/mathpad}
- \print</p>
-
- <p>\package{MEwin} <a id="ap03.mewin"
- name="ap03.mewin"></a> \author{Pierre Perret}
- \ftp{oak.oakland.edu:/pub/msdos/windows3} \print</p>
-
- <p>\package{MicroEMACS} \xref{MEwin}{ap03:mewin} \print</p>
-
- <p>\package{Multi-Edit} \author{American Cybernetics}
- \address{1830 West University Drive, Suite 112\\Tempe, AZ
- 85821} \phone{(602) 968--1945 / (602) 966--1654 FAX}
- \print</p>
-
- <p>\package{Scientific Word} \author{TCI Software Research}
- \address{1190 Foster Road\\Las Cruces, NM 88001\\USA}
- \phone{(505) 522--4600 / (505) 522--0116} \print</p>
-
- <p>\package{Xnot} \author{Julie Melbin}
- \ftp{oak.oakland.edu:/pub/msdos/editor} \print</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2946460"
- name="id2946460"></a>Macro Packages (Formats)</h2>
- </div>
- </div>
-
- <p>\vskip2pt</p>
-
- <p>\package{\AMSTeX} \author{\ams}
- \ftp{CTAN:fonts/ams/amstex} \print</p>
-
- <p>\package{Eplain} \xref{Extended Plain \TeX}{ap03:eplain}
- \print</p>
-
- <p>\package{Extended Plain \TeX} <a id="ap03.eplain"
- name="ap03.eplain"></a> \author{Karl Berry}
- \ftp{CTAN:macros/eplain} \print</p>
-
- <p>\package{Lame\TeX} \author{Jonathan Monsarrat}
- \ftp{CTAN:misc/lametex} \print</p>
-
- <p>\package{\LamSTeX} \author{Michael Spivak}
- \ftp{CTAN:macros/lamstex} \print</p>
-
- <p>\package{\LaTeX} \author{Leslie Lamport}
- \ftp{CTAN:macros/latex/core} \print</p>
-
- <p>\package{\LaTeXe} \author{Leslie Lamport, et. al.}
- \ftp{CTAN:macros/latex2e/core} \print</p>
-
- <p>\package{Lollipop} \author{Victor Eijkhout}
- \ftp{CTAN:macros/lollipop} \print</p>
-
- <p>\package{\MusicTeX} \author{Daniel Taupin}
- \ftp{CTAN:macros/musictex} \print</p>
-
- <p>\package{Plain \TeX} \author{Donald Knuth}
- \ftp{CTAN:macros/plain/base} \print</p>
-
- <p>\package{\SliTeX} \author{Leslie Lamport}
- \ftp{CTAN:macros/latex/core} \print</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2946539"
- name="id2946539"></a>Styles and Macros</h2>
- </div>
- </div>
-
- <p>\vskip2pt</p>
-
- <p>\package{\AMSLaTeX} \author{\ams}
- \ftp{CTAN:fonts/ams/amslatex} \print</p>
-
- <p>\package{\arabTeX} \author{Klaus Lagally}
- \ftp{CTAN:language/arabtex} \print</p>
-
- <p>\package{ascii.sty} \author{R. W. D. Nickalls}
- \ftp{CTAN:fonts/ascii} \print</p>
-
- <p>\package{Babel} \author{J. L. Braams}
- \ftp{language/babel} \print</p>
-
- <p>\package{bibunits.sty} \author{Jose Alberto}
- \ftp{CTAN:macros/latex/contrib/misc} \print</p>
-
- <p>\package{chapterbib} \author{Niel Kempson and Donald
- Arseneau} \ftp{CTAN:macros/latex/contrib/misc} \print</p>
-
- <p>\package{Chem\TeX} \author{Roswitha T. Haas and Kevin C.
- O'Kane} \ftp{CTAN:macros/latex/contrib/chemtex} \print</p>
-
- <p>\package{ChemStruct} \author{Michael Ramek}
- \ftp{CTAN:macros/latex/contrib/chemstruct} \print</p>
-
- <p>\package{\DraTeX} \author{Eitan M. Gurari}
- \ftp{CTAN:macros/generic/dratex} \print</p>
-
- <p>\package{EDMAC} \author{John Lavagnino}
- \ftp{CTAN:macros/plain/contrib/edmac} \print</p>
-
- <p>\package{eepic.sty} \author{Conrad Kwok}
- \ftp{CTAN:macros/latex/contrib/eepic} \print</p>
-
- <p>\package{epic.sty} \author{Sunil Podar}
- \ftp{CTAN:macros/latex/contrib/epic} \print</p>
-
- <p>\package{epsf.tex} \xref{dvips}{ap03:dvips} \print</p>
-
- <p>\package{epsfig.sty} \author{Sebastian Rahtz, Tom
- Rokicki, Trevor Darrell, et. al.}
- \ftp{CTAN:macros/latex/contrib/epsfig} \print</p>
-
- <p>\package{\FoilTeX} \author{James Hafner}
- \ftp{CTAN:macros/foiltex} \print</p>
-
- <p>\package{idxmac.tex} \ftp{CTAN:indexing/makeindex/lib}
- \print</p>
-
- <p>\package{index.sty} \author{David Jones}
- \ftp{CTAN:macros/latex/contrib/misc}</p>
-
- <p>\package{\INRSTeX} \author{Michael J. Ferguson}
- \ftp{CTAN:macros/inrstex} \print</p>
-
- <p>\package{isolatin1.sty}
- \ftp{CTAN:macros/latex/contrib/misc} \print</p>
-
- <p>\package{Midnight} \author{Marcel van der Goot}
- \ftp{CTAN:macros/generic/midnight} \print</p>
-
- <p>\package{multind} \author{F. W. Long}
- \ftp{CTAN:macros/latex/contrib/misc} \print</p>
-
- <p>\package{\PiCTeX} \author{Michael Wichura}
- \ftp{CTAN:graphics/pictex} \print</p>
-
- <p>\package{\REVTeX} \author{American Physical Society,
- American Institute of Physics, and Optical Society of
- America} \ftp{CTAN:macros/latex/contrib/revtex} \print</p>
-
- <p>\package{\ScriptTeX} \author{Adrian McCarthy}
- \ftp{CTAN:macros/scripttex} \print</p>
-
- <p>\package{Seminar} \author{Timothy Van Zandt}
- \ftp{CTAN:macros/latex/contrib/seminar} \print</p>
-
- <p>\package{\TeX/Mathematica} \author{Dan Dill}
- \ftp{CTAN:macros/mathematica} \print</p>
-
- <p>\package{\TeX{}sis} \author{Eric Myers and Frank E.
- Paige} \ftp{CTAN:macros/texsis} \print</p>
-
- <p>\package{Ver\TeX} \author{Hal Varian}
- \ftp{CTAN:macros/plain/contrib} \print</p>
-
- <p>\package{\XYPic} \author{Kristoffer H. Rose}
- \ftp{ftp.diku.dk:/diku/users/kris} \print</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2946714"
- name="id2946714"></a>Styles That Produced This
- Book</h3>
- </div>
- </div>
-
- <p>This book was formatted with an extensively modified
- version of the standard LaTeX book style. In addition to
- the <tt>pstricks</tt>, <tt>index.sty</tt>,
- <tt>epsfig.sty</tt>, <tt>epic.sty</tt>, and
- <tt>eepic.sty</tt> files described above, the following
- styles were used to format this book: \vskip6pt</p>
-
- <p>\package{pageframe.sty} \author{Cameron Smith}
- \ftp{CTAN:macros/latex/contrib/pageframe} \print</p>
-
- <p>\package{footnpag.sty} \author{Joachim Schrod}
- \ftp{CTAN:macros/latex/contrib/footnpag} \print</p>
-
- <p>\package{fancybox.sty} \author{Timothy Van Zandt}
- \ftp{CTAN:macros/latex/contrib/misc} \print</p>
-
- <p>\package{fancyheadings.sty} \author{Piet van Oostrum}
- \ftp{CTAN:macros/latex/contrib/fancyheadings} \print</p>
-
- <p>\package{array.sty} \author{Frank Mittelbach and David
- Carlisle} \ftp{CTAN:macros/latex/distribs/array}
- \print</p>
-
- <p>\package{dcolumn.sty} \author{David Carlisle}
- \ftp{CTAN:macros/latex/distribs/array} \print</p>
-
- <p>\package{tabularx.sty} \author{David Carlisle}
- \ftp{CTAN:macros/latex/distribs/array} \print</p>
-
- <p>\package{longtable.sty} \author{David Carlisle}
- \ftp{CTAN:macros/latex/distribs/array} \print</p>
-
- <p>\package{verbatim.sty} \author{Rainer Sch\"opf}
- \ftp{CTAN:macros/latex/distribs/verbatim} \print</p>
-
- <p>\package{vrbinput.sty} \author{Bernd Raichle}
- \ftp{CTAN:macros/latex/distribs/verbatim} \print</p>
-
- <p>\package{path.sty} \author{Philip Taylor}
- \ftp{CTAN:macros/latex/contrib/misc} \print</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2946829"
- name="id2946829"></a>Utilities</h2>
- </div>
- </div>
-
- <p>\vskip2pt</p>
-
- <p>\package{afm2tfm} \xref{dvips}{ap03:dvips} \print</p>
-
- <p>\package{amSpell} \author{Erik Frambach}
- \address{Faculty of Econometrics\\University of
- Groningen\\Netherlands} \ftp{CTAN:support/amspel}
- \print</p>
-
- <p>\package{animate} \xref{Image Magick}{ap03:imagemagick}
- \print</p>
-
- <p>\package{\auctex} \author{Kresten Krab Thorup and Per
- Abrahamsen} \ftp{CTAN:support/auctex} \print</p>
-
- <p>\package{awk} \author{Free Software Foundation}
- \address{675 Massachusetts Avenue\\Cambridge, MA
- 02139\\USA} \comment{The FSF's version of \program{awk} is
- called \program{gawk}. Many commercial implementations of
- \program{awk} are also available.}
- \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{bbfig} \author{Ned Betchelder}
- \ftp{CTAN:dviware/dvips/dvips/contrib/bbfig} \print</p>
-
- <p>\package{bibclean} \author{Nelson H. F. Beebe}
- \ftp{CTAN:bibtex/utils/bibclean} \print</p>
-
- <p>\package{bibdb} \author{Eyal Doron}
- \ftp{CTAN:support/bibdb} \print</p>
-
- <p>\package{bibdestringify}
- \xref{lookbibtex}{ap03:lookbibtex} \print</p>
-
- <p>\package{bibextract} <a id="ap03.bibextract"
- name="ap03.bibextract"></a> \author{Nelson H. F. Beebe}
- \ftp{CTAN:biblio/bibtex/utils/bibextract} \print</p>
-
- <p>\package{bibindex} <a id="ap03.bibindex"
- name="ap03.bibindex"></a> \author{Nelson H. F. Beebe}
- \ftp{CTAN:biblio/bibtex/utils/bibindex} \print</p>
-
- <p>\package{biblook} \xref{bibindex}{ap03:bibindex}
- \print</p>
-
- <p>\package{bibsort} \author{Nelson H. F. Beebe}
- \ftp{CTAN:biblio/bibtex/utils/bibsort} \print</p>
-
- <p>\package{\BibTeX} <a id="ap03.bibtex"
- name="ap03.bibtex"></a> \author{Oren Patashnik}
- \ftp{CTAN:biblio/bibtex} \print</p>
-
- <p>\package{bibview} \author{Holger Martin, Peter Urban,
- and Armin Liebl} \comment{Available from volume 18 of the
- \texttt{comp.sources.x} newsgroup.} \print</p>
-
- <p>\package{Bitmap} \author{Davor Matic}
- \ftp{ftp.x.org:/contrib} \print</p>
-
- <p>\package{Bm2font} \author{Friedhelm Sowa}
- \ftp{CTAN:graphics/bm2font} \print</p>
-
- <p>\package{citefind} \xref{bibextract}{ap03:bibextract}
- \print</p>
-
- <p>\package{citetags} \xref{bibextract}{ap03:bibextract}
- \print</p>
-
- <p>\package{combine} \xref{Image Magick}{ap03:imagemagick}
- \print</p>
-
- <p>\package{convert} \xref{Image Magick}{ap03:imagemagick}
- \print</p>
-
- <p>\package{crudetype} \author{R. M. Damerell}
- \ftp{CTAN:dviware/crudetype} \print</p>
-
- <p>\package{detex} \author{Daniel Trinkle}
- \ftp{CTAN:support/detex} \print</p>
-
- <p>\package{display} \xref{Image Magick}{ap03:imagemagick}
- \print</p>
-
- <p>\package{dvgt} \author{Geoffrey Tobin}
- \ftp{CTAN:dviware/dvgt} \print</p>
-
- <p>\package{dvi2tty} \author{Marcel J. E. Mol}
- \ftp{CTAN:dviware/dvi2tty} \print</p>
-
- <p>\package{dvi2xx} <a id="ap03.dvi2xx"
- name="ap03.dvi2xx"></a> \author{Gustaf Neumann}
- \ftp{CTAN:dviware/dvi2xx} \print</p>
-
- <p>\package{dvicopy} <a id="ap03.dvicopy"
- name="ap03.dvicopy"></a> \author{Peter Breitenlohner}
- \ftp{CTAN:dviware/dvicopy} \print</p>
-
- <p>\package{dvideo} \xref{\TurboTeX}{ap03:turbotex}
- \print</p>
-
- <p>\package{dvidot} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{dvidrv} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{dvidvi} \author{Tom Rokicki}
- \ftp{CTAN:dviware/dvidvi} \print</p>
-
- <p>\package{dvidxx} \comment{See
- Example&#160;\ref{ex:dvidxx} in
- Chapter&#160;\ref{app:examples},
- \textit{\nameref{app:examples}}.} \print</p>
-
- <p>\package{dvihplj} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{DVILASER/HP} \xref{\utex}{ap03:utex} \print</p>
-
- <p>\package{DVILASER/PS} \xref{\utex}{ap03:utex} \print</p>
-
- <p>\package{\dvilaserhp} \xref{\utex}{ap03:utex} \print</p>
-
- <p>\package{\dvilaserps} \xref{\utex}{ap03:utex} \print</p>
-
- <p>\package{dvilj2} \xref{dvi2xx}{ap03:dvi2xx} \print</p>
-
- <p>\package{dvimsp} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{dvimswin} \author{J. D. McDonald}
- \ftp{CTAN:dviware/dvimswin} \print</p>
-
- <p>\package{dvipaste} \author{Michael Spivak}
- \ftp{CTAN:macros/lamstex/dvipaste} \print</p>
-
- <p>\package{dvipcx} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{dvipm} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{dvips} <a id="ap03.dvips"
- name="ap03.dvips"></a> \author{Tomas Rokicki}
- \ftp{CTAN:dviware/dvips} \print</p>
-
- <p>\package{dvipsk} \author{Karl Berry}
- \ftp{CTAN:dviware/dvipsk} \comment{\program{dvips} enhanced
- to support path searching for fonts.} \print</p>
-
- <p>\package{dvipsone} \xref{\yyTeX}{ap03:yytex} \print</p>
-
- <p>\package{dviscr} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{dvispell} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{DVITool} \author{Jeff W. McCarrell}
- \ftp{CTAN:support/vortex/dvitool} \comment{Unrelated to the
- \program{Textures} tool of the same name.} \print</p>
-
- <p>\package{dvitovdu} \author{Andrew Trevorrow}
- \ftp{CTAN:dviware/dvitovdu} \print</p>
-
- <p>\package{dvitype} \xref{\texware}{ap03:texware}
- \print</p>
-
- <p>\package{dvivga} \ftp{CTAN:dviware/dvivga} \print</p>
-
- <p>\package{dviwin} <a id="ap03.dviwin"
- name="ap03.dviwin"></a> \author{Hippocrates Sendoukas}
- \ftp{CTAN:dviware/dviwin} \print</p>
-
- <p>\package{DVIWindo} \xref{\yyTeX}{ap03:yytex} \print</p>
-
- <p>\package{enc-afm.pl} \comment{See
- Example&#160;\ref{ex:encafmpl} in
- Chapter&#160;\ref{app:examples},
- \textit{\nameref{app:examples}}.} \print</p>
-
- <p>\package{epmtex} \author{Jon Hacker}
- \ftp{CTAN:systems/os2/epmtex} \print</p>
-
- <p>\package{epsfig} \author{Peter Whaite}
- \ftp{CTAN:macros/latex/contrib/epsfig}</p>
-
- <p>\package{Excalibur} \author{Rick Zaccone}
- \ftp{CTAN:systems/mac/excalibur} \print</p>
-
- <p>\package{Fig} \author{Supoj Sutanthavibul} \print</p>
-
- <p>\package{\FigMF} \author{Anthony Starks}
- \ftp{CTAN:graphics/fig2mf} \print</p>
-
- <p>\package{fontinst} \author{Alan Jeffrey}
- \ftp{CTAN:fonts/utilities/fontinst} \print</p>
-
- <p>\package{fontlib} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{GFtoDVI} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{GFtoPK} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{Ghostscript} <a id="ap03.ghostscript"
- name="ap03.ghostscript"></a> \author{Aladdin Enterprises}
- \address{P.O. box 60264\\Palo Alto, CA 94306\\USA}
- \phone{(415) 322--0103 / (415) 322--1734 FAX}
- \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{Ghostview} \author{Timothy O. Theisen}
- \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{gnuplot} \author{Free Software Foundation}
- \address{675 Massachusetts Avenue\\Cambridge, MA
- 02139\\USA} \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{GoScript} <a id="ap03.goscript"
- name="ap03.goscript"></a> \author{LaserGo, Inc.}
- \address{9369 Carroll Park Drive, Suite A\\San Diego, CA
- 92121\\USA} \phone{(619) 450--4600 / (619) 450-9334 FAX}
- \print</p>
-
- <p>\package{GoScript Plus} \xref{GoScript}{ap03:goscript}
- \print</p>
-
- <p>\package{groff} <a id="ap03.groff"
- name="ap03.groff"></a> \author{Free Software Foundation}
- \address{675 Massachusetts Avenue\\Cambridge, MA
- 02139\\USA} \comment{The FSF's version of \program{troff}
- is called \program{groff}. Many commercial implementations
- of \program{troff} are also available.}
- \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{hp2xx} \author{Heinz W. Werntges}
- \ftp{CTAN:support/hp2xx} \print</p>
-
- <p>\package{HPTFM2PL} \author{Norman Walsh}
- \ftp{CTAN:support/hp2pl} \print</p>
-
- <p>\package{Hyper\BibTeX} \author{Evan Antwork}
- \ftp{mac.archive.umich.edu:/mac/misc/tex} \print</p>
-
- <p>\package{idraw} <a id="ap03.idraw"
- name="ap03.idraw"></a> \ftp{interviews.stanford.edu}
- \print</p>
-
- <p>\package{Image Alchemy} \author{Handmade Software, Inc.}
- \address{15951 Los Gatos Blvd., Ste. 17\\Los Gatos, CA
- 95032\\USA} \phone{(408) 358--1292 / (408) 358--2694}
- \ftp{oak.oakland.edu:/pub/msdos/graphics} \print</p>
-
- <p>\package{Image Magick} <a id="ap03.imagemagick"
- name="ap03.imagemagick"></a> \author{John Cristy}
- \ftp{ftp.x.org:/contrib} \print</p>
-
- <p>\package{import} \xref{Image Magick}{ap03:imagemagick}
- \print</p>
-
- <p>\package{Info-Zip} <a id="ap03.info-zip"
- name="ap03.info-zip"></a> \author{Mark Adler, et. al.}
- \files{zip, unzip} \ftp{ftp.uu.net:/pub/archiving/zip}
- \print</p>
-
- <p>\package{\iniMF} \xref{\MF}{ap03:mf} \print</p>
-
- <p>\package{\iniTeX} \xref{\TeX}{ap03:tex} \print</p>
-
- <p>\package{ispell} \ftp{CTAN:support/ispell} \print</p>
-
- <p>\package{ivd2dvi} \author{Larry Denenberg}
- \ftp{CTAN:dviware/ivd2dvi} \print</p>
-
- <p>\package{\jemtex} \author{Fran\c cois Jalbert}
- \ftp{CTAN:systems/msdos/jemtex2} \print</p>
-
- <p>\package{LaCheck} \author{Kresten Krab Thorup and Per
- Abrahamsen} \ftp{CTAN:support/lacheck} \print</p>
-
- <p>\package{lookbibtex} <a id="ap03.lookbibtex"
- name="ap03.lookbibtex"></a> \author{John Heidemann}
- \ftp{CTAN:biblio/bibtex/utils/lookbibtex} \print</p>
-
- <p>\package{Mac\BibTeX} \xref{\BibTeX}{ap03:bibtex}
- \author{Michael Kahn} \ftp{CTAN:systems/mac} \comment{This
- is a Mac port of \BibTeX.} \print</p>
-
- <p>\package{MacDVIcopy} \author{Yannis Haralambous}
- \xref{dvicopy}{ap03:dvicopy} \comment{This is a Mac port of
- \program{dvicopy}.} \print</p>
-
- <p>\package{MacGS} \author{Martin Fong}
- \xref{GhostScript}{ap03:ghostscript}
- \ftp{mac.archive.umich.edu:/mac/graphics/graphicsutil}
- \comment{This is a Mac port of \program{GhostScript}.}
- \print</p>
-
- <p>\package{MacMakeIndex} \author{Johnny Tolliver}
- \xref{MakeIndex}{ap03:makeindex} \ftp{CTAN:systems/mac}
- \comment{This is a Mac port of \program{MakeIndex}.}
- \print</p>
-
- <p>\package{makebst} \author{Patrick W. Daly}
- \ftp{CTAN:macros/latex/contrib/custom-bib} \print</p>
-
- <p>\package{makeidx.sty} \ftp{CTAN:indexing/makeindex/lib}
- \print</p>
-
- <p>\package{MakeIndex} \author{Pehong Chen}
- \ftp{CTAN:indexing/makeindex} <a id="ap03.makeindex"
- name="ap03.makeindex"></a> \print</p>
-
- <p>\package{MakeIndx} \xref{MakeIndex}{ap03:makeindex}
- \print</p>
-
- <p>\package{MakeInfo} \xref{\TeXinfo}{ap03:texinfo}
- \print</p>
-
- <p>\package{maketcp} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{MakeTeXPK} \xref{dvips}{ap03:dvips}
- \comment{There are several versions of this file available.
- See Example&#160;\ref{ex:maketexpk} in
- Chapter&#160;\ref{app:examples},
- \textit{\nameref{app:examples}}.} \print</p>
-
- <p>\package{MakeTeXTFM} \comment{See
- Example&#160;\ref{ex:maketextfm} in
- Chapter&#160;\ref{app:examples},
- \textit{\nameref{app:examples}}.} \print</p>
-
- <p>\package{\MF} <a id="ap03.mf" name="ap03.mf"></a>
- \author{Donald Knuth} \ftp{CTAN:systems/web2c} \comment{The
- \Web sources and the \Web2C programs are both available
- here.} \print</p>
-
- <p>\package{\MF for Textures} \author{Blue Sky Research}
- \address{534 SW Third Avenue\\Portland, OR 97204\\USA}
- \phone{(800) 622--8398 or (503) 222--9571 / (503) 222--1643
- FAX} \ftp{CTAN:systems/mac/metafont/bluesky} \print</p>
-
- <p>\package{MFjob} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{\MFpic} \author{Thomas Leathrum}
- \ftp{CTAN:graphics/mfpic} \print</p>
-
- <p>\package{MFT} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{\mfware} <a id="ap03.mfware"
- name="ap03.mfware"></a> \author{Donald Knuth}
- \ftp{CTAN:systems/web2c} \comment{The \Web sources and the
- \Web2C programs are both available here.} \print</p>
-
- <p>\package{mogrify} \xref{Image Magick}{ap03:imagemagick}
- \print</p>
-
- <p>\package{montage} \xref{Image Magick}{ap03:imagemagick}
- \print</p>
-
- <p>\package{Nikon II} \author{Bitware, Software &amp;
- Services} \address{P.O. Box 3097\\Manuka A.C.T.
- 2603\\Australia} \ftp{ftp.cdrom.com:/pub/os2/2_x/graphics}
- \print</p>
-
- <p>\package{nroff} \xref{groff}{ap03:groff} \print</p>
-
- <p>\package{PBMplus} <a id="ap03.pbmplus"
- name="ap03.pbmplus"></a> \author{Jef Poskanzer}
- \ftp{ftp.x.org:/contrib} \print</p>
-
- <p>\package{pbmtopk} <a id="ap03.pbmtopk"
- name="ap03.pbmtopk"></a> \author{Angus Duggan}
- \ftp{CTAN:graphics/pbmtopk} \print</p>
-
- <p>\package{pfatopfb} \xref{\tutils}{ap03:t1utils}
- \print</p>
-
- <p>\package{pfbtopfa} \xref{\tutils}{ap03:t1utils}
- \print</p>
-
- <p>\package{PFM2AFM} \author{Ken Borgendale}
- \ftp{CTAN:fonts/utilities/pfm2afm} \print</p>
-
- <p>\package{pixmap} \author{Lionel Mallet}
- \ftp{ftp.x.org:/contrib/pixmap} \print</p>
-
- <p>\package{PKBBOX} \author{Norman Walsh}
- \ftp{CTAN:fonts/utilities/pkbbox} \print</p>
-
- <p>\package{PKEdit} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{PKtoGF} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{pktopbm} \xref{pbmtopk}{ap03:pbmtopk}
- \print</p>
-
- <p>\package{pktops} \xref{\yyTeX}{ap03:yytex} \print</p>
-
- <p>\package{PKtoPX} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{PKtoSFP} \author{Norman Walsh}
- \ftp{CTAN:font/softfonts} \print</p>
-
- <p>\package{PKtype} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{PLtoTF} \xref{\texware}{ap03:texware}
- \print</p>
-
- <p>\package{PM-Cam} \author{J. von Kaenel}
- \ftp{ftp.cdrom.com:/pub/os2/ibm/ews} \print</p>
-
- <p>\package{\pmc} \author{Tom Ridgeway}
- \ftp{CTAN:fonts/poorman} \print</p>
-
- <p>\package{\pmj} \author{Tom Ridgeway}
- \ftp{CTAN:fonts/poorman} \print</p>
-
- <p>\package{Pmjpeg} \author{Norman Yee}
- \ftp{ftp.cdrom.com:/pub/os2/2_x/graphics} \print</p>
-
- <p>\package{ps2epsi} \xref{ghostscript}{ap03:ghostscript}
- \print</p>
-
- <p>\package{PS2PK} \author{Piet Tutelaers}
- \ftp{CTAN:fonts/utilities/ps2pk} \print</p>
-
- <p>\package{\PSTricks} \author{Timothy Van Zandt}
- \ftp{CTAN:graphics/pstricks} \print</p>
-
- <p>\package{PTI Jet} \xref{\PCTeX}{ap03:pctex} \print</p>
-
- <p>\package{PTI Laser/HP} \xref{\PCTeX}{ap03:pctex}
- \print</p>
-
- <p>\package{PTI Laser/HP4} \xref{\PCTeX}{ap03:pctex}
- \print</p>
-
- <p>\package{PTI Laser/PS} \xref{\PCTeX}{ap03:pctex}
- \print</p>
-
- <p>\package{PTI View} \xref{\PCTeX}{ap03:pctex} \print</p>
-
- <p>\package{PXtoPK} \author{Peter Breitenlohner}
- \ftp{systems/msdos/utilities} \print</p>
-
- <p>\package{RCS} \author{Walter F. Tichy}
- \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{Recode} \author{Francois Pinard}
- \ftp{prep.ai.mit.edu:/pub/gnu} \print</p>
-
- <p>\package{REXX} \author{International Business Machines}
- \print</p>
-
- <p>\package{\sbMF} \xref{\sbTeX}{ap03:sbtex} \print</p>
-
- <p>\package{sed} \author{Free Software Foundation}
- \address{675 Massachusetts Avenue\\Cambridge, MA
- 02139\\USA} \ftp{prep.ai.mit.edu:/pub/gnu} \comment{Many
- commercial implementations of \program{sed} are also
- available.} \print</p>
-
- <p>\package{\SeeTeX} <a id="ap03.seetex"
- name="ap03.seetex"></a> \author{David Grunwald}
- \ftp{CTAN:dviware/seetex} \print</p>
-
- <p>\package{sffx} \xref{Sfware}{ap03:sfware} \print</p>
-
- <p>\package{Sfload} \xref{Sfware}{ap03:sfware} \print</p>
-
- <p>\package{SFPtoPK} \author{Norman Walsh}
- \ftp{CTAN:font/softfonts} \print</p>
-
- <p>\package{Sfware} <a id="ap03.sfware"
- name="ap03.sfware"></a> \author{Norman Walsh}
- \ftp{CTAN:font/softfonts/sfware} \print</p>
-
- <p>\package{tangle} \xref{\Web2c}{ap03:web2c} \print</p>
-
- <p>\package{tar} \author{Free Software Foundation}
- \address{675 Massachusetts Avenue\\Cambridge, MA
- 02139\\USA} \ftp{prep.ai.mit.edu:/pub/gnu} \comment{Many
- commercial implementations of \program{tar} are also
- available.} \print</p>
-
- <p>\package{tex386} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{\TeX Preview} \xref{\utex}{ap03:utex}
- \print</p>
-
- <p>\package{texcad} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{texchk} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{texconv} \xref{\emTeX}{ap03:emtex} \print</p>
-
- <p>\package{\TeXinfo} <a id="ap03.texinfo"
- name="ap03.texinfo"></a> \author{Free Software Foundation}
- \address{675 Massachusetts Avenue\\Cambridge, MA
- 02139\\USA} \ftp{prep.ai.mit.edu:/pbu/gnu} \print</p>
-
- <p>\package{\TeXtoXfont} \comment{See
- Example&#160;\ref{ex:textoxfont} in
- Chapter&#160;\ref{app:examples},
- \textit{\nameref{app:examples}}.} \print</p>
-
- <p>\package{\texware} <a id="ap03.texware"
- name="ap03.texware"></a> \author{Donald Knuth}
- \ftp{CTAN:systems/web2c} \comment{The \Web sources and the
- \Web2C programs are both available here.} \print</p>
-
- <p>\package{TFtoPL} \xref{\texware}{ap03:texware}
- \print</p>
-
- <p>\package{Tgif} \author{William Chia-Wei Cheng}
- \ftp{ftp.x.org:/contrib} \print</p>
-
- <p>\package{\Tib} \author{James C. Alexander}
- \ftp{CTAN:biblio/tib} \print</p>
-
- <p>\package{\tpre} \xref{\utex}{ap03:utex} \print</p>
-
- <p>\package{troff} \xref{groff}{ap03:groff} \print</p>
-
- <p>\package{\tutils} <a id="ap03.t1utils"
- name="ap03.t1utils"></a> \author{I. Lee Hetherington}
- \ftp{CTAN:fonts/utilities/t1utils} \print</p>
-
- <p>\package{txt2pcx} \author{DECISIONS Software}
- \address{P.O. Box 31418\\Phoenix, AZ 85046\\USA}
- \phone{(602) 992--0310} \print</p>
-
- <p>\package{unzip} \xref{Info-Zip}{ap03:info-zip}
- \print</p>
-
- <p>\package{VFtoVP} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{VPtoVF} \xref{\mfware}{ap03:mfware} \print</p>
-
- <p>\package{wbr} \xref{dviwin}{ap03:dviwin} \print</p>
-
- <p>\package{wdviwin} \xref{\TurboTeX}{ap03:turbotex}
- \print</p>
-
- <p>\package{weave} \xref{\Web2c}{ap03:web2c} \print</p>
-
- <p>\package{xbibtex} \author{Nicholas Kelly and Christian
- H. Bischof} \ftp{CTAN:biblio/bibtex/utils/xbibtex}
- \print</p>
-
- <p>\package{Xdvi} \author{Paul Vojta}
- \ftp{CTAN:dviware/xdvi} \print</p>
-
- <p>\package{\XeT} \ftp{noa.huji.ac.il:/tex}
- \comment{Several implementations of \XeT-{}-\TeX are
- available here.} \print</p>
-
- <p>\package{xfig} \author{Brian V. Smith}
- \ftp{ftp.x.org:/contrib} \print</p>
-
- <p>\package{xloadimage} \author{Jim Frost}
- \ftp{ftp.x.org:/contrib} \print</p>
-
- <p>\package{xpaint} \author{David Koblas}
- \ftp{ftp.x.org:/contrib}</p>
-
- <p>\package{\XTeX} \xref{See\TeX}{ap03:seetex} \print</p>
-
- <p>\package{Xtexcad} \comment{Available from volume 17 of
- the \texttt{comp.sources.x} newsgroup.} \print</p>
-
- <p>\package{xv} \author{John Bradley}
- \ftp{ftp.x.org:/contrib} \print</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2948003"
- name="id2948003"></a>Miscellaneous</h2>
- </div>
- </div>
-
- <p>\vskip2pt</p>
-
- <p>\package{4DOS} \author{JP Software Inc.} \address{P.O.
- Box 1470\\E. Arlington, MA 02174\\USA} \phone{(617)
- 646--3975} \ftp{oak.oakland.edu:/pub/msdos/4dos} \print</p>
-
- <p>\package{4OS2} \author{JP Software Inc.} \address{P.O.
- Box 1470\\E. Arlington, MA 02174\\USA} \phone{(617)
- 646--3975} \ftp{ftp.cdrom.com:/pub/os2/2_x/sysutils}
- \print</p>
-
- <p>\package{Channel 1\regtm} \address{1030 Massachusetts
- Avenue\\Cambridge, MA 02138} \phone{(617) 864--0100 voice /
- (617) 354-3230 v32.bis modem} \comment{The Channel 1 BBS
- carries a \TeX conference with many MS-DOS tools available
- for downloading to registered users.} \print</p>
-
- <p>\package{edb} \author{Michael Ernst}
- \ftp{theory.lcs.mit.edu:/pub/emacs/edb} \comment{Database
- manager for GNU Emacs.} \print</p>
-
- <p>\package{Linux} \author{Linus Torvalds}
- \ftp{ftp.cdrom.com:/pub/linux} \print</p>
-
- <p>\package{mewltx} \author{Michael F. Reid}
- \ftp{CTAN:support/mewltx} \comment{\LaTeX extensions for
- \filename{MicroEMACS}.} \xref{MEwin}{ap03:mewin} \print</p>
-
- <p>\package{modes.mf} \author{Karl Berry}
- \ftp{CTAN:fonts/modes} \print</p>
-
- <p>\package{Perl} \author{Larry Wall} \print</p>
-
- <p>\package{TeX-index} <a id="ap03.texindex"
- name="ap03.texindex"></a> \author{David Jones}
- \ftp{CTAN:info} \comment{Also known as
- \filename{tex-styles-and-macros.txt}.} \print</p>
-
- <p>\package{tex-styles-and-macros.txt}
- \xref{TeX-index}{ap03:texindex} \print</p>
-
- <p>\package{\Web2c} <a id="ap03.web2c"
- name="ap03.web2c"></a> \author{Karl Berry}
- \ftp{CTAN:systems/web2c} \print</p>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Appendix&#160;B.&#160;Font Samples"
- href="apb.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Appendix&#160;D.&#160;Long Examples"
- href="apd.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Appendix&#160;B.&#160;Font
- Samples&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Appendix&#160;D.&#160;Long Examples</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/apd.html b/Master/texmf-doc/doc/english/make-tex-work/html/apd.html
deleted file mode 100644
index e7e99b4f4b9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/apd.html
+++ /dev/null
@@ -1,229 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Appendix&#160;D.&#160;Long Examples</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="apc.html"
- title="Appendix&#160;C.&#160;Resources" />
- <link rel="next" href="ape.html"
- title="Appendix&#160;E.&#160;GNU Free Documentation License" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Appendix&#160;C.&#160;Resources"
- href="apc.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Appendix&#160;E.&#160;GNU Free Documentation License"
- href="ape.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="appendix">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="app.examples"
- name="app.examples"></a>Appendix&#160;D.&#160;Long
- Examples</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- </div>
-
- <p>This appendix contains the source for several scripts that
- seemed too long to place in the running text. These scripts
- are provided as examples only, they may not run on your
- system without some modification.</p>
-
- <p>These examples are available online, see the Preface for
- more information about retrieving online examples.</p>
-
- <p>The \program{MakeTeXPK.pl} script builds PK files from
- MetaFont and PostScript fonts.</p>
-
- <div class="example">
- <a id="ex.maketexpk" name="ex.maketexpk"></a>
-
- <p class="title">
- <b>Example&#160;D.1.&#160;MakeTeXPK.pl</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="MakeTeXPK.pl"></a>
-</pre>
- </div>
-
- <p>The \program{MakeTeXTFM.pl} script builds TFM files from
- \MF\ and PostScript (\ext{AFM} file) fonts.</p>
-
- <div class="example">
- <a id="ex.maketextfm" name="ex.maketextfm"></a>
-
- <p class="title">
- <b>Example&#160;D.2.&#160;MakeTeXTFM.pl</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="MakeTeXTFM.pl"></a>
-</pre>
- </div>
-
- <p>The \program{dvidxx.btm} script is written in
- \program{4DOS}'s extended batch language. It performs
- automatic font generation for \MF\ and PostScript fonts using
- \emTeX's drivers (version 1.4s).</p>
-
- <div class="example">
- <a id="ex.dvidxx" name="ex.dvidxx"></a>
-
- <p class="title">
- <b>Example&#160;D.3.&#160;dvidxx.btm</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="dvidxx.btm"></a>
-</pre>
- </div>
-
- <p>The \program{makepk.btm} script is used by
- \program{dvidxx.btm}, shown in Example~\ref{ex:dvidxx} in
- this appendix.</p>
-
- <div class="example">
- <a id="ex.makepk" name="ex.makepk"></a>
-
- <p class="title">
- <b>Example&#160;D.4.&#160;makepk.btm</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="makepk.btm"></a>
-</pre>
- </div>
-
- <p>The \program{enc-afm.pl} script changes the encoding
- vector in an \ext{AFM} file.</p>
-
- <div class="example">
- <a id="ex.encafmpl" name="ex.encafmpl"></a>
-
- <p class="title">
- <b>Example&#160;D.5.&#160;enc-afm.pl</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="enc-afm.pl"></a>
-</pre>
- </div>
-
- <p>The \program{TeXtoXfont} script is a \Unix\ shell script
- (written in \program{bash}) which builds an X11 font from a
- \MF\ or PostScript font.</p>
-
- <div class="example">
- <a id="ex.textoxfont" name="ex.textoxfont"></a>
-
- <p class="title">
- <b>Example&#160;D.6.&#160;TeXtoXfont</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="TeXtoXfont"></a>
-</pre>
- </div>
-
- <p>The \program{PStoXfont} script is used by
- \program{TeXtoXfont}, shown in Example~\ref{ex:textoxfont} in
- this appendix.</p>
-
- <div class="example">
- <a id="ex.pstoxfont" name="ex.pstoxfont"></a>
-
- <p class="title">
- <b>Example&#160;D.7.&#160;PStoXfont</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="PStoXfont"></a>
-</pre>
- </div>
-
- <p>The \program{txt2verb.pl} script translates arbitrary text
- lines into a format suitable for including in
- \verb|\verbatim| material in \TeX.</p>
-
- <div class="example">
- <a id="ex.txt2verb" name="ex.txt2verb"></a>
-
- <p class="title">
- <b>Example&#160;D.8.&#160;txt2verb.pl</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="txt2verb.pl"></a>
-</pre>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Appendix&#160;C.&#160;Resources"
- href="apc.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Appendix&#160;E.&#160;GNU Free Documentation License"
- href="ape.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Appendix&#160;C.&#160;Resources&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Appendix&#160;E.&#160;GNU Free Documentation
- License</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ape.html b/Master/texmf-doc/doc/english/make-tex-work/html/ape.html
deleted file mode 100644
index 6e68d8f0bba..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ape.html
+++ /dev/null
@@ -1,639 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Appendix&#160;E.&#160;GNU Free Documentation
- License</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples" />
- <link rel="next" href="bi01.html" title="Bibliography" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Appendix&#160;D.&#160;Long Examples"
- href="apd.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a title="Bibliography"
- href="bi01.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="appendix">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="gfdl"
- name="gfdl"></a>Appendix&#160;E.&#160;GNU Free
- Documentation License</h2>
- </div>
- </div>
-
- <p>Version 1.1, March 2000</p>
-
- <blockquote class="blockquote">
- <p>Copyright (C) 2000 Free Software Foundation, Inc. 59
- Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone
- is permitted to copy and distribute verbatim copies of this
- license document, but changing it is not allowed.</p>
- </blockquote>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2948209"
- name="id2948209"></a>PREAMBLE</h2>
- </div>
- </div>
-
- <p>The purpose of this License is to make a manual,
- textbook, or other written document "free" in the sense of
- freedom: to assure everyone the effective freedom to copy
- and redistribute it, with or without modifying it, either
- commercially or noncommercially. Secondarily, this License
- preserves for the author and publisher a way to get credit
- for their work, while not being considered responsible for
- modifications made by others.</p>
-
- <p>This License is a kind of "copyleft", which means that
- derivative works of the document must themselves be free in
- the same sense. It complements the GNU General Public
- License, which is a copyleft license designed for free
- software.</p>
-
- <p>We have designed this License in order to use it for
- manuals for free software, because free software needs free
- documentation: a free program should come with manuals
- providing the same freedoms that the software does. But
- this License is not limited to software manuals; it can be
- used for any textual work, regardless of subject matter or
- whether it is published as a printed book. We recommend
- this License principally for works whose purpose is
- instruction or reference.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2948100"
- name="id2948100"></a>APPLICABILITY AND DEFINITIONS</h2>
- </div>
- </div>
-
- <p>This License applies to any manual or other work that
- contains a notice placed by the copyright holder saying it
- can be distributed under the terms of this License. The
- "Document", below, refers to any such manual or work. Any
- member of the public is a licensee, and is addressed as
- "you".</p>
-
- <p>A "Modified Version" of the Document means any work
- containing the Document or a portion of it, either copied
- verbatim, or with modifications and/or translated into
- another language.</p>
-
- <p>A "Secondary Section" is a named appendix or a
- front-matter section of the Document that deals exclusively
- with the relationship of the publishers or authors of the
- Document to the Document's overall subject (or to related
- matters) and contains nothing that could fall directly
- within that overall subject. (For example, if the Document
- is in part a textbook of mathematics, a Secondary Section
- may not explain any mathematics.) The relationship could be
- a matter of historical connection with the subject or with
- related matters, or of legal, commercial, philosophical,
- ethical or political position regarding them.</p>
-
- <p>The "Invariant Sections" are certain Secondary Sections
- whose titles are designated, as being those of Invariant
- Sections, in the notice that says that the Document is
- released under this License.</p>
-
- <p>The "Cover Texts" are certain short passages of text
- that are listed, as Front-Cover Texts or Back-Cover Texts,
- in the notice that says that the Document is released under
- this License.</p>
-
- <p>A "Transparent" copy of the Document means a
- machine-readable copy, represented in a format whose
- specification is available to the general public, whose
- contents can be viewed and edited directly and
- straightforwardly with generic text editors or (for images
- composed of pixels) generic paint programs or (for
- drawings) some widely available drawing editor, and that is
- suitable for input to text formatters or for automatic
- translation to a variety of formats suitable for input to
- text formatters. A copy made in an otherwise Transparent
- file format whose markup has been designed to thwart or
- discourage subsequent modification by readers is not
- Transparent. A copy that is not "Transparent" is called
- "Opaque".</p>
-
- <p>Examples of suitable formats for Transparent copies
- include plain ASCII without markup, Texinfo input format,
- LaTeX input format, SGML or XML using a publicly available
- DTD, and standard-conforming simple HTML designed for human
- modification. Opaque formats include PostScript, PDF,
- proprietary formats that can be read and edited only by
- proprietary word processors, SGML or XML for which the DTD
- and/or processing tools are not generally available, and
- the machine-generated HTML produced by some word processors
- for output purposes only.</p>
-
- <p>The "Title Page" means, for a printed book, the title
- page itself, plus such following pages as are needed to
- hold, legibly, the material this License requires to appear
- in the title page. For works in formats which do not have
- any title page as such, "Title Page" means the text near
- the most prominent appearance of the work's title,
- preceding the beginning of the body of the text.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2948673"
- name="id2948673"></a>VERBATIM COPYING</h2>
- </div>
- </div>
-
- <p>You may copy and distribute the Document in any medium,
- either commercially or noncommercially, provided that this
- License, the copyright notices, and the license notice
- saying this License applies to the Document are reproduced
- in all copies, and that you add no other conditions
- whatsoever to those of this License. You may not use
- technical measures to obstruct or control the reading or
- further copying of the copies you make or distribute.
- However, you may accept compensation in exchange for
- copies. If you distribute a large enough number of copies
- you must also follow the conditions in section 3.</p>
-
- <p>You may also lend copies, under the same conditions
- stated above, and you may publicly display copies.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2948707"
- name="id2948707"></a>COPYING IN QUANTITY</h2>
- </div>
- </div>
-
- <p>If you publish printed copies of the Document numbering
- more than 100, and the Document's license notice requires
- Cover Texts, you must enclose the copies in covers that
- carry, clearly and legibly, all these Cover Texts:
- Front-Cover Texts on the front cover, and Back-Cover Texts
- on the back cover. Both covers must also clearly and
- legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of
- the title equally prominent and visible. You may add other
- material on the covers in addition. Copying with changes
- limited to the covers, as long as they preserve the title
- of the Document and satisfy these conditions, can be
- treated as verbatim copying in other respects.</p>
-
- <p>If the required texts for either cover are too
- voluminous to fit legibly, you should put the first ones
- listed (as many as fit reasonably) on the actual cover, and
- continue the rest onto adjacent pages.</p>
-
- <p>If you publish or distribute Opaque copies of the
- Document numbering more than 100, you must either include a
- machine-readable Transparent copy along with each Opaque
- copy, or state in or with each Opaque copy a
- publicly-accessible computer-network location containing a
- complete Transparent copy of the Document, free of added
- material, which the general network-using public has access
- to download anonymously at no charge using public-standard
- network protocols. If you use the latter option, you must
- take reasonably prudent steps, when you begin distribution
- of Opaque copies in quantity, to ensure that this
- Transparent copy will remain thus accessible at the stated
- location until at least one year after the last time you
- distribute an Opaque copy (directly or through your agents
- or retailers) of that edition to the public.</p>
-
- <p>It is requested, but not required, that you contact the
- authors of the Document well before redistributing any
- large number of copies, to give them a chance to provide
- you with an updated version of the Document.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2948791"
- name="id2948791"></a>MODIFICATIONS</h2>
- </div>
- </div>
-
- <p>You may copy and distribute a Modified Version of the
- Document under the conditions of sections 2 and 3 above,
- provided that you release the Modified Version under
- precisely this License, with the Modified Version filling
- the role of the Document, thus licensing distribution and
- modification of the Modified Version to whoever possesses a
- copy of it. In addition, you must do these things in the
- Modified Version:</p>
-
- <div class="orderedlist">
- <ol type="A">
- <li>
- <p>Use in the Title Page (and on the covers, if any)
- a title distinct from that of the Document, and from
- those of previous versions (which should, if there
- were any, be listed in the History section of the
- Document). You may use the same title as a previous
- version if the original publisher of that version
- gives permission.</p>
- </li>
-
- <li>
- <p>List on the Title Page, as authors, one or more
- persons or entities responsible for authorship of the
- modifications in the Modified Version, together with
- at least five of the principal authors of the
- Document (all of its principal authors, if it has
- less than five).</p>
- </li>
-
- <li>
- <p>State on the Title page the name of the publisher
- of the Modified Version, as the publisher.</p>
- </li>
-
- <li>
- <p>Preserve all the copyright notices of the
- Document.</p>
- </li>
-
- <li>
- <p>Add an appropriate copyright notice for your
- modifications adjacent to the other copyright
- notices.</p>
- </li>
-
- <li>
- <p>Include, immediately after the copyright notices,
- a license notice giving the public permission to use
- the Modified Version under the terms of this License,
- in the form shown in the Addendum below.</p>
- </li>
-
- <li>
- <p>Preserve in that license notice the full lists of
- Invariant Sections and required Cover Texts given in
- the Document's license notice.</p>
- </li>
-
- <li>
- <p>Include an unaltered copy of this License.</p>
- </li>
-
- <li>
- <p>Preserve the section entitled "History", and its
- title, and add to it an item stating at least the
- title, year, new authors, and publisher of the
- Modified Version as given on the Title Page. If there
- is no section entitled "History" in the Document,
- create one stating the title, year, authors, and
- publisher of the Document as given on its Title Page,
- then add an item describing the Modified Version as
- stated in the previous sentence.</p>
- </li>
-
- <li>
- <p>Preserve the network location, if any, given in
- the Document for public access to a Transparent copy
- of the Document, and likewise the network locations
- given in the Document for previous versions it was
- based on. These may be placed in the "History"
- section. You may omit a network location for a work
- that was published at least four years before the
- Document itself, or if the original publisher of the
- version it refers to gives permission.</p>
- </li>
-
- <li>
- <p>In any section entitled "Acknowledgements" or
- "Dedications", preserve the section's title, and
- preserve in the section all the substance and tone of
- each of the contributor acknowledgements and/or
- dedications given therein.</p>
- </li>
-
- <li>
- <p>Preserve all the Invariant Sections of the
- Document, unaltered in their text and in their
- titles. Section numbers or the equivalent are not
- considered part of the section titles.</p>
- </li>
-
- <li>
- <p>Delete any section entitled "Endorsements". Such a
- section may not be included in the Modified
- Version.</p>
- </li>
-
- <li>
- <p>Do not retitle any existing section as
- "Endorsements" or to conflict in title with any
- Invariant Section.</p>
- </li>
- </ol>
- </div>
-
- <p>If the Modified Version includes new front-matter
- sections or appendices that qualify as Secondary Sections
- and contain no material copied from the Document, you may
- at your option designate some or all of these sections as
- invariant. To do this, add their titles to the list of
- Invariant Sections in the Modified Version's license
- notice. These titles must be distinct from any other
- section titles.</p>
-
- <p>You may add a section entitled "Endorsements", provided
- it contains nothing but endorsements of your Modified
- Version by various parties--for example, statements of peer
- review or that the text has been approved by an
- organization as the authoritative definition of a
- standard.</p>
-
- <p>You may add a passage of up to five words as a
- Front-Cover Text, and a passage of up to 25 words as a
- Back-Cover Text, to the end of the list of Cover Texts in
- the Modified Version. Only one passage of Front-Cover Text
- and one of Back-Cover Text may be added by (or through
- arrangements made by) any one entity. If the Document
- already includes a cover text for the same cover,
- previously added by you or by arrangement made by the same
- entity you are acting on behalf of, you may not add
- another; but you may replace the old one, on explicit
- permission from the previous publisher that added the old
- one.</p>
-
- <p>The author(s) and publisher(s) of the Document do not by
- this License give permission to use their names for
- publicity for or to assert or imply endorsement of any
- Modified Version.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2949025"
- name="id2949025"></a>COMBINING DOCUMENTS</h2>
- </div>
- </div>
-
- <p>You may combine the Document with other documents
- released under this License, under the terms defined in
- section 4 above for modified versions, provided that you
- include in the combination all of the Invariant Sections of
- all of the original documents, unmodified, and list them
- all as Invariant Sections of your combined work in its
- license notice.</p>
-
- <p>The combined work need only contain one copy of this
- License, and multiple identical Invariant Sections may be
- replaced with a single copy. If there are multiple
- Invariant Sections with the same name but different
- contents, make the title of each such section unique by
- adding at the end of it, in parentheses, the name of the
- original author or publisher of that section if known, or
- else a unique number. Make the same adjustment to the
- section titles in the list of Invariant Sections in the
- license notice of the combined work.</p>
-
- <p>In the combination, you must combine any sections
- entitled "History" in the various original documents,
- forming one section entitled "History"; likewise combine
- any sections entitled "Acknowledgements", and any sections
- entitled "Dedications". You must delete all sections
- entitled "Endorsements."</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2949073"
- name="id2949073"></a>COLLECTIONS OF DOCUMENTS</h2>
- </div>
- </div>
-
- <p>You may make a collection consisting of the Document and
- other documents released under this License, and replace
- the individual copies of this License in the various
- documents with a single copy that is included in the
- collection, provided that you follow the rules of this
- License for verbatim copying of each of the documents in
- all other respects.</p>
-
- <p>You may extract a single document from such a
- collection, and distribute it individually under this
- License, provided you insert a copy of this License into
- the extracted document, and follow this License in all
- other respects regarding verbatim copying of that
- document.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2949112"
- name="id2949112"></a>AGGREGATION WITH INDEPENDENT
- WORKS</h2>
- </div>
- </div>
-
- <p>A compilation of the Document or its derivatives with
- other separate and independent documents or works, in or on
- a volume of a storage or distribution medium, does not as a
- whole count as a Modified Version of the Document, provided
- no compilation copyright is claimed for the compilation.
- Such a compilation is called an "aggregate", and this
- License does not apply to the other self-contained works
- thus compiled with the Document, on account of their being
- thus compiled, if they are not themselves derivative works
- of the Document.</p>
-
- <p>If the Cover Text requirement of section 3 is applicable
- to these copies of the Document, then if the Document is
- less than one quarter of the entire aggregate, the
- Document's Cover Texts may be placed on covers that
- surround only the Document within the aggregate. Otherwise
- they must appear on covers around the whole aggregate.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2949149"
- name="id2949149"></a>TRANSLATION</h2>
- </div>
- </div>
-
- <p>Translation is considered a kind of modification, so you
- may distribute translations of the Document under the terms
- of section 4. Replacing Invariant Sections with
- translations requires special permission from their
- copyright holders, but you may include translations of some
- or all Invariant Sections in addition to the original
- versions of these Invariant Sections. You may include a
- translation of this License provided that you also include
- the original English version of this License. In case of a
- disagreement between the translation and the original
- English version of this License, the original English
- version will prevail.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2949177"
- name="id2949177"></a>TERMINATION</h2>
- </div>
- </div>
-
- <p>You may not copy, modify, sublicense, or distribute the
- Document except as expressly provided for under this
- License. Any other attempt to copy, modify, sublicense or
- distribute the Document is void, and will automatically
- terminate your rights under this License. However, parties
- who have received copies, or rights, from you under this
- License will not have their licenses terminated so long as
- such parties remain in full compliance.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2949201"
- name="id2949201"></a>FUTURE REVISIONS OF THIS
- LICENSE</h2>
- </div>
- </div>
-
- <p>The Free Software Foundation may publish new, revised
- versions of the GNU Free Documentation License from time to
- time. Such new versions will be similar in spirit to the
- present version, but may differ in detail to address new
- problems or concerns. See <a
- href="http://www.gnu.org/copyleft/"
- target="_top">http://www.gnu.org/copyleft/</a>.</p>
-
- <p>Each version of the License is given a distinguishing
- version number. If the Document specifies that a particular
- numbered version of this License "or any later version"
- applies to it, you have the option of following the terms
- and conditions either of that specified version or of any
- later version that has been published (not as a draft) by
- the Free Software Foundation. If the Document does not
- specify a version number of this License, you may choose
- any version ever published (not as a draft) by the Free
- Software Foundation.</p>
- </div>
-
- <div class="sect1">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2948479"
- name="id2948479"></a>How to use this License for your
- documents</h2>
- </div>
- </div>
-
- <p>To use this License in a document you have written,
- include a copy of the License in the document and put the
- following copyright and license notices just after the
- title page:</p>
-
- <blockquote class="blockquote">
- <p>Copyright (c) YEAR YOUR NAME. Permission is granted to
- copy, distribute and/or modify this document under the
- terms of the GNU Free Documentation License, Version 1.1
- or any later version published by the Free Software
- Foundation; with the Invariant Sections being LIST THEIR
- TITLES, with the Front-Cover Texts being LIST, and with
- the Back-Cover Texts being LIST. A copy of the license is
- included in the section entitled "GNU Free Documentation
- License".</p>
- </blockquote>
-
- <p>If you have no Invariant Sections, write "with no
- Invariant Sections" instead of saying which ones are
- invariant. If you have no Front-Cover Texts, write "no
- Front-Cover Texts" instead of "Front-Cover Texts being
- LIST"; likewise for Back-Cover Texts.</p>
-
- <p>If your document contains nontrivial examples of program
- code, we recommend releasing these examples in parallel
- under your choice of free software license, such as the GNU
- General Public License, to permit their use in free
- software.</p>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Appendix&#160;D.&#160;Long Examples"
- href="apd.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Bibliography" href="bi01.html"><img
- src="figures/nav-next.png" alt="Next" border="0" />
- </a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Appendix&#160;D.&#160;Long
- Examples&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">&#160;Bibliography</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch01.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch01.html
deleted file mode 100644
index 0a685eef905..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch01.html
+++ /dev/null
@@ -1,2103 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;1.&#160;The Big Picture</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX" />
- <link rel="previous" href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX" />
- <link rel="next" href="ch02.html"
- title="Chapter&#160;2.&#160;Editing" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;2.&#160;Editing"
- href="ch02.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.tex"
- name="chap.tex"></a>Chapter&#160;1.&#160;The Big
- Picture</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.texforbeginners"
- name="sec.texforbeginners"></a>What Is TeX?</h2>
- </div>
- </div>
-
- <p>TeX<a id="id2856076" class="indexterm"
- name="id2856076"></a><a id="id2855998" class="indexterm"
- name="id2855998"></a> is a <span
- class="emphasis"><em>typesetting system</em></span>. It is
- a collection of programs, files, and procedures for
- producing professional quality documents with minimum
- effort.</p>
-
- <p>TeX's job is to translate the text you type into a
- beautiful<a id="id2856025" class="indexterm"
- name="id2856025"></a> typeset page. The key word here is
- &#8220;beautiful,&#8221; and it is a very lofty
- goal.<sup>[<a id="id2856038" name="id2856038"
- href="#ftn.id2856038">1</a>]</sup> What I mean by beautiful
- is that TeX, when presented with several paragraphs of
- plain text and left to its own devices, produces a
- remarkably aesthetic page. Despite the fact that TeX may
- have to contend with multiple fonts<a id="id2856069"
- class="indexterm" name="id2856069"></a> and mathematics<a
- id="id2857340" class="indexterm" name="id2857340"></a>, it
- still manages to typeset pages in which each of the
- following aesthetic principles hold <span
- class="emphasis"><em>simultaneously:</em></span></p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>The right margin is justified<a id="id2857364"
- class="indexterm" name="id2857364"></a>.</p>
- </li>
-
- <li>
- <p>Proper justification is achieved without
- letterspacing<a id="id2857382" class="indexterm"
- name="id2857382"></a>.</p>
- </li>
-
- <li>
- <p>Interword spacing is neither too tight nor too
- loose.<a id="id2857400" class="indexterm"
- name="id2857400"></a></p>
- </li>
-
- <li>
- <p>The page is evenly gray.</p>
- </li>
-
- <li>
- <p>The baselines<a id="id2857426" class="indexterm"
- name="id2857426"></a><a id="id2857433"
- class="indexterm" name="id2857433"></a> of multiple
- fonts are properly aligned.</p>
- </li>
-
- <li>
- <p>Hyphenation<a id="id2857454" class="indexterm"
- name="id2857454"></a> is automatic, if required, and
- usually correct.</p>
- </li>
-
- <li>
- <p>Ladders<a id="id2857471" class="indexterm"
- name="id2857471"></a> are avoided.</p>
- </li>
- </ul>
- </div>
-
- <p>TeX processes documents a paragraph at a time, rather
- than a line at a time like most other programs. Internally,
- TeX computes a value called <span
- class="emphasis"><em>badness<a id="id2857492"
- class="indexterm" name="id2857492"></a></em></span> for
- each line of the paragraph<a id="id2857501"
- class="indexterm" name="id2857501"></a>. Anything that
- detracts from the appearance of a line (tight or loose
- spacing, a hyphen, etc.) increases the badness associated
- with that line. Every paragraph that TeX produces is
- optimal in terms of the total amount of badness present.
- Because TeX searches for an optimal solution, changing the
- last word of a paragraph can affect the spacing of the
- first line of the paragraph. After you've gained a little
- bit of experience with TeX, you'll be able to override any
- one, or all, of the rules it uses to compute badness, but
- in most situations you won't want to. I will describe more
- of TeX's approach to text formatting and how it differs
- from that of word processors, desktop publishers, and other
- markup languages in the following sections.</p>
-
- <p>TeX is not a simple program, but a set of programs,
- tools, fonts, and other types of files. Two programs form
- the core of the TeX typesetting system. One of them is TeX
- itself, the program that reads your input files and
- transforms them into typeset form. The other program is
- MetaFont, a tool for creating fonts. Producing TeX
- documents involves a series of steps, including editing the
- document, running TeX itself, and processing TeX's output
- in various ways.</p>
-
- <p>Over the years, TeX has been made available on almost
- every computer platform<a id="id2857542" class="indexterm"
- name="id2857542"></a>, so it is probably available for the
- computer system that you use. Compiling TeX on different
- systems has been possible, in large part, because TeX is a
- text formatter and not a word processor. Unlike a word
- processor, TeX never deals directly with displaying text on
- the screen or interacting with input from the keyboard
- (except in a very basic way). These features of an
- application are typically the most difficult to port from
- one system to another.</p>
-
- <p>Beyond the technical details that make translation from
- one system to another possible, Donald Knuth<a
- id="id2857571" class="indexterm" name="id2857571"></a>
- added an important stipulation to the free distribution of
- TeX: in order for any program to be called
- &#8220;TeX,&#8221; it must pass a rigorous test suite<a
- id="id2857586" class="indexterm" name="id2857586"></a>.
- This means that the TeX you use behaves exactly like the
- TeX I use.<sup>[<a id="id2857595" name="id2857595"
- href="#ftn.id2857595">2</a>]</sup> This feature has
- contributed greatly to TeX's success. It means that a large
- community of TeX users can transparently share<a
- id="id2857615" class="indexterm" name="id2857615"></a>
- documents.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2857628"
- name="id2857628"></a>TeX for Beginners</h2>
- </div>
- </div>
-
- <p>If you are already familiar with TeX, you may find some
- of the material in this section repetitive. If so, just
- skim it quickly. This section will help you understand how
- TeX interprets the things you type into your input file.
- When you understand the concepts discussed here, you'll be
- ready to write really, really simple documents in TeX.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.tex.controlsequences"
- name="sec.tex.controlsequences"></a>Boxes and
- Glue</h3>
- </div>
- </div>
- <a id="boxes.start" class="indexterm"
- name="boxes.start"></a>
-
- <p>Despite the apparent complexity of TeX's job, it uses
- a very simple metaphor: all typographic elements are
- boxes<a id="id2857670" class="indexterm"
- name="id2857670"></a>. The simplest boxes, individual
- characters<a id="id2857681" class="indexterm"
- name="id2857681"></a><a id="id2857691" class="indexterm"
- name="id2857691"></a> have a set shape defined by the
- font they come from. There are three parameters that
- define a box: width<a id="id2857704" class="indexterm"
- name="id2857704"></a><a id="id2857714" class="indexterm"
- name="id2857714"></a>, height<a id="id2857725"
- class="indexterm" name="id2857725"></a><a id="id2857735"
- class="indexterm" name="id2857735"></a>, and depth<a
- id="id2857744" class="indexterm" name="id2857744"></a><a
- id="id2857754" class="indexterm" name="id2857754"></a>.
- The distinction between height and depth is a bit subtle.
- When a row of characters is typeset, every character
- rests on an imaginary line called the <span
- class="emphasis"><em>baseline</em></span>. Some
- characters, like the lowercase &#8220;g,&#8221; descend
- below the baseline<a id="id2857774" class="indexterm"
- name="id2857774"></a>. The distance from the baseline to
- the top of a box is its height; the distance from the
- baseline to the bottom is its depth.</p>
-
- <p>Figure&#160;<a href="ch01.html#fig.charbox"
- title="Figure&#160;1.1.&#160;The Letters g and h inside their boxes.">
- Figure&#160;1.1</a> shows the character boxes formed by
- the Computer Modern<a id="id2857800" class="indexterm"
- name="id2857800"></a> Roman letters &#8220;g&#8221; and
- &#8220;h.&#8221; The <span
- class="emphasis"><em>x-y</em></span> distance of each box
- is its height and the <span
- class="emphasis"><em>y-z</em></span> distance is its
- depth. The <span class="emphasis"><em>reference
- point</em></span><a id="id2857830" class="indexterm"
- name="id2857830"></a> of the box, marked with an <span
- class="emphasis"><em>r</em></span>, is on the leftmost
- edge of the box where the height and depth meet.
- Characters that have no <span
- class="emphasis"><em>descenders<a id="id2857848"
- class="indexterm" name="id2857848"></a></em></span> (no
- elements that go below the baseline), have a depth of
- zero. TeX uses the character box metrics, but font
- designers are free to allow glyphs to extend outside the
- box (for example, at the top of the &#8220;g&#8221;).</p>
-
- <div class="figure">
- <a id="fig.charbox" name="fig.charbox"></a>
-
- <p class="title"><b>Figure&#160;1.1.&#160;The Letters
- &#8220;g&#8221; and &#8220;h&#8221; inside their
- boxes.</b></p>
-
- <div class="mediaobject">
- <img src="figures/g-h.png"
- alt="The Letters 'g' and 'h' inside their boxes" />
- </div>
- </div>
-
- <p>The following paragraph demonstrates how TeX uses the
- metrics from the physical dimensions of each character to
- build word, line, and paragraph boxes.</p>
-
- <p class="box">TeX &#8220;glues&#8221;<a id="id2857937"
- class="indexterm" name="id2857937"></a> character boxes
- together to form words. When boxes are joined, they are
- always joined so their reference points are horizontally
- aligned as shown in <a href="ch01.html#ex.csexample"
- title="Example&#160;1.1.&#160;An Example of a TeX Document">
- Example&#160;1.1</a>.<sup>[<a id="id2857956"
- name="id2857956" href="#ftn.id2857956">3</a>]</sup>
- Character-boxes (like <span class="box">t</span><span
- class="box">h</span><span class="box">i</span><span
- class="box">s</span>) are joined to form words,
- word-boxes<a id="id2857992" class="indexterm"
- name="id2857992"></a> (like <span
- class="box">this</span>) are joined to form lines, and
- line-boxes<a id="id2858011" class="indexterm"
- name="id2858011"></a> form paragraphs. TeX accomplishes
- the task of forming a justified paragraph by allowing the
- glue between words to stretch<a id="id2858026"
- class="indexterm" name="id2858026"></a> and shrink<a
- id="id2858037" class="indexterm" name="id2858037"></a> a
- little bit and by occasionally breaking the glue between
- characters to insert a hyphen. Although the rules are
- slightly different, TeX builds a page out of vertical
- boxes (paragraphs, figures, etc.) in an analogous
- manner.</p>
-
- <p>This is a very generalized overview. In reality, a lot
- of subtlety is required to capture all of the nuances of
- typographical appearance.</p>
- <a id="id2858059" class="indexterm" name="id2858059"></a>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2858068"
- name="id2858068"></a>Control Sequences</h3>
- </div>
- </div>
-
- <p>A <span class="emphasis"><em>control sequence<a
- id="id2858081" class="indexterm"
- name="id2858081"></a></em></span> is a special
- &#8220;word&#8221; that you put in your document. These
- extra words are instructions for TeX, and they do not
- usually appear in your typeset document. Example&#160;<a
- href="ch01.html#ex.csexample"
- title="Example&#160;1.1.&#160;An Example of a TeX Document">
- Example&#160;1.1</a> shows a contrived example of a TeX
- document that uses several control sequences.</p>
-
- <div class="example">
- <a id="ex.csexample" name="ex.csexample"></a>
-
- <p class="title"><b>Example&#160;1.1.&#160;An Example
- of a TeX Document</b></p>
-<pre class="screen">
-\def\ora{O'Reilly \&amp; Associates}
-\font\orafont=grlg10
-\parskip=\baselineskip
-\parindent=0pt
-\pageno=5
-This book is published by \ora in
-the \textit{Nutshell} series.
-\bye
-</pre>
- </div>
-
- <p>In most macro packages, a control sequence is a
- backslash followed by a sequence of letters.<sup>[<a
- id="id2858135" name="id2858135"
- href="#ftn.id2858135">4</a>]</sup> TeX is case-sensitive,
- so the control sequence \large is different from \Large
- (these control sequences switch to large and very large
- fonts in the LaTeX macro package). Control sequences end
- with the first non-letter, even if it isn't a space. For
- example, \parskip0pt is the control sequence \parskip
- followed by <tt>0pt</tt>. This control sequence tells TeX
- to insert zero points of extra space between
- paragraphs.</p>
-
- <p>Unless instructed otherwise (with control sequences),
- TeX builds rectangular paragraphs out of lines of words.
- Changing fonts, building tables, and typesetting
- mathematical equations<a id="id2858193" class="indexterm"
- name="id2858193"></a> are examples of situations in your
- document where TeX needs extra information.</p>
-
- <p>The number of control sequences used in a TeX document
- may seem overwhelming at first. Luckily, every control
- sequence falls into one of several categories:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">Macro control
- sequences</span></dt>
-
- <dd>
- <p>Macro control sequences<a id="id2858228"
- class="indexterm" name="id2858228"></a> associate a
- name with an arbitrary string of text (including
- other control sequences). They are interpreted by
- replacing the control sequence with the text of its
- definition.<sup>[<a id="id2858243" name="id2858243"
- href="#ftn.id2858243">5</a>]</sup></p>
-
- <p>Macro control sequences are the root of TeX's
- tremendous flexibility. By defining control
- sequences with meaningful names, like \chapter and
- \footnote, TeX can present a reasonably simple
- interface to the user. By redefining those control
- sequences, the typeset output can be modified
- without requiring you to retype large quantities of
- text.</p>
-
- <p>In <a href="ch01.html#ex.csexample"
- title="Example&#160;1.1.&#160;An Example of a TeX Document">
- Example&#160;1.1</a>, the macro control sequence
- \ora is defined as a shortcut for typing
- &#8220;O'Reilly &amp; Associates.&#8221; This is a
- simple example of how a macro control sequence can
- be used.</p>
- </dd>
-
- <dt><span class="term">Font control sequences<a
- id="id2858301" class="indexterm"
- name="id2858301"></a></span></dt>
-
- <dd>
- <p>In <a href="ch01.html#ex.csexample"
- title="Example&#160;1.1.&#160;An Example of a TeX Document">
- Example&#160;1.1</a>, the line \font\orafont=grlg10
- creates a font control sequence called \orafont.
- When \orafont is used, TeX will begin typesetting
- in the font <tt>grlg10</tt>. The name of the font,
- <tt>grlg10</tt> in this case, refers to an external
- file that contains font metric information. Fonts
- are discussed in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.</p>
- </dd>
-
- <dt><span class="term">Registers</span></dt>
-
- <dd>
- <p>Registers<a id="id2858391" class="indexterm"
- name="id2858391"></a> are like variables in a
- programming language. They hold a single value of a
- particular type. Many types of values can be
- stored: numbers (also called &#8220;count&#8221;
- values because they are simple counting numbers
- like 1, 2, 17, or -5), dimensions (also called
- &#8220;lengths&#8221;; they are distances like
- 3.5pt or 2in), boxes, glue, and token lists (an
- internal representation of your document used by
- TeX).<sup>[<a id="id2858415" name="id2858415"
- href="#ftn.id2858415">6</a>]</sup></p>
-
- <p>If you are unfamiliar with computer programming,
- think of these registers as place holders. When TeX
- needs to save a piece of information, like how much
- space should be inserted between paragraphs, it
- stores the information in a register. When the
- information is needed again, in this case when TeX
- has finished typesetting one paragraph and is about
- to start another, it can retrieve that information
- from the register. Registers are usually given
- names that at least hint at how they are used. This
- helps people read and modify the rules that TeX
- uses to typeset documents.</p>
-
- <p>In Example&#160;<a href="ch01.html#ex.csexample"
- title="Example&#160;1.1.&#160;An Example of a TeX Document">
- Example&#160;1.1</a>, \parskip, \baselineskip, and
- \parindent are dimension registers. The \pageno
- control sequence is a count register.</p>
-
- <p>There are only 256 registers of each type. The
- type of information (number, dimension, or token
- list) that a register can contain is defined when
- the control sequence is created. Once a variable
- like \parindent is created to hold a dimension, it
- can never hold a number or a token list.<sup>[<a
- id="id2858485" name="id2858485"
- href="#ftn.id2858485">7</a>]</sup></p>
-
- <p>Registers may seem unnecessary now that you know
- about macro control sequences, which can store
- arbitrary information. However, registers differ
- from macro control sequences not only in the types
- of values they can hold, but also in the types of
- operations that can be performed on them. There is
- a TeX command called \advance, for example, that
- can increment the value stored in a register by an
- arbitrary amount. You can't \advance a macro
- control sequence.</p>
- </dd>
-
- <dt><span class="term">Built-in commands</span></dt>
-
- <dd>
- <p>A number of control<a id="id2858535"
- class="indexterm" name="id2858535"></a> sequences
- are built into TeX. These &#8220;primitive&#8221;
- operations form the basis for all higher-level
- functionality. There are a wide variety of control
- sequences of this type. Everything that can be done
- in TeX can be reduced to a sequence of primitive
- operations.</p>
-
- <p>There is no way to know, simply by inspection,
- if a control sequence is one of the built-in
- sequences or not. Luckily, it doesn't matter very
- often; it really only matters when you are writing
- complex macros.</p>
-
- <p>The \font control sequence in <a
- href="ch01.html#ex.csexample"
- title="Example&#160;1.1.&#160;An Example of a TeX Document">
- Example&#160;1.1</a> is a built-in control
- sequence. So is \advance, mentioned above.</p>
- </dd>
- </dl>
- </div>
-
- <p>The number and kind of control sequences available
- depends upon the macro package that you are using. (Macro
- packages are discussed fully in Chapter&#160;<a
- href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.)
- For the rest of this chapter, the default settings of
- Plain TeX<a id="id2858616" class="indexterm"
- name="id2858616"></a> are assumed.<sup>[<a id="id2858627"
- name="id2858627" href="#ftn.id2858627">8</a>]</sup> There
- are other macro packages, like LaTeX, Lollipop, and
- TeXinfo, which have different default values.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.textformVSwordproc"
- name="sec.textformVSwordproc"></a>Special
- Characters</h3>
- </div>
- </div>
- <a id="id2858665" class="indexterm" name="id2858665"></a>
-
- <p>In addition to control sequences, TeX reserves several
- characters <a id="id2858675" class="indexterm"
- name="id2858675"></a> for special purposes. Most of them
- do not occur very frequently in ordinary text, but you
- must be aware of them because there will be very
- surprising consequences if you use them incorrectly.</p>
-
- <p>Table&#160;<a href="ch01.html#tab.activechars"
- title="Table&#160;1.1.&#160;Special Characters in Plain TeX ">
- Table&#160;1.1</a> shows all of the special characters in
- Plain TeX.<sup>[<a id="id2858704" name="id2858704"
- href="#ftn.id2858704">9</a>]</sup> Most of these
- characters are special in other macro packages as well.
- Font-specific characters are not reserved by TeX, but
- they don't produce the results you would expect when
- typeset in Computer Modern because of the way TeX expects
- fonts to be laid out. Fonts are discussed in detail in
- Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.</p>
-
- <div class="table">
- <a id="tab.activechars" name="tab.activechars"></a>
-
- <p class="title"><b>Table&#160;1.1.&#160;Special
- Characters in Plain TeX <a id="id2858750"
- class="indexterm" name="id2858750"></a></b></p>
-
- <table
- summary="Special Characters in Plain TeX charactersspecialtypesetting"
- border="1">
- <colgroup>
- <col align="center" />
- <col />
- </colgroup>
-
- <thead>
- <tr>
- <th align="center">Character</th>
-
- <th>Meaning</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="center">#</td>
-
- <td>Used for parameter definition in macros and
- tables</td>
- </tr>
-
- <tr>
- <td align="center">$</td>
-
- <td>Toggles in and out of math mode</td>
- </tr>
-
- <tr>
- <td align="center">%</td>
-
- <td>A comment (TeX ignores everything to the end
- of the line)</td>
- </tr>
-
- <tr>
- <td align="center">&amp;</td>
-
- <td>The column separator in tables</td>
- </tr>
-
- <tr>
- <td align="center">~</td>
-
- <td>The active space (an unbreakable space)</td>
- </tr>
-
- <tr>
- <td align="center">_</td>
-
- <td>Marks a subscript (valid only in math
- mode)</td>
- </tr>
-
- <tr>
- <td align="center">^</td>
-
- <td>Marks a superscript (valid only in math
- mode)</td>
- </tr>
-
- <tr>
- <td align="center">\</td>
-
- <td>Begins a control sequence</td>
- </tr>
-
- <tr>
- <td align="center">{</td>
-
- <td>Begins a group</td>
- </tr>
-
- <tr>
- <td align="center">}</td>
-
- <td>Ends a group</td>
- </tr>
-
- <tr>
- <td align="center">|</td>
-
- <td>Produces an em-dash (&#8212;)
- (font-specific)</td>
- </tr>
-
- <tr>
- <td align="center">&lt;</td>
-
- <td>Produces an upside down exclamation mark (¡)
- (font-specific)</td>
- </tr>
-
- <tr>
- <td align="center">&gt;</td>
-
- <td>Produces an upside down question mark (¿)
- (font-specific)</td>
- </tr>
-
- <tr>
- <td align="center">"</td>
-
- <td>Incorrect for quoted text; use &#8220; and
- &#8221; instead (font-specific)</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>It is best to avoid these characters until you are
- familiar with TeX. If you need to typeset<a
- id="id2859024" class="indexterm" name="id2859024"></a>
- one of these characters, <a href="ch01.html#tab.acttype"
- title="Table&#160;1.2.&#160;How to Typeset Special Characters">
- Table&#160;1.2</a> shows what to put in your document.
- You should also avoid characters outside the standard
- printable ASCII character set<a id="id2859048"
- class="indexterm" name="id2859048"></a> (characters with
- ASCII values below 32 and above 126). TeX can be
- configured to accept characters outside the printable
- ASCII range, to support non-English languages, for
- example, but it is not configured to do so &#8220;out of
- the box.&#8221; Chapter&#160;<a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a>, <span class="emphasis"><em><a
- href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a></em></span>, discusses the issues of
- typesetting in different languages.</p>
-
- <div class="table">
- <a id="tab.acttype" name="tab.acttype"></a>
-
- <p class="title"><b>Table&#160;1.2.&#160;How to Typeset
- Special Characters<a id="id2859097" class="indexterm"
- name="id2859097"></a></b></p>
-
- <table
- summary="How to Typeset Special Charactersspecial characterstypesetting"
- border="1">
- <colgroup>
- <col align="center" />
- <col />
- </colgroup>
-
- <thead>
- <tr>
- <th align="center">To Get</th>
-
- <th>Put This in Your Document</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="center">#</td>
-
- <td>\#</td>
- </tr>
-
- <tr>
- <td align="center">$</td>
-
- <td>\$</td>
- </tr>
-
- <tr>
- <td align="center">%</td>
-
- <td>\%</td>
- </tr>
-
- <tr>
- <td align="center">&amp;</td>
-
- <td>\&amp;</td>
- </tr>
-
- <tr>
- <td align="center">&#8220;</td>
-
- <td>``</td>
- </tr>
-
- <tr>
- <td align="center">&#8221;</td>
-
- <td>''</td>
- </tr>
-
- <tr>
- <td align="center">~</td>
-
- <td>\~</td>
- </tr>
-
- <tr>
- <td align="center">{</td>
-
- <td>$\{$</td>
- </tr>
-
- <tr>
- <td align="center">}</td>
-
- <td>$\}$</td>
- </tr>
-
- <tr>
- <td align="center">&lt;</td>
-
- <td>$&lt;$</td>
- </tr>
-
- <tr>
- <td align="center">&gt;</td>
-
- <td>$&gt;$</td>
- </tr>
-
- <tr>
- <td align="center">|</td>
-
- <td>$|$</td>
- </tr>
-
- <tr>
- <td align="center">_</td>
-
- <td>$\underbar{\hbox{\ }}$</td>
- </tr>
-
- <tr>
- <td align="center">^</td>
-
- <td>$\hat{\hbox{ }}$</td>
- </tr>
-
- <tr>
- <td align="center">\</td>
-
- <td>$\backslash$</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <div class="sidebar">
- <p>Some of the suggestions in <a
- href="ch01.html#tab.acttype"
- title="Table&#160;1.2.&#160;How to Typeset Special Characters">
- Table&#160;1.2</a> will not always produce exactly what
- you want. The entry for &#8220;~&#8221; really produces
- a tilde accent, not a tilde character and the entries
- for &#8220;{&#8221; through &#8220;\&#8221; all get the
- actual characters from TeX's math fonts. The Computer
- Modern text fonts don't include these characters so it
- is necessary to get them from the math fonts. However,
- if you are using PostScript or other kinds of fonts,
- you may very well have curly braces, angle brackets,
- underscores, etc. in the font. You can access these
- characters directly with the \char primitive. I
- strongly recommend that you always define macros for
- this purpose, so that you can easily switch to some
- other method if you change fonts. Introducing \char
- primitives makes your document less portable. To use
- the \char primitive, simply put the decimal ASCII value
- of the character that you want to print. For example,
- this book is typeset with PostScript fonts that include
- a backslash character at position 92, so I defined \bs
- to print a backslash like this:</p>
-<pre class="screen">
-\def\bs{\char92\relax}
-</pre>
-
- <p>Using \relax after the decimal value assures that
- TeX won't get confused if I put a backslash in front of
- other digits like this \bs300dpi.</p>
- </div>
-
- <p>The braces<a id="id2859474" class="indexterm"
- name="id2859474"></a> &#8220;{&#8221; and &#8220;}&#8221;
- are a very special case. TeX uses curly braces to delimit
- arguments and make changes (like switching fonts) that
- are local to a small section of the document. These are
- called <span class="emphasis"><em>grouping characters<a
- id="id2859497" class="indexterm"
- name="id2859497"></a></em></span><a id="id2859504"
- class="indexterm" name="id2859504"></a> in TeX jargon.
- For example, to typeset a single word in boldface, you
- put {\bf word} into your input file. The \bf control
- sequence switches to boldface type, and the curly braces
- localize the effect to the single word <span
- class="bold">word</span>. As a result, it is very
- important that you avoid braces (except when you use them
- as delimiters) and that you carefully match all opening
- and closing braces. One of the most common errors in TeX
- is to forget a closing brace.</p>
-
- <p>One last special character is the blank space<a
- id="id2859543" class="indexterm" name="id2859543"></a>.
- For the most part, TeX doesn't care how you space your
- lines of text. Any space that occurs is simply a word
- break to TeX, and inserting multiple spaces doesn't
- influence how TeX typesets the line. TeX also considers
- the end of a line an implicit space. If you are trying to
- control the layout of your input text and want to break a
- line without introducing a space, place a comment
- character (% in most macro packages)<a id="id2859552"
- class="indexterm" name="id2859552"></a> at the very end
- of the line. If the last character of a line is the
- comment character, TeX ignores the line break and all the
- leading spaces on the following line. This allows you to
- use indentation<a id="id2859574" class="indexterm"
- name="id2859574"></a> to make your input file more
- readable. \goodbreak</p>
-
- <p>For example, the following lines in your input
- file:</p>
-<pre class="screen">
-&#8220;This is some ex
- ample text.&#8221;
-</pre>
-
- <p>and this line:</p>
-<pre class="screen">
-&#8220;This is some example text.&#8221;
-</pre>
-
- <p>both produce:</p>
-
- <div class="literallayout">
- <p>
- &#8220;This&#160;is&#160;some&#160;example&#160;text.&#8221;</p>
- </div>
-
- <p>in your typeset document.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2859644"
- name="id2859644"></a>Text Formatting Versus Word
- Processing</h2>
- </div>
- </div>
-
- <p>For many people, writing documents with a computer
- implies using a word processor like WordPerfect<a
- id="id2859660" class="indexterm" name="id2859660"></a> or
- Microsoft Word<a id="id2859674" class="indexterm"
- name="id2859674"></a>.<a id="id2859683" class="indexterm"
- name="id2859683"></a><a id="id2859696" class="indexterm"
- name="id2859696"></a> The word processing program controls
- every aspect of what you do: it's where you type your text,
- where you see what it will look like, where you print, and
- where you do everything else. Some of these environments,
- the so-called WYSIWYG<a id="id2859715" class="indexterm"
- name="id2859715"></a> (what-you-see-is-what-you-get)
- programs, attempt to show you what the printed document
- will actually look like <span
- class="emphasis"><em>while</em></span> you edit it.<sup>[<a
- id="id2859730" name="id2859730"
- href="#ftn.id2859730">10</a>]</sup></p>
-
- <p>If WYSIWYG environments are what you're used to, or what
- you expect, TeX's approach may seem very strange at first
- because TeX is a <span class="emphasis"><em>text
- formatter</em></span>,<a id="id2859754" class="indexterm"
- name="id2859754"></a><a id="id2859767" class="indexterm"
- name="id2859767"></a> not a word processor. Instead of
- trying to show you what your document will look like while
- you type, TeX expects you to do all the typing somewhere
- else, and then pass it a source file containing all of your
- text plus control sequences that tell TeX how you'd like it
- printed.</p>
-
- <p>In <span class="emphasis"><em>The Psychology of Everyday
- Things</em></span>&#160;[<a
- href="bi01.html#dn:psyeveryday">dn:psyeveryday</a>], Donald
- Norman<a id="id2859798" class="indexterm"
- name="id2859798"></a> describes these two modes of
- interaction as first person and third person. First person
- interaction provides the user with the ability to directly
- manipulate the elements of a task, whether it's flying an
- airplane or resizing text. Third person interaction, on the
- other hand, occurs where the user is expected to type
- commands to the computer in an appropriate command
- language; the shell prompt is a good example of third
- person interaction.</p>
-
- <p>Is first person interaction really better? Well, it
- depends. Norman writes, &#8220;Although they [WYSIWYG
- environments] are often easy to use, fun, and entertaining,
- it is often difficult to do a really good job with
- them.&#8221; The problem which arises is that the user is
- required to do the task, and he or she may not be very good
- at it. Third person systems are better when the computer
- program can be trusted to do a better job of the task than
- the user.</p>
-
- <p>Is TeX really better than a word processor? Well, it
- depends on the task and the person doing it. TeX probably
- isn't better for designing one page flyers with lots of
- fonts and graphics (although I've done it). But for longer
- documents, TeX offers all of these advantages:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>TeX has a precise understanding of the rules of
- typesetting,<a id="id2859861" class="indexterm"
- name="id2859861"></a> so you don't have to.</p>
- </li>
-
- <li>
- <p>Predefined styles allow experts to extend (or
- bend) the rules of typesetting without burdening the
- user.</p>
- </li>
-
- <li>
- <p>Journals and magazines can achieve consistency of
- appearance much more reliably because the consistency
- is in the style files.</p>
- </li>
-
- <li>
- <p>TeX runs on cheap systems (old PCs with monochrome
- monitors and no graphics capability, for
- example).</p>
- </li>
-
- <li>
- <p>Although complex and difficult to learn, TeX
- offers incredibly flexible table construction
- tools.</p>
- </li>
-
- <li>
- <p>Few, if any, word processors can provide running
- headers and footers as flexibly as TeX. Imagine the
- task of writing a dictionary: the left and right hand
- side headers change on each page, each time a new
- entry is added.</p>
- </li>
-
- <li>
- <p>TeX offers flexible bibliography layouts.</p>
- </li>
-
- <li>
- <p>TeX is extensible.<a id="id2859945"
- class="indexterm" name="id2859945"></a> Its behavior
- can be modified by defining new commands and
- environments without changing the actual program.</p>
- </li>
- </ul>
- </div>
-
- <p>There are some other good reasons to separate document
- creation from text formatting:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Documents are portable.<a id="id2859978"
- class="indexterm" name="id2859978"></a> Because the
- source files are just plain text without any
- nonprintable characters, they can easily be copied
- from one system to another.</p>
- </li>
-
- <li>
- <p>TeX is portable. TeX runs everywhere. You can
- process your documents with TeX on unix workstations;
- personal computers running MS-DOS, OS/2, and Windows;
- IBM mainframes running VM/CMS; workstations running
- VAX/VMS; Macintoshes; Amigas; Ataris; and just about
- every other computer with a reasonable amount of
- memory. And the typeset output will be the same! This
- adds another dimension of portability to your
- documents.</p>
- </li>
-
- <li>
- <p>TeX is free. You can afford to have it on every
- system you use. Several sources of TeX software are
- listed in the preface of this book.</p>
- </li>
-
- <li>
- <p>TeX allows you to separate markup and output.
- Logical divisions in the text (chapters, sections,
- itemized lists, etc.) are identified by control
- sequences. An entirely different page layout can
- result from simply changing the definition of a few
- control sequences.</p>
-
- <p>This means that the look of your documents can be
- changed (to fit the style guidelines of a particular
- journal or publisher, for example) without changing
- the text of your documents at all.</p>
- </li>
-
- <li>
- <p>Plain text files are easier to manipulate with
- other tools than specially encoded word processor
- files are. This means that you can use standard
- utilities on your documents: revision control, grep,
- shell scripts, etc. This is a less common practice in
- non-unix environments, but it is still
- convenient.</p>
- </li>
-
- <li>
- <p>You can continue to use your favorite editing
- tools. The extent to which you find this advantageous
- is dependent, naturally, on the extent to which you
- have a favorite editing program. Nevertheless, this
- can be a considerable advantage. For example, users
- familiar with <b>emacs</b><a id="id2860077"
- class="indexterm" name="id2860077"></a> can continue
- to rely on all of the features they are used to,
- including interactive spellchecking, access to online
- services like Webster's dictionary, customized editor
- macros, and convenient services like reading
- mail.</p>
- </li>
-
- <li>
- <p>You get better looking output. TeX gives you far
- more precise control over the placement of elements
- on the page than most word processing programs. And
- TeX is very intelligent about typesetting (paragraph
- breaking, kerning<a id="id2860098" class="indexterm"
- name="id2860098"></a>, ligatures<a id="id2860112"
- class="indexterm" name="id2860112"></a>, etc.).</p>
- </li>
- </ul>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.howtexworks"
- name="sec.howtexworks"></a>What About Desktop
- Publishing?</h3>
- </div>
- </div>
-
- <p>Desktop publishing systems<a id="id2860137"
- class="indexterm" name="id2860137"></a><a id="id2860150"
- class="indexterm" name="id2860150"></a> like Ventura
- Publisher<a id="id2860171" class="indexterm"
- name="id2860171"></a> and Aldus PageMaker<a
- id="id2860185" class="indexterm" name="id2860185"></a>
- are noted for their ability to incorporate multiple fonts
- and graphics into a document. As word processors become
- more sophisticated, the line between word processing and
- desktop publishing is becoming blurry.</p>
-
- <p>This book shows you many ways that TeX can provide
- access to the same sophisticated features. TeX can
- incorporate pictures and figures in a number of ways
- (just take a look at the way I've wrapped text around
- this kiwi),<sup>[<a id="id2860201" name="id2860201"
- href="#ftn.id2860201">11</a>]</sup> and TeX can use
- almost any font that another program can use---it can
- certainly use <span class="emphasis"><em>all</em></span>
- of the popular types of fonts. Like typical word
- processors, desktop publishing programs force you to use
- a single application to create your entire document, and
- they lack the flexibility required to combine just the
- pieces that you want. All of the advantages of text
- formatting over word processing also apply to desktop
- publishing programs. I'll grant, however, that WYSIWYG
- environments are easier for first-time users. But that
- doesn't make them better, it just makes them more
- popular.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2860232"
- name="id2860232"></a>What About troff?</h3>
- </div>
- </div>
-
- <p><b>troff</b><a id="id2860245" class="indexterm"
- name="id2860245"></a> <a id="id2860259" class="indexterm"
- name="id2860259"></a> is the &#8220;other&#8221; text
- formatting system. If you've ever tried to read a unix
- reference page without formatting it first, you've seen
- <b>troff</b>. For a long time it was distributed as part
- of all unix systems. Now it is more likely an extra-cost
- option. The Free Software Foundation's <a id="id2860290"
- class="indexterm" name="id2860290"></a><b>groff</b><a
- id="id2860303" class="indexterm" name="id2860303"></a>
- processor is a free, <b>troff</b>-compatible system.</p>
-
- <p>On the surface, it is easier to compare TeX and troff
- than to compare TeX to the other document preparation
- systems described in this chapter. In reality, the
- differences are subtle: TeX and troff have the same
- general paradigm; they are equally powerful to a large
- extent, and both have advantages and disadvantages.</p>
-
- <p><b>troff</b> is similar to TeX in many ways. Like TeX,
- troff processes a plain text file and produces a typeset
- document. TeX and troff differ in the way that formatting
- information is inserted into the text. TeX uses control
- sequences<a id="id2860356" class="indexterm"
- name="id2860356"></a>, where troff uses a mixture of
- control sequences<sup>[<a id="id2860372" name="id2860372"
- href="#ftn.id2860372">12</a>]</sup> and &#8220;dot&#8221;
- commands (lines of text that begin with a period and
- contain typesetting commands).</p>
-
- <p>Although I am inclined to say that troff documents are
- far more cryptic than TeX documents, I am certain that
- there are plenty of troff users who would disagree
- (strongly).</p>
-
- <p>Objectively, TeX handles mathematical typesetting<a
- id="id2860407" class="indexterm" name="id2860407"></a>
- far better than troff and probably has better support for
- multilingual documents<a id="id2860424" class="indexterm"
- name="id2860424"></a><a id="id2860434" class="indexterm"
- name="id2860434"></a>. The <b>nroff</b><a id="id2860451"
- class="indexterm" name="id2860451"></a> processor, which
- produces plain text output from a troff document, at one
- time provided a strong argument in favor of troff for
- typesetting documents required in both typeset and plain
- text formats. However, the TeXinfo<a id="id2860469"
- class="indexterm" name="id2860469"></a> macro package for
- TeX has largely defeated that argument. In troff's
- defense, TeXinfo is very, very different from other TeX
- macro packages, so it really is necessary to plan ahead
- and learn a very different set of macros to typeset both
- plain text and typeset documents with TeXinfo.
- Chapter&#160;<a href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation">Chapter&#160;10</a>,
- <span class="emphasis"><em><a href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation">Chapter&#160;10</a></em></span>,
- discusses this issue further.</p>
-
- <p>In my experience, there is more free support for TeX
- than troff. TeX is supported by a large community of
- users actively producing new, useful document-preparation
- formats, styles, and tools. In addition, TeX is more
- widely available than troff: a TeX port exists for almost
- every practical computer system, whereas troff is still
- mostly confined to unix systems (although the Free
- Software Foundation's <b>groff</b> package has been
- ported to similar systems like MS-DOS, Windows NT, and
- OS/2).</p>
-
- <p>The following fragments show a side-by-side comparison
- of TeX commands, on the left, and troff commands, on the
- right:</p>
-<pre class="screen">
-\begin{figure} .(z
- \begin{center} .hl
- \hrule Text to be floated.
- \vspace{8pt} .sp
- Text to be floated. .ce
- \hrule .hl
- \caption{Example figure...} Figure \*[fig]: Example figure...
- \vspace{8pt} .)z
- \end{center}
-\end{figure}
-</pre>
-
- <p>Both examples produce a floating figure that looks
- like this:</p>
-
- <div class="figure">
- <a id="id2860574" name="id2860574"></a>
-
- <p class="title"><b>Figure&#160;1.2.&#160;Example
- figure produced by both TeX and troff</b></p>
-
- <div class="informaltable">
- <table width="100%" border="1">
- <colgroup>
- <col />
- </colgroup>
-
- <tbody>
- <tr>
- <td>Text to be floated.</td>
- </tr>
- </tbody>
- </table>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2860619"
- name="id2860619"></a>What About SGML?</h3>
- </div>
- </div>
-
- <p>The Standard Generalized Markup Language (SGML)<a
- id="id2860629" class="indexterm" name="id2860629"></a> is
- a document description language. SGML aims to separate
- the content of a document from its presentation. In other
- words, SGML identifies the features of a document
- (chapter headings, paragraphs, etc.) without specifying
- how they are to be presented.</p>
-
- <p>This means that all SGML documents must interact with
- a document formatter of some sort. Many people are
- finding that TeX is a natural choice when selecting a
- document formatter for their SGML environment. In fact,
- LaTeX<a id="id2860647" class="indexterm"
- name="id2860647"></a> already provides many SGML-like
- commands because it was designed to separate markup from
- presentation. One of the specific goals of an effort
- (currently underway) to develop a new version of LaTeX is
- to make SGML and LaTeX work together easily, cleanly, and
- efficiently. For more information about the goals of this
- project and information about what you can do to help,
- please read <span class="emphasis"><em>The LaTeX3
- Project</em></span>&#160;[<a
- href="bi01.html#l3:project">l3:project</a>].</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2860690"
- name="id2860690"></a>How TeX Works</h2>
- </div>
- </div>
-
- <p>A functioning TeX system<a id="id2860698"
- class="indexterm" name="id2860698"></a> in which you are
- producing documents of medium size and complexity is really
- a collection of tools and files that are related to each
- other in well defined (if somewhat subtle) ways.</p>
-
- <p>One of the fundamental goals of this book is to shed
- light on these relationships and allow you to put together
- a TeX system that quickly and easily does the jobs you need
- to accomplish.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="subsubsec.runningtex"
- name="subsubsec.runningtex"></a>TeXing a Simple
- Document</h3>
- </div>
- </div>
-
- <p>This section briefly describes what you need to know
- about how TeX processes a simple document (that is, one
- that does not contain complex document elements like a
- table of contents, indexes, bibliographies, etc.).
- Figure&#160;<a href="ch01.html#fig.wholesimple"
- title="Figure&#160;1.3.&#160;A high-level view of TeX">Figure&#160;1.3</a>
- shows how the standard TeX tools fit together at the most
- basic level.</p>
-
- <div class="figure">
- <a id="fig.wholesimple" name="fig.wholesimple"></a>
-
- <p class="title"><b>Figure&#160;1.3.&#160;A high-level
- view of TeX</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.01.03.png" />
- </div>
- </div>
-
- <p>Figure&#160;<a href="ch01.html#fig.wholething"
- title="Figure&#160;1.4.&#160;High-level view of TeX including more detail">
- Figure&#160;1.4</a> expands on Figure&#160;<a
- href="ch01.html#fig.wholesimple"
- title="Figure&#160;1.3.&#160;A high-level view of TeX">Figure&#160;1.3</a>,
- showing additional tools and files that you'll often need
- to use.</p>
-
- <div class="figure">
- <a id="fig.wholething" name="fig.wholething"></a>
-
- <p class="title"><b>Figure&#160;1.4.&#160;High-level
- view of TeX including more detail</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.01.04.png" />
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2860862"
- name="id2860862"></a>Editing your document</h4>
- </div>
- </div>
-
- <p>The most tangible and important part of your TeX
- system is your document<a id="id2860872"
- class="indexterm" name="id2860872"></a>. This is the
- file (or files) in which you write down what you want
- to typeset with TeX. In addition to the actual text,
- you include control sequences to describe how you want
- the final text to appear (size, font, justification,
- etc.). The section &#8220;<a
- href="ch01.html#sec.texforbeginners"
- title="What Is TeX?">the section called &#8220;What Is
- TeX?&#8221;</a>&#8221; earlier in this chapter tells
- you briefly what goes into your document file.</p>
-
- <p>The most common way to create a document is with an
- editor<a id="id2860909" class="indexterm"
- name="id2860909"></a><a id="id2860916"
- class="indexterm" name="id2860916"></a><a
- id="id2860926" class="indexterm" name="id2860926"></a>,
- which can provide you with a number of features to make
- typing TeX documents easier. For example, an editor can
- help you insert common control sequences<a
- id="id2860940" class="indexterm" name="id2860940"></a>
- automatically, run TeX automatically (from within the
- editor), and keep you from making common mistakes (like
- typing a left brace, but not the matching right one).
- These features and how they work in editors including
- GNU Emacs, aucTeX, and Multi-Edit are described in
- Chapter&#160;<a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a>,
- <span class="emphasis"><em><a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a></em></span>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2860982"
- name="id2860982"></a>Running TeX</h4>
- </div>
- </div>
-
- <p>Once you have prepared your document file, it is
- time to run<a id="id2860991" class="indexterm"
- name="id2860991"></a><a id="id2861001"
- class="indexterm" name="id2861001"></a> the TeX program
- itself. This may not be as easy as it sounds. You need
- to determine the name of the TeX program at your site,
- to make sure all of the files TeX needs are available
- to it; you also need to specify the correct
- command-line options. Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>,
- describes everything you need to know.</p>
-
- <p>TeX may find errors in your document (places where
- TeX doesn't understand the instructions you used; not
- spelling or grammatical errors, unfortunately ;-).
- Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>
- also describes the most common errors you're likely to
- make and gives advice for interpreting error
- messages.</p>
-
- <p>If TeX is successful in formatting your document
- (i.e., your document doesn't contain any errors), it
- produces a <tt>DVI</tt> (DeVice Independent)<a
- id="id2861075" class="indexterm" name="id2861075"></a>
- file. The <tt>DVI</tt> file is a device-independent
- representation of the typeset output of your document.
- <tt>DVI</tt> files are transitory. Although there are a
- few programs that can manipulate them (to rearrange the
- order of the pages in the output, for example), most of
- the time you will immediately transform them into
- something else---either printed output or previewed
- output on the screen. (See the following section
- &#8220;<a href="ch01.html#subsubsec.printpreview"
- title="Using macros">the section called &#8220;Using
- macros&#8221;</a>.&#8221;)</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="subsubsec.printpreview"
- name="subsubsec.printpreview"></a>Using macros</h4>
- </div>
- </div>
-
- <p>The control sequences<a id="id2861139"
- class="indexterm" name="id2861139"></a> that you insert
- in your document are defined by a macro package<a
- id="id2861152" class="indexterm"
- name="id2861152"></a>.<sup>[<a id="id2861160"
- name="id2861160" href="#ftn.id2861160">13</a>]</sup>
- Macro packages are collections of TeX commands (macros)
- that extend TeX. Macro packages are frequently stored
- in format files, specially compiled versions of the
- macro package. The iniTeX<a id="id2861169"
- class="indexterm" name="id2861169"></a> program
- interprets all of the control sequences in a macro
- package to create a format file that TeX reads when it
- runs.</p>
-
- <p>Many macro packages are particularly effective in
- implementing particular document styles or supporting
- particular types of writing. Two of the most common are
- Plain TeX<a id="id2861194" class="indexterm"
- name="id2861194"></a> and LaTeX<a id="id2861205"
- class="indexterm" name="id2861205"></a>.
- Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>,
- describes Plain TeX, LaTeX, and a number of other macro
- packages that extend the power and ease of TeX.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2861241"
- name="id2861241"></a>Using fonts</h4>
- </div>
- </div>
-
- <p>One of TeX's strengths is its support for a myriad
- of predefined fonts<a id="id2861249" class="indexterm"
- name="id2861249"></a> and its ability to let you create
- fonts of your own. In addition to your document and the
- format file, when TeX runs it needs font information as
- well. This is provided in the form of a set of
- <tt>TFM</tt> (TeX Font Metric)<a id="id2861277"
- class="indexterm" name="id2861277"></a> files that tell
- TeX the size and shape (roughly speaking, at least) of
- each character, as well as some other information about
- how characters are related to each other.</p>
-
- <p>Historically, the MetaFont<a id="id2861292"
- class="indexterm" name="id2861292"></a> program was the
- way a TeX user created fonts. Like TeX itself, MetaFont
- is about ten years old. Ten years ago, it was a unique
- program that was indispensible for creating the type of
- output TeX produces. Today there are many competing
- font technologies, all of them more common than
- MetaFont, and MetaFont's role is diminishing. Many
- people use TeX today without ever using MetaFont at
- all. Nevertheless, MetaFont still has some importance,
- and we describe how to run and use it in
- Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>,
- <span class="emphasis"><em><a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a></em></span>.
- Because the standard fonts that come with TeX are still
- the fonts produced by MetaFont, it will also be
- mentioned elsewhere in this book.</p>
-
- <p>If you are writing complex documents, you may need
- to learn a lot about fonts and how to define and use
- them. Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>,
- tells you everything you need to know, including
- information about the New Font Selection Scheme, a new
- way of describing and selecting fonts in TeX.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2861369"
- name="id2861369"></a>Previewing or printing TeX
- documents</h4>
- </div>
- </div>
-
- <p>After you have produced a <tt>DVI</tt> file, as
- described in the section &#8220;<a
- href="ch01.html#subsubsec.runningtex"
- title="TeXing a Simple Document">the section called
- &#8220;TeXing a Simple Document&#8221;</a>,&#8221;
- later in this chapter, you run another program
- (generically called a DVI driver)<a id="id2861405"
- class="indexterm" name="id2861405"></a> to translate
- the <tt>DVI</tt> file so you can either preview or
- print your document. Driver programs need your
- <tt>DVI</tt> file and some collection of fonts (usually
- <tt>PK</tt> (packed)<a id="id2861442" class="indexterm"
- name="id2861442"></a><a id="id2861461"
- class="indexterm" name="id2861461"></a><a
- id="id2861469" class="indexterm" name="id2861469"></a>
- font files).<sup>[<a id="id2861489" name="id2861489"
- href="#ftn.id2861489">14</a>]</sup> Many different
- kinds of fonts are described in Chapter&#160;<a
- href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>.</p>
-
- <p>Chapter&#160;<a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a>,
- <span class="emphasis"><em><a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a></em></span>,
- tells you how to print<a id="id2861540"
- class="indexterm" name="id2861540"></a><a
- id="id2861546" class="indexterm" name="id2861546"></a>
- your documents and deal with the problems you may
- encounter using bitmapped or scalable fonts, printing
- pictures and figures, and other printing issues.</p>
-
- <p>Often you will want to look at your document before
- you actually print it. Because TeX is not a WYSIWYG
- system,<sup>[<a id="id2861567" name="id2861567"
- href="#ftn.id2861567">15</a>]</sup> you cannot do this
- until you have processed the <tt>DVI</tt> file. There
- are a number of good previewing products<a
- id="id2861597" class="indexterm"
- name="id2861597"></a><a id="id2861603"
- class="indexterm" name="id2861603"></a>, including
- xdvi<a id="id2861617" class="indexterm"
- name="id2861617"></a>, <b>dvimswin</b><a id="id2861634"
- class="indexterm" name="id2861634"></a>, and
- <b>dviscr</b><a id="id2861648" class="indexterm"
- name="id2861648"></a>, that let you look at your
- processed document on the screen before you decide
- whether to print it. See Chapter&#160;<a
- href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- <span class="emphasis"><em><a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a></em></span>,
- for complete information.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2861683"
- name="id2861683"></a>TeXing More Complex
- Documents</h3>
- </div>
- </div>
-
- <p>This section briefly describes how TeX processes a
- more complex document (that is, one that includes
- elements like a table of contents, indexes,
- bibliographies, etc.).</p>
-
- <p>Many TeX formats implement sophisticated
- cross-referencing schemes. Cross references<a
- id="id2861700" class="indexterm" name="id2861700"></a>
- may sound rather esoteric, but they occur frequently.
- Tables of contents, figure and table numbers, indexes,
- and bibliographic references are all flavors of cross
- referencing.</p>
-
- <p>Cross references make your document more complex
- because they require more information than is immediately
- available when TeX initially processes your document. For
- example, if you refer to a figure which occurs later in
- the document, TeX has no way of knowing what figure
- number to insert into the text at the point of the
- reference. These are called <span
- class="emphasis"><em>forward references</em></span><a
- id="id2861726" class="indexterm"
- name="id2861726"></a>.</p>
-
- <p>TeX macro packages that support cross referencing
- overcome the difficulty of forward references by
- requiring you to process your document more than once.
- Each time your document is processed, the necessary
- reference information is stored into a separate file. If
- that file exists when you process your document, the
- information saved <span class="emphasis"><em>last
- time</em></span> is loaded so that it is available <span
- class="emphasis"><em>this time</em></span>. The practical
- implication of this functionality is that documents with
- cross references frequently have to be processed twice.
- Occasionally, you may have to process a document three
- times. This occurs when the inserted reference causes TeX
- to format a paragraph differently, which in turn causes
- TeX to change a page break.<sup>[<a id="id2861760"
- name="id2861760" href="#ftn.id2861760">16</a>]</sup>
- Because most changes are incremental while revising a
- document, this is normally only an issue the first time
- you process a document.</p>
-
- <p>The following sections describe the LaTeX methods for
- constructing a table of contents, figure references, an
- index, and a bibliography. LaTeX is used in this example
- because it is a very common macro package and is typical
- of the way macro packages provide these features. Similar
- mechanisms exist in most formats, except Plain TeX.</p>
-
- <p>Figure&#160;<a href="ch01.html#fig.texcmplx"
- title="Figure&#160;1.5.&#160;TeXing a More Complex Document">
- Figure&#160;1.5</a> shows the relationships between many
- of the components described in the following sections.
- LaTeX creates several sorts of auxiliary files depending
- on the kind of cross references required by your document
- and the style files you use. These auxiliary files may be
- modified (and others may be created) by other sorts of
- post-processing programs (like <b>MakeIndex</b><a
- id="id2861811" class="indexterm" name="id2861811"></a>
- for constructing indexes or BibTeX<a id="id2861819"
- class="indexterm" name="id2861819"></a> for constructing
- bibliographies). LaTeX uses these auxiliary files, if
- they exist, to update your document when it is processed
- again.</p>
-
- <div class="figure">
- <a id="fig.texcmplx" name="fig.texcmplx"></a>
-
- <p class="title"><b>Figure&#160;1.5.&#160;TeXing a More
- Complex Document</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.01.05.png" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2861875"
- name="id2861875"></a>Building a Table of
- Contents</h3>
- </div>
- </div>
-
- <p>A table of contents<a id="id2861885" class="indexterm"
- name="id2861885"></a> is the simplest form of cross
- reference. In LaTeX, you request a table of contents by
- inserting the \tableofcontents command wherever you want
- it to appear in your document. If you request the table
- of contents at the end of your document rather than the
- beginning, your document can be printed with only one
- pass through TeX.</p>
-
- <p>LaTeX uses a file with the same name as your document
- and the extension <tt>.toc</tt> to hold the table of
- contents entries. You can control the level of detail in
- your table of contents by setting the \secnumdepth
- counter. A value of zero includes only chapters; one
- includes chapters and sections; two includes chapters,
- sections, and subsections, and so on.</p>
-
- <p>The LaTeX commands \listoftables and \listoffigures
- perform the same functions as \tableofcontents for lists
- of tables and figures. They use external files with the
- extensions <tt>.lot</tt><a id="id2861950"
- class="indexterm" name="id2861950"></a> and
- <tt>.lof</tt><a id="id2861966" class="indexterm"
- name="id2861966"></a>, respectively. As with the table of
- contents, your document can be correctly formatted in one
- pass if the \listoftables and \listoffigures commands are
- placed at the end of the document.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2861991"
- name="id2861991"></a>Figure References</h3>
- </div>
- </div>
-
- <p>Figure references<a id="id2862000" class="indexterm"
- name="id2862000"></a> are a special case of LaTeX's cross
- referencing mechanism. The LaTeX command
- \label{<i><tt>string</tt></i>} creates a referent. You
- refer to the label with the command
- \ref{<i><tt>string</tt></i>}. In normal body text, the
- label refers to the current section or subsection. In a
- figure or table environment, the label refers to that
- figure or table.</p>
-
- <p>If your document contains no forward references<a
- id="id2862038" class="indexterm" name="id2862038"></a>
- (if all \label commands occur before the \ref's that
- refer to them) then it can be formatted in one pass.
- Otherwise, TeX will have to be run two or three times to
- make all of the references correct.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2862061"
- name="id2862061"></a>Indexes and Glossaries</h3>
- </div>
- </div>
-
- <p>Indexes<a id="id2862070" class="indexterm"
- name="id2862070"></a> and glossaries<a id="id2862079"
- class="indexterm" name="id2862079"></a> differ from the
- preceding forms of reference in that they must be
- processed by a separate program. In general, this is true
- regardless of the macro package or format you use. An
- external program is required because indexes and
- glossaries must be alphabetized, and in indexes,
- consecutive page numbers have to be converted into
- ranges, and so on.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2862096"
- name="id2862096"></a>Bibliographies</h3>
- </div>
- </div>
-
- <p>LaTeX works in conjunction with another program,
- called BibTeX<a id="id2862105" class="indexterm"
- name="id2862105"></a>, to provide a flexible, convenient
- way to construct bibliographies<a id="id2862119"
- class="indexterm" name="id2862119"></a>. The \cite
- commands allows you to refer to other documents in much
- the same way that the \ref command allows you to refer to
- other portions of the same document.</p>
-
- <p>You make a citation by placing the command
- \cite{<i><tt>string</tt></i>} where you wish the citation
- to occur. The <span
- class="emphasis"><em>string</em></span> is a key that
- refers to the document in your bibliography database that
- you wish to cite. Example&#160;<a
- href="ch01.html#ex.knuthbbl"
- title="Example&#160;1.2.&#160;A typical bibliography database entry">
- Example&#160;1.2</a> is a typical entry in a bibliography
- database. It describes Knuth's<a id="id2862157"
- class="indexterm" name="id2862157"></a> classic book
- <span class="emphasis"><em>The
- TeXbook</em></span>&#160;[<a
- href="bi01.html#kn:texbook">kn:texbook</a>]. The key for
- this entry is &#8220;kn:texbook.&#8221;</p>
-
- <div class="example">
- <a id="ex.knuthbbl" name="ex.knuthbbl"></a>
-
- <p class="title"><b>Example&#160;1.2.&#160;A typical
- bibliography database entry</b></p>
-<pre class="screen">
-@Book{kn:texbook,
- author = "Donald E. Knuth",
- title = "The {TeX}book",
- publisher = "Addison-Wesley",
- year = 1989,
- edition = "Fifteenth",
- isbn = "0-201-13447-0"
- note = "Paperback ISBN: 0-201-13448-9"
-}
-</pre>
- </div>
-
- <p>Each entry in the database consists of a type (book,
- article, magazine, etc.), a key, and a number of fields.
- The number and names of the fields depend on the type of
- entry. The database is simply a plain ASCII file
- containing any number of entries. You can have multiple
- databases.</p>
-
- <p>These are the commands you use, in addition to \cite,
- to include a bibliography in your document:</p>
-<pre class="screen">
-\bibliographystyle{plain}
-\bibliography{textools,refbooks}
-</pre>
-
- <p>The \bibliographystyle command tells BibTeX how to
- format the bibliography, and the \bibliography command
- identifies which bibliographic databases contain the
- citations that you have made. The &#8220;plain&#8221;
- style of bibliography is selected, and the
- <tt>textools</tt> and <tt>refbooks</tt> files contain the
- bibliographic information for the documents cited.
- Document styles can be used to alter the format of
- citations in your text. The default extension for
- bibliographic styles is <tt>.bst</tt><a id="id2862291"
- class="indexterm" name="id2862291"></a>. The default
- extension for database files is <tt>.bib</tt><a
- id="id2862308" class="indexterm"
- name="id2862308"></a>.</p>
-
- <p>LaTeX places citations and bibliography information
- into the <tt>.aux</tt> file<a id="id2862331"
- class="indexterm" name="id2862331"></a>. BibTeX reads the
- <tt>.aux</tt><a id="id2862348" class="indexterm"
- name="id2862348"></a> file and constructs a bibliography,
- which it places into a file with the extension
- <tt>.bbl</tt><a id="id2862366" class="indexterm"
- name="id2862366"></a>, using the entries you cited and
- the bibliography style you selected.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2862381"
- name="id2862381"></a>Special Things</h3>
- </div>
- </div>
-
- <p>Sometimes, producing a complex document requires the
- ability to interface with objects outside of TeX
- (pictures or figures created by high-end graphics
- packages, special features of a particular printer,
- etc.). To support this kind of communication, TeX
- provides a control sequence called \special. The
- arguments passed to the \special command are written
- directly to the <tt>DVI</tt> file for the DVI driver. It
- is the responsibility of the DVI driver to handle them.
- DVI drivers typically ignore \special commands that they
- do not recognize.</p>
-
- <p>You will find \special commands of various kinds
- described throughout this book, particularly when
- discussing color typesetting in Chapter&#160;<a
- href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>,
- and graphics in Chapter&#160;<a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a>,
- <span class="emphasis"><em><a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a></em></span>.</p>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2856038" name="ftn.id2856038"
- href="#id2856038">1</a>]</sup> Before I proceed, the
- notion of beautiful in this context needs some
- explanation. Several people have pointed out that the
- logo type used by many TeX-related programs (including
- TeX itself) is intrinsically ugly. These same folks argue
- that a sentence like &#8220;TeX is designed to typeset
- beautiful pages&#8221; is self-contradictory because it
- begins with such an ugly construction. Obviously, TeX
- can't <span class="emphasis"><em>prevent</em></span> you
- from typesetting ugly things. But TeX can typeset
- beautiful things too. We at O'Reilly &amp; Associates
- think that this book, typeset completely in TeX, is an
- excellent example.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2857595" name="ftn.id2857595"
- href="#id2857595">2</a>]</sup> This is not a whole-truth.
- Implementors of TeX may make some system-dependent
- alterations as long as the resulting program still passes
- the test suite; so our TeXs may not behave <span
- class="emphasis"><em>exactly</em></span> the same way.
- They will, however, produce identical documents given
- identical input (unless the input relies on
- system-dependent features not available in both TeXs,
- naturally. ;-)</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2857956" name="ftn.id2857956"
- href="#id2857956">3</a>]</sup> This is subtly different
- from saying that they are joined at the baseline. There
- are TeX commands which can change the position of the
- reference point in a box, whereas the baseline is an
- imaginary line that depends solely on the shape of the
- character.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2858135" name="ftn.id2858135"
- href="#id2858135">4</a>]</sup> Technically, it's any
- character defined to be in the &#8220;escape&#8221;
- category followed by any sequence of characters defined
- to be in the &#8220;letter&#8221; category or a single
- character in the &#8220;other&#8221; category.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2858243" name="ftn.id2858243"
- href="#id2858243">5</a>]</sup> Actually, macro expansion
- differs from pure textual replacement in a number of
- technical ways, but they aren't important here.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2858415" name="ftn.id2858415"
- href="#id2858415">6</a>]</sup> Technically, several other
- kinds of values are stored this way as well, but they are
- less common and won't be discussed in this book at
- all.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2858485" name="ftn.id2858485"
- href="#id2858485">7</a>]</sup> Most control sequences can
- be redefined to hold different kinds of values, but they
- can never hold different kinds of values at the same
- time. A dimension register can be redefined to hold
- tokens, for example, but then it can't hold dimensions
- anymore (unless it is redefined again).</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2858627" name="ftn.id2858627"
- href="#id2858627">8</a>]</sup> Plain TeX is the name of a
- particular macro package. I selected it for the purpose
- of example in this chapter because it is always installed
- with TeX. Most of what follows in this chapter is true in
- other macro packages as well, but some of the details are
- different. See Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>
- for more information.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2858704" name="ftn.id2858704"
- href="#id2858704">9</a>]</sup> All of these special
- characters are configurable, but most macro packages use
- the Plain TeX defaults.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2859730" name="ftn.id2859730"
- href="#id2859730">10</a>]</sup> TeX pundits, and other
- folks who have been frustrated by the limitations of
- these environments, frequently refer to this as
- WYSIAYG&#8212;what you see is <span
- class="emphasis"><em>all</em></span> you get.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2860201" name="ftn.id2860201"
- href="#id2860201">11</a>]</sup> TeX doesn't do this sort
- of thing automatically, but it isn't hard to do. Why the
- kiwi? It was on my business card at the time.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2860372" name="ftn.id2860372"
- href="#id2860372">12</a>]</sup> Although it has a very
- different notion of what constitutes a control
- sequence.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2861160" name="ftn.id2861160"
- href="#id2861160">13</a>]</sup> Well, actually, they're
- TeX primitives, are defined by a macro package, defined
- in a file loaded by a macro package, or defined in your
- document.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2861489" name="ftn.id2861489"
- href="#id2861489">14</a>]</sup> Some drivers may also
- benefit from loading the <tt>TFM</tt> files used to
- create your document.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2861567" name="ftn.id2861567"
- href="#id2861567">15</a>]</sup> Textures for the Mac and
- <b>Scientific Word</b> offer WYSIWYG-like environments,
- but that's not the point ;-)</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2861760" name="ftn.id2861760"
- href="#id2861760">16</a>]</sup> With extreme cleverness
- or extreme bad luck you can create a document which will
- <span class="emphasis"><em>never</em></span> format
- correctly.</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;2.&#160;Editing"
- href="ch02.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Part&#160;I.&#160;An
- Introduction to TeX&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;2.&#160;Editing</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch02.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch02.html
deleted file mode 100644
index 77c3f6ec357..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch02.html
+++ /dev/null
@@ -1,2438 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;2.&#160;Editing</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX" />
- <link rel="previous" href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture" />
- <link rel="next" href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;1.&#160;The Big Picture"
- href="ch01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;3.&#160;Running TeX"
- href="ch03.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.editing"
- name="chap.editing"></a>Chapter&#160;2.&#160;Editing</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>This chapter describes several writing environments
- available for creating and modifying TeX documents. In
- practice, you can use almost any editing program<a
- id="id2788466" class="indexterm" name="id2788466"></a><a
- id="id2788476" class="indexterm" name="id2788476"></a><a
- id="id2788489" class="indexterm" name="id2788489"></a> you
- wish, but I'll focus on GNU emacs<a id="id2788501"
- class="indexterm" name="id2788501"></a> in this chapter. I've
- chosen GNU emacs for two reasons: it is a popular and very
- powerful editor available on many platforms (unix, NeXT,
- MS-DOS, OS/2, Macintosh, VMS, Amiga, $&#8230;$), and it has
- the most comprehensive TeX editing environment that I've ever
- seen. At the end of the chapter, I'll discuss several other
- editors for MS-DOS and OS/2 that also have TeX editing
- environments.</p>
-
- <p>The sole requirement for a TeX editor is that it must save
- files in a flat, ASCII<a id="id2788517" class="indexterm"
- name="id2788517"></a> format without any additional
- formatting characters or special encodings. Word processors,
- such as Microsoft Word<a id="id2788382" class="indexterm"
- name="id2788382"></a>, usually add special formatting
- information to your document when they save it to disk. TeX
- will not understand this information, so you cannot use a
- word processor to edit TeX documents.<sup>[<a id="id2788393"
- name="id2788393" href="#ftn.id2788393">17</a>]</sup></p>
-
- <p>A program that allows you to edit flat ASCII files is
- usually called an editor (as opposed to a word processor<a
- id="id2788413" class="indexterm" name="id2788413"></a>, for
- example). Choosing an editor is a remarkably personal
- decision. Computer programmers and other people who use
- editors every day frequently become very attached to a
- particular editor. This chapter explores a number of features
- that an editor can provide to make editing TeX documents
- easier. If possible, choose an editor that offers these
- features. In any event, make sure you choose an editor you
- will be comfortable using. You'll spend a lot of time using
- it.</p>
-
- <p>Many editors have some sort of built-in programming
- language. The features described in this chapter rely on
- modifying the behavior of the editor with its programming
- language. This does not mean that <span
- class="emphasis"><em>you</em></span> will have to do any
- programming. All of the editors discussed in this chapter
- have TeX editing environments already available. However, if
- you use another editor and it doesn't have a programming
- language, it's unlikely that these features will be available
- to you.</p>
-
- <p>The next section explores some helpful editor features.
- All of the editors in this chapter provide some or all of the
- features discussed, and require little or no programming on
- your part.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.whatcando" name="sec.whatcando"></a>What Can an
- Editor Do?</h2>
- </div>
- </div>
-
- <p>You will do most of your work with TeX in the editor<a
- id="id2862669" class="indexterm" name="id2862669"></a>.
- There are two ways that an editor can help you edit TeX
- documents. One is to provide typing shortcuts that are
- either intuitive replacements for cumbersome operations or
- quick ways of typing common TeX commands. The other way
- that an editor can help is by running TeX for you and
- automatically displaying the location of formatting errors
- in your document.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.auctex"
- name="sec.auctex"></a>Quoting Automatically</h3>
- </div>
- </div>
- <a id="id2862700" class="indexterm" name="id2862700"></a>
-
- <p>Most typewriters and many word processors use the same
- symbol for opening and closing quotations. You are
- probably used to typing the double-quote key to insert
- quotation marks into your text. However, if you look
- carefully at TeX output (or any professionally typeset
- document) you will notice that the opening and closing
- quotation marks do not look the same. The proper way to
- type an opening quote (&#8220;) in TeX is with two single
- back-quotes in a row (<tt>``</tt>). A closing quote
- (&#8221;) is entered with two single quotes (apostrophes)
- in a row (<tt>''</tt>). This process is tedious and
- error-prone since you are used to typing something
- else.</p>
-
- <p>If you accidentally use the double quote symbol in
- your input, you most frequently get text that looks like
- &#8221;this.&#8221; The exact result is actually
- dependent upon the font you are using. This is explained
- in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.
- Most programmable editors can change the meaning of the
- double-quote key to insert the correct quotation
- marks.</p>
-
- <p>If you are interested in programming your editor to do
- this, you can use the following algorithm to select the
- correct quotation marks most of the time: if the
- character to the immediate left of the cursor is a space,
- opening brace, parenthesis, or bracket, insert opening
- quotes; otherwise, insert closing quotes. As a further
- enhancement, double quotes should be inserted immediately
- following a backslash.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2862787"
- name="id2862787"></a>Matching Braces</h3>
- </div>
- </div>
- <a id="id2862792" class="indexterm" name="id2862792"></a>
-
- <p>Braces, as mentioned in Chapter&#160;<a
- href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a>,
- <span class="emphasis"><em><a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a></em></span>,
- are used by TeX to delimit sections of text; they appear
- often in TeX documents. GNU emacs<a id="id2862829"
- class="indexterm" name="id2862829"></a>, Multi-Edit<a
- id="id2862842" class="indexterm" name="id2862842"></a>,
- and <b>Brief</b><a id="id2862858" class="indexterm"
- name="id2862858"></a> can all be programmed to highlight
- the matching open brace whenever you type a closing
- brace.</p>
-
- <p>For example, if you have entered the text</p>
-<pre class="screen">
-\footnote{This is {\it not} the only case.}
-</pre>
-
- <p>and the next character that you type is <b>}</b>, the
- open brace immediately following the word \footnote is
- highlighted, or all of the text between that brace and
- the current cursor position is highlighted. This feature
- makes it easier to find places where you have forgotten
- to insert a closing brace.</p>
-
- <p>If you usually work in &#8220;insert&#8221; mode, you
- may also find it convenient to have the editor insert
- braces in pairs and then insert text between them. This
- can be accomplished in almost any editor that can be
- programmed, even one that isn't equipped to handle brace
- matching.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2862919"
- name="id2862919"></a>Inserting Common Control
- Sequences</h3>
- </div>
- </div>
-
- <p>Most editors can be programmed to insert arbitrary
- text when a special key is pressed. This feature can be
- used to insert common control sequences<a id="id2862931"
- class="indexterm" name="id2862931"></a>. For example, you
- might have <b>Alt-c</b> insert the \chapter control
- sequence or <b>Ctrl-e</b> insert \begin{enumerate}.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2862968"
- name="id2862968"></a>Running TeX Automatically</h3>
- </div>
- </div>
-
- <p>One of the nicest features that an editor can provide
- is the ability to run TeX automatically<a id="id2862979"
- class="indexterm" name="id2862979"></a> without leaving
- the editor. This is a feature that programmers demand
- because it allows them to run compilers<a id="id2862995"
- class="indexterm" name="id2862995"></a> directly from the
- editor. Editors that provide this feature usually include
- some mechanism for programming the editor to locate the
- position of errors reported by the compiler. The editor
- searches for error messages<a id="id2863008"
- class="indexterm" name="id2863008"></a> in the output
- generated by the compiler, and it positions the cursor at
- the location of each error. This speeds up the
- traditional edit/compile/debug cycle of programming. You
- can take advantage of these features to shorten the
- edit/typeset/rewrite cycle of creating a TeX
- document.</p>
-
- <p>All of the editors discussed in this chapter can
- easily be adapted to run TeX in this way. If you already
- have a favorite editor and want to add this functionality
- for TeX, see the section &#8220;<a
- href="ch02.html#sec.texcomp" title="Running TeX">the
- section called &#8220;Running TeX&#8221;</a>&#8221; later
- in this chapter; it describes the process at a very
- general level.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2863045"
- name="id2863045"></a>GNU Emacs</h2>
- </div>
- </div>
-
- <p>This section describes the TeX modes distributed as part
- of GNU emacs<a id="id2863054" class="indexterm"
- name="id2863054"></a>. Emacs is one of the most popular and
- most powerful editors around. Distributed by the Free
- Software Foundation (FSF)<a id="id2863066"
- class="indexterm" name="id2863066"></a>, GNU emacs is the
- de facto standard editor in many unix environments.
- Recently, GNU emacs has been ported to many other
- platforms, including MS-DOS (<b>demacs</b><a id="id2863083"
- class="indexterm" name="id2863083"></a>), OS/2, Macintosh,
- VMS, Amiga, and NeXT.</p>
-
- <div class="sidebar">
- <p>This section and the following section on aucTeX
- assume that you are familiar with general emacs concepts.
- In particular, you should be familiar with the concepts
- of buffers, files, regions, command keys, editing modes,
- and prefix arguments. If you are unfamiliar with these
- concepts, you can learn about them in the online help,
- called Info pages, for GNU emacs. Info pages should be
- available by pressing <b>Ctrl-H</b> <b>i</b> in emacs.
- You can also consult a reference to GNU emacs, such as
- <span class="emphasis"><em>Learning GNU
- Emacs</em></span>&#160;[<a
- href="bi01.html#or:emacs">or:emacs</a>] for more
- information.</p>
- </div>
-
- <p>Customizing some of the features of GNU emacs requires
- familiarity with GNU emacs lisp<a id="id2863141"
- class="indexterm" name="id2863141"></a>, which is also
- described in the Info pages.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2863154"
- name="id2863154"></a>Starting TeX Mode</h3>
- </div>
- </div>
-
- <p>GNU emacs<a id="id2863163" class="indexterm"
- name="id2863163"></a> provides two similar TeX editing
- modes: one designed for editing Plain TeX documents
- (<span class="emphasis"><em>plain-tex-mode</em></span>)
- and the other for editing LaTeX documents (<span
- class="emphasis"><em>latex-mode</em></span>). The <span
- class="emphasis"><em>latex-mode</em></span> is a superset
- of <span class="emphasis"><em>plain-tex-mode</em></span>
- that provides additional shortcut keys for some LaTeX
- control sequences.</p>
-
- <p>There are three ways to start TeX mode in GNU
- emacs:</p>
-
- <div class="informaltable">
- <table border="1">
- <colgroup>
- <col />
- <col />
- </colgroup>
-
- <tbody>
- <tr>
- <td><b>M-x tex-mode</b></td>
-
- <td>Attempts to select the correct mode.</td>
- </tr>
-
- <tr>
- <td><b>M-x plain-tex-mode</b></td>
-
- <td>Always selects Plain TeX mode.</td>
- </tr>
-
- <tr>
- <td><b>M-x latex-mode</b></td>
-
- <td>Always selects LaTeX mode.</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>If you use <b>M-x tex-mode</b>, emacs examines the top
- of the buffer in order to select the appropriate mode. If
- the control sequences \documentstyle or \begin{document}
- occur near the top of the buffer, <span
- class="emphasis"><em>latex-mode</em></span> is selected;
- otherwise, the default mode is selected. The default mode
- is stored in the emacs lisp variable
- <tt>TeX-default-mode</tt>.</p>
-
- <p>You can also tell emacs to invoke TeX mode
- automatically whenever you edit a file that has a name
- ending in <tt>.tex</tt><a id="id2863317"
- class="indexterm" name="id2863317"></a>. To do so, add
- the following lines to your emacs startup file<a
- id="id2863326" class="indexterm" name="id2863326"></a>,
- usually called <tt>.emacs</tt> in your home
- directory:<sup>[<a id="id2863345" name="id2863345"
- href="#ftn.id2863345">18</a>]</sup></p>
-<pre class="screen">
-(setq auto-mode-alist (append '(("\\.tex$" . tex-mode))
- auto-mode-alist))
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2863366"
- name="id2863366"></a>Typing in Emacs</h3>
- </div>
- </div>
-
- <p>The emacs TeX modes change the meaning of several keys
- to provide features useful for editing TeX documents.
- These special<a id="id2863375" class="indexterm"
- name="id2863375"></a><a id="id2863388" class="indexterm"
- name="id2863388"></a> key bindings apply only to buffers
- that you edit while emacs is in <span
- class="emphasis"><em>plain-tex-mode</em></span> or <span
- class="emphasis"><em>latex-mode</em></span>.</p>
-
- <p>Automatic quotation, brace balancing in paragraphs,
- inserting brace pairs, skipping over unmatched braces,
- and closing open environments are supported.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2863418"
- name="id2863418"></a>Running TeX Automatically</h3>
- </div>
- </div>
-
- <p>When TeX typesets your document, it produces
- processing and error messages. By<a id="id2863429"
- class="indexterm" name="id2863429"></a><a id="id2863442"
- class="indexterm" name="id2863442"></a> running TeX for
- you, emacs can capture these messages and display them in
- a window. You can use this feature to help locate and
- correct errors.</p>
-
- <p>Functions that run TeX from inside the editor rely on
- emacs' ability to run a subshell<a id="id2863463"
- class="indexterm" name="id2863463"></a>. Some
- implementations of emacs, particularly implementations
- for MS-DOS, which is unable to run concurrent processes,
- cannot use this feature. aucTeX, a different editing
- environment for GNU emacs, does allow you to use these
- features with MS-DOS ports<a id="id2863473"
- class="indexterm" name="id2863473"></a> of GNU emacs.
- (aucTeX is described in the next section.)</p>
-
- <p>GNU emacs supports processing of both buffers and
- regions. These modes don't locate errors for you
- automatically, but they do place the output from TeX in
- an emacs buffer so that you can find them yourself.
- Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>,
- describes how to interpret TeX output and find the
- location of errors.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2863525"
- name="id2863525"></a>aucTeX</h2>
- </div>
- </div>
-
- <p>This section provides an overview of aucTeX<a
- id="id2863533" class="indexterm" name="id2863533"></a>,<a
- id="id2863544" class="indexterm" name="id2863544"></a> a
- powerful emacs macro package for editing LaTeX documents.
- aucTeX is available on the CTAN archives in
- <tt>support/auctex</tt>. More detailed information about
- installing and customizing aucTeX can be found in the
- documentation distributed with the package.</p>
-
- <p>aucTeX provides extensive support for editing TeX and
- LaTeX documents in emacs. It provides many more features
- than the ordinary GNU emacs TeX modes. Although useful for
- both Plain TeX and LaTeX documents, aucTeX is designed with
- the LaTeX user in mind.</p>
-
- <p>aucTeX is <span class="emphasis"><em>a lot</em></span>
- more complex than GNU emacs TeX mode. In fact, it is so
- complex that it may not be useful if you have a relatively
- slow computer.<sup>[<a id="id2863594" name="id2863594"
- href="#ftn.id2863594">19</a>]</sup> On my machine,<sup>[<a
- id="id2863603" name="id2863603"
- href="#ftn.id2863603">20</a>]</sup> aucTeX's performance
- leaves a lot to be desired. On the other hand, aucTeX is
- extensively configurable, and it is possible to streamline
- it quite a bit.</p>
-
- <p>The descriptions that follow are for aucTeX version 8.0.
- The versions change frequently as new features are added.
- Consult the documentation which comes with aucTeX for a
- list of the new features that have been added since this
- book was published.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.multifile"
- name="sec.multifile"></a>Starting aucTeX</h3>
- </div>
- </div>
-
- <p>The instructions provided with each release of aucTeX
- describe how to build and install the software so that
- aucTeX will automatically be invoked<a id="id2863666"
- class="indexterm" name="id2863666"></a> when you edit a
- file with a name ending in <tt>.tex</tt>.</p>
-
- <p>If you think aucTeX is already installed on your
- system (because the emacs Info page for it is present,
- for example), ask your system administrator where it is
- installed. One common location is
- <tt>/usr/local/lib/emacs/site-lisp/auctex</tt>.</p>
-
- <p>Adding the following line to your emacs startup file<a
- id="id2863710" class="indexterm" name="id2863710"></a>
- (typically <tt>.emacs</tt> in your home directory) will
- load aucTeX each time you start emacs:</p>
-
- <div class="informalexample">
-<pre class="screen">
- (load-file "<span
-class="emphasis"><em>/path/for/auctex</em></span>/tex-site.elc")
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2863748"
- name="id2863748"></a>Typing in aucTeX</h3>
- </div>
- </div>
-
- <p>aucTeX provides a large number of typing shortcuts<a
- id="id2863758" class="indexterm" name="id2863758"></a>.
- Many of the keystroke shortcuts are designed specifically
- to aid in typing LaTeX documents. In addition to command
- keys, aucTeX provides another typing shortcut---command
- completion<a id="id2863775" class="indexterm"
- name="id2863775"></a> for LaTeX control sequences with
- <b>C-c</b> <b>TAB</b>.</p>
-
- <p>If you type a backslash followed by the beginning of a
- control sequence name into a buffer and then type
- <b>C-c</b> <b>TAB</b>, aucTeX completes as much of the
- control sequence as possible. Every time aucTeX adds
- another letter to the control sequence name, it compares
- the resulting name to a configurable list of LaTeX
- control sequences. If it reaches a point where the
- control sequence could be continued in two different
- ways, it stops and displays all the possible completions.
- For example, there are two control sequences in standard
- LaTeX that begin with \re: \renewcommand and
- \renewenvironment.</p>
-
- <p>If you type:</p>
-
- <div class="informalexample">
-<pre class="screen">
-\re <b>C-c</b> <b>TAB</b>
-</pre>
- </div>
-
- <p>aucTeX will insert <tt>new</tt> because that much of
- the control sequence name can be deduced from the known
- possibilities. This changes the text in your document
- to:</p>
-<pre class="screen">
-\renew
-</pre>
-
- <p>Because aucTeX cannot figure out which of the
- possibilities you want, it displays a list of the LaTeX
- commands that begin with \renew. You can complete the
- command by typing <span class="bold"><b>c</b></span> or
- <span class="bold"><b>e</b></span> and pressing
- <b>C-c</b> <b>TAB</b> again. If you want the
- \renewcommand function, type:</p>
-
- <div class="informalexample">
-<pre class="screen">
-\renewc<b>C-c</b> <b>TAB</b>
-</pre>
- </div>
-
- <p>Now, aucTeX will insert <tt>ommand</tt> and return to
- normal typing mode with the cursor positioned just after
- the control sequence name:</p>
-<pre class="screen">
-\renewcommand _
-</pre>
-
- <p>aucTeX has special support for LaTeX sectioning
- commands and environments, changing fonts, commenting out
- sections of a document, reformatting the input text, and
- entering mathematics.</p>
-
- <p>TeX contains a lot of support for typesetting
- mathematics<a id="id2863993" class="indexterm"
- name="id2863993"></a>. In that spirit, aucTeX provides
- a<a id="id2864010" class="indexterm"
- name="id2864010"></a> minor mode<sup>[<a id="id2864021"
- name="id2864021" href="#ftn.id2864021">21</a>]</sup> for
- entering mathematical formulae.</p>
-
- <p>In mathematics minor mode, pressing <b>`</b> changes
- the meaning of the next character you type. The next
- character is interpreted as an abbreviation for a
- mathematical symbol or function. For example, in aucTeX,
- typing</p>
-
- <div class="informalexample">
- <p><b>$</b> <b>C-c</b> <b>~</b> <b>`</b> <b>a</b>
- <b>`</b> <b>&lt;</b> <b>`</b> <b>b</b> <b>$</b></p>
- </div>
-
- <p>inserts</p>
-<pre class="screen">
-$&#945; \leq &#946;$
-</pre>
-
- <p>into your document (which is typeset like this:
- &#945;&#8804;&#946;).</p>
-
- <p>Table&#160;<a href="ch02.html#tbl.mathops"
- title="Table&#160;2.1.&#160;aucTeX Math Operators in Mathematics Minor-mode">
- Table&#160;2.1</a> lists all of the abbreviations. The
- first column of the table displays the shortcut keys. The
- second and third columns show the command inserted in
- your document and the typeset symbol, respectively <a
- id="id2864136" class="indexterm" name="id2864136"></a><a
- id="id2864171" class="indexterm"
- name="id2864171"></a>.</p>
-
- <div class="table">
- <a id="tbl.mathops" name="tbl.mathops"></a>
-
- <p class="title"><b>Table&#160;2.1.&#160;aucTeX Math
- Operators in Mathematics Minor-mode</b></p>
-
- <table
- summary="aucTeX Math Operators in Mathematics Minor-mode"
- border="1">
- <colgroup>
- <col />
- <col />
- <col />
- <col />
- <col />
- <col />
- </colgroup>
-
- <thead>
- <tr>
- <th>Keys</th>
-
- <th>Control Sequence</th>
-
- <th>Symbol</th>
-
- <th>Keys</th>
-
- <th>Control Sequence</th>
-
- <th>Symbol</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td><tt>`a</tt></td>
-
- <td><tt>\alpha</tt></td>
-
- <td>$\alpha$</td>
-
- <td><tt>`C-f</tt></td>
-
- <td><tt>\rightarrow</tt></td>
-
- <td>$\rightarrow$</td>
- </tr>
-
- <tr>
- <td><tt>`b</tt></td>
-
- <td><tt>\beta</tt></td>
-
- <td>$\beta$</td>
-
- <td><tt>`C-p</tt></td>
-
- <td><tt>\uparrow</tt></td>
-
- <td>$\uparrow$</td>
- </tr>
-
- <tr>
- <td><tt>`d</tt></td>
-
- <td><tt>\delta</tt></td>
-
- <td>$\delta$</td>
-
- <td><tt>`C-n</tt></td>
-
- <td><tt>\downarrow</tt></td>
-
- <td>$\downarrow$</td>
- </tr>
-
- <tr>
- <td><tt>`e</tt></td>
-
- <td><tt>\epsilon</tt></td>
-
- <td>$\epsilon$</td>
-
- <td><tt>`&lt;</tt></td>
-
- <td><tt>\leq</tt></td>
-
- <td>$\leq$</td>
- </tr>
-
- <tr>
- <td><tt>`f</tt></td>
-
- <td><tt>\phi</tt></td>
-
- <td>$\phi$</td>
-
- <td><tt>`&gt;</tt></td>
-
- <td><tt>\geq</tt></td>
-
- <td>$\geq$</td>
- </tr>
-
- <tr>
- <td><tt>`g</tt></td>
-
- <td><tt>\gamma</tt></td>
-
- <td>$\gamma$</td>
-
- <td><tt>`~</tt></td>
-
- <td><tt>\tilde</tt></td>
-
- <td>$\tilde{\phantom{a}}</td>
- </tr>
-
- <tr>
- <td><tt>`h</tt></td>
-
- <td><tt>\eta</tt></td>
-
- <td>$\eta$</td>
-
- <td><tt>`I</tt></td>
-
- <td><tt>\infty</tt></td>
-
- <td>$\infty$</td>
- </tr>
-
- <tr>
- <td><tt>`k</tt></td>
-
- <td><tt>\kappa</tt></td>
-
- <td>$\kappa$</td>
-
- <td><tt>`A</tt></td>
-
- <td><tt>\forall</tt></td>
-
- <td>$\forall$</td>
- </tr>
-
- <tr>
- <td><tt>`l</tt></td>
-
- <td><tt>\lambda</tt></td>
-
- <td>$\lambda$</td>
-
- <td><tt>`E</tt></td>
-
- <td><tt>\exists</tt></td>
-
- <td>$\exists$</td>
- </tr>
-
- <tr>
- <td><tt>`m</tt></td>
-
- <td><tt>\mu</tt></td>
-
- <td>$\mu$</td>
-
- <td><tt>`!</tt></td>
-
- <td><tt>\not</tt></td>
-
- <td>$\not\phantom{=}$</td>
- </tr>
-
- <tr>
- <td><tt>`n</tt></td>
-
- <td><tt>\nu</tt></td>
-
- <td>$\nu$</td>
-
- <td><tt>`i</tt></td>
-
- <td><tt>\in</tt></td>
-
- <td>$\in$</td>
- </tr>
-
- <tr>
- <td><tt>`o</tt></td>
-
- <td><tt>\omega</tt></td>
-
- <td>$\omega$</td>
-
- <td><tt>`*</tt></td>
-
- <td><tt>\times</tt></td>
-
- <td>$\times$</td>
- </tr>
-
- <tr>
- <td><tt>`p</tt></td>
-
- <td><tt>\pi</tt></td>
-
- <td>$\pi$</td>
-
- <td><tt>`.</tt></td>
-
- <td><tt>\cdot</tt></td>
-
- <td>$\cdot$</td>
- </tr>
-
- <tr>
- <td><tt>`q</tt></td>
-
- <td><tt>\theta</tt></td>
-
- <td>$\theta$</td>
-
- <td><tt>`@{</tt></td>
-
- <td><tt>\subset</tt></td>
-
- <td>$\subset$</td>
- </tr>
-
- <tr>
- <td><tt>`r</tt></td>
-
- <td><tt>\rho</tt></td>
-
- <td>$\rho$</td>
-
- <td><tt>`@}</tt></td>
-
- <td><tt>\supset</tt></td>
-
- <td>$\supset$</td>
- </tr>
-
- <tr>
- <td><tt>`s</tt></td>
-
- <td><tt>\sigma</tt></td>
-
- <td>$\sigma$</td>
-
- <td><tt>`[</tt></td>
-
- <td><tt>\subseteq</tt></td>
-
- <td>$\subseteq$</td>
- </tr>
-
- <tr>
- <td><tt>`t</tt></td>
-
- <td><tt>\tau</tt></td>
-
- <td>$\tau$</td>
-
- <td><tt>`]</tt></td>
-
- <td><tt>\supseteq</tt></td>
-
- <td>$\supseteq$</td>
- </tr>
-
- <tr>
- <td><tt>`v</tt></td>
-
- <td><tt>\vee</tt></td>
-
- <td>$\vee$</td>
-
- <td><tt>`\</tt></td>
-
- <td><tt>\backslash</tt></td>
-
- <td>$\backslash$</td>
- </tr>
-
- <tr>
- <td><tt>`u</tt></td>
-
- <td><tt>\upsilon</tt></td>
-
- <td>$\upsilon$</td>
-
- <td><tt>`/</tt></td>
-
- <td><tt>\setminus</tt></td>
-
- <td>$\setminus$</td>
- </tr>
-
- <tr>
- <td><tt>`x</tt></td>
-
- <td><tt>\chi</tt></td>
-
- <td>$\chi$</td>
-
- <td><tt>`+</tt></td>
-
- <td><tt>\cup</tt></td>
-
- <td>$\cup$</td>
- </tr>
-
- <tr>
- <td><tt>`y</tt></td>
-
- <td><tt>\psi</tt></td>
-
- <td>$\psi$</td>
-
- <td><tt>`-</tt></td>
-
- <td><tt>\cap</tt></td>
-
- <td>$\cap$</td>
- </tr>
-
- <tr>
- <td><tt>`z</tt></td>
-
- <td><tt>\zeta</tt></td>
-
- <td>$\zeta$</td>
-
- <td><tt>`(</tt></td>
-
- <td><tt>\langle</tt></td>
-
- <td>$\langle$</td>
- </tr>
-
- <tr>
- <td><tt>`D</tt></td>
-
- <td><tt>\Delta</tt></td>
-
- <td>$\Delta$</td>
-
- <td><tt>`)</tt></td>
-
- <td><tt>\rangle</tt></td>
-
- <td>$\rangle$</td>
- </tr>
-
- <tr>
- <td><tt>`G</tt></td>
-
- <td><tt>\Gamma</tt></td>
-
- <td>$\Gamma$</td>
-
- <td><tt>`C-e</tt></td>
-
- <td><tt>\exp</tt></td>
-
- <td>$\exp$</td>
- </tr>
-
- <tr>
- <td><tt>`Q</tt></td>
-
- <td><tt>\Theta</tt></td>
-
- <td>$\Theta$</td>
-
- <td><tt>`C-s</tt></td>
-
- <td><tt>\sin</tt></td>
-
- <td>$\sin$</td>
- </tr>
-
- <tr>
- <td><tt>`L</tt></td>
-
- <td><tt>\Lambda</tt></td>
-
- <td>$\Lambda$</td>
-
- <td><tt>`C-c</tt></td>
-
- <td><tt>\cos</tt></td>
-
- <td>$\cos$</td>
- </tr>
-
- <tr>
- <td><tt>`Y</tt></td>
-
- <td><tt>\Psi</tt></td>
-
- <td>$\Psi$</td>
-
- <td><tt>`C-^</tt></td>
-
- <td><tt>\sup</tt></td>
-
- <td>$\sup$</td>
- </tr>
-
- <tr>
- <td><tt>`P</tt></td>
-
- <td><tt>\Pi</tt></td>
-
- <td>$\Pi$</td>
-
- <td><tt>`C-_</tt></td>
-
- <td><tt>\inf</tt></td>
-
- <td>$\inf$</td>
- </tr>
-
- <tr>
- <td><tt>`S</tt></td>
-
- <td><tt>\Sigma</tt></td>
-
- <td>$\Sigma$</td>
-
- <td><tt>`C-d</tt></td>
-
- <td><tt>\det</tt></td>
-
- <td>$\det$</td>
- </tr>
-
- <tr>
- <td><tt>`U</tt></td>
-
- <td><tt>\Upsilon</tt></td>
-
- <td>$\Upsilon$</td>
-
- <td><tt>`C-l</tt></td>
-
- <td><tt>\lim</tt></td>
-
- <td>$\lim$</td>
- </tr>
-
- <tr>
- <td><tt>`V</tt></td>
-
- <td><tt>\Phi</tt></td>
-
- <td>$\Phi$</td>
-
- <td><tt>`C-t</tt></td>
-
- <td><tt>\tan</tt></td>
-
- <td>$\tan$</td>
- </tr>
-
- <tr>
- <td><tt>`O</tt></td>
-
- <td><tt>\Omega</tt></td>
-
- <td>$\Omega$</td>
-
- <td><tt>`^</tt></td>
-
- <td><tt>\hat</tt></td>
-
- <td>$\hat{\phantom{a}}$</td>
- </tr>
-
- <tr>
- <td><tt>`C-b</tt></td>
-
- <td><tt>\leftarrow</tt></td>
-
- <td>$\leftarrow$</td>
-
- <td>&#160;</td>
-
- <td>&#160;</td>
-
- <td>&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>Additional miscellaneous commands in aucTeX provide
- automatic quotation, completion of &#8220;items&#8221; in
- appropriate environments (<tt>itemize</tt> and
- <tt>enumeration</tt> environments, for example), and
- insertion of brace pairs<a id="id2865777"
- class="indexterm" name="id2865777"></a> and skeletal
- control sequences.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2865794"
- name="id2865794"></a>aucTeX Outline Mode</h3>
- </div>
- </div>
-
- <p>Outline mode<a id="id2865803" class="indexterm"
- name="id2865803"></a> is a convenient way to edit large
- documents. In outline mode, portions of the document that
- you are not editing are hidden from view. They aren't
- removed or deleted. Emacs indicates hidden text with
- ellipses.</p>
-
- <p>For example, in a large document with many sections,
- you can use outline mode to hide all text except the
- section headings, and then selectively expand just the
- sections that you wish to edit.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2865831"
- name="id2865831"></a>Intelligent Paragraph
- Reformatting</h3>
- </div>
- </div>
-
- <p>aucTeX understands the TeX constructions for many
- kinds of environments (the list environments, for
- example) and performs paragraph reformatting<a
- id="id2865843" class="indexterm" name="id2865843"></a>
- within the restrictions of these environments. aucTeX
- won't concatenate a whole series of list items together
- into one huge paragraph, for example.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2865862"
- name="id2865862"></a>Multi-file Documents</h3>
- </div>
- </div>
-
- <p>It is often convenient to edit a large document in
- small pieces<a id="id2865873" class="indexterm"
- name="id2865873"></a> rather than in one huge file. For
- example, when writing a book, it is convenient to work on
- chapters independently and store them in different files.
- If you are working on a collaborative project, it may be
- absolutely necessary to separate the document into
- pieces.</p>
-
- <p>The TeX \input command allows you to construct a
- driver file that automatically combines the individual
- files that make up your document when you run TeX. The
- driver file contains the document style options and other
- setup information for the whole document. Each chapter
- contains just the necessary text. When TeX encounters an
- \input command, it typesets all of the text in the
- specified file before continuing with the current
- document. Example&#160;<a href="ch02.html#ex.driver"
- title="Example&#160;2.1.&#160;A Simple Driver File">Example&#160;2.1</a>
- shows an example of a driver file.</p>
-
- <div class="example">
- <a id="ex.driver" name="ex.driver"></a>
-
- <p class="title"><b>Example&#160;2.1.&#160;A Simple
- Driver File</b></p>
-<pre class="screen">
-\documentstyle[ora]{book}
-\begin{document}
- \input{intro}
- \input{chap1}
- \input{chap2}
-\end{document}
-</pre>
- </div>
-
- <p>aucTeX provides seamless support for multi-file
- documents. In order to provide this support, aucTeX
- relies on the &#8220;file variables&#8221; feature of
- emacs, which allows you to associate editor variables
- with particular buffers. An editor variable<a
- id="id2865956" class="indexterm" name="id2865956"></a><a
- id="id2865966" class="indexterm" name="id2865966"></a> is
- a named variable that is local to the current buffer and
- accessible by macro packages like aucTeX running under
- emacs. Look up file variables in your emacs reference for
- a more complete description. Example&#160;<a
- href="ch02.html#ex.localvars"
- title="Example&#160;2.2.&#160;Local Variables in an Emacs Buffer">
- Example&#160;2.2</a> shows some common local variables in
- aucTeX.</p>
-
- <p>When you run TeX on a buffer, aucTeX looks for the
- editor variable <tt>TeX-master</tt>. If
- <tt>TeX-master</tt> is set to a filename, aucTeX runs TeX
- on that file instead of running it directly on the file
- you are editing. This is a tremendously useful feature
- because it means that you do not have to put macro
- definitions, document style options, and other setup
- information at the top of each chapter. Simply set the
- <tt>TeX-master</tt> variable in each chapter to name the
- driver file.</p>
-
- <p>If you do not set the <tt>TeX-master</tt> variable,
- aucTeX will prompt you for it the first time you run a
- command. If the \documentstyle command occurs near the
- top of your document, aucTeX assumes that the current
- buffer <span class="emphasis"><em>is</em></span> the
- master (because it contains setup information) and will
- not prompt you for a different master file.</p>
-
- <p>Editor variables are defined by a &#8220;Local
- Variables&#8221; declaration at the bottom of your file.
- aucTeX inserts a Local Variables declaration
- automatically if it prompts you for a master file.
- Example&#160;<a href="ch02.html#ex.localvars"
- title="Example&#160;2.2.&#160;Local Variables in an Emacs Buffer">
- Example&#160;2.2</a> shows how local variables
- <tt>TeX-master</tt><a id="id2866076" class="indexterm"
- name="id2866076"></a> and <tt>TeX-command-default</tt><a
- id="id2866102" class="indexterm" name="id2866102"></a>
- can be set to <tt>driver.tex</tt> and <tt>LaTeX</tt>,
- respectively. Because these lines begin with a percent
- sign, they are considered comments by TeX and do not
- appear in the output. These should be the last lines in
- the file.</p>
-
- <div class="example">
- <a id="ex.localvars" name="ex.localvars"></a>
-
- <p class="title"><b>Example&#160;2.2.&#160;Local
- Variables in an Emacs Buffer</b></p>
-<pre class="screen">
-% Local Variables:
-% TeX-master: "driver.tex"
-% TeX-command-default: "LaTeX"
-% End:
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.texcomp"
- name="sec.texcomp"></a>Running TeX</h3>
- </div>
- </div>
-
- <p>Like GNU emacs TeX mode, aucTeX allows you to run
- TeX<a id="id2866176" class="indexterm"
- name="id2866176"></a> directly from within emacs as a
- subshell. Running a program inside emacs creates a
- process<a id="id2866196" class="indexterm"
- name="id2866196"></a>. You can have only one active
- process for each document, plus one process for TeXing a
- region<a id="id2866208" class="indexterm"
- name="id2866208"></a>. If you try to run two processes on
- the same document, aucTeX will ask for permission to kill
- the first before running the second. aucTeX supports the
- processing of both the documents and the regions of a
- document.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2866224"
- name="id2866224"></a>Finding Errors</h3>
- </div>
- </div>
-
- <p>No matter how much experience you have with TeX, some
- of the documents that you write will contain errors<a
- id="id2866235" class="indexterm" name="id2866235"></a>.
- aucTeX eases the burden of correcting these errors by
- locating them automatically in your document.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2866254"
- name="id2866254"></a>Multi-Edit</h2>
- </div>
- </div>
-
- <p><b>Multi-Edit<a id="id2866268" class="indexterm"
- name="id2866268"></a></b><a id="id2866275"
- class="indexterm" name="id2866275"></a> is an editor for
- the MS-DOS environment. This section describes the
- text-based version of <b>Multi-Edit</b>. A Windows version
- is in the works, and it may exist by the time you read
- this.</p>
-
- <p>Built to be a programmer's editor, <b>Multi-Edit</b> has
- a number of features designed to add language-specific
- intelligence to the editing environment. These features
- (template editing, a customizable spellchecker, and
- configurable brace matching) can be exploited for TeX as
- readily as for any programming language. For several years,
- at least since version 5.0, <b>Multi-Edit</b> has included
- support for TeX.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2866322"
- name="id2866322"></a>Setting Up TeX Support</h3>
- </div>
- </div>
-
- <p>Support for TeX<a id="id2866330" class="indexterm"
- name="id2866330"></a> is included as a language type in
- <b>Multi-Edit</b>. Language types are selected by
- filename extension; this means that you configure
- <b>Multi-Edit</b> to provide support for the &#8220;TeX
- language&#8221; whenever you edit files with the
- extension <tt>.tex</tt><a id="id2866371"
- class="indexterm" name="id2866371"></a> (and other
- extensions if you choose).</p>
-
- <p>Selecting the &#8220;Other/Install/Filename
- extensions...&#8221; menu displays a list of configured
- extensions. If TEX is not listed, press <b>Insert</b> to
- add it. You will see a screen like the one shown in
- Figure&#160;<a href="ch02.html#fig.meextsetup"
- title="Figure&#160;2.1.&#160;Extension setup in Multi-Edit">
- Figure&#160;2.1</a>.</p>
-
- <div class="figure">
- <a id="fig.meextsetup" name="fig.meextsetup"></a>
-
- <p class="title"><b>Figure&#160;2.1.&#160;Extension
- setup in Multi-Edit</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.01.png" alt="Screenshot" />
- </div>
- </div>
-
- <p>Customize the right margin, tab spacing, indent style,
- and colors to values that you find comfortable. The edit
- mode should be &#8220;text,&#8221; and the tab settings
- should be set to &#8220;use tab and margin settings,
- ignore format line.&#8221;</p>
-
- <p>Select TEX as the language type, and add TeX as a
- compiler. One possible setting for TeX as a compiler (for
- LaTeX documents, in this case) is shown in Figure&#160;<a
- href="ch02.html#fig.melatexcmp"
- title="Figure&#160;2.2.&#160;LaTeX as a compiler in Multi-Edit">
- Figure&#160;2.2</a>.</p>
-
- <div class="figure">
- <a id="fig.melatexcmp" name="fig.melatexcmp"></a>
-
- <p class="title"><b>Figure&#160;2.2.&#160;LaTeX as a
- compiler in Multi-Edit</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.02.png" alt="Screenshot" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2866543"
- name="id2866543"></a>Typing in Multi-Edit</h3>
- </div>
- </div>
-
- <p>Brace matching<a id="id2866552" class="indexterm"
- name="id2866552"></a> is provided automatically with
- Multi-Edit's template expansion support. Consult your
- Multi-Edit reference for more information about
- templates.</p>
-
- <p>Multi-Edit language support does not include any TeX
- key bindings by default. However, the macros are
- provided, and you can install them with the
- &#8220;Other/Install/Key mapping...&#8221; menu. The
- following macros are available:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p><tt>tex^texquote</tt> inserts the appropriate
- quotation marks. This macro can be bound to
- <b>"</b> to provide smart quoting<a id="id2866605"
- class="indexterm" name="id2866605"></a>.</p>
- </li>
-
- <li>
- <p><tt>tex^texnquote</tt> inserts the literal
- double quote. It can be bound to <b>Alt-"</b>, for
- example.</p>
- </li>
-
- <li>
- <p><tt>tex^texreformat</tt> is a replacement for
- the reformat macro. If the filename extension is
- <tt>.tex</tt>, this macro reformats the paragraph
- with sensitivity to TeX macros. Otherwise it calls
- the default reformatting macro.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2866670"
- name="id2866670"></a>Running TeX</h3>
- </div>
- </div>
-
- <p>Running TeX within Multi-Edit is accomplished by
- specifying a compiler for TeX or LaTeX documents<a
- id="id2866678" class="indexterm" name="id2866678"></a>.
- In Figure&#160;<a href="ch02.html#fig.melatexcmp"
- title="Figure&#160;2.2.&#160;LaTeX as a compiler in Multi-Edit">
- Figure&#160;2.2</a>, a batch file called <tt>TEXIT</tt>
- is being used as the compiler for documents with the
- extension <tt>.tex</tt>.</p>
-
- <p>Automatic compilation and location of errors is
- provided by Multi-Edit language support when you have
- selected <tt>TEX</tt> as the language-type for
- <tt>.tex</tt> files.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2866742"
- name="id2866742"></a>Brief</h2>
- </div>
- </div>
-
- <p><b>Brief</b><a id="id2866755" class="indexterm"
- name="id2866755"></a><a id="id2866765" class="indexterm"
- name="id2866765"></a><a id="id2866775" class="indexterm"
- name="id2866775"></a> is a powerful programmer's editor
- recently acquired by Borland International<a id="id2866788"
- class="indexterm" name="id2866788"></a>. It is available
- for both DOS and OS/2 systems. Like the other editors
- discussed in this section, <b>Brief</b> offers a strong set
- of programming features, including the ability to run
- compilers automatically, and a flexible, C-like macro
- programming language that allows you to customize the
- editor.</p>
-
- <p>There is a LaTeX editing environment for <b>Brief</b> in
- the CTAN archives. It includes multiple-language support
- (currently supporting Norwegian) and control-key shortcuts
- for many common LaTeX commands.</p>
-
- <p>The installation and setup program includes instructions
- for defining program compilers. TeX can be defined to
- process files with particular extensions. Once again, it is
- a good idea to have the editor run a batch file so that the
- batch file can determine what format file to use when
- processing the document.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2866836"
- name="id2866836"></a>MicroEMACS</h2>
- </div>
- </div>
-
- <p><b>MicroEMACS</b><a id="id2866848" class="indexterm"
- name="id2866848"></a><a id="id2866855" class="indexterm"
- name="id2866855"></a><a id="id2866865" class="indexterm"
- name="id2866865"></a> is a powerful emacs-like editor for
- MS-DOS and Microsoft Windows.<sup>[<a id="id2866878"
- name="id2866878" href="#ftn.id2866878">22</a>]</sup>
- Figure&#160;<a href="ch02.html#fig.editing.mew"
- title="Figure&#160;2.3.&#160;Editing a file with MicroEMACS">
- Figure&#160;2.3</a> shows an example of <b>MicroEMACS</b>
- editing a LaTeX document. In this case, the LaTeX
- extensions to <b>MicroEMACS</b> have been loaded, and
- &#8220;Help&#8221; is selected.</p>
-
- <div class="figure">
- <a id="fig.editing.mew" name="fig.editing.mew"></a>
-
- <p class="title"><b>Figure&#160;2.3.&#160;Editing a file
- with MicroEMACS</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.03.png" alt="Screenshot" />
- </div>
- </div>
-
- <p>The online help for LaTeX is shown in Figure&#160;<a
- href="ch02.html#fig.winhelp"
- title="Figure&#160;2.4.&#160;Microsoft Windows online help for LaTeX">
- Figure&#160;2.4</a>. This is a Microsoft Windows help file,
- available independently of <b>MicroEMACS</b> (although it
- is nicely integrated here).</p>
-
- <div class="figure">
- <a id="fig.winhelp" name="fig.winhelp"></a>
-
- <p class="title"><b>Figure&#160;2.4.&#160;Microsoft
- Windows online help for LaTeX</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.04.png" alt="Screenshot" />
- </div>
- </div>
-
- <p>The <b>MicroEMACS</b> environment also has the ability
- to run other programs (including TeX to process documents)
- and process the error output to aid in locating errors.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2867057"
- name="id2867057"></a>epm: OS/2's Enhanced Editor</h2>
- </div>
- </div>
-
- <p><b>epm</b><a id="id2867070" class="indexterm"
- name="id2867070"></a><a id="id2867077" class="indexterm"
- name="id2867077"></a>, the enhanced editor for OS/2, can be
- used to edit TeX documents. The <b>epmtex</b><a
- id="id2867094" class="indexterm" name="id2867094"></a>
- package adds a TeX item to the menu bar as shown in
- Figure&#160;<a href="ch02.html#fig.editing.epm"
- title="Figure&#160;2.5.&#160;Editing a TeX document with epm under OS/2">
- Figure&#160;2.5</a>.</p>
-
- <div class="figure">
- <a id="fig.editing.epm" name="fig.editing.epm"></a>
-
- <p class="title"><b>Figure&#160;2.5.&#160;Editing a TeX
- document with epm under OS/2</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.05.png" alt="Screenshot" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2867165"
- name="id2867165"></a>Other Tools</h2>
- </div>
- </div>
-
- <p>There are many other editors that can be effective tools
- for editing TeX documents. Some of the editors that you
- might want to consider are <b>Jove</b><a id="id2867182"
- class="indexterm" name="id2867182"></a>, an emacs-like
- editor; <b>Xnot</b><a id="id2867203" class="indexterm"
- name="id2867203"></a>, a Windows port of emacs;
- <b>LSedit</b><a id="id2867217" class="indexterm"
- name="id2867217"></a>, the VMS language-sensitive editor;
- and <b>Alpha</b><a id="id2867232" class="indexterm"
- name="id2867232"></a> and <b>BBedit</b><a id="id2867246"
- class="indexterm" name="id2867246"></a>, two Macintosh
- editors described in Chapter&#160;<a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a>,
- <span class="emphasis"><em><a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a></em></span>.</p>
-
- <p>There are also a number of tools designed specifically
- for editing TeX documents. <b>Scientific Word</b><a
- id="id2867285" class="indexterm" name="id2867285"></a>, a
- commercial environment, is described in Chapter&#160;<a
- href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a>,
- <span class="emphasis"><em><a href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a></em></span>.
- Several free tools (<b>MathPad</b><a id="id2867324"
- class="indexterm" name="id2867324"></a>, <b>Doc</b>, and
- <b>XTeXShell</b><a id="id2867344" class="indexterm"
- name="id2867344"></a>, for example) also exist, although
- none were available<sup>[<a id="id2867356" name="id2867356"
- href="#ftn.id2867356">23</a>]</sup> in time for review in
- this edition of <i>Making TeX Work</i>.</p>
-
- <p>Another helpful tool is <b>LaCheck</b><a id="id2867378"
- class="indexterm" name="id2867378"></a>, a LaTeX syntax
- checker. <b>LaCheck</b> attempts to find and identify
- problems with your document that will cause it to format
- incorrectly. It runs much more quickly than TeX over a long
- document and may identify some things (like</p>
-
- <p>missing italic correction) that are potentially
- incorrect, even though they are not errors that will
- prevent the document from formatting.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2867406"
- name="id2867406"></a>TeX as a Compiler</h2>
- </div>
- </div>
-
- <p>This section discusses how to use TeX like a compiler<a
- id="id2867415" class="indexterm" name="id2867415"></a> from
- within your editor, and it is rather technical. You should
- read this section before you attempt to program your own
- editor to run TeX (if it doesn't already include support
- for TeX). You may not be interested in this material if you
- aren't planning to do that programming yourself. More
- details on the types of TeX output used in this section can
- be found in Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>.</p>
-
- <p>Many editors can run a compiler, capture the error
- messages that the compiler produces, and walk through the
- source file highlighting each error. Most editors with this
- functionality can run TeX as a &#8220;compiler&#8221; for
- documents.</p>
-
- <p>The discussion that follows is at a very abstract level.
- The details vary so much from one editor to the next that
- presenting more detail only confuses the issue further. To
- implement this feature, you'll need to read your editor
- reference carefully, and probably experiment on your own a
- little bit.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2867481"
- name="id2867481"></a>Processing a Document</h3>
- </div>
- </div>
-
- <p>Establish the TeX program as a compiler using whatever
- features your editor provides to set up a compiler.
- Experiment with your editor until you can process an
- error-free document.</p>
-
- <p>After you have everything working, it may be desirable
- to modify the compiler to run a batch file or shell
- script instead of invoking the TeX program directly. This
- will allow you to program the shell script so that it can
- determine which format file to use.</p>
-
- <p>Running TeX is only the first step. Next, you have to
- interpret the error messages<a id="id2867509"
- class="indexterm" name="id2867509"></a> that TeX
- produces. As a concrete example, Example&#160;<a
- href="ch02.html#ex.madeuperr"
- title="Example&#160;2.3.&#160;A Contrived Error">Example&#160;2.3</a>
- shows some contrived output which demonstrates an
- &#8220;undefined control sequence&#8221; error on line 6
- of the file <tt>wilma.tex</tt>.</p>
-
- <div class="example">
- <a id="ex.madeuperr" name="ex.madeuperr"></a>
-
- <p class="title"><b>Example&#160;2.3.&#160;A Contrived
- Error</b></p>
-<pre class="screen">
-This is TeX version 3.141...
-** (flintstone.tex
-some
-messages [1]
-(fred.tex [2]
-some more
-messages
-[3] ) (wilma.tex [4]
-! Undefined control sequence.
-the dog \dino
- tipped over the car.
-l.6 the dog \dino tipped over the car.
-</pre>
- </div>
-
- <p>Here are some suggestions for attacking the problem of
- programming your favorite editor to process TeX error
- messages<a id="id2867574" class="indexterm"
- name="id2867574"></a>:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">Using the log file</span></dt>
-
- <dd>
- <p>Don't worry about capturing the error messages
- that TeX produces. It is much easier to get the
- information from the log file<a id="id2867609"
- class="indexterm" name="id2867609"></a>. Log files
- are described in the section called &#8220;<a
- href="ch03.html#sec.logfiles" title="Log Files">the
- section called &#8220;Log Files&#8221;</a>&#8221;
- in Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>.</p>
- </dd>
-
- <dt><span class="term">Finding error
- messages</span></dt>
-
- <dd>
- <p>Any line in the log file that begins with an
- exclamation point is an error message. In
- Example&#160;<a href="ch02.html#ex.madeuperr"
- title="Example&#160;2.3.&#160;A Contrived Error">Example&#160;2.3</a>,
- the line that begins</p>
-<pre class="screen">
-! Undefined control sequence.
-</pre>
-
- <p>is an example of an error message.</p>
- </dd>
-
- <dt><span class="term">Finding the source
- line</span></dt>
-
- <dd>
- <p>Following the error message, TeX shows the
- context in which the error occurred. After that,
- the line that begins with
- <tt>l.<i><tt>nnn</tt></i></tt> (where
- <tt><i><tt>nnn</tt></i></tt> is some decimal
- number) identifies the line of the input file that
- TeX was processing when the error occurred (in
- Example&#160;<a href="ch02.html#ex.madeuperr"
- title="Example&#160;2.3.&#160;A Contrived Error">Example&#160;2.3</a>,
- TeX was on line 6 when the error occurred).</p>
- </dd>
-
- <dt><span class="term">Finding the source
- file</span></dt>
-
- <dd>
- <p>When processing a document that uses the \input
- command to include other files, there is no
- guaranteed method of finding out the name of the
- file TeX was processing when the error occurred.
- Whenever TeX starts processing a file, it prints an
- open parenthesis followed by the name of the file.
- When it finishes processing the document, it prints
- a close parenthesis.<sup>[<a id="id2867763"
- name="id2867763"
- href="#ftn.id2867763">24</a>]</sup> So the
- following algorithm <span
- class="emphasis"><em>usually</em></span> identifies
- what file the error occurred in:</p>
-
- <p>Beginning at the line in the log file that
- announces the error message (the line beginning
- with &#8220;!&#8221;), search backwards for the
- first unmatched open parenthesis. The word
- following that open parenthesis is probably the
- name of the file TeX was processing when the error
- occurred.</p>
- </dd>
-
- <dt><span class="term">Ignoring errors</span></dt>
-
- <dd>
- <p>When you run TeX &#8220;by hand,&#8221; you want
- TeX to stop and report errors to you as they occur
- in your document. But if your editor is going to
- handle any errors that occur, it is inconvenient to
- have TeX stop and ask questions. In fact, it may
- not be possible to run TeX from your editor in a
- way that makes it even <span
- class="emphasis"><em>feasible</em></span> for TeX
- to stop and ask questions. You can use several
- built-in control sequences to control the way TeX
- responds to errors. They are summarized in
- Table&#160;<a href="ch02.html#tab.modes"
- title="Table&#160;2.2.&#160;TeX Modes of Interaction ">
- Table&#160;2.2</a>.</p>
-
- <div class="table">
- <a id="tab.modes" name="tab.modes"></a>
-
- <p class="title"><b>Table&#160;2.2.&#160;TeX
- Modes of Interaction</b></p>
-
- <table summary="TeX Modes of Interaction "
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">Mode</th>
-
- <th align="left">TeX's Behavior</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\errorstopmode</td>
-
- <td align="left">Stop on errors (the
- default behavior)</td>
- </tr>
-
- <tr>
- <td align="left">\scrollmode</td>
-
- <td align="left">Scroll errors, stop on
- missing files</td>
- </tr>
-
- <tr>
- <td align="left">\nonstopmode</td>
-
- <td align="left">Scroll errors and missing
- files</td>
- </tr>
-
- <tr>
- <td align="left">\batchmode</td>
-
- <td align="left">Scroll both and don't
- summarize on screen</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>One common way of invoking TeX from an editor to
- process a document is to use the command:</p>
-<pre class="screen">
-tex \nonstopmode \input flintstone
-</pre>
-
- <p>This uses the features discussed in the section
- &#8220;<a href="ch03.html#sec.clineopts"
- title="The Command Line">the section called
- &#8220;The Command Line&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>
- to pass a command to TeX on the command line. In
- this case, the command tells TeX not to stop on any
- kind of error.</p>
- </dd>
-
- <dt><span class="term">Handling other
- errors</span></dt>
-
- <dd>
- <p>When searching for errors in the log file, you
- may find it helpful to search for lines that begin
- with the words &#8220;Overfull box&#8221;<a
- id="id2868015" class="indexterm"
- name="id2868015"></a> or &#8220;Underfull
- box&#8221;<a id="id2868029" class="indexterm"
- name="id2868029"></a> as well as lines that begin
- with an exclamation point. Because TeX does not
- print the <tt>l.nnn</tt> form of line-number
- message in this case, you will have to look for the
- line numbers in the warning message.</p>
-
- <p>Overfull box messages have the form:</p>
-
- <div class="informalexample">
-<pre class="screen">
-Overfull <span class="emphasis"><em>box</em></span> (<span
-class="emphasis"><em>99.9</em></span>pt too wide) in paragraph at lines <span
- class="emphasis"><em>n--m</em></span>
-</pre>
- </div>
-
- <p>The <tt><i><tt>box</tt></i></tt> will be either
- <tt>hbox</tt>, indicating that something is too
- wide, or <tt>vbox</tt> indicating that something is
- too tall or too deep. The distance,
- <tt><i><tt>99.9</tt></i>pt</tt>, indicates how
- badly the box is overfull, and
- <tt><i><tt>n</tt></i></tt> is the first line of the
- paragraph in which the error occurs. Underfull box
- messages are the same, except that they begin with
- the word &#8220;Underfull.&#8221;</p>
-
- <p>There are several control sequences that you can
- use to control how sensitive TeX is to
- &#8220;bad&#8221; boxes. Any good TeX reference
- will discuss these parameters in detail.</p>
- </dd>
- </dl>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2868148"
- name="id2868148"></a>Spellchecking</h2>
- </div>
- </div>
-
- <p>Checking for spelling mistakes<a id="id2868157"
- class="indexterm" name="id2868157"></a> is an important
- part of any document creation process. Checking TeX
- documents is difficult because these documents contain
- control sequences that aren't words in the traditional
- sense.</p>
-
- <p>Some editors offer ways of customizing the spellchecker.
- Multi-Edit, for example, allows you to indicate that any
- word beginning with a backslash should be ignored for the
- purpose of spellchecking. Figure&#160;<a
- href="ch02.html#fig.mespell"
- title="Figure&#160;2.6.&#160;Edit settings control word delimiters">
- Figure&#160;2.6</a> shows the &#8220;Other/Install/Edit
- Settings...&#8221; dialog where word delimiters are
- controlled. This simple customization goes a long way
- towards making spellchecking tolerable.</p>
-
- <p>External spellcheckers, such as the ones described here,
- can also frequently be customized to ignore TeX control
- sequences.</p>
-
- <div class="figure">
- <a id="fig.mespell" name="fig.mespell"></a>
-
- <p class="title"><b>Figure&#160;2.6.&#160;Edit settings
- control word delimiters</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.06.png" alt="Screenshot" />
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2868250"
- name="id2868250"></a>ispell</h3>
- </div>
- </div>
-
- <p><b>ispell</b><a id="id2868263" class="indexterm"
- name="id2868263"></a> is a common unix spellchecker. In
- addition to being available from the shell prompt, GNU
- emacs includes an <span
- class="emphasis"><em>ispell-mode</em></span> that handles
- TeX documents intelligently.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2868280"
- name="id2868280"></a>amSpell</h3>
- </div>
- </div>
-
- <p><b>amSpell<a id="id2868293" class="indexterm"
- name="id2868293"></a></b> is an MS-DOS spellchecker that
- includes special support for TeX documents. When
- spellchecking a TeX document, <b>amSpell</b> ignores all
- TeX control sequences, as well as mathematics and the
- arguments to reference and citation commands. The
- standard accent primitives are also recognized, and
- <b>amSpell</b> can identify and correct misspellings in
- words that use them.</p>
-
- <p>An example of <b>amSpell</b> checking a document is
- shown in Figure&#160;<a href="ch02.html#fig.amspell"
- title="Figure&#160;2.7.&#160;Spellchecking a document with amSpell">
- Figure&#160;2.7</a>.</p>
-
- <div class="figure">
- <a id="fig.amspell" name="fig.amspell"></a>
-
- <p class="title"><b>Figure&#160;2.7.&#160;Spellchecking
- a document with amSpell</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.07.png" alt="Screenshot" />
- </div>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2868394"
- name="id2868394"></a>Revision Control</h2>
- </div>
- </div>
-
- <p>Revision control<a id="id2868403" class="indexterm"
- name="id2868403"></a> allows you to track modifications to
- a file. It is frequently associated with programming where
- the ability to find and correct bugs relies on being able
- to recreate a problem exactly. It can be just as useful for
- writers wishing to keep track of changes to an evolving
- document. For example, I use revision control to keep track
- of which versions of each chapter my editor has seen.</p>
-
- <p>One of the most common revision control systems is RCS<a
- id="id2868424" class="indexterm" name="id2868424"></a>,
- which was derived from SCCS<a id="id2868433"
- class="indexterm" name="id2868433"></a>, a commercial
- package. RCS is freely available under the GNU license. It
- is possible to use RCS under unix, MS-DOS, and OS/2.</p>
-
- <p>The TeX macros shown in Example&#160;<a
- href="ch02.html#ex.rcsmac"
- title="Example&#160;2.4.&#160;Revision Control Macros for TeX Documents Using RCS}">
- Example&#160;2.4</a> can be used to include RCS information
- as marginal notes in a document. The marginal notes in this
- example are printed only when a draft is being
- produced.</p>
-
- <p>These macros are my own, you will find others in the
- CTAN archives in the directory
- <tt>macros/latex/contrib/misc</tt>.</p>
-
- <div class="example">
- <a id="ex.rcsmac" name="ex.rcsmac"></a>
-
- <p class="title"><b>Example&#160;2.4.&#160;Revision
- Control Macros for TeX Documents Using RCS}</b></p>
-<pre class="screen">
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-% RCS definitions...
-\newif\ifdraft
-\def\RCSID$#1${
- \ifdraft{\tolerance=100000
- \hbadness=100000
- \raggedright
- \marginpar{\tiny Draft #1}}
- \typeout{Draft #1}
- \else\typeout{Production run #1}\fi
-}
-
-\def\RCSmargid$#1: #2 #3 #4 #5 #6 #7${
-% #1 = &#8220;Id&#8221;
-% #2 = filename
-% #3 = vers
-% #4 = date
-% #5 = time
-% #6 = author
-% #7 = state [locker]
- \ifdraft
- \setbox0=\hbox to 0pt{
- \tolerance=100000
- \hbadness=100000
- \parbox{4in}{
- \rm\tiny #2\\ #3\\ #4}
- \hss}
- \marginpar{\box0}
- \typeout{Draft Id: #2 #3 #4 #5 #6 #7}
- \fi
-}
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2868511"
- name="id2868511"></a>TeX Shells</h2>
- </div>
- </div>
-
- <p>The iterative nature of TeX (edit, TeX, BibTeX, make
- indexes, preview, repeat) can be tedious to perform by
- hand. As a result, several TeX &#8220;shells&#8221;<a
- id="id2868526" class="indexterm" name="id2868526"></a> have
- been developed which provide a more automatic interface to
- many aspects of the TeX process. Several of these packages
- are described below. In everyday use, they make TeX much
- more user friendly.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2868544"
- name="id2868544"></a>TeXShell</h3>
- </div>
- </div>
-
- <p>TeXShell<a id="id2868553" class="indexterm"
- name="id2868553"></a> was designed as an add-on for
- emTeX<a id="id2868569" class="indexterm"
- name="id2868569"></a> (it installs directly into the
- emTeX directory hierarchy). This character-based
- interface is available for both MS-DOS and OS/2. TeXShell
- provides an editor, a complete help system, and fully
- customizable push-button access to TeX. An example of the
- TeXShell interface is shown in Figure&#160;<a
- href="ch02.html#fig.texshell"
- title="Figure&#160;2.8.&#160;TeXShell">Figure&#160;2.8</a>.
- The default TeX menu and help windows are shown.</p>
-
- <div class="figure">
- <a id="fig.texshell" name="fig.texshell"></a>
-
- <p class="title">
- <b>Figure&#160;2.8.&#160;TeXShell</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.08.png" alt="Screenshot" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2868647"
- name="id2868647"></a>TeXPert</h3>
- </div>
- </div>
-
- <p>TeXPert<a id="id2868656" class="indexterm"
- name="id2868656"></a> is a character-based shell for TeX.
- MS-DOS and OS/2 versions of TeXPert are available in
- either German or English. The default configuration files
- for TeXPert are designed to work with emTeX, but TeXPert
- does not install directly into the emTeX directory
- heirarchy. The TeXPert interface is shown in
- Figure&#160;<a href="ch02.html#fig.texpert"
- title="Figure&#160;2.9.&#160;TeXPert">Figure&#160;2.9</a>.</p>
-
- <div class="figure">
- <a id="fig.texpert" name="fig.texpert"></a>
-
- <p class="title">
- <b>Figure&#160;2.9.&#160;TeXPert</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.09.png" alt="Screenshot" />
- </div>
- </div>
-
- <p>TeXPert provides an editor, an archive tool for speedy
- access to commonly used files, and an interface to
- <b>grep</b> for quickly scanning files. The exact look
- and feel of TeXPert can be customized.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2868748"
- name="id2868748"></a>4TeX</h3>
- </div>
- </div>
-
- <p>The 4TeX<a id="id2868757" class="indexterm"
- name="id2868757"></a> system uses the <b>4DOS</b><a
- id="id2868776" class="indexterm" name="id2868776"></a>
- extended batch language and a number of utilities to
- integrate emTeX<a id="id2868784" class="indexterm"
- name="id2868784"></a> with a wide variety of free,
- shareware, and commercial tools. The system is well
- documented in a manual that describes installation,
- setup, use, and customization. The 4TeX interface is
- shown in Figure&#160;<a href="ch02.html#fig.fourtex"
- title="Figure&#160;2.10.&#160;4TeX">Figure&#160;2.10</a>.</p>
-
- <div class="figure">
- <a id="fig.fourtex" name="fig.fourtex"></a>
-
- <p class="title"><b>Figure&#160;2.10.&#160;4TeX</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.10.png" alt="Screenshot" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2868860"
- name="id2868860"></a>PMTeX</h3>
- </div>
- </div>
-
- <p>PMTeX<a id="id2868868" class="indexterm"
- name="id2868868"></a> is an OS/2 presentation manager
- program. Although it does not provide a built-in editor,
- it can control four independent DOS and OS/2 sessions,
- one each for editing, TeX processing, previewing, and
- printing. The options passed to each program can be
- controlled from the PMTeX Options menu.</p>
-
- <p>PMTeX was designed to work with emTeX, but can be
- configured to use any TeX system. PMTeX was also designed
- to support two preprocessors for phonetic transcription:
- the TeuTeX-P<a id="id2868895" class="indexterm"
- name="id2868895"></a> and ALDTeX-P<a id="id2868905"
- class="indexterm" name="id2868905"></a> scanners. These
- scanners are useful in dialectology and are available
- separately from PMTeX's author.</p>
-
- <p>A example of the PMTeX interface is shown in
- Figure&#160;<a href="ch02.html#fig.pmtex"
- title="Figure&#160;2.11.&#160;PMTeX">Figure&#160;2.11</a>.
- Note that the menu bar is very wide and does not fit in a
- standard 640x480 VGA window.</p>
-
- <div class="figure">
- <a id="fig.pmtex" name="fig.pmtex"></a>
-
- <p class="title">
- <b>Figure&#160;2.11.&#160;PMTeX</b></p>
-
- <div class="mediaobject">
- <img src="figures/tex.02.11.png" alt="Screenshot" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2868984"
- name="id2868984"></a>TeXit</h3>
- </div>
- </div>
-
- <p>The TeXit<a id="id2868993" class="indexterm"
- name="id2868993"></a> shell (which I wrote) is much less
- ambitious in many ways. Written entirely in Perl, TeXit
- does not offer a full screen interface or an editor at
- all. Instead, it provides a simple menu of choices as
- shown in Figure&#160;<a href="ch02.html#fig.texit"
- title="Figure&#160;2.12.&#160;TeXit">Figure&#160;2.12</a>
- (all of the menu choices are completely
- customizable).</p>
-
- <div class="figure">
- <a id="fig.texit" name="fig.texit"></a>
-
- <p class="title">
- <b>Figure&#160;2.12.&#160;TeXit</b></p>
-<pre class="screen">
-Processing: ./driver.tex
-Again? [?]status, [T]eX &amp; View, [b]ibtex, [c]leanup,
- [e]dit a file, [p]rint, [q]uery printer, [t]ex,
- [v]iew, e[x]it:
-</pre>
- </div>
-
- <p>One of TeXit's strengths is its ability to parse the
- log file created by TeX and to determine when additional
- actions are required. For example, TeXit will recognize
- when a document contains unresolved references and
- citations and can automatically run BibTeX and repeatedly
- run TeX to resolve the references. With the addition of a
- few &#8220;user specified&#8221; rules in the document,
- TeXit can easily handle index construction and other more
- sophisticated relationships.</p>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2788393" name="ftn.id2788393"
- href="#id2788393">17</a>]</sup> Most word processors can
- be coerced into saving your document in plain text. If
- your word processor can do this, you may be able to edit
- TeX documents with it.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2863345" name="ftn.id2863345"
- href="#id2863345">18</a>]</sup> On file systems that
- don't allow filenames to begin with a period, the name
- frequently begins with an underscore instead.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2863594" name="ftn.id2863594"
- href="#id2863594">19</a>]</sup> That's one of the reasons
- that the regular GNU emacs TeX modes are described
- first.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2863603" name="ftn.id2863603"
- href="#id2863603">20</a>]</sup> A 16MHz 386SX machine
- with only 8Mb of memory struggling to run GNU emacs under
- OS/2. ;-)</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2864021" name="ftn.id2864021"
- href="#id2864021">21</a>]</sup> A minor mode is a kind of
- editing environment provided by GNU emacs. If you are
- unfamiliar with minor modes, consult your emacs
- reference.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2866878" name="ftn.id2866878"
- href="#id2866878">22</a>]</sup> There are two versions of
- the program; the one discussed here is the version for
- Windows.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2867356" name="ftn.id2867356"
- href="#id2867356">23</a>]</sup> Or known to me,
- anyway.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2867763" name="ftn.id2867763"
- href="#id2867763">24</a>]</sup> Unfortunately,
- parentheses can occur in the log file for other
- reasons.</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;1.&#160;The Big Picture"
- href="ch01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;3.&#160;Running TeX"
- href="ch03.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Chapter&#160;1.&#160;The Big
- Picture&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;3.&#160;Running TeX</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch03.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch03.html
deleted file mode 100644
index 788caf7f753..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch03.html
+++ /dev/null
@@ -1,1894 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;3.&#160;Running TeX</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX" />
- <link rel="previous" href="ch02.html"
- title="Chapter&#160;2.&#160;Editing" />
- <link rel="next" href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;2.&#160;Editing"
- href="ch02.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;4.&#160;Macro Packages"
- href="ch04.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.running"
- name="chap.running"></a>Chapter&#160;3.&#160;Running
- TeX</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>The heart of processing a document with TeX is running<a
- id="id2862591" class="indexterm" name="id2862591"></a><a
- id="id2862603" class="indexterm" name="id2862603"></a> the
- TeX program. In this chapter, you'll learn what happens
- between the time you first start the TeX program and the time
- it finishes. You'll also learn what files TeX really needs
- (in addition to your document) and what to do when TeX finds
- things in your document that it doesn't understand.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="run.sec.formatfiles"
- name="run.sec.formatfiles"></a>What Do You Run?</h2>
- </div>
- </div>
-
- <p>The first thing you have to know is what program to run.
- Unfortunately, the actual file you have to execute varies
- between platforms and implementations. If you have built
- and/or installed TeX yourself, you probably already know
- what program to run. You'll have to ask your system
- administrator for help if you can't figure out what the
- name of the TeX executable is on your computer. The rest of
- this chapter assumes that the command <tt>tex</tt> runs
- TeX. You should substitute the name of the executable
- program on your own system for <tt>tex</tt><a
- id="id2862504" class="indexterm" name="id2862504"></a> in
- the examples that follow.</p>
-
- <p>Most implementations of TeX have some hard-coded memory
- limits<a id="id2862517" class="indexterm"
- name="id2862517"></a>. These limitations may cause problems
- if you are trying to run a very complex document through
- TeX. To combat this problem, some distributions include two
- versions of the TeX executable. One version is a
- &#8220;small&#8221; TeX<a id="id2862533" class="indexterm"
- name="id2862533"></a><a id="id2862543" class="indexterm"
- name="id2862543"></a> that generally runs faster but has
- less memory available to process your documents. The other
- version, a &#8220;big&#8221; TeX<a id="id2869219"
- class="indexterm" name="id2869219"></a><a id="id2869229"
- class="indexterm" name="id2869229"></a>, can process more
- complex documents but may run more slowly. If you get a
- &#8220;TeX capacity exceeded&#8221; error, and you have a
- big TeX available on your system, try processing your
- document with the big TeX.</p>
-
- <p>If you still get an error, you have a document that is
- simply too complex for your implementation of TeX to
- handle, or you have an error in one of the macros in your
- document. By examining the error log, described later in
- this chapter in the section &#8220;<a
- href="ch03.html#sec.logfiles" title="Log Files">the section
- called &#8220;Log Files&#8221;</a>,&#8221; you can
- determine what macro TeX is interpreting when the error
- occurs. If the error occurs in a macro that you wrote,
- check to make sure the macro functions the way you intended
- by using it in a small test document.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2869278"
- name="id2869278"></a>What Files Does TeX Need?</h2>
- </div>
- </div>
-
- <p>Naturally, TeX needs your input file in order to process
- it. However, TeX must be able to find several other files<a
- id="id2869287" class="indexterm" name="id2869287"></a><a
- id="id2869299" class="indexterm" name="id2869299"></a> as
- well. The files that TeX needs are normally created during
- the installation process. Here is a common directory layout
- for TeX on a unix system:</p>
-
- <div class="informaltable">
- <table border="1">
- <colgroup>
- <col />
- <col />
- </colgroup>
-
- <tbody>
- <tr>
- <td><tt>/usr/local/lib/tex/formats</tt></td>
-
- <td>Format files</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/pool</tt></td>
-
- <td>Pool files</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/formats</tt></td>
-
- <td>Format files</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/inputs</tt></td>
-
- <td>&#8220;System&#8221; input files</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/macros</tt></td>
-
- <td>(styles, macros, and miscellaneous</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/lib</tt></td>
-
- <td>files distributed with TeX)</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/ps</tt></td>
-
- <td>PostScript support files</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/fonts/pk</tt></td>
-
- <td><tt>PK</tt> fonts</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/fonts/vf</tt></td>
-
- <td>Virtual fonts</td>
- </tr>
-
- <tr>
- <td><tt>/usr/local/lib/tex/fonts/tfm</tt></td>
-
- <td><tt>TFM</tt> metrics</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>A similar layout is frequently used on other operating
- systems, except that the TeX files are often stored in a
- top-level directory (for example, <tt>C:$\$TEX</tt> under
- MS-DOS). Because TeX is very flexible and has many
- different implementations, the exact directory structure
- varies. Pool files are sometimes placed in the format file
- directory (which is sometimes called <tt>fmt</tt> or
- <tt>fmts</tt>, rather than <tt>formats</tt>). Input files
- may occur in one or more of the standard places listed
- above (<tt>inputs</tt>, <tt>macros</tt>, and <tt>lib</tt>)
- as well as a number of other places (<tt>texinputs</tt> is
- another common name).</p>
-
- <p>The files under the TeX tree usually come from outside
- distributions, so you don't have to change them often. (You
- definitely <span class="emphasis"><em>shouldn't</em></span>
- put your personal macro files in that tree, even if you do
- have access to it.)</p>
-
- <p>The following sections describe, in more detail, each of
- the files that TeX needs.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2869610"
- name="id2869610"></a>Pool Files</h3>
- </div>
- </div>
-
- <p>Pool files contain string constants used by TeX at
- runtime. Each time TeX is compiled, it creates a pool
- file<a id="id2869621" class="indexterm"
- name="id2869621"></a> unique to the version being
- compiled. The pool file from one version of TeX will not
- work with a different version.</p>
-
- <p>In contrast to format files (discussed in the next
- section), if you don't have a pool file, there's nothing
- you can do about it. If you obtained precompiled programs
- (from the Internet, from a friend, or commercially) and
- you don't have a pool file, you received an incomplete
- distribution.</p>
-
- <p>If you did not install TeX yourself, but find that the
- pool file is missing, contact the system administrator
- who performed the installation. He or she did something
- wrong.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2869651"
- name="id2869651"></a>Format Files</h3>
- </div>
- </div>
-
- <p>As mentioned in the section &#8220;<a
- href="ch01.html#sec.tex.controlsequences"
- title="Boxes and Glue">the section called &#8220;Boxes
- and Glue&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a>,
- <span class="emphasis"><em><a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a></em></span>,
- all of the control sequences and macros that your
- document uses must be defined somewhere. One way to do
- this is to use the \input command to load all of the
- definitions at the beginning of each document. However,
- with large macro packages like LaTeX, this process can be
- very time consuming. Format files<a id="id2869699"
- class="indexterm" name="id2869699"></a> are a way of
- predefining control sequences and macros so they don't
- have to be interpreted by TeX every time they're used. If
- TeX didn't use format files, you'd have to wait for TeX
- to interpret all of LaTeX every time you processed a
- document that used LaTeX.</p>
-
- <p><a id="run.sec.initexintro"
- name="run.sec.initexintro"></a>Format files are created
- by a special version of TeX, usually called iniTeX<a
- id="id2869724" class="indexterm" name="id2869724"></a>.
- Some implementations combine TeX and iniTeX into one
- program. In this case, you must select iniTeX with a
- special option when you run TeX. IniTeX interprets all
- the control sequences in a macro package and builds the
- in-memory data structures that the TeX program needs.
- After loading the whole macro package, iniTeX writes the
- memory image it has constructed to a format file. When
- TeX later loads the format file, it simply copies it into
- memory; no interpretation is necessary. This is why
- loading a format file is such a fast way to define
- control sequences<a id="id2869736" class="indexterm"
- name="id2869736"></a>. This is also why format files are
- not usually portable from one system to another,<sup>[<a
- id="id2869760" name="id2869760"
- href="#ftn.id2869760">25</a>]</sup> or even between
- different versions of TeX on the same system. Different
- versions of TeX are stored differently in memory, and
- this difference in loading makes the format files
- incompatible. For this reason, you need a
- &#8220;big&#8221; iniTeX to make format files for a big
- TeX and a &#8220;small&#8221; iniTeX for a small TeX.</p>
-
- <p>You will find a complete discussion of macro packages
- and instructions for building format files for many of
- the common macro packages in Chapter&#160;<a
- href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.userfiles"
- name="sec.userfiles"></a>User Files</h3>
- </div>
- </div>
-
- <p>When you run TeX<a id="id2869826" class="indexterm"
- name="id2869826"></a>, you have to tell it what file to
- process. If you specify a complete pathname, TeX will
- load the specific file that you request. For example, I
- could process the document <tt>myreport.tex</tt> in the
- directory <tt>/home/norm/tex/</tt> by running:</p>
-<pre class="screen">
-\$ <span class="bold"><b>tex /home/norm/tex/myreport</b></span>
-</pre>
-
- <p>This example applies to both unix and PC
- implementations of TeX. Even though MS-DOS and OS/2
- typically use the backslash to separate directory names,
- <span class="emphasis"><em>always</em></span> use a
- forward slash when entering filenames for TeX.</p>
-
- <p>If you specify a simple filename without a path, TeX
- looks for the file in several user-defined and, possibly,
- system-defined locations. In the following example, TeX
- will attempt to locate the file <tt>myreport.tex</tt> in
- order to process it:</p>
-<pre class="screen">
-\$ <span class="bold"><b>tex myreport</b></span>
-</pre>
-
- <p>If the file <tt>myreport.tex</tt> exists in several
- directories, TeX will process the first file it finds
- without looking for any others. TeX always prints the
- complete name of the file it processes both on the
- display and in the log file, so you can always tell what
- file was really processed.</p>
-
- <p>The most common way to specify user-defined locations
- is by setting the <tt>TEXINPUTS</tt> environment
- variable<sup>[<a id="id2869931" name="id2869931"
- href="#ftn.id2869931">26</a>]</sup> to a list of
- subdirectories where TeX documents are kept. Setting
- <tt>TEXINPUTS</tt> specifies where TeX should look for
- <span class="emphasis"><em>documents</em></span> (files
- that you input with \input or some other construct, style
- files, and macros). To change where TeX looks for other
- kinds of files (fonts, formats, pool files, etc.),
- setting different environment variables or performing
- some other customization is required. The format of the
- environment variable differs according to the platform
- you use. On unix systems, it is a list of directory names
- separated by colons. Here is a typical example:</p>
-<pre class="screen">
-.:/usr/local/lib/tex/inputs:/home/norm/tex/inputs
-</pre>
-
- <p>On MS-DOS and OS/2 systems, it is a list of directory
- names separated by semicolons. A typical example looks
- like this:<sup>[<a id="id2869999" name="id2869999"
- href="#ftn.id2869999">27</a>]</sup></p>
-<pre class="screen">
-.;\tex\inputs;\tex\styles;\tex\macros
-</pre>
-
- <p>Consult the documentation for your particular
- implementation of TeX for more information about
- system-defined locations where TeX looks for input files.
- Unfortunately, this is not always well documented. For
- example, an undocumented feature of version 1.4s of emTeX
- always searches in the directory
- <tt>\emtex\texinputs</tt> even if it does not occur in
- the <tt>TEXINPUTS</tt> path. In fact, there is no way to
- tell it <span class="emphasis"><em>not</em></span> to
- look there, short of renaming the directory (which is
- what I did).</p>
-
- <p>If TeX cannot find a file you specify, for example
- <tt>rpt-data.tex</tt>, it displays a prompt like this
- one:</p>
-<pre class="screen">
-! I can't find file `rpt-data.tex'.
-&lt;*&gt; \input rpt-data
-
-Please type another input filename:
-</pre>
-
- <p>The general form of TeX error messages is discussed in
- the section called &#8220;<a href="ch03.html#sec.errors"
- title="What About Errors?">the section called &#8220;What
- About Errors?&#8221;</a>&#8221; later in this chapter.
- TeX announces an error by printing the error message on a
- line that begins with an exclamation mark. Below the
- error, TeX provides the context in which the error
- occurred. In the example above, TeX encountered the
- command \input rpt-data and tried to find the file
- <tt>rpt-data.tex</tt> which it could not locate.</p>
-
- <p>Notice that TeX automatically added the extension
- <tt>.tex</tt><a id="id2870120" class="indexterm"
- name="id2870120"></a> to the name of the file it was
- looking for. In any context where you specify a filename,
- TeX will append <tt>.tex</tt> unless you specify an
- alternate extension.</p>
-
- <p>TeX responds to a &#8220;can't find file&#8221; error
- by asking you to type the name of a different file. Some
- implementations of TeX allow you to abort by typing
- Ctrl-C or Ctrl-D at this point,<sup>[<a id="id2870149"
- name="id2870149" href="#ftn.id2870149">28</a>]</sup> but
- other implementations insist that you enter a filename.
- In this case, you'll find it convenient to create an
- empty file called <tt>nul.tex</tt><a id="id2870165"
- class="indexterm" name="id2870165"></a> in a directory in
- your <tt>TEXINPUTS</tt> path so you can get around this
- requirement by supplying a dummy answer to the prompt.
- <tt>nul.tex</tt> is part of many standard
- distributions.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.clineopts" name="sec.clineopts"></a>The Command
- Line</h2>
- </div>
- </div>
-
- <p>Except for the name of a document, TeX has very few
- command-line options<a id="id2870206" class="indexterm"
- name="id2870206"></a>. The only option that is regularly
- used is the name of a format file, but the use of this
- option is frequently buried inside a batch file or shell
- script.</p>
-
- <p>It is helpful to think of TeX, LaTeX, SliTeX,
- etc.&#160;as different text processors (they aren't really;
- they're all TeX with different format files). This illusion
- is easy to provide with shell scripts or batch files. For
- example, on an MS-DOS system, you could easily have three
- batch files called <tt>tex.bat</tt>, <tt>latex.bat</tt>,
- and <tt>slitex.bat</tt>:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>The <tt>tex.bat</tt> file runs the TeX executable
- with the <tt>plain</tt> format file specified as an
- option.</p>
- </li>
-
- <li>
- <p>The <tt>latex.bat</tt> file runs TeX with the
- <tt>lplain</tt> format file.</p>
- </li>
-
- <li>
- <p>The <tt>slitex.bat</tt> file runs TeX with the
- <tt>splain</tt> format file.</p>
- </li>
- </ul>
- </div>
-
- <p>Now typing <span class="bold"><b>tex <span
- class="emphasis"><em>filename</em></span></b></span>
- processes Plain TeX documents; typing <span
- class="bold"><b>latex <span
- class="emphasis"><em>filename</em></span></b></span>
- processes LaTeX documents; and typing <span
- class="bold"><b>slitex <span
- class="emphasis"><em>filename</em></span></b></span>
- processes SliTeX documents.<sup>[<a id="id2870360"
- name="id2870360" href="#ftn.id2870360">29</a>]</sup> The
- role of format files and macro packages is described fully
- in Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.runtex.cmdcautions"
- name="sec.runtex.cmdcautions"></a>Command-line
- Options</h3>
- </div>
- </div>
-
- <p>A formal specification of the TeX command line<a
- id="id2870407" class="indexterm" name="id2870407"></a>
- looks like this:</p>
-
- <div class="informalexample">
-<pre class="screen">
-$ tex &lt;<span
-class="emphasis"><em>switches</em></span>&gt; &lt;&amp;<span
-class="emphasis"><em>format</em></span>&gt; &lt;|<span
-class="emphasis"><em>document</em></span>&gt; &lt;<span
-class="emphasis"><em>tex-commands</em></span>&gt;
-</pre>
- </div>
-
- <p>If this looks confusing, have no fear. I'll explain
- what it means in English.</p>
-
- <p>After the name of the TeX program (or batch file), the
- first things that can go on the command line are
- implementation-dependent switches and options. For
- example, implementations of TeX that combine iniTeX and
- TeX into a single program may use <span
- class="bold"><b>/I</b></span> as the switch to specify
- that iniTeX processing<a id="id2870468" class="indexterm"
- name="id2870468"></a> is desired (iniTeX, you may
- remember, was described in the section &#8220;<a
- href="ch03.html#run.sec.formatfiles"
- title="What Do You Run?">the section called &#8220;What
- Do You Run?&#8221;</a>,&#8221; earlier in this chapter).
- There are no system-independent switches for TeX. Consult
- the documentation that comes with your implementation for
- more information about system-dependent switches.</p>
-
- <p>After any system-dependent switches, the first thing
- that you can put on the TeX command line is the name of
- the format file<a id="id2870509" class="indexterm"
- name="id2870509"></a> to use. If you specify this option,
- you must include it before any other options, and you
- must put an ampersand (&amp;)<a id="id2870520"
- class="indexterm" name="id2870520"></a> in front of the
- format file name. If you do not specify a format file,
- TeX will use a default format, usually Plain TeX.</p>
-
- <p>After the format, TeX looks for the name of a document
- to process. If TeX finds a filename on the command line,
- it will process the document<a id="id2870537"
- class="indexterm" name="id2870537"></a> contained in that
- file before looking at any other options that may
- follow.</p>
-
- <p>Finally, you can insert arbitrary TeX commands on the
- command line by typing them just as you would in a
- document. The section &#8220;<a
- href="ch02.html#sec.texcomp" title="Running TeX">the
- section called &#8220;Running TeX&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a>,
- <span class="emphasis"><em><a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a></em></span>,
- describes one particular instance where this is very
- useful, but it isn't something that you are likely to do
- very often.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2870602"
- name="id2870602"></a>Command-line Cautions</h3>
- </div>
- </div>
-
- <p>There are some special restrictions on file names used
- on the command line and on the way TeX interprets the
- command line. These restrictions are summarized here.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="run.sec.misinterpret"
- name="run.sec.misinterpret"></a>Misinterpretation
- of the command line</h4>
- </div>
- </div>
-
- <p>Command lines that are typed at the operating system
- prompt are actually seen by your operating system's
- &#8220;command processor&#8221; before they are seen by
- TeX. You must be aware of special processing that might
- be performed by the command processor. Under unix, for
- example, the backslash<a id="id2870634"
- class="indexterm" name="id2870634"></a> is frequently
- interpreted as a <span class="emphasis"><em>shell
- escape</em></span> character<a id="id2870656"
- class="indexterm" name="id2870656"></a>, and the
- ampersand<a id="id2870668" class="indexterm"
- name="id2870668"></a> has another special meaning
- related to job control<a id="id2870677"
- class="indexterm" name="id2870677"></a>. The ampersand
- is also special under some MS-DOS and OS/2 command
- processors where it is the default command separation
- character and will not be passed to TeX as you would
- expect.</p>
-
- <p>To insert these troublesome characters literally,
- you must enclose the relevant sections of the command
- line in quotation marks<a id="id2870695"
- class="indexterm" name="id2870695"></a> or use some
- form of shell escape mechanism. Under unix, place the
- name of the format file, including the ampersand, in
- double or single quotes and use two backslashes in a
- row if you include TeX control sequences on the command
- line. For example, type:</p>
-
- <div class="informalexample">
-<pre class="screen">
-$ <span
-class="bold"><b>tex '&amp;lplain' \\nonstopmode \\input doc1</b></span>
-</pre>
- </div>
-
- <p>instead of</p>
-
- <div class="informalexample">
-<pre class="screen">
-$ <span
-class="bold"><b>tex &amp;lplain \nonstopmode \input doc1</b></span>
-</pre>
- </div>
-
- <p>When using OS/2, place a ^ in front of an ampersand
- to prevent it from being interpreted as a command
- separator.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.runtex.texwoopts"
- name="sec.runtex.texwoopts"></a>Filenames and
- TeX</h4>
- </div>
- </div>
-
- <p><a id="id2870772" class="indexterm"
- name="id2870772"></a><a id="id2870779"
- class="indexterm" name="id2870779"></a> <a
- id="id2870793" class="indexterm" name="id2870793"></a>
- It is easy for TeX to recognize the presence of a
- format file on the command line; it must be the first
- option and it must begin with an ampersand.<sup>[<a
- id="id2870805" name="id2870805"
- href="#ftn.id2870805">30</a>]</sup> After the format
- file, TeX determines whether the next option is a file
- name by looking at the first character of the option.
- If the first character is not a backslash, it is a
- filename; otherwise it is a TeX command, and TeX
- assumes that no filename is present.</p>
-
- <p>On some systems, notably MS-DOS and OS/2, the
- backslash<a id="id2870848" class="indexterm"
- name="id2870848"></a> is used to delimit the
- subdirectory components of a file name. On other
- systems, a forward slash is used. Regardless of the
- system you use, filenames passed to TeX <span
- class="emphasis"><em>must</em></span> use forward
- slashes to delimit filenames.</p>
-
- <p>For example, TeX will not process the file
- <tt>letter.tex</tt> in the <tt>\tex\docs</tt> directory
- of the current drive if you execute the following
- command line on an MS-DOS system:</p>
-
- <div class="informalexample">
-<pre class="screen">
-\$ <span class="bold"><b>tex \tex\docs\letter</b></span>
-</pre>
- </div>
-
- <p>Instead, you must type the following, regardless of
- the operating system you're using:</p>
-
- <div class="informalexample">
-<pre class="screen">
-\$ <span class="bold"><b>tex /tex/docs/letter</b></span>
-</pre>
- </div>
-
- <p>If you don't, TeX will complain that the control
- sequence \tex is undefined. Even more confusing errors
- may result if the first subdirectory happens to be a
- valid control sequence.</p>
-
- <p>Unfortunately, filenames containing forward slashes
- are not always recognized by operating systems that use
- backslashes to delimit filenames. For example, under
- MS-DOS, <tt>IF EXIST C:/CONFIG.SYS</tt> returns
- false,<a id="id2870956" class="indexterm"
- name="id2870956"></a> even when a file called
- <tt>config.sys</tt> exists in the root directory of
- drive C:. Therefore, it is most convenient to use
- filenames with backslashes when other commands will be
- used (for example in a batch file). Filenames in batch
- files must have any backslashes translated into forward
- slashes before being passed to TeX. MS-DOS's command
- processor isn't really powerful enough, but the task is
- quite doable with JP Software<a id="id2870971"
- class="indexterm" name="id2870971"></a>'s <b>4DOS</b>
- command processor. <b>4DOS</b><a id="id2871000"
- class="indexterm" name="id2871000"></a> is a
- replacement for MS-DOS's normal command processor; it
- offers many advantages over the normal processor. You
- can get a shareware version of <b>4DOS</b> from many
- large MS-DOS archive sites on the Internet<sup>[<a
- id="id2871022" name="id2871022"
- href="#ftn.id2871022">31</a>]</sup> as well as most
- large bulletin board systems. The following lines,
- written in <b>4DOS</b><a id="id2871048"
- class="indexterm" name="id2871048"></a>'s extended
- batch language, will translate all backslashes in the
- environment variable <tt>TEXFN</tt> to forward
- slashes:</p>
-<pre class="screen">
-:FixBacks
- Set Count=%@Index[%TexFn,\]
- If "%Count" eq "-1" Goto FixDone
- Set Place=%@Eval[%Count+1]
- Set TexFn=%@SubStr[%TexFn,0,%Count]/%@SubStr[%TexFn,%Place]
- Goto FixBacks
-:FixDone
-</pre>
-
- <p>These lines also work under OS/2 with JP Software's
- <b>4OS2</b> command processor (akin to <b>4DOS</b>;
- shareware versions of <b>4OS2</b> are also available).
- The same task can be completed in a single line with
- <b>REXX</b><a id="id2871106" class="indexterm"
- name="id2871106"></a> under OS/2:</p>
-<pre class="screen">
-TEXFN = TRANSLATE(TEXFN, '\', '/')
-</pre>
-
- <p><b>REXX</b> is an interpreted systems-programming
- language distributed with OS/2. <b>REXX</b> runs under
- many other IBM operating systems in addition to OS/2.
- Several versions of <b>REXX</b> are available for
- MS-DOS and unix systems, too.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2871151"
- name="id2871151"></a>Multiple documents</h4>
- </div>
- </div>
-
- <p>Keep in mind<a id="id2871161" class="indexterm"
- name="id2871161"></a> that TeX interprets only the
- first option after the format file name as a document
- name. If you type the command line:</p>
-
- <div class="informalexample">
-<pre class="screen">
-\$ <span class="bold"><b>tex doc1 doc2</b></span>
-</pre>
- </div>
-
- <p>TeX will process only <tt>doc1.tex</tt> as a
- document. The result of the above command line<a
- id="id2871206" class="indexterm" name="id2871206"></a>
- will be exactly as if you had typed the literal word
- &#8220;doc2&#8221; at the very end of the file
- <tt>doc1.tex</tt>.</p>
-
- <p>To get TeX to process both <tt>doc1</tt> and
- <tt>doc2</tt> as documents, type a command like the
- following:</p>
-
- <div class="informalexample">
-<pre class="screen">
-\$ <span class="bold"><b>tex doc1 \input doc2</b></span>
-</pre>
- </div>
-
- <p>or, for complete clarity,</p>
-
- <div class="informalexample">
-<pre class="screen">
-\$ <span class="bold"><b>tex \input doc1 \input doc2</b></span>
-</pre>
- </div>
-
- <p>In either case, the structure of your document files
- must allow them to be concatenated together. TeX does
- not process <tt>doc1</tt> and then process
- <tt>doc2</tt> separately. Instead, it processes all of
- <tt>doc1</tt> and appends the text in the file
- <tt>doc2</tt> directly onto the end of
- <tt>doc1</tt>.</p>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2871334"
- name="id2871334"></a>TeX Without Options</h2>
- </div>
- </div>
-
- <p>If you run TeX without specifying any options<a
- id="id2871343" class="indexterm" name="id2871343"></a> at
- all, it prints out some introductory information, then
- produces a <tt>**</tt> prompt<a id="id2871366"
- class="indexterm" name="id2871366"></a> and stops. Here's
- what emTeX's <tt>tex386</tt> produces:</p>
-<pre class="screen">
-This is emTeX (tex386), Version 3.141 [3c-beta8]
-**
-</pre>
-
- <p>This is the only situation where the <tt>**</tt> prompt
- occurs. TeX now expects you to enter text. TeX will
- interpret anything you type after the <tt>**</tt> prompt
- <span class="emphasis"><em>exactly</em></span> as if you
- had typed it on the command line. All of the rules
- regarding slashes (described in &#8220;<a
- href="ch03.html#run.sec.misinterpret"
- title="Misinterpretation of the command line">the section
- called &#8220;Misinterpretation of the command
- line&#8221;</a>&#8221; earlier) apply to commands that you
- type at the <tt>**</tt> prompt. Remember, however, that
- input entered at the <tt>**</tt> prompt is not seen by the
- operating system, so don't use quotation marks or doubled
- backslashes.</p>
-
- <p>The last line of a document is usually a command telling
- TeX that the document is finished. TeX responds by writing
- the last page of the document and ending (returning control
- to the operating system). If a document doesn't end with
- such a command, TeX will wait for more input. When TeX runs
- out of input, it displays the <tt>*</tt> prompt<a
- id="id2871494" class="indexterm" name="id2871494"></a>
- (single asterisk). Anything you type at the <tt>*</tt>
- prompt is interpreted exactly as if it occurred in the
- document that TeX was processing. You cannot specify an
- alternate format or name a document at the <tt>*</tt>
- prompt. You can, however, use \input to insert another
- file.</p>
-
- <p>If emTeX processes a document called
- <tt>unended.tex</tt>:</p>
-<pre class="screen">
-% This is UNENDED.TEX
-Now is the time for all good men
-to come to the aid of their country.
-% Note: there's no \bye command to end
-% TeX's processing...
-</pre>
-
- <p>the following output appears on the terminal:</p>
-<pre class="screen">
-This is emTeX (tex386), Version 3.141 [3c-beta8]
-**unended
-(unended.tex)
-*
-</pre>
-
- <p>You can exit from the TeX program at the <tt>*</tt>
- prompt by telling TeX that it should stop processing the
- current document. Exactly how you get out depends on the
- format file you use. The following table shows the stop
- commands for some TeX macro packages<a id="id2871573"
- class="indexterm" name="id2871573"></a><a id="id2871590"
- class="indexterm" name="id2871590"></a><a id="id2871603"
- class="indexterm" name="id2871603"></a><a id="id2871616"
- class="indexterm" name="id2871616"></a><a id="id2871626"
- class="indexterm" name="id2871626"></a>.</p>
-
- <div class="table">
- <a id="id2871639" name="id2871639"></a>
-
- <p class="title"><b>Table&#160;3.1.&#160;</b></p>
-
- <table summary="" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">Package</th>
-
- <th align="left">Command</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">Plain TeX</td>
-
- <td align="left">\bye</td>
- </tr>
-
- <tr>
- <td align="left">LaTeX</td>
-
- <td align="left">\end{document}<a id="id2871705"
- class="indexterm" name="id2871705"></a></td>
- </tr>
-
- <tr>
- <td align="left">SliTeX</td>
-
- <td align="left">\end{document}</td>
- </tr>
-
- <tr>
- <td align="left">Lollipop</td>
-
- <td align="left">\Stop</td>
- </tr>
-
- <tr>
- <td align="left">TeXinfo</td>
-
- <td align="left"><tt>@bye</tt></td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>If you do not know which format is in use, you can
- almost always get out with the following steps:<sup>[<a
- id="id2871781" name="id2871781"
- href="#ftn.id2871781">32</a>]</sup></p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>Type a control sequence that TeX will not
- recognize (control sequences \undefined and
- \gobbledygook will work). TeX will respond with the
- question mark prompt.</p>
- </li>
-
- <li>
- <p>Enter <span class="bold"><b>x</b></span> at the
- prompt. The question mark prompt is discussed fully
- in the section &#8220;<a href="ch03.html#sec.qprompt"
- title="Interpreting TeX Error Messages">the section
- called &#8220;Interpreting TeX Error
- Messages&#8221;</a>,&#8221; later in this
- chapter.</p>
- </li>
- </ol>
- </div>
-
- <p>To continue the above example, if I type \undefined at
- the <tt>*</tt> prompt, TeX will respond:</p>
-<pre class="screen">
-This is emTeX (tex386), Version 3.141 [3c-beta8]
-**unended
-(unended.tex)
-*<span class="bold"><b>\undefined</b></span>
-! Undefined control sequence.
-&lt;*&gt; \undefined
-
-?
-</pre>
-
- <p>If I enter <span class="bold"><b>x</b></span> at the
- question mark prompt, TeX will print several informative
- messages and then end, returning control to the operating
- system.</p>
-<pre class="screen">
-This is emTeX (tex386), Version 3.141 [3c-beta8]
-**unended
-(unended.tex)
-*\undefined
-! Undefined control sequence.
-&lt;*&gt; \undefined
-
-? <span class="bold"><b>x</b></span>
-No pages of output.
-Transcript written on unended.log.
-</pre>
-
- <p>One word of caution: some macro packages redefine the
- meaning of the backslash (\)<a id="id2871940"
- class="indexterm" name="id2871940"></a> character so that
- it doesn't function as the beginning of a control sequence
- (for example, the TeXinfo format uses the at-sign,
- &#8220;@&#8221;). In this case, you must precede the
- undefined control sequence by the escape character, even if
- it isn't the backslash.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.errors" name="sec.errors"></a>What About
- Errors?</h2>
- </div>
- </div>
-
- <p>When you write TeX documents, you will occasionally make
- mistakes<a id="id2871979" class="indexterm"
- name="id2871979"></a><a id="id2871992" class="indexterm"
- name="id2871992"></a><a id="id2872002" class="indexterm"
- name="id2872002"></a> and as a result, TeX won't be able to
- process your document. There are six broad classes of
- mistakes you're likely to make:</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>Naming documents or files that TeX cannot
- find.</p>
- </li>
-
- <li>
- <p>Misspelling the name of a TeX control
- sequence.</p>
- </li>
-
- <li>
- <p>Failing to close an environment or forgetting to
- insert a closing brace after an opening brace.</p>
- </li>
-
- <li>
- <p>Using math operators outside of math mode or
- forgetting to close an opened math environment.</p>
- </li>
-
- <li>
- <p>Requesting a font that TeX cannot find.</p>
- </li>
-
- <li>
- <p>Everything else.</p>
- </li>
- </ol>
- </div>
-
- <p>TeX is legitimately criticized for having error messages
- that are very difficult to understand. TeX frequently
- provides far more information than you really need or want,
- and the excess information often obscures the actual cause
- of the error.</p>
-
- <p>Nevertheless, understanding what TeX does when it
- encounters an error will help make error messages easier to
- understand. Let's begin with an example. Example&#160;<a
- href="ch03.html#ex.badfonttex"
- title="Example&#160;3.1.&#160;The Document BADFONT.TEX">Example&#160;3.1</a>
- shows a simple LaTeX document using the New Font Selection
- Scheme (NFSS), which contains an error.<sup>[<a
- id="id2872107" name="id2872107"
- href="#ftn.id2872107">33</a>]</sup> The error is that the
- control sequence \Large, which has been redefined to
- request a 17pt font, contains a typo:
- \cs[fontsize]{fontsiz} should be \fontsize.<sup>[<a
- id="id2872135" name="id2872135"
- href="#ftn.id2872135">34</a>]</sup></p>
-
- <div class="example">
- <a id="ex.badfonttex" name="ex.badfonttex"></a>
-
- <p class="title"><b>Example&#160;3.1.&#160;The Document
- BADFONT.TEX</b></p>
-<pre class="screen">
-\documentstyle{article}
-% The following definition changes the font that LaTeX
-% uses for the 'Large' font. I have introduced a typo
-% into the definition, &#8220;\fontsiz&#8221; should be &#8220;\fontsize&#8221;.
-% The first time a \Large font is requested, an error will occur.
-\renewcommand{\Large}{\fontsiz{17}{20pt}\selectfont}
-\begin{document}
-
-This text precedes the first section header.
-
-% Note: LaTeX uses the \Large font in section
-% headers...this will fail in a confusing way
-% because the error is deep within the definition
-% of \section where \Large is used...
-\section{First Section}
-
-This is the first and only sentence of the first section.
-
-\end{document}
-</pre>
- </div>
-
- <p>When TeX processes this file, using LaTeX with the New
- Font Selection Scheme, it produces these error
- messages:</p>
-<pre class="screen">
-This is TeX, Version 3.1415 (C version 6.1)
-LaTeX Version 2.09 &lt;25 March 1992&gt; with NFSS2
-(badfont.tex (/work/nutshell/texguide/styles/latex/article.sty
-Standard Document Style `article' &lt;14 Jan 92&gt;.
-(/work/nutshell/texguide/styles/latex/art10.sty)) (badfont.aux)
-(/usr/local/lib/tex/inputs/nfss2/T1cmr.fd)
-! Undefined control sequence.
-\Large -&gt;\fontsiz{17}{20pt}\selectfont
-&lt;argument&gt; \reset@font \Large
- \bf
-\@sect ...x \ifdim \@tempskipa &gt;\z@ \begingroup #6
- \relax \@hangfrom {\hskip ...
-l.21 \end{section}
-\section{First Section}
-
-?
-</pre>
-
- <p>These messages exemplify the kind of confusing error
- messages that TeX produces. Remember the following rule:
- Always look at the first and last line of the TeX error
- message when trying to figure out what went wrong and where
- it went wrong. In this case, the first line is:</p>
-<pre class="screen">
-! Undefined control sequence.
-</pre>
-
- <p>and the last line is:</p>
-<pre class="screen">
-l.21 \end{section}
-\section{First Section}
-</pre>
-
- <p>The error is that the control sequence
- \cs[fontsize]{fontsiz} is not defined and TeX was
- processing line 21 of the file when it occurred.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.logfiles"
- name="sec.logfiles"></a>Log Files</h3>
- </div>
- </div>
-
- <p>You don't have to remember or write down the error
- messages that TeX produces. When TeX processes a
- document, it produces a transcript<a id="id2872267"
- class="indexterm" name="id2872267"></a> of everything
- that occurs; you can refer to this transcript later if
- you need to recall what errors occurred when you
- processed your document. TeX stores this transcript in a
- file which has the same name as the document and the
- extension <tt>.log</tt>. For example, if you process
- <tt>main.tex</tt>, TeX produces a transcript in
- <tt>main.log</tt>.</p>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>Log files go in the current directory. TeX always
- places the log file in the current directory, even if
- you specify a path when you format your document. For
- example, if you process <tt>lectures/main.tex</tt>, TeX
- produces a transcript in <tt>main.log</tt>, not in
- <tt>lectures/main.log</tt> as you might expect.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.qprompt"
- name="sec.qprompt"></a>Interpreting TeX Error
- Messages</h3>
- </div>
- </div>
-
- <p>The first line of a TeX error message begins with an
- exclamation point followed by the text of the message<a
- id="id2872354" class="indexterm" name="id2872354"></a>.
- The lines that follow it show the context in which the
- error occurred.<sup>[<a id="id2872367" name="id2872367"
- href="#ftn.id2872367">35</a>]</sup> In the previous
- example, the error message indicates an <tt>Undefined
- control sequence</tt>. This means that TeX encountered a
- control sequence which was not previously defined.</p>
-
- <p>The final line, which says <tt>l.21 \section{First
- Section}</tt>, occurs right above the question mark
- prompt. It identifies the line in your document that TeX
- was processing when it encountered the error. The error
- occurred when TeX was at line 21 of the file, and that
- line began with <tt>\section{First Section}</tt>.</p>
-
- <p>Between the first and last lines, TeX prints a
- detailed description of how the error occurred. This is
- necessary because the error may have occurred inside the
- replacement text of a macro that you used. When TeX
- encounters a control sequence, like \section, it has to
- look up the definition to figure out how to typeset your
- document. The definition of a control sequence may
- contain other control sequences which also have to be
- interpreted. It is possible for TeX to be several levels
- deep, as it was in this case, when an error occurs. To
- give the person who wrote the definition of the control
- sequence an opportunity to figure out what went wrong,
- TeX prints out a <span class="emphasis"><em>trace
- back</em></span><a id="id2872434" class="indexterm"
- name="id2872434"></a> of what happened before the error.
- As you gain experience with a particular macro package,
- you'll find the intervening lines more meaningful.</p>
-
- <p>Correcting an error depends entirely on the nature of
- the error. In this case, all you need to do is correct
- the typo.</p>
-
- <p>As stated above, there are six general classes of
- errors you might encounter when you run TeX. The
- following sections briefly describe each class.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2872461"
- name="id2872461"></a>Naming a File TeX Cannot
- Find</h3>
- </div>
- </div>
-
- <p>Missing documents are discussed in the section called
- &#8220;<a href="ch03.html#sec.userfiles"
- title="User Files">the section called &#8220;User
- Files&#8221;</a>,&#8221; earlier in this chapter.</p>
-
- <p>If you request a format file<a id="id2872489"
- class="indexterm" name="id2872489"></a> that cannot be
- found, TeX issues the following warning message:</p>
-<pre class="screen">
-Sorry, I can't find that format; will try the default
-</pre>
-
- <p>TeX then attempts to typeset your document with Plain
- TeX.<sup>[<a id="id2872514" name="id2872514"
- href="#ftn.id2872514">36</a>]</sup> To correct this
- problem, run TeX with the correct format file name. If
- the format file isn't available, you will have to build
- it. Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>,
- describes how to build format files for several common
- macro packages.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2872549"
- name="id2872549"></a>Misspelling a Control Sequence
- Name</h3>
- </div>
- </div>
-
- <p>Misspelling a control sequence name<a id="id2872558"
- class="indexterm" name="id2872558"></a> is one of the
- most common errors. For example, you might type
- \ipnut{chap1} in your document instead of \input{chap1}.
- The solution is straightforward and usually easy to
- identify. In many cases, you can simply proceed after
- encountering this error. Although TeX may not typeset
- your document correctly, you can continue to look for
- other errors. The section called &#8220;<a
- href="ch03.html#sec.qprompt"
- title="Interpreting TeX Error Messages">the section
- called &#8220;Interpreting TeX Error
- Messages&#8221;</a>,&#8221; later in this chapter,
- describes how to continue after an error.</p>
-
- <p>In some cases, TeX may become badly confused by a
- misspelled control sequence name, in which case you
- should give up and fix the spelling error before trying
- to process your document further. This may happen if you
- misspell a LaTeX environment name (\begin{itemze} instead
- of \begin{itemize}, for example),<sup>[<a id="id2872615"
- name="id2872615" href="#ftn.id2872615">37</a>]</sup>
- which will make LaTeX misinterpret many of the control
- sequences which follow.</p>
-
- <p>Sometimes TeX will complain that a control sequence is
- undefined when you <span
- class="emphasis"><em>know</em></span> that the control
- sequence is spelled correctly. When this occurs, make
- sure that you are using the correct format file (see the
- section &#8220;<a href="ch03.html#sec.clineopts"
- title="The Command Line">the section called &#8220;The
- Command Line&#8221;</a>&#8221; earlier in this chapter),
- loading the correct macro files, and using the correct
- style options.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2872653"
- name="id2872653"></a>Failure to Close an
- Environment</h3>
- </div>
- </div>
-
- <p>Failure to close an environment<a id="id2872662"
- class="indexterm" name="id2872662"></a> is another very
- common error. There are several distinct errors in this
- category:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Failure to insert a closing brace (<tt>}</tt>)
- for each opening brace may cause a &#8220;TeX
- capacity exceeded&#8221; error when TeX processes
- your document. This happens because sometimes TeX
- tries to read everything between braces into
- memory. If the closing brace is absent, TeX may run
- out of memory.</p>
-
- <p>If the braces are supposed to enclose the
- argument to a macro, you may also get this error:<a
- id="id2872709" class="indexterm"
- name="id2872709"></a></p>
-<pre class="screen">
-! Paragraph ended before <span
-class="emphasis"><em>macro</em></span> was complete.
-</pre>
-
- <p>In order to help detect errors of this type, TeX
- doesn't ordinarily allow the argument of a macro to
- consist of more than one paragraph, so the first
- blank line after the place where you failed to type
- the closing brace may produce this error.</p>
- </li>
-
- <li>
- <p>Failure to close a begin/end environment pair
- causes LaTeX to complain about a mismatch when it
- encounters the next
- \end{\texttt{<i><tt>environment</tt></i>}}
- command.<a id="id2872764" class="indexterm"
- name="id2872764"></a></p>
- </li>
-
- <li>
- <p>If your document ends with an open environment,
- TeX will warn you that:</p>
-<pre class="screen">
-! (\end occurs inside a group at level <span
-class="emphasis"><em>n</em></span>)
-</pre>
-
- <p>where <tt><i><tt>n</tt></i></tt> is the number
- of open groups, usually 1.</p>
- </li>
-
- <li>
- <p>Failure to close a mathematics environment will
- result in the error:</p>
-<pre class="screen">
-! Missing $ inserted
-</pre>
-
- <p>when TeX reaches a macro that does not make
- sense in mathematics mode (like \section) or when a
- surrounding group ends.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2872844"
- name="id2872844"></a>Math Outside of Math Mode</h3>
- </div>
- </div>
-
- <p>TeX has a lot of operators for special treatment of
- mathematical formulas. These operators must occur inside
- <span class="emphasis"><em>mathematics mode</em></span><a
- id="id2872858" class="indexterm" name="id2872858"></a>,<a
- id="id2872867" class="indexterm" name="id2872867"></a>
- which is usually delimited by dollar signs in your
- document.<a id="id2872879" class="indexterm"
- name="id2872879"></a></p>
-
- <p>If you attempt to use math operators, superscripts,
- subscripts, or other math-mode control sequences outside
- of mathematics mode, the following error will occur:<a
- id="id2872899" class="indexterm"
- name="id2872899"></a></p>
-<pre class="screen">
-! Missing $ inserted
-</pre>
-
- <p>This is your clue that a mathematics environment has
- not been closed properly or that you failed to open one
- before using a math-mode operator.</p>
-
- <p>For example, the underscore character is usually
- defined to be a math-mode operator which starts a
- subscript, in other words <tt>H${}_2$O</tt> produces
- &#8220;H${}_2$O&#8221; in your document.<sup>[<a
- id="id2872944" name="id2872944"
- href="#ftn.id2872944">38</a>]</sup> If you use the
- underscore outside of mathematics mode, such as in
- regular text:</p>
-<pre class="screen">
-The file &#8220;test_one&#8221; contains the ...
-</pre>
-
- <p>TeX will respond:</p>
-<pre class="screen">
-! Missing $ inserted
-&lt;inserted text&gt;
- $
-&lt;to be read again&gt;
- _
-The file &#8220;test_
- one&#8221; contains the ...
-?
-</pre>
-
- <p>In LaTeX, the easiest way around this problem is to
- enclose the offending text in a &#8220;verbatim&#8221;
- macro, like this:</p>
-<pre class="screen">
- The file &#8220;<tt>test_one</tt>&#8221; contains the ...
-</pre>
-
- <p>Note that the argument to the <tt>macro</tt>is
- delimited by any two identical characters (in this case,
- two &#8220;<tt>+</tt>&#8221; signs).</p>
-
- <p>In Plain TeX or another format, the problem can be
- circumvented in similar ways; consult the reference for
- the format you are using. Also consult Table&#160;<a
- href="ch01.html#tab.acttype"
- title="Table&#160;1.2.&#160;How to Typeset Special Characters">
- Table&#160;1.2</a> in Chapter&#160;<a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a>,
- <span class="emphasis"><em><a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a></em></span>,
- for a list of special characters and how to type them in
- your documents.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2873082"
- name="id2873082"></a>Missing Fonts</h3>
- </div>
- </div>
-
- <p>The first<a id="id2873090" class="indexterm"
- name="id2873090"></a> time that you use each font, TeX
- loads font metric information about the font. The font
- metric information, stored in a <tt>TFM</tt> file,
- includes information about the sizes of each character as
- well as kerning and ligature information. These topics
- are discussed fully in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.</p>
-
- <p>If you request a font that does not exist, for example
- <tt>crm10</tt> (a misspelling of <tt>cmr10</tt>), TeX
- cannot find a <tt>TFM</tt> file for the font and
- therefore displays:</p>
-<pre class="screen">
-Font \myfont=crm10 not loadable: Metric (TFM) file not found
-</pre>
-
- <p>This means that TeX attempted to associate the font
- described by the <tt>TFM</tt> file <tt>crm10.tfm</tt>
- with the control sequence \myfont, but the <tt>TFM</tt>
- file didn't exist. You must have a <tt>TFM</tt> file for
- every font that you use.</p>
-
- <p>A second kind of error---actually, a warning---occurs
- when you are using the New Font Selection Scheme (NFSS)<a
- id="id2873221" class="indexterm" name="id2873221"></a>.
- The NFSS performs font substitution, if possible, when an
- unknown font is requested. The NFSS is described in
- Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>,
- in the &#8220;<a href="ch04.html#sec.latex"
- title="LaTeX">the section called
- &#8220;LaTeX&#8221;</a>&#8221; section.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2873273"
- name="id2873273"></a>Everything Else</h3>
- </div>
- </div>
-
- <p>There are, unfortunately, lots of other errors that
- can occur. Some of the errors are directly related to TeX
- while others are warning and error messages associated
- with particular macro packages. There is no way to
- catalog every one of them or suggest what can be done in
- every case.</p>
-
- <p>The best advice I can offer is to isolate the problem
- in as small a document as possible, consult the
- references you have available very carefully, and, if all
- else fails, forward your problem to one of the electronic
- forums that deal with TeX (the <tt>Info-TeX</tt> mailing
- list<a id="id2873302" class="indexterm"
- name="id2873302"></a> and the <tt>comp.text.tex</tt>
- newsgroup<a id="id2873326" class="indexterm"
- name="id2873326"></a>, for example).</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2873346"
- name="id2873346"></a>The Question Mark Prompt</h2>
- </div>
- </div>
- <a id="id2873352" class="indexterm" name="id2873352"></a>
-
- <p>When TeX encounters an error, it displays an error
- message and a summary of the error, as described in the
- section called &#8220;<a href="ch03.html#sec.errors"
- title="What About Errors?">the section called &#8220;What
- About Errors?&#8221;</a>&#8221; earlier in this chapter.
- Following the error, TeX normally stops and displays the
- question mark prompt.</p>
-
- <p>If you type a question mark of your own at the prompt,
- TeX displays the actions available to you:</p>
-<pre class="screen">
-? ?
-Type &lt;return&gt; to proceed,
-S to scroll future error messages,
-R to run without stopping, Q to run quietly,
-I to insert something, E to edit your file,
-1 or ... or 9 to ignore the next 1 to 9 tokens
-of input, H for help, X to quit.
-?
-</pre>
-
- <p>You can type any of the following responses at the
- question mark prompt:<a id="id2873401" class="indexterm"
- name="id2873401"></a></p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">Type <b>Return</b> to
- proceed.</span></dt>
-
- <dd>
- <p>Simply typing Return will cause TeX to ignore the
- error and proceed. Depending on the nature of the
- error, this may cause more errors immediately or
- later on.</p>
- </dd>
-
- <dt><span class="term">Type <b>S</b> to scroll future
- error messages.</span></dt>
-
- <dd>
- <p>Typing <b>S</b> tells TeX to continue and not to
- stop for most future errors. TeX will continue to
- print the error messages, both to the terminal and to
- the log file, but it will not display the question
- mark prompt again.</p>
-
- <p>TeX will still stop and ask about missing
- files.</p>
- </dd>
-
- <dt><span class="term">Type <b>R</b> to run without
- stopping.</span></dt>
-
- <dd>
- <p>The <b>R</b> option is just like <b>S</b> except
- that it tells TeX to ignore missing files as well.
- TeX will proceed blindly forward as best as it can.
- You will still see all of the error messages scroll
- by as TeX proceeds.</p>
- </dd>
-
- <dt><span class="term">Type <b>Q</b> to run
- quietly.</span></dt>
-
- <dd>
- <p>This option is just like <b>R</b> except that
- error messages are not displayed on the screen. The
- messages are saved in the log file, however, even
- though they are not displayed.</p>
- </dd>
-
- <dt><span class="term">Type <b>I</b> to insert
- something.</span></dt>
-
- <dd>
- <p>If you notice a simple typo, you can correct it
- with the <b>I</b> command. For example, suppose that
- TeX complains of an undefined control sequence:
- \cte{kn:art1}. You recognize that this should have
- been \cite{kn:art1}. You can insert the correct
- control sequence by responding <tt>i\cite</tt> to the
- question mark prompt. TeX will ignore the misspelled
- control sequence and insert the (correct) sequence
- \cite in its place.</p>
-
- <p>Inserting words or commands at the question mark
- prompt <span class="emphasis"><em>does
- not</em></span> change your input file. It simply
- instructs TeX to <span
- class="emphasis"><em>pretend</em></span> that your
- file contained a different sequence of words and
- commands. You must change the input file with an
- editor, or the same error will occur the next time
- you format the document.</p>
- </dd>
-
- <dt><span class="term">Type <b>E</b> to edit your
- file.</span></dt>
-
- <dd>
- <p>This option terminates TeX. If your system is
- configured appropriately, an editor will be loaded
- automatically, and the cursor will be placed at the
- offending line in your input file. This is not
- possible in all environments.</p>
- </dd>
-
- <dt><span class="term">Type <b><i><tt>n</tt></i></b>,
- where <i><tt>n</tt></i> is a number between 1 and
- 9.</span></dt>
-
- <dd>
- <p>This option tells TeX to ignore some of the input.
- After skipping over the number of <span
- class="emphasis"><em>tokens</em></span> you request,
- TeX returns to the question mark prompt so that you
- can delete more tokens.</p>
-
- <p>What's a token<a id="id2873692" class="indexterm"
- name="id2873692"></a>? When TeX reads an input file,
- it breaks each line down into the smallest,
- indivisible chunks that have meaning. These are
- called tokens. For the most part, tokens are
- individual characters. The exceptions are control
- sequences<a id="id2873705" class="indexterm"
- name="id2873705"></a>, which are single tokens, and
- white spaces which are also single tokens. There
- <span class="emphasis"><em>are</em></span> other
- exceptions (and more technical definitions of
- &#8220;token&#8221;), but that's the gist of it.</p>
- </dd>
-
- <dt><span class="term">Type <b>H</b> for
- help.</span></dt>
-
- <dd>
- <p>Typing <b>H</b> displays a slightly more verbose
- description of the error that occurred and, usually,
- suggests the nature of the corrective action that you
- might take.</p>
- </dd>
-
- <dt><span class="term">Type <b>X</b> to
- quit.</span></dt>
-
- <dd>
- <p>Typing <b>X</b> tells TeX to stop immediately and
- ends the TeX program. If there are any completed
- pages (pages processed before the error, in other
- words), they are written to the <tt>DVI</tt> file
- before TeX ends.</p>
- </dd>
- </dl>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2869760" name="ftn.id2869760"
- href="#id2869760">25</a>]</sup> {The exception occurs in
- some unix versions of TeX where provisions are made for
- different architectures to share the same format files.
- The exact same version of TeX must be running on both
- architectures for this to work.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2869931" name="ftn.id2869931"
- href="#id2869931">26</a>]</sup> {The exact name of the
- environment variable<a id="id2869936" class="indexterm"
- name="id2869936"></a><a id="id2869947" class="indexterm"
- name="id2869947"></a> differs between
- implementations.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2869999" name="ftn.id2869999"
- href="#id2869999">27</a>]</sup> You will notice that I've
- used backslashes<a id="id2870004" class="indexterm"
- name="id2870004"></a> to separate directory components in
- the path. Environment variables are handled by the
- system-dependent portions of TeX, so it's okay to use
- backslashes here. You can also use forward slashes, but I
- use backslashes because that is more typical of MS-DOS
- and OS/2 environments.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2870149" name="ftn.id2870149"
- href="#id2870149">28</a>]</sup> {MS-DOS and OS/2
- implementations of TeX may use Ctrl-Z (possibly followed
- by a carriage return) instead of Ctrl-C or Ctrl-D.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2870360" name="ftn.id2870360"
- href="#id2870360">29</a>]</sup> {On unix systems, the
- same effect is often achieved with symbolic links. Most
- unix implementations look for different standard format
- files based upon the name of the executable that starts
- them.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2870805" name="ftn.id2870805"
- href="#id2870805">30</a>]</sup> {In the unlikely event
- that you have a TeX document stored in a file with a name
- beginning with an ampersand, use the following trick to
- process that file: instead of running <b>tex
- &amp;file</b>, run <b>tex \input &amp;file</b> (or even
- <b>tex &amp;format \input &amp;file</b>).</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2871022" name="ftn.id2871022"
- href="#id2871022">31</a>]</sup> {For example,
- <tt>oak.oakland.edu</tt> in the directory
- <tt>/pub/msdos/4DOS</tt>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2871781" name="ftn.id2871781"
- href="#id2871781">32</a>]</sup> {Typing the break
- character (<b>Ctrl-C</b> or <b>Ctrl-Break</b>, for
- example) sometimes works as well, but some
- implementations of TeX don't respond to the break
- character at every prompt. On unix systems, use
- <b>Ctrl-D</b>. EmTeX responds to <b>Ctrl-Z</b> followed
- by <b>Return</b>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2872107" name="ftn.id2872107"
- href="#id2872107">33</a>]</sup> {The details of LaTeX and
- the NFSS are discussed in Chapter&#160;<a
- href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.
- It is simply convenient to use a concrete example in this
- case. Do not be concerned if you do not use LaTeX or the
- NFSS.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2872135" name="ftn.id2872135"
- href="#id2872135">34</a>]</sup> {In practice, redefining
- a control sequence like $\$<tt>Large</tt> in a document
- is a bad idea. I've done it here only to provide an
- example of an error that occurs inside another
- macro.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2872367" name="ftn.id2872367"
- href="#id2872367">35</a>]</sup> {The number of lines of
- context shown in the error message is determined by the
- value of the built-in parameter
- $\$<tt>errorcontextlines</tt>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2872514" name="ftn.id2872514"
- href="#id2872514">36</a>]</sup> {It is possible to make
- other formats the default, but in practice I've never
- seen it done.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2872615" name="ftn.id2872615"
- href="#id2872615">37</a>]</sup> Technically, LaTeX
- environment names are not a control sequence names, but
- they behave in very much the same way in LaTeX.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2872944" name="ftn.id2872944"
- href="#id2872944">38</a>]</sup> {The empty curly braces
- are necessary in this example because otherwise there
- wouldn't be anything in front of the subscript command
- for TeX to subscript below. Typically, another digit or
- symbol would come in front of the subscript command. In
- this case, I didn't want the &#8220;H&#8221; and
- &#8220;O&#8221; in the math environment because letters
- are printed in math-italics in math mode.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;2.&#160;Editing"
- href="ch02.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;4.&#160;Macro Packages"
- href="ch04.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;2.&#160;Editing&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;4.&#160;Macro Packages</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch04.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch04.html
deleted file mode 100644
index a64b3e597fb..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch04.html
+++ /dev/null
@@ -1,2206 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;4.&#160;Macro Packages</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX" />
- <link rel="previous" href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX" />
- <link rel="next" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;3.&#160;Running TeX"
- href="ch03.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.macpack"
- name="chap.macpack"></a>Chapter&#160;4.&#160;Macro
- Packages</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>Everyone who uses TeX uses a macro package<a
- id="id2869171" class="indexterm" name="id2869171"></a><a
- id="id2869178" class="indexterm" name="id2869178"></a> (also
- called a &#8220;format&#8221;). A macro package extends TeX
- to provide functionality that is suited to a particular task
- or set of tasks.</p>
-
- <p>This chapter provides a summary of TeX macro packages.
- General-purpose packages designed to typeset a wide range of
- documents---articles, books, letters, and reports---are
- examined first. The general-purpose packages described are
- Plain TeX, Extended Plain TeX, LaTeX2e, LaTeX, AMSTeX,
- AMSLaTeX, Lollipop, and TeXinfo. After surveying the
- general-purpose packages, several special-purpose packages
- designed to handle specific tasks---typesetting
- transparencies, music, chemistry or physics diagrams,
- etc.---are described. The special-purpose packages surveyed
- are SliTeX, FoilTeX, Seminar, MusicTeX, ChemStruct, and
- ChemTeX.</p>
-
- <p>There are a lot of overlapping features and similar
- commands in the general-purpose packages. To understand why
- this is the case, consider how a new macro package comes into
- existence. An ambitious person, who is very familiar with
- TeX, decides that there are some things she would like to
- express in her documents that are difficult to express with
- existing formats. Perhaps, for example, no existing format
- produces documents that match the precise specifications
- required for publishing in her field, or perhaps she has in
- mind a whole new document structuring paradigm. A more
- mundane possibility is simply that she has been customizing
- an existing format for some time and now feels it has enough
- unique features to be useful to others.</p>
-
- <p>In any event, a new format is born. Now, if this format is
- designed for a very specific task, writing multiple-choice
- mathematics exams, for example, it might not have very many
- general-purpose writing features. On the other hand, if it is
- designed for writing longer, more general documents (e.g.,
- history textbooks or papers to appear in a particular
- journal) then there are a number of features that it is
- likely to include; provisions for numbered lists, cross
- references, tables of contents, indexes, and quotations are
- all examples of features common to many documents.</p>
-
- <p>To support these common features, many macro packages have
- similar control sequences. This stems from the fact that they
- are all built on top of a common set of primitives<a
- id="id2869134" class="indexterm" name="id2869134"></a> and
- that macro package authors tend to copy some features of
- other packages into their own.</p>
-
- <p>You may find that you'd like to use the features of
- several different packages in the same document.
- Unfortunately, there is no provision for using multiple
- formats to process a single document. The features required
- to process most documents are shared by all of the
- general-purpose formats, however. You are more likely to need
- multiple macro packages if you want to use a special format
- to construct a diagram or figure and incorporate it into a
- document. Chapter&#160;<a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a>,
- <span class="emphasis"><em><a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a></em></span>,
- describes several ways to take &#8220;electronic
- snippets&#8221; of one document and insert them into another,
- which is one possible solution to this problem.</p>
-
- <p>If you're beginning to feel a little lost, have no fear.
- Most general-purpose formats are sufficient for most
- documents. And there's no reason why every document you write
- has to be done with the same format. Many people find LaTeX
- and Plain TeX sufficient, but if you're writing an article
- for a particular journal and someone has written a format
- specifically for that journal's documents, by all means use
- it. It is more likely, however, that someone has written a
- style file<a id="id2873990" class="indexterm"
- name="id2873990"></a> which tailors LaTeX to the requirements
- of the journal.</p>
-
- <p>In addition to describing some common macro packages in
- this chapter, I'll describe how to build format files for
- them. If the packages that you want to use have already been
- installed at your site, you can ignore the installation
- sections.</p>
-
- <p>The packages that you find most convenient will depend on
- the tasks you perform and how well each package suits your
- work style. The list of packages in this chapter is not meant
- to be all-inclusive, nor is it my intention to suggest which
- packages are best. Use the ones <span
- class="emphasis"><em>you</em></span> like, for whatever
- reasons.</p>
-
- <p>I can hear some of you already, &#8220;I don't really need
- a macro package,&#8221; you say, &#8220;I can roll my own
- with just TeX.&#8221;</p>
-
- <p>And you are absolutely correct.</p>
-
- <p>I don't recommend it, however. It's akin to using your
- compiler without any of the built-in functions. Most TeX
- primitives offer little support by themselves for writing
- documents.</p>
-
- <div class="sidebar">
- <p class="title"><b>A New Perspective</b></p>
-
- <p>LaTeX2e<a id="id2874066" class="indexterm"
- name="id2874066"></a> (and its successor, which will be
- LaTeX3<a id="id2874077" class="indexterm"
- name="id2874077"></a>) seek to address many of the problems
- mentioned above by defining a core LaTeX format with
- extension packages to provide custom features.</p>
-
- <p>The LaTeX2e system provides a single format <a
- id="id2874097" class="indexterm" name="id2874097"></a> file
- that supports LaTeX<a id="id2874111" class="indexterm"
- name="id2874111"></a>, AMSTeX<a id="id2874123"
- class="indexterm" name="id2874123"></a>, and SliTeX<a
- id="id2874134" class="indexterm" name="id2874134"></a>. For
- the time being, LaTeX2e is described separately in this
- chapter along with the other formats. Be aware, however,
- that LaTeX2e is now the standard LaTeX<sup>[<a
- id="id2874145" name="id2874145"
- href="#ftn.id2874145">39</a>]</sup>and you should migrate
- to it as soon as possible.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="macpack.sec.latexvslatexe"
- name="macpack.sec.latexvslatexe"></a>Installation:
- Making Format Files</h2>
- </div>
- </div>
-
- <p>A format file<a id="id2874176" class="indexterm"
- name="id2874176"></a><a id="id2874186" class="indexterm"
- name="id2874186"></a>, as described in Chapter&#160;<a
- href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>,
- is a special &#8220;compiled&#8221; version of a macro
- package. The iniTeX<a id="id2874224" class="indexterm"
- name="id2874224"></a> program interprets all of the control
- sequences in a macro package and writes the corresponding
- memory image into a file. Loading a format file is much
- faster than loading individual macro packages in your
- document because TeX does not have to interpret any of the
- control sequences while it is also processing text.</p>
-
- <p>In general, all format files should be stored in the
- same directory.<sup>[<a id="id2874246" name="id2874246"
- href="#ftn.id2874246">40</a>]</sup> If you install TeX in a
- directory called <tt>tex</tt>, then formats typically go in
- a directory called <tt>formats</tt><a id="id2874268"
- class="indexterm" name="id2874268"></a> in the <tt>tex</tt>
- directory<a id="id2874283" class="indexterm"
- name="id2874283"></a>. This is not universally the case
- because you need separate format directories for big and
- small TeXs.<sup>[<a id="id2874291" name="id2874291"
- href="#ftn.id2874291">41</a>]</sup></p>
-
- <p>Usually, an environment variable<a id="id2874326"
- class="indexterm" name="id2874326"></a><a id="id2874333"
- class="indexterm" name="id2874333"></a> indicates where the
- format files are located. Environment variables are a
- common way of customizing your interaction with programs.
- They are usually set in your <tt>AUTOEXEC.BAT</tt> file<a
- id="id2874354" class="indexterm" name="id2874354"></a> for
- MS-DOS, <tt>CONFIG.SYS</tt><a id="id2874371"
- class="indexterm" name="id2874371"></a> for OS/2, or the
- <span class="emphasis"><em>rc</em></span>-file for a shell
- (i.e., <tt>.cshrc</tt><a id="id2874392" class="indexterm"
- name="id2874392"></a>, <tt>.kshrc</tt><a id="id2874409"
- class="indexterm" name="id2874409"></a>) on unix systems.
- Any good reference book for your operating system or shell
- will describe how to use environment variables.</p>
-
- <p>A common name for the environment variable that
- indicates where TeX formats are located is
- <tt>TEXFORMATS</tt>. Implementations that provide big and
- small TeXs need another variable to indicate the directory
- that contains formats for big TeX.</p>
-
- <p>IniTeX is not always a separate program. Some
- implementations of TeX combine the functionality of TeX and
- iniTeX into a single program and use a special switch at
- runtime to determine which function to perform. In this
- chapter, all of the examples use the program name
- <tt>initex</tt> to identify iniTeX. If you use an
- implementation that doesn't provide a separate iniTeX
- program, you should use the TeX program with the iniTeX
- switch<a id="id2874454" class="indexterm"
- name="id2874454"></a> instead. For example, for emTeX, use
- <tt>tex /i</tt> instead of <tt>initex</tt> when you build a
- format.</p>
-
- <p>Like TeX, iniTeX needs to be able to find input files<a
- id="id2874487" class="indexterm" name="id2874487"></a>.
- Usually, this is accomplished by searching the directories
- listed in the <tt>TEXINPUTS</tt> environment variable.
- Place the input files that iniTeX needs in a directory on
- the <tt>TEXINPUTS</tt> path before running iniTeX unless
- otherwise directed. The <tt>TEXINPUTS</tt> environment
- variable is discussed in the &#8220;<a
- href="ch03.html#sec.userfiles" title="User Files">the
- section called &#8220;User Files&#8221;</a>&#8221; section
- of Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2874541"
- name="id2874541"></a>Hyphenation Patterns</h3>
- </div>
- </div>
-
- <p>In order for TeX to correctly hyphenate words, every
- format file must contain a set of hyphenation patterns<a
- id="id2874552" class="indexterm" name="id2874552"></a>.
- The patterns are part of an algorithmic solution to the
- problem of breaking a word into syllables for
- hyphenation.</p>
-
- <p>The details of the hyphenation algorithm (given in
- Appendix H of <span class="emphasis"><em>The
- TeXbook</em></span>&#160;[<a
- href="bi01.html#kn:texbook">kn:texbook</a>]) are too
- complex to describe here, but two aspects of this
- solution deserve particular emphasis. First, using
- patterns means that a dictionary of hyphenated words is
- not necessary.<sup>[<a id="id2874585" name="id2874585"
- href="#ftn.id2874585">42</a>]</sup> This saves a lot of
- space and time. Second, by loading different sets of
- patterns, TeX can achieve equal success at hyphenating
- any language---even English ;-). There are actually at
- least two sets of hyphenation patterns for English, one
- for British English and one for American English.
- Chapter&#160;<a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a>, <span class="emphasis"><em><a
- href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a></em></span>, describes how to load
- multiple sets of hyphenation patterns for typesetting
- multilingual documents<a id="id2874620" class="indexterm"
- name="id2874620"></a>.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2874634"
- name="id2874634"></a>General-purpose Formats</h2>
- </div>
- </div>
-
- <p>This section describes several macro packages <a
- id="id2874644" class="indexterm" name="id2874644"></a> that
- are designed for formatting standard documents like
- articles or books. In order to provide some form of
- comparative measure, each macro package is used to create
- the same document, a one-page report that looks like
- Figure&#160;<a href="ch04.html#fig.sampresults"
- title="Figure&#160;4.1.&#160;Sample page">Figure&#160;4.1</a>.
- I constructed this example to demonstrate a few common
- elements in a document: several sizes of headings, a
- paragraph of text, inline and displayed mathematics, and a
- few fonts. There are lots of other things that aren't shown
- (tables, figures, footnotes, etc.), and these elements vary
- as much as any other in the different macro packages.</p>
-
- <div class="figure">
- <a id="fig.sampresults" name="fig.sampresults"></a>
-
- <p class="title"><b>Figure&#160;4.1.&#160;Sample
- page</b></p>
-
- <div class="mediaobject">
- <img src="perf-ltx.eps" />
- </div>
- </div>
-
- <p>Observant readers will notice that the examples are
- shown in the Computer Modern fonts while the rest of this
- book uses different fonts.<sup>[<a id="id2874736"
- name="id2874736" href="#ftn.id2874736">43</a>]</sup> There
- are a number of reasons why the example is shown in
- Computer Modern. For one thing, all of the formats
- discussed here use the Computer Modern fonts by default.
- Using a different set of fonts would only add more
- complexity to each example. A more subtle problem is that I
- do not have appropriate mathematics fonts for Garamond.
- There are a number of complex issues involving the use of
- fonts in TeX. They are discussed in Chapter&#160;<a
- href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2874772"
- name="id2874772"></a>Plain TeX</h3>
- </div>
- </div>
-
- <p>Plain TeX<a id="id2874779" class="indexterm"
- name="id2874779"></a> is the format <a id="id2874790"
- class="indexterm" name="id2874790"></a> written by Donald
- Knuth<a id="id2874805" class="indexterm"
- name="id2874805"></a> during the development of TeX. It
- is described fully in <span class="emphasis"><em>The
- {TeX}book</em></span>&#160;[<a
- href="bi01.html#kn:texbook">kn:texbook</a>].</p>
-
- <p>Plain TeX ties together the TeX primitives <a
- id="id2874830" class="indexterm" name="id2874830"></a> in
- a way that makes it practical to work in TeX. If you do
- not have a computer programming background, you may find
- Plain TeX a little bit intimidating. It is definitely a
- &#8220;roll your own&#8221; environment. Although it
- demonstrably contains all of the functionality required
- to write everything from letters to books, there is very
- little &#8220;user-friendly&#8221; packaging around the
- internals of TeX.</p>
-
- <p>Aside from user interface considerations, which are
- highly subjective, Plain TeX lacks some functionality
- when compared to other formats. There is no provision in
- Plain TeX for automatically numbered sections, labelled
- figures, tables of contents, indexes, or bibliographies.
- Any of these functions can be constructed in Plain TeX if
- you are willing to invest the time and energy required to
- write your own macros, but they are not built into Plain
- TeX.</p>
-
- <p>If you enjoy writing your own macros or plan to
- produce novel types of documents, a firm grasp of Plain
- TeX will allow you to write anything in TeX. A firm grasp
- of Plain TeX also makes it easier to understand and
- modify other formats (like LaTeX) that are built on top
- of Plain TeX.</p>
-
- <p>In addition, Plain TeX is the only format that is
- always distributed with TeX. The other formats discussed
- in this chapter are freely available but do not come with
- TeX.</p>
-
- <p>The Plain TeX input that produces the report in
- Figure&#160;<a href="ch04.html#fig.sampresults"
- title="Figure&#160;4.1.&#160;Sample page">Figure&#160;4.1</a>
- is shown in Example&#160;<a
- href="ch04.html#ex.sampplaintex"
- title="Figure&#160;4.2.&#160;Plain TeX Input">Figure&#160;4.2</a>.</p>
-
- <div class="figure">
- <a id="ex.sampplaintex" name="ex.sampplaintex"></a>
-
- <p class="title"><b>Figure&#160;4.2.&#160;Plain TeX
- Input</b></p>
-
- <div class="mediaobject">
- <img src="perf-ptx" />
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2874942"
- name="id2874942"></a>Building the Plain TeX
- format</h4>
- </div>
- </div>
-
- <p>To build Plain TeX<a id="id2874951"
- class="indexterm" name="id2874951"></a>, you need only
- two files: <tt>plain.tex</tt><a id="id2874971"
- class="indexterm" name="id2874971"></a> and
- <tt>hyphen.tex</tt><a id="id2874994" class="indexterm"
- name="id2874994"></a>. These files are distributed with
- TeX so they should be available as soon as you have
- installed TeX. The <tt>hyphen.tex</tt> file is
- language-dependent. Readers who frequently work with
- non-English text should read Chapter&#160;<a
- href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a> for more information about obtaining
- non-English hyphenation patterns.</p>
-
- <p>The command:</p>
-<pre class="screen">
-\$ <span class="bold"><b>initex plain \dump</b></span>
-</pre>
-
- <p>will create the Plain TeX format. Move the resulting
- files, <tt>plain.fmt</tt><a id="id2875061"
- class="indexterm" name="id2875061"></a> and
- <tt>plain.log</tt><a id="id2875077" class="indexterm"
- name="id2875077"></a>, into your TeX formats
- directory.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2875093"
- name="id2875093"></a>Extended Plain TeX</h3>
- </div>
- </div>
-
- <p>Extended Plain TeX<a id="id2875102" class="indexterm"
- name="id2875102"></a><a id="id2875112" class="indexterm"
- name="id2875112"></a> extends Plain TeX in a number of
- useful ways without forcing you to use any particular
- &#8220;style&#8221; of output. The argument is this:
- although Plain TeX really doesn't provide all of the
- features that you need (tables of contents, cross
- references, citations, enumerated lists, convenient
- access to verbatim input, etc), many of these features
- don't have any direct impact on the appearance of your
- document. Unfortunately, other general-purpose macro
- packages like LaTeX, which do provide these features,
- tend to force you to accept their notion of what the
- typeset page should look like.<sup>[<a id="id2875131"
- name="id2875131" href="#ftn.id2875131">44</a>]</sup></p>
-
- <p>Extended Plain TeX is an attempt to solve that
- problem. It provides many behind-the-scenes features
- without providing any general page layout commands (like
- \chapter or \section), which means that these features
- can be used inside Plain TeX without much difficulty and
- without changing the layout of typeset pages.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2875171"
- name="id2875171"></a>Building the Extended Plain
- TeX format</h4>
- </div>
- </div>
-
- <p>To build the Extended Plain TeX format<a
- id="id2875181" class="indexterm" name="id2875181"></a>,
- you need the <tt>plain.tex</tt><a id="id2875201"
- class="indexterm" name="id2875201"></a> and
- <tt>hyphen.tex</tt> files <a id="id2875225"
- class="indexterm" name="id2875225"></a> required to
- build the Plain format as well as the
- <tt>eplain.tex</tt> file <a id="id2875250"
- class="indexterm" name="id2875250"></a> distributed
- with Extended Plain TeX.<sup>[<a id="id2875268"
- name="id2875268" href="#ftn.id2875268">45</a>]</sup>
- Make and install the Plain TeX format first, then
- change to the directory that contains the Extended
- Plain TeX distribution.</p>
-
- <p>The command:</p>
-<pre class="screen">
-$ <span class="bold"><b>initex \&amp;plain eplain \dump</b></span>
-</pre>
-
- <p>will create the Extended Plain TeX format. Move the
- resulting files, <tt>eplain.fmt</tt> <a id="id2875315"
- class="indexterm" name="id2875315"></a> and
- <tt>eplain.log</tt><a id="id2875338" class="indexterm"
- name="id2875338"></a>, into your TeX formats
- directory.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2875359"
- name="id2875359"></a>LaTeX2e Versus LaTeX</h3>
- </div>
- </div>
-
- <p>The tremendous popularity of LaTeX<a id="id2875368"
- class="indexterm" name="id2875368"></a><a id="id2875378"
- class="indexterm" name="id2875378"></a> in the TeX
- community has had an unfortunate side effect: because it
- is a very familiar and flexible format, many people have
- used it as the basis for extensions of one sort or
- another. This has resulted in a wide range of (slightly)
- incompatible formats and a lot of frustration.</p>
-
- <p>This situation is being rectified by a new release of
- LaTeX, currently called LaTeX2e<a id="id2875402"
- class="indexterm" name="id2875402"></a><a id="id2875414"
- class="indexterm" name="id2875414"></a>. The new release
- replaces the existing dialects of LaTeX (LaTeX with and
- without NFSS, SliTeX, AMSLaTeX, etc.) with a single core
- system and a set of extension packages. LaTeX2e includes
- a compatibility mode which will allow it to continue to
- format existing documents without change (provided that
- they do not rely on local modifications to the LaTeX
- format, of course). Local modifications can also be
- incorporated into the LaTeX2e system as extension
- packages, making LaTeX2e a complete replacement for all
- existing versions of LaTeX and packages closely derived
- from LaTeX.</p>
-
- <p>The most significant and least compatible difference
- between LaTeX and LaTeX2e<a id="id2875443"
- class="indexterm" name="id2875443"></a><a id="id2875460"
- class="indexterm" name="id2875460"></a> is the font
- selection scheme. There are many control sequences for
- selecting fonts in LaTeX. Some control the typeface (\rm,
- \tt, \sc, etc.); some the size (\small, \normalsize,
- \large, etc.); and some the appearance (\it, \bf, \em,
- etc.). Under the Old Font Selection Scheme (OFSS)<a
- id="id2875523" class="indexterm" name="id2875523"></a>,
- the control sequences for selecting a font completely
- override any font selection already in place. Consider,
- for example, the control sequences \it and \bf, which
- switch to italic and boldface. Using \bf\it produces
- italic text, and \it\bf produces boldface text, and <span
- class="emphasis"><em>neither</em></span> produces
- boldfaced-italic text (which is probably what you
- wanted).</p>
-
- <p>Under the New Font Selection Scheme<a id="id2875563"
- class="indexterm" name="id2875563"></a><a id="id2875570"
- class="indexterm" name="id2875570"></a>, typeface (called
- <span class="emphasis"><em>family</em></span> in NFSS
- parlance), appearance (called <span
- class="emphasis"><em>series</em></span> and <span
- class="emphasis"><em>shape</em></span>), and size are
- viewed as orthogonal components in font selection.
- Because these parameters are independent, selecting an
- italic appearance with the \it control sequence switches
- to italic in the current typeface and size. Under the
- NFSS, \bf\cs{it} <span
- class="emphasis"><em>does</em></span> select
- boldface-italic in both the current typeface and size (if
- it is available).</p>
-
- <p>LaTeX2e supports only the NFSS, version 2 (called
- NFSS2)<a id="id2875613" class="indexterm"
- name="id2875613"></a><a id="id2875624" class="indexterm"
- name="id2875624"></a>. For more than a year, the NFSS
- (initially version 1, and more recently version 2) has
- been available as an extension for LaTeX 2.09. However,
- in light of stable test releases of LaTeX2e, the NFSS2
- package for LaTeX 2.09 has been withdrawn. The discussion
- of NFSS in this book applies equally well to LaTeX 2.09
- with NFSS2, but it is described in terms of LaTeX2e in an
- effort to be more applicable in the future. The NFSS is
- discussed in more detail in Chapter&#160;<a
- href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.latexe"
- name="sec.latexe"></a>LaTeX2e</h3>
- </div>
- </div>
-
- <p>Leslie Lamport<a id="id2875668" class="indexterm"
- name="id2875668"></a>'s LaTeX format is probably the most
- commonly used TeX format. It is described in <span
- class="emphasis"><em>LaTeX: A Document Preparation
- System</em></span>&#160;[<a
- href="bi01.html#ll:latexbook">ll:latexbook</a>] and many
- other TeX books. LaTeX2e<a id="id2875692"
- class="indexterm" name="id2875692"></a> is the new
- standard LaTeX. It is described in <span
- class="emphasis"><em>{The LaTeX
- Companion}</em></span>&#160;[<a
- href="bi01.html#latexcompanion">latexcompanion</a>]. The
- next edition of <span class="emphasis"><em>LaTeX: A
- Document Preparation System</em></span>&#160;[<a
- href="bi01.html#ll:latexbook">ll:latexbook</a>] will also
- describe LaTeX2e.</p>
-
- <div class="sidebar">
- <p>At the time of this writing, LaTeX2e is available
- only in a test release, but by the time you read this,
- it is likely to be available as the new standard LaTeX.
- It is described first in this chapter to emphasize that
- you should begin using LaTeX2e as soon as possible.
- Once LaTeX2e is out of testing, it will become LaTeX,
- and support for older versions will not be provided (at
- least not by the LaTeX developers). LaTeX2e includes a
- compatibility mode<a id="id2875736" class="indexterm"
- name="id2875736"></a> for old LaTeX documents so the
- transition should be relatively painless.</p>
- </div>
-
- <p>The central theme of LaTeX is &#8220;structured
- document preparation.&#8221; An ideal LaTeX document is
- described entirely in terms of its structure: chapters,
- sections, paragraphs, numbered lists, bulleted items,
- tables, figures, and all the other elements of a document
- are identified descriptively. For example, you enclose
- figures in a figure <span
- class="emphasis"><em>environment</em></span> identified
- by the control sequences \begin{figure} and
- \end{figure}.</p>
-
- <p>When you are ready to print your document, select an
- appropriate document class<a id="id2875794"
- class="indexterm" name="id2875794"></a>, and LaTeX
- formats your document according to the rules of the
- selected style. In the case of the ideal document, it
- might first be printed in a magazine or newsletter using
- the article class. Later, when it is incorporated into a
- book, selecting the book class is <span
- class="emphasis"><em>all</em></span> that is required to
- produce appropriate output; the document itself is
- unchanged.</p>
-
- <p>LaTeX is written on top of Plain TeX. This means that
- almost any control sequence <a id="id2875821"
- class="indexterm" name="id2875821"></a> or macro that you
- learn about in Plain TeX can also be used in LaTeX. Of
- course, LaTeX insulates you from many Plain TeX commands
- by wrapping a much more user-friendly interface around
- them.</p>
-
- <p>The LaTeX2e input that produces the sample page in
- Figure&#160;<a href="ch04.html#fig.sampresults"
- title="Figure&#160;4.1.&#160;Sample page">Figure&#160;4.1</a>
- is shown in Example&#160;<a
- href="ch04.html#fig.samplatex2e"
- title="Figure&#160;4.3.&#160;LaTeX2e Input">Figure&#160;4.3</a>.
- The only difference between this document and an old
- LaTeX document is the use of the \documentclass
- declaration instead of the \documentstyle
- declaration.<sup>[<a id="id2875867" name="id2875867"
- href="#ftn.id2875867">46</a>]</sup> For more complex
- documents, other minor changes may also be necessary.</p>
-
- <div class="figure">
- <a id="fig.samplatex2e" name="fig.samplatex2e"></a>
-
- <p class="title"><b>Figure&#160;4.3.&#160;LaTeX2e
- Input</b></p>
-
- <div class="mediaobject">
- <img src="perf-l2e.eps" />
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.buildlatexe"
- name="sec.buildlatexe"></a>Building the LaTeX2e
- format</h4>
- </div>
- </div>
-
- <p>The LaTeX2e distribution is available from the
- directory <tt>macros/latex2e/core</tt> in the CTAN
- archives<a id="id2875937" class="indexterm"
- name="id2875937"></a>.</p>
-
- <p>The following steps will build the LaTeX2e format.
- For more complete installation instructions, read the
- file <tt>install.l2e</tt> in the LaTeX2e
- distribution.</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>Place the LaTeX2e distribution in a temporary
- directory and make that directory the current
- directory. After the installation is complete,
- you will need to move only selected files into
- the standard places.</p>
- </li>
-
- <li>
- <p>Restrict to only the current directory the
- directories that TeX searches for input files</p>
-
- <p>This can usually be accomplished by setting
- the environment variable
- <tt>TEXINPUTS</tt><sup>[<a id="id2876004"
- name="id2876004"
- href="#ftn.id2876004">47</a>]</sup> to a single
- period or the absolute path name of the current
- directory.</p>
- </li>
-
- <li>
- <p>Copy the <tt>hyphen.tex</tt> file <a
- id="id2876037" class="indexterm"
- name="id2876037"></a> from the Plain TeX
- distribution into the current directory.</p>
- </li>
-
- <li>
- <p>Issue the command:</p>
-<pre class="screen">
-\$ <span class="bold"><b>initex unpack2e.ins</b></span>
-</pre>
-
- <p>This will unpack all of the distribution
- files.</p>
- </li>
-
- <li>
- <p>Build the format file by issuing the
- command:</p>
-<pre class="screen">
-\$ <span class="bold"><b>initex latex2e.ltx</b></span>
-</pre>
-
- <p>Move the resulting files <tt>latex2e.fmt</tt>
- <a id="id2876114" class="indexterm"
- name="id2876114"></a> and <tt>latex2e.log</tt><a
- id="id2876128" class="indexterm"
- name="id2876128"></a> into the TeX formats
- directory.</p>
- </li>
-
- <li>
- <p>In addition to the files needed to build the
- format, unpacking the LaTeX2e distribution
- creates many files that are needed for formatting
- documents. These files must be placed in a
- location where TeX will find them. However, in
- order to maintain a functioning LaTeX 2.09
- system, you must not place the new files in the
- same input directory as the existing
- files.<sup>[<a id="id2876148" name="id2876148"
- href="#ftn.id2876148">48</a>]</sup></p>
-
- <p>Create a new directory (or folder) for the new
- files. On the unix system that I use, where
- existing input files are stored in a directory
- called <tt>/usr/local/lib/tex/inputs</tt>, I
- created <tt>/usr/local/lib/tex/latex2e</tt> to
- store the new files. You will have to add the new
- directory to the <span
- class="emphasis"><em>front</em></span> of the
- list of directories that TeX searches for input
- files whenever you format a document with
- LaTeX2e.</p>
-
- <p>Move the files that the installation script
- produces into the new directory. Move the files
- <tt>docstrip.tex</tt>, <tt>latexbug.tex</tt>,
- <tt>sfontdef.ltx</tt>, <tt>slides.ltx</tt>,
- <tt>testpage.tex</tt>, and all of the files that
- end in <tt>.cfg</tt>, <tt>.cls</tt>,
- <tt>.clo</tt>, <tt>.def</tt>, <tt>.fd</tt>, and
- <tt>.sty</tt>. You should also move the files
- <tt>gglo.ist</tt> and <tt>gind.ist</tt> someplace
- where <b>MakeIndex</b> can find them.
- (<b>MakeIndex</b> is described in Chapter&#160;<a
- href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a>, <span
- class="emphasis"><em><a href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a></em></span>.)</p>
-
- <p>One of the aspects of the test releases that
- continues to change is the exact list of files
- that must be moved. Consult the
- <tt>install.l2e</tt> file in the distribution for
- the exact list. The list above is from the test
- version of January 28, 1994.</p>
- </li>
- </ol>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.latex"
- name="sec.latex"></a>LaTeX</h3>
- </div>
- </div>
-
- <p>This section briefly covers LaTeX version 2.09. This
- version of LaTeX<a id="id2876362" class="indexterm"
- name="id2876362"></a><a id="id2876373" class="indexterm"
- name="id2876373"></a> is still very widely used but it is
- being phased out.</p>
-
- <p>The LaTeX input to produce the sample page in
- Figure&#160;<a href="ch04.html#fig.sampresults"
- title="Figure&#160;4.1.&#160;Sample page">Figure&#160;4.1</a>
- is shown in Example&#160;<a
- href="ch04.html#fig.samplatex"
- title="Figure&#160;4.4.&#160;LaTeX Input File">Figure&#160;4.4</a>.</p>
-
- <div class="figure">
- <a id="fig.samplatex" name="fig.samplatex"></a>
-
- <p class="title"><b>Figure&#160;4.4.&#160;LaTeX Input
- File</b></p>
-
- <div class="mediaobject">
- <img src="perf-ltx.eps" />
- </div>
- </div>
-
- <p>Support for the NFSS in LaTeX 2.09 has been withdrawn.
- If you need to build a format with support for NFSS,
- consult the &#8220;<a href="ch04.html#sec.latexe"
- title="LaTeX2e">the section called
- &#8220;LaTeX2e&#8221;</a>&#8221; section of this
- chapter.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.buildlatexofss"
- name="sec.buildlatexofss"></a>Building the LaTeX
- format with the OFSS</h4>
- </div>
- </div>
-
- <p>The LaTeX <a id="id2876478" class="indexterm"
- name="id2876478"></a><a id="id2876490"
- class="indexterm"
- name="id2876490"></a>distribution<sup>[<a
- id="id2876500" name="id2876500"
- href="#ftn.id2876500">49</a>]</sup> includes three
- subdirectories, <tt>sty</tt>, <tt>doc</tt>, and
- <tt>general</tt>. All of the LaTeX files required to
- build the format file are in the <tt>general</tt>
- subdirectory. You will also need the
- <tt>hyphen.tex</tt> file <a id="id2876557"
- class="indexterm" name="id2876557"></a> required to
- build the Plain format.</p>
-
- <p>In the <tt>general</tt> subdirectory, the
- command:</p>
-<pre class="screen">
-\$ <span class="bold"><b>initex lplain</b></span>
-</pre>
-
- <p>will create the LaTeX format. Move the resulting
- files, <tt>lplain.fmt</tt> <a id="id2876609"
- class="indexterm" name="id2876609"></a> and
- <tt>lplain.log</tt><a id="id2876632" class="indexterm"
- name="id2876632"></a>, to the TeX formats directory. In
- order to complete the installation, copy the files from
- the <tt>sty</tt> directory in the LaTeX distribution
- into a directory where TeX searches for input
- files.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.texincolor"
- name="sec.texincolor"></a>AMSTeX</h3>
- </div>
- </div>
-
- <p>When the American Mathematical Society<a
- id="id2876675" class="indexterm" name="id2876675"></a>
- selected TeX as a document preparation system, they
- decided to extend it in a number of ways to make the
- creation of papers and journals easier. They had two
- goals: to make it easier for authors to write
- mathematical papers in TeX and to make the resulting
- papers conform to a particular set of style
- specifications. AMSTeX<a id="id2876684" class="indexterm"
- name="id2876684"></a> is described completely in <span
- class="emphasis"><em>The Joy of TeX</em></span>&#160;[<a
- href="bi01.html#ms:joyoftex">ms:joyoftex</a>].</p>
-
- <p>AMSTeX provides many commands that resemble LaTeX
- environments. These have the form
- \<i><tt>environment</tt></i> &#8230;
- \end<i><tt>environment</tt></i>. In addition, AMSTeX
- provides the notion of a document style to control
- style-related formatting issues.</p>
-
- <p>Another important contribution made by the American
- Mathematical Society when creating AMSTeX was the
- construction of a large number of new fonts<a
- id="id2876739" class="indexterm" name="id2876739"></a><a
- id="id2876757" class="indexterm" name="id2876757"></a>.
- The American Mathematical Society provides fonts with
- many more mathematical symbols than the fonts that come
- with TeX. These fonts are available as a separate package
- and can be used with any TeX macro package, not just
- AMSTeX.</p>
-
- <p>The AMSTeX input required to produce the document in
- Figure&#160;<a href="ch04.html#fig.amsresults"
- title="Figure&#160;4.6.&#160;AMS sample page">Figure&#160;4.6</a>
- is shown in Example&#160;<a
- href="ch04.html#ex.sampamstex"
- title="Figure&#160;4.5.&#160;AMSTeX Input File">Figure&#160;4.5</a>.
- The result of formatting this document does not appear
- exactly like Figure&#160;<a
- href="ch04.html#fig.sampresults"
- title="Figure&#160;4.1.&#160;Sample page">Figure&#160;4.1</a>
- because AMSTeX uses the style conventions of the American
- Mathematical Society.</p>
-
- <div class="figure">
- <a id="ex.sampamstex" name="ex.sampamstex"></a>
-
- <p class="title"><b>Figure&#160;4.5.&#160;AMSTeX Input
- File</b></p>
-
- <div class="mediaobject">
- <a type="simple" show="embed" actuate="onLoad"
- href="perf-amt"></a>
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.amsresults" name="fig.amsresults"></a>
-
- <p class="title"><b>Figure&#160;4.6.&#160;AMS sample
- page</b></p>
-
- <div class="mediaobject">
- <img src="perf-amt.eps" />
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2876876"
- name="id2876876"></a>Building the AMSTeX
- format</h4>
- </div>
- </div>
-
- <p>In order to build the AMSTeX format, you need the
- <tt>plain.tex</tt> <a id="id2876893" class="indexterm"
- name="id2876893"></a> and <tt>hyphen.tex</tt> files <a
- id="id2876917" class="indexterm" name="id2876917"></a>
- from Plain TeX and the <tt>amstex.ini</tt> <a
- id="id2876941" class="indexterm" name="id2876941"></a>
- and <tt>amstex.tex</tt> <a id="id2876959"
- class="indexterm" name="id2876959"></a> files from the
- AMSTeX distribution<a id="id2876970" class="indexterm"
- name="id2876970"></a>.</p>
-
- <p>The command:</p>
-<pre class="screen">
-\$ <span class="bold"><b>initex amstex.ini</b></span>
-</pre>
-
- <p>will create the AMSTeX format. Move the resulting
- files, <tt>amstex.fmt</tt> <a id="id2877015"
- class="indexterm" name="id2877015"></a> and
- <tt>amstex.log</tt><a id="id2877031" class="indexterm"
- name="id2877031"></a>, into your TeX formats
- directory.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2877047"
- name="id2877047"></a>AMSLaTeX</h3>
- </div>
- </div>
-
- <p>AMSLaTeX<a id="id2877055" class="indexterm"
- name="id2877055"></a><a id="id2877065" class="indexterm"
- name="id2877065"></a>, like AMSTeX, provides many
- features to make typesetting mathematics convenient while
- meeting the standards of the American Mathematical
- Society<a id="id2877079" class="indexterm"
- name="id2877079"></a> for publication. However, AMSTeX
- lacks many of the features that are present in LaTeX,
- like automatically numbered sections and tools for
- creating tables of contents and indexes.</p>
-
- <p>When LaTeX gained popularity, many authors requested
- permission to submit articles to the American
- Mathematical Society in LaTeX. In 1987, the American
- Mathematical Society began a project to combine the
- features of AMSTeX with the features of LaTeX. The result
- is AMSLaTeX.</p>
-
- <p>AMSLaTeX provides all of the functionality of LaTeX
- because it is an extension of LaTeX. It also provides the
- functionality of AMSTeX in LaTeX syntax and access to
- additional mathematical constructs and math symbols not
- present in LaTeX. .</p>
-
- <p>The input required to produce Figure&#160;<a
- href="ch04.html#fig.sampresults"
- title="Figure&#160;4.1.&#160;Sample page">Figure&#160;4.1</a>
- is not shown because they do not differ significantly
- from the LaTeX sample. Because the sample document
- doesn't use any of AMSLaTeX's additional features, it is
- exactly the same as the LaTeX document.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2877132"
- name="id2877132"></a>Building the AMSLaTeX
- format</h4>
- </div>
- </div>
-
- <p>The AMSLaTeX macros are embodied entirely in style
- files for LaTeX. It is not necessary to build a special
- format file<a id="id2877141" class="indexterm"
- name="id2877141"></a>. However, the AMSLaTeX macros
- require the New Font Selection Scheme (NFSS). Consult
- the section on LaTeX, above, for instructions on
- building the LaTeX format with NFSS.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2877164"
- name="id2877164"></a>Lollipop</h3>
- </div>
- </div>
-
- <p>It can be argued that LaTeX has the following
- deficiency: although there are many different style
- options available, it is not easy for a novice user to
- change a style option. Changing the internals of most
- LaTeX style options requires a deep understanding of
- TeX.</p>
-
- <p>The Lollipop<a id="id2877183" class="indexterm"
- name="id2877183"></a><a id="id2877189" class="indexterm"
- name="id2877189"></a> format is very different from the
- other formats. The central thrust of Lollipop is that it
- should be easy to change and customize document styles.
- All Lollipop documents are built from five different
- generic constructs: headings, lists, text blocks, page
- grids, and external items.</p>
-
- <p>The Lollipop input required to produce a document like
- the sample page in Figure&#160;<a
- href="ch04.html#fig.sampresults"
- title="Figure&#160;4.1.&#160;Sample page">Figure&#160;4.1</a>
- is shown in Example&#160;<a
- href="ch04.html#ex.samplollipop"
- title="Figure&#160;4.7.&#160;Lollipop Input File">Figure&#160;4.7</a>.</p>
-
- <div class="figure">
- <a id="ex.samplollipop" name="ex.samplollipop"></a>
-
- <p class="title"><b>Figure&#160;4.7.&#160;Lollipop
- Input File</b></p>
-
- <div class="mediaobject">
- <a type="simple" show="embed" actuate="onLoad"
- href="perf-lol"></a>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2873878"
- name="id2873878"></a>Building the Lollipop
- format</h4>
- </div>
- </div>
-
- <p>To make <a id="id2873887" class="indexterm"
- name="id2873887"></a>the Lollipop format, you need the
- Lollipop distribution and the file <tt>hyphen.tex</tt>
- from the Plain TeX distribution.</p>
-
- <p>This command will create the Lollipop format:</p>
-<pre class="screen">
-\$ <span class="bold"><b>initex lollipop \dump</b></span>
-</pre>
-
- <p>It should be performed in the directory where you
- installed the Lollipop distribution so that all of the
- Lollipop files can be located. Move the resulting files
- <tt>lollipop.fmt</tt><a id="id2873932"
- class="indexterm" name="id2873932"></a> and
- <tt>lollipop.log</tt><a id="id2873950"
- class="indexterm" name="id2873950"></a> into your TeX
- formats directory.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2873910"
- name="id2873910"></a>TeXinfo</h3>
- </div>
- </div>
-
- <p>The TeXinfo format is a general-purpose format, but it
- was designed to support a particular application: to
- produce both online documentation and professional
- quality typeset documentation from the same source file.
- It is discussed in more detail in Chapter&#160;<a
- href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation">Chapter&#160;10</a>,
- <span class="emphasis"><em><a href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation">Chapter&#160;10</a></em></span>.</p>
-
- <p>The input file shown in Example&#160;<a
- href="ch04.html#ex.infinp"
- title="Figure&#160;4.8.&#160;TeXinfo Input">Figure&#160;4.8</a>
- produces the typeset output shown in Figure&#160;<a
- href="ch04.html#fig.infex"
- title="Figure&#160;4.9.&#160;TeXinfo sample page">Figure&#160;4.9</a>.
- The input file for this example is complicated by the
- fact that it contains mathematics. None of TeX's
- sophisticated mechanisms for handling mathematics are
- applicable to plain ASCII online documentation. The
- online documentation produced by the example in
- Example&#160;<a href="ch04.html#ex.infinp"
- title="Figure&#160;4.8.&#160;TeXinfo Input">Figure&#160;4.8</a>
- is shown in Figure&#160;<a href="ch04.html#fig.infinf"
- title="Figure&#160;4.10.&#160;Online documentation produced by MakeInfo">
- Figure&#160;4.10</a>.</p>
-
- <p>The TeXinfo<a id="id2877600" class="indexterm"
- name="id2877600"></a><a id="id2877609" class="indexterm"
- name="id2877609"></a> format is the official
- documentation format of the Free Software Foundation
- (FSF)<a id="id2877625" class="indexterm"
- name="id2877625"></a>. Although less commonly used, a
- LaTeX variant called LaTeXinfo<a id="id2877634"
- class="indexterm" name="id2877634"></a> is also
- available.</p>
-
- <div class="figure">
- <a id="ex.infinp" name="ex.infinp"></a>
-
- <p class="title"><b>Figure&#160;4.8.&#160;TeXinfo
- Input</b></p>
-
- <div class="mediaobject">
- <a type="simple" show="embed" actuate="onLoad"
- href="perf-inf"></a>
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.infex" name="fig.infex"></a>
-
- <p class="title"><b>Figure&#160;4.9.&#160;TeXinfo
- sample page</b></p>
-
- <div class="mediaobject">
- <img src="perf-inf.eps" />
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.infinf" name="fig.infinf"></a>
-
- <p class="title"><b>Figure&#160;4.10.&#160;Online
- documentation produced by MakeInfo</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="perf-inf.inf"></a>
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2877747"
- name="id2877747"></a>Other Formats</h3>
- </div>
- </div>
-
- <p>There are a number of other macro packages available
- for TeX. Some of them are summarized below. The fact that
- they are not discussed more fully here (or listed below,
- for that matter) is not intended to reflect on the
- quality of the format. The formats discussed above are
- examples of the ways in which TeX can be extended. All of
- the formats below extend TeX in a way similar to one of
- the formats already mentioned. For any particular
- application, one of these macro packages might be a
- better choice than the formats discussed above.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">EDMAC</span></dt>
-
- <dd>
- <p>Provides support for typesetting critical
- editions of texts in a format similar to the Oxford
- Classical Texts with marginal line numbers and
- multiple series of footnotes and endnotes keyed by
- line number. EDMAC<a id="id2877788"
- class="indexterm" name="id2877788"></a><a
- id="id2877796" class="indexterm"
- name="id2877796"></a> is available from the CTAN
- archives in the directory
- <tt>macros/plain/contrib/edmac</tt>.</p>
- </dd>
-
- <dt><span class="term">INRSTeX</span></dt>
-
- <dd>
- <p>Provides support for multilingual documents in
- French<a id="id2877842" class="indexterm"
- name="id2877842"></a> and English. INRSTeX<a
- id="id2877853" class="indexterm"
- name="id2877853"></a><a id="id2877862"
- class="indexterm" name="id2877862"></a> is
- available from the CTAN archives in the directory
- <tt>macros/inrstex</tt>.</p>
- </dd>
-
- <dt><span class="term">LamSTeX</span></dt>
-
- <dd>
- <p>Extends AMSTeX with LaTeX-like features and
- improved support for commutative diagrams.
- LamSTeX<a id="id2877908" class="indexterm"
- name="id2877908"></a><a id="id2877921"
- class="indexterm" name="id2877921"></a> is
- available from the CTAN archives in
- <tt>macros/lamstex</tt>.</p>
- </dd>
-
- <dt><span class="term">REVTeX</span></dt>
-
- <dd>
- <p>Extends LaTeX to provide support for typesetting
- articles for journals of the American Physical
- Society<a id="id2877974" class="indexterm"
- name="id2877974"></a>, the Optical Society of
- America<a id="id2877982" class="indexterm"
- name="id2877982"></a>, and the American Institute
- for Physics<a id="id2877992" class="indexterm"
- name="id2877992"></a>. REVTeX<a id="id2878000"
- class="indexterm" name="id2878000"></a><a
- id="id2878010" class="indexterm"
- name="id2878010"></a> is available in the directory
- <tt>macros/latex/contrib/revtex</tt> of the CTAN
- archives.</p>
- </dd>
-
- <dt><span class="term">TeXsis</span></dt>
-
- <dd>
- <p>Provides facilities for typesetting articles,
- papers, and theses. It is particularly tuned for
- physics papers. TeXsis<a id="id2878061"
- class="indexterm" name="id2878061"></a><a
- id="id2878071" class="indexterm"
- name="id2878071"></a> also provides support for
- other kinds of documents, such as letters and
- memos. It is based upon Plain TeX. TeXsis is
- available from the CTAN archives in the directory
- <tt>macros/texsis</tt>.</p>
-
- <p>In addition to REVTeX and TeXsis, there are
- several other packages in the <tt>macros</tt>
- directory on CTAN that were designed for
- typesetting documents about physics: PHYSE<a
- id="id2878115" class="indexterm"
- name="id2878115"></a><a id="id2878122"
- class="indexterm" name="id2878122"></a>, PHYZZX<a
- id="id2878134" class="indexterm"
- name="id2878134"></a><a id="id2878141"
- class="indexterm" name="id2878141"></a>, and
- PSIZZLE<a id="id2878152" class="indexterm"
- name="id2878152"></a><a id="id2878159"
- class="indexterm" name="id2878159"></a>.</p>
- </dd>
-
- <dt><span class="term">TeX/Mathematica</span></dt>
-
- <dd>
- <p>Supports interactive use of Mathematica<a
- id="id2878190" class="indexterm"
- name="id2878190"></a> on unix workstations running
- GNU emacs. Mathematica explorations can be
- annotated with TeX/LaTeX, and Mathematica graphics
- can be incorporated into documents.
- TeX/Mathematica<a id="id2878198" class="indexterm"
- name="id2878198"></a><a id="id2878213"
- class="indexterm" name="id2878213"></a> is
- available from the CTAN archives in the directory
- <tt>macros/mathematica</tt>.</p>
- </dd>
-
- <dt><span class="term">ScriptTeX</span></dt>
-
- <dd>
- <p>Supports typesetting screenplays in TeX.
- ScriptTeX<a id="id2878261" class="indexterm"
- name="id2878261"></a><a id="id2878271"
- class="indexterm" name="id2878271"></a> is
- available from the CTAN archives in the directory
- <tt>macros/scripttex</tt>.</p>
- </dd>
-
- <dt><span class="term">VerTeX</span></dt>
-
- <dd>
- <p>Supports typesetting articles for economic
- journals. VerTeX<a id="id2878320" class="indexterm"
- name="id2878320"></a><a id="id2878330"
- class="indexterm" name="id2878330"></a> is
- available from the CTAN archives in the directory
- <tt>macros/plain/contrib/vertex</tt>.</p>
- </dd>
- </dl>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2878394"
- name="id2878394"></a>Special-purpose Formats</h2>
- </div>
- </div>
-
- <p>In addition to the general-purpose packages <a
- id="id2878402" class="indexterm" name="id2878402"></a>
- discussed above, there are dozens, if not hundreds, of
- extensions to TeX that are designed for very specific
- tasks. Many of the extensions are LaTeX style files; they
- provide styles for many academic journals, university
- theses, resum\'es, diagrams of various sorts, PostScript
- interfaces, linguistics, multinational language support,
- unix &#8220;man&#8221; pages, program listings, and
- countless other tasks.</p>
-
- <p>To give you a feel for the range of tasks that TeX can
- perform, I've selected a few packages to highlight the
- latitude of customization that is possible. Figure&#160;<a
- href="ch04.html#fig.caffeine"
- title="Figure&#160;4.11.&#160;Caffeine by ChemTeX">Figure&#160;4.11</a>
- shows the chemical structure of caffeine (a molecule dear
- to my heart) rendered with the ChemTeX<a id="id2878431"
- class="indexterm" name="id2878431"></a><a id="id2878453"
- class="indexterm" name="id2878453"></a> package. The source
- is shown in Example&#160;<a
- href="ch04.html#fig.caffeine-source"
- title="Figure&#160;4.12.&#160;The ChemTeX Source for Caffeine">
- Figure&#160;4.12</a>. Another chemistry package,
- ChemStruct<a id="id2878479" class="indexterm"
- name="id2878479"></a><a id="id2878486" class="indexterm"
- name="id2878486"></a>, was used to draw Figure&#160;<a
- href="ch04.html#fig.lithium"
- title="Figure&#160;4.13.&#160;A lithium cation rendered by ChemStruct">
- Figure&#160;4.13</a>. Its source is shown in
- Example&#160;<a href="ch04.html#fig.lithium-source"
- title="Figure&#160;4.14.&#160;The ChemStruct Source for the Lithium Cation">
- Figure&#160;4.14</a>. Taking TeX in another direction, the
- MusicTeX<a id="id2878521" class="indexterm"
- name="id2878521"></a><a id="id2878529" class="indexterm"
- name="id2878529"></a> package was used to typeset the first
- two bars of Mozart's K545 sonata in C-major in
- Figure&#160;<a href="ch04.html#fig.mozart"
- title="Figure&#160;4.15.&#160;A little Mozart&#8230;">Figure&#160;4.15</a>.
- The MusicTeX input is shown in Example&#160;<a
- href="ch04.html#fig.mozart-source"
- title="Figure&#160;4.16.&#160;The MusicTeX Source for Figure ">
- Figure&#160;4.16</a>. Several more examples are presented
- in Chapter&#160;<a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">Chapter&#160;7</a>
- where formats for typesetting non-English languages are
- described.</p>
-
- <div class="figure">
- <a id="fig.caffeine" name="fig.caffeine"></a>
-
- <p class="title"><b>Figure&#160;4.11.&#160;Caffeine by
- ChemTeX</b></p>
-
- <div class="mediaobject">
- <img src="caffeine.eps" />
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.caffeine-source"
- name="fig.caffeine-source"></a>
-
- <p class="title"><b>Figure&#160;4.12.&#160;The ChemTeX
- Source for Caffeine</b></p>
-
- <div class="mediaobject">
- <a type="simple" show="embed" actuate="onLoad"
- href="caffeine.tex"></a>
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.lithium" name="fig.lithium"></a>
-
- <p class="title"><b>Figure&#160;4.13.&#160;A lithium
- cation rendered by ChemStruct</b></p>
-
- <div class="mediaobject">
- <img src="lithium.eps" />
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.lithium-source" name="fig.lithium-source"></a>
-
- <p class="title"><b>Figure&#160;4.14.&#160;The ChemStruct
- Source for the Lithium Cation</b></p>
-
- <div class="mediaobject">
- <a type="simple" show="embed" actuate="onLoad"
- href="lithium.tex"></a>
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.mozart" name="fig.mozart"></a>
-
- <p class="title"><b>Figure&#160;4.15.&#160;A little
- Mozart&#8230;</b></p>
-
- <div class="mediaobject">
- <img src="mozart.eps" />
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.mozart-source" name="fig.mozart-source"></a>
-
- <p class="title"><b>Figure&#160;4.16.&#160;The MusicTeX
- Source for Figure <a href="ch04.html#fig.mozart"
- title="Figure&#160;4.15.&#160;A little Mozart&#8230;">Figure&#160;4.15</a></b></p>
-
- <div class="mediaobject">
- <a type="simple" show="embed" actuate="onLoad"
- href="mozart.tex"></a>
- </div>
- </div>
-
- <p>Another popular special-purpose application of TeX is
- the production of transparencies<a id="id2878799"
- class="indexterm" name="id2878799"></a>, also called
- foils<a id="id2878808" class="indexterm"
- name="id2878808"></a> or slides<a id="id2878816"
- class="indexterm" name="id2878816"></a>. There are a few
- different options for this application.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2878827"
- name="id2878827"></a>SliTeX</h3>
- </div>
- </div>
-
- <p>SliTeX is part of the standard LaTeX distribution.
- Input to SliTeX consists of a main file and a slides
- file. Individual slides are composed in a <tt>slide</tt>
- environment.</p>
-
- <p>SliTeX<a id="id2878850" class="indexterm"
- name="id2878850"></a><a id="id2878859" class="indexterm"
- name="id2878859"></a> has provisions for black-and-white
- slides, color slides, and overlays. Unlike the other
- slide-making formats, which rely on \special printer
- commands<sup>[<a id="id2878876" name="id2878876"
- href="#ftn.id2878876">50</a>]</sup> to incorporate color,
- SliTeX produces separate output pages for each color. For
- example, if you use red to highlight words on an
- otherwise black-and-white slide, SliTeX will produce two
- output pages for the slide: one with all the black text
- (excluding the words in red) and one with just the red
- words. Both of these pages will be printed in black. You
- must construct the colored slide by copying the pages
- onto colored transparencies and overlaying them.
- Producing slides with overlays in the same color is
- accomplished with a special &#8220;invisible&#8221;
- color. This method of producing colored transparencies
- has been made obsolete by modern color printers. Of
- course, nothing prevents you from using the \special
- extensions of your DVI driver in SliTeX to produce
- colored transparencies directly on a color printer.</p>
-
- <p>SliTeX has always been a separate macro package,
- distinct from and not 100\% compatible with LaTeX. With
- the introduction of LaTeX2e, SliTeX is simply an
- extension package to the LaTeX2e core format. Support for
- a separate SliTeX format is being phased out.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2878922"
- name="id2878922"></a>FoilTeX</h3>
- </div>
- </div>
-
- <p>FoilTeX<a id="id2878931" class="indexterm"
- name="id2878931"></a> is an extension of LaTeX for
- producing slides. The primary advantage of FoilTeX over
- SliTeX is that it is completely compatible with
- LaTeX.<sup>[<a id="id2878942" name="id2878942"
- href="#ftn.id2878942">51</a>]</sup> Note, however, that
- the defaults in many cases are not precisely the same as
- LaTeX because of the radically different goal of
- FoilTeX.</p>
-
- <p>FoilTeX provides support for running headers and
- footers, modified theorem environments for better
- mathematics in slides, support for AMS and PostScript
- fonts, and colors.</p>
-
- <p>Color slides in FoilTeX are handled by DVI driver
- \special commands (most commonly <b>dvips</b> \specials).
- However, FoilTeX includes a number of new and extended
- features for better handling of color. See the section
- &#8220;<a href="ch04.html#sec.texincolor"
- title="AMSTeX">the section called
- &#8220;AMSTeX&#8221;</a>&#8221; later in this chapter for
- a detailed discussion of using color in TeX.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2878993"
- name="id2878993"></a>Seminar</h3>
- </div>
- </div>
-
- <p>The Seminar<a id="id2879000" class="indexterm"
- name="id2879000"></a> style is another alternative for
- producing slides and notes. Like FoilTeX, the Seminar
- style is designed to work on top of LaTeX. (Seminar also
- works with AMSLaTeX.) \ The Seminar style is designed to
- produce output for a PostScript printer. It isn't
- strictly necessary to produce PostScript output, but if
- you do not, many of Seminar's features will be
- unavailable to you.</p>
-
- <p>Seminar provides for a mixture of portrait and
- landscape styles and can support color using either a
- color-separation technique (similar to SliTeX's method)
- or direct use of PostScript color. In either case, the
- PSTricks<a id="id2879012" class="indexterm"
- name="id2879012"></a> macro package is required. (Consult
- the section &#8220;<a
- href="ch06.html#sec.pictures.pstricks"
- title="PSTricks">the section called
- &#8220;PSTricks&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a>,
- <span class="emphasis"><em><a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a></em></span>,
- for more information.)</p>
-
- <p>The Seminar style has support for a number of
- interesting options (including two-up printing of
- slides), automatic resizing by changing a magnification
- parameter, instructions for converting your SliTeX
- slides, and several extensive demonstration files. Also
- included are explicit instructions for placing
- Encapsulated PostScript drawings in your slides.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2879086"
- name="id2879086"></a>TeX in Color</h2>
- </div>
- </div>
-
- <p>With color printers<a id="id2879094" class="indexterm"
- name="id2879094"></a><a id="id2879107" class="indexterm"
- name="id2879107"></a> and copiers becoming more common, the
- application of color, especially in transparencies, is more
- important than ever. Unfortunately, TeX knows <span
- class="emphasis"><em>nothing</em></span> about color.</p>
-
- <p>A little reflection about the design of TeX will make it
- clear why this is the case. TeX produces device-independent
- output. Even when color printers are as common as
- &#8220;regular&#8221; printers, if that ever becomes the
- case, it will always be true that color is an inherently
- device-dependent attribute. It does not make sense for TeX
- to understand color. However, this does not prevent TeX
- from using color.</p>
-
- <p>At the lowest level, all that is required to use color
- in TeX is some way of telling the printer &#8220;start
- printing in &lt;<span
- class="emphasis"><em>color</em></span>&gt; here.&#8221;
- This is easily accomplished with a \special command. In the
- discussion that follows, the <b>dvips</b> \special commands
- are used as concrete examples, but conceptually, any color
- printer can be used in this way.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2879169"
- name="id2879169"></a>Setting Up Color</h3>
- </div>
- </div>
-
- <p>Color <a id="id2879178" class="indexterm"
- name="id2879178"></a> support at the DVI driver level is
- provided by \special commands, but these are not
- typically convenient to enter directly into your
- document. Frequently, these commands are specified in
- terms of percentages of red, green, and blue (RGB color)
- <a id="id2879192" class="indexterm" name="id2879192"></a>
- or cyan, magenta, yellow, and black (CMYK color)<a
- id="id2879209" class="indexterm"
- name="id2879209"></a>.</p>
-
- <p>Higher-level support is provided by a collection of
- color control sequences. These sequences are loaded
- either by inputting the file <tt>colordvi.tex</tt><a
- id="id2879233" class="indexterm" name="id2879233"></a>
- (in Plain TeX, for example) or using the
- <tt>colordvi</tt><a id="id2879253" class="indexterm"
- name="id2879253"></a> style file (in LaTeX).</p>
-
- <p><b>dvips</b> defines the colors in terms of
- &#8220;crayon names.&#8221; If you need very precise
- control of the colors, you can adjust the precise mix of
- CMYK values in the file <tt>colordvi.tex</tt> after
- comparing the output of your printer with a standard
- scale (typically, the PANTONE scale). The following color
- names are standard in <b>dvips</b>.</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>Apricot</td>
-
- <td>Emerald</td>
-
- <td>OliveGreen</td>
-
- <td>RubineRed</td>
- </tr>
-
- <tr>
- <td>Aquamarine</td>
-
- <td>ForestGreen</td>
-
- <td>Orange</td>
-
- <td>Salmon</td>
- </tr>
-
- <tr>
- <td>Bittersweet</td>
-
- <td>Fuchsia</td>
-
- <td>OrangeRed</td>
-
- <td>SeaGreen</td>
- </tr>
-
- <tr>
- <td>Black</td>
-
- <td>Goldenrod</td>
-
- <td>Orchid</td>
-
- <td>Sepia</td>
- </tr>
-
- <tr>
- <td>Blue</td>
-
- <td>Gray</td>
-
- <td>Peach</td>
-
- <td>SkyBlue</td>
- </tr>
-
- <tr>
- <td>BlueGreen</td>
-
- <td>Green</td>
-
- <td>Periwinkle</td>
-
- <td>SpringGreen</td>
- </tr>
-
- <tr>
- <td>BlueViolet</td>
-
- <td>GreenYellow</td>
-
- <td>PineGreen</td>
-
- <td>Tan</td>
- </tr>
-
- <tr>
- <td>BrickRed</td>
-
- <td>JungleGreen</td>
-
- <td>Plum</td>
-
- <td>TealBlue</td>
- </tr>
-
- <tr>
- <td>Brown</td>
-
- <td>Lavender</td>
-
- <td>ProcessBlue</td>
-
- <td>Thistle</td>
- </tr>
-
- <tr>
- <td>BurntOrange</td>
-
- <td>LimeGreen</td>
-
- <td>Purple</td>
-
- <td>Turquoise</td>
- </tr>
-
- <tr>
- <td>CadetBlue</td>
-
- <td>Magenta</td>
-
- <td>RawSienna</td>
-
- <td>Violet</td>
- </tr>
-
- <tr>
- <td>CarnationPink</td>
-
- <td>Mahogany</td>
-
- <td>Red</td>
-
- <td>VioletRed</td>
- </tr>
-
- <tr>
- <td>Cerulean</td>
-
- <td>Maroon</td>
-
- <td>RedOrange</td>
-
- <td>White</td>
- </tr>
-
- <tr>
- <td>CornflowerBlue</td>
-
- <td>Melon</td>
-
- <td>RedViolet</td>
-
- <td>WildStrawberry</td>
- </tr>
-
- <tr>
- <td>Cyan</td>
-
- <td>MidnightBlue</td>
-
- <td>Rhodamine</td>
-
- <td>Yellow</td>
- </tr>
-
- <tr>
- <td>Dandelion</td>
-
- <td>Mulberry</td>
-
- <td>RoyalBlue</td>
-
- <td>YellowGreen</td>
- </tr>
-
- <tr>
- <td>DarkOrchid</td>
-
- <td>NavyBlue</td>
-
- <td>RoyalPurple</td>
-
- <td>YellowOrange</td>
- </tr>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2879595"
- name="id2879595"></a>Using Color</h3>
- </div>
- </div>
-
- <p>After <b>dvips</b> has loaded <tt>colordvi</tt>,
- typesetting text in color is simply a matter of using the
- appropriate color control sequence<a id="id2879619"
- class="indexterm" name="id2879619"></a><a id="id2879629"
- class="indexterm" name="id2879629"></a>. For example, to
- typeset something in red, use the \Red control sequence
- in your document, like this:</p>
-<pre class="screen">
-\Red{something in red}
-</pre>
-
- <p>Alternatively, you can change the default text color
- with the \text\texttt{<span
- class="emphasis"><em>color</em></span>} control
- sequences. To make default color for all text blue,
- enter:</p>
-<pre class="screen">
-\textBlue
-</pre>
-
- <p>To change the background color, use the \background
- macro. For example, to make the current and all future
- pages yellow, enter:</p>
-<pre class="screen">
-\background{Yellow}
-</pre>
-
- <p>You can enter a precise color by specifying it in
- terms of its CMYK components. The \Color and \textColor
- macros exist for this purpose. To typeset some text in a
- color that is 25\% cyan, 35\% magenta, 40\% yellow, and
- 10\% black,<sup>[<a id="id2879690" name="id2879690"
- href="#ftn.id2879690">52</a>]</sup> enter:</p>
-<pre class="screen">
-\Color{.25 .35 .4 .1}{some text}
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2879708"
- name="id2879708"></a>Now I've Got Color, but I Need
- Black and White!</h3>
- </div>
- </div>
-
- <p>If you have reason to print a colored TeX document on
- a black and white printer, you don't have to tear out all
- of the color commands. <b>dvips</b> includes a
- <tt>blackdvi</tt> file <a id="id2879734"
- class="indexterm" name="id2879734"></a>(analogous to
- <tt>colordvi</tt><a id="id2879748" class="indexterm"
- name="id2879748"></a>---an input file or style file
- depending on your macro package), which translates all
- color commands into black and white.</p>
-
- <p>Alternatively, &#8220;good&#8221; implementations of
- PostScript in a black and white printer should translate
- all colors into shades of grey. This can be an
- inexpensive way to preview a color document. Most screen
- previewers simply ignore color commands so they print in
- black and white even if the document is colored.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2879774"
- name="id2879774"></a>Color Under LaTeX2e</h3>
- </div>
- </div>
-
- <p>At the time of this writing, the LaTeX2e<a
- id="id2879783" class="indexterm" name="id2879783"></a><a
- id="id2879797" class="indexterm" name="id2879797"></a>
- team has not officially adopted a standard for using
- color. However, it is likely to follow a slightly
- different model than the one described above. The final
- design should provide color selection commands that are
- device-independent at the DVI driver level (in other
- words, the color commands will not insert device-specific
- commands, like snippets of PostScript, into the
- <tt>DVI</tt> files).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2879830"
- name="id2879830"></a>Color Is Subtle</h3>
- </div>
- </div>
-
- <p>Color commands implemented as \special commands may
- introduce occasional problems. For example, if TeX
- introduces a page break in a paragraph that you have
- typeset in yellow (<tt>\Yellow{This is a long
- paragraph...}</tt>), the resulting output may print the
- page footer (and even the header) in yellow, although
- that was not intended.</p>
-
- <p>Circumventing these problems may require careful use
- of color commands in front of text that you want to
- appear black. For example, in Plain TeX the difficulty
- described above can be avoided by specifying that the
- page number should be printed this way:</p>
-<pre class="screen">
-\footline{\Black{\hss\tenrm\folio\hss}}
-</pre>
-
- <p>This definition guarantees that the page number will
- be set in black, and because it is a local color change,
- colored text can flow across the page around it.</p>
-
- <p>You may want to make sure that other typographic
- elements are printed in the current global color (which
- may vary). <b>dvips</b> provides a local color macro
- called \globalColor for that purpose. Every time the text
- color is changed globally (with a \text\texttt{<span
- class="emphasis"><em>Color</em></span>} command),
- \globalColor is redefined to print text in that
- color.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2879898"
- name="id2879898"></a>Further Reading</h3>
- </div>
- </div>
-
- <p>Read the documentation for your DVI driver carefully
- with respect to color. Because it is device-dependent,
- there is a lot of room for interpretation, and it may not
- always be obvious why some things appear the way they do.
- And DVI drivers are free to implement color in any way
- they choose.</p>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2874145" name="ftn.id2874145"
- href="#id2874145">39</a>]</sup> At the time of this
- writing, it's actually still in test-release, but it may
- be available as a standard release by the time you read
- this.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2874246" name="ftn.id2874246"
- href="#id2874246">40</a>]</sup> On Macintosh systems and
- other environments that don't have directories, format
- files are typically stored in their own folders (or other
- metaphorically appropriate place ;-).</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2874291" name="ftn.id2874291"
- href="#id2874291">41</a>]</sup> The distinction between
- big and small TeX is described in the section called
- &#8220;<a href="ch03.html#run.sec.formatfiles"
- title="What Do You Run?">the section called &#8220;What
- Do You Run?&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2874585" name="ftn.id2874585"
- href="#id2874585">42</a>]</sup> {A small set of
- exceptions is maintained because the algorithm isn't
- perfect.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2874736" name="ftn.id2874736"
- href="#id2874736">43</a>]</sup> {Really observant readers
- may have noticed that it's a version of Garamond ;-)}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2875131" name="ftn.id2875131"
- href="#id2875131">44</a>]</sup> {Of course, that's not
- strictly true. You can change the page layout of LaTeX
- (and most other packages) to be almost anything, but it
- does require learning a lot about the macro package. If
- you are already familiar with Plain TeX (or some other
- Plain TeX-derived package), you probably have a set of
- macros that produce documents in the style you like. Why
- reinvent the wheel?</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2875268" name="ftn.id2875268"
- href="#id2875268">45</a>]</sup> {Extended Plain TeX is
- available in the <tt>macros/eplain</tt> directory in the
- CTAN archives.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2875867" name="ftn.id2875867"
- href="#id2875867">46</a>]</sup> {LaTeX2e will process
- documents that use <tt>\ documentstyle</tt> in LaTeX 2.09
- compatibility mode.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2876004" name="ftn.id2876004"
- href="#id2876004">47</a>]</sup> {Under emTeX, this
- variable is called <tt>TEXINPUT</tt>. On the Macintosh,
- file searching is frequently controlled by a
- configuration file or dialog box.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2876148" name="ftn.id2876148"
- href="#id2876148">48</a>]</sup> {Strictly speaking, this
- is only true for files that have the extension
- <tt>.sty</tt> because the old version of LaTeX will not
- attempt to use the other files.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2876500" name="ftn.id2876500"
- href="#id2876500">49</a>]</sup> {LaTeX is available in
- the <tt>macros/latex/distribs/latex</tt> directory in the
- CTAN archives.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2878876" name="ftn.id2878876"
- href="#id2878876">50</a>]</sup> {The $\$<tt>special</tt>
- mechanism is a way of passing arbitrary information
- through TeX to the DVI driver that will ultimately print
- the document.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2878942" name="ftn.id2878942"
- href="#id2878942">51</a>]</sup> {With the caveat that it
- still uses the Old Font Selection Scheme.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2879690" name="ftn.id2879690"
- href="#id2879690">52</a>]</sup> {I made these numbers up.
- I take no responsibility for the artistic merits (or lack
- thereof) of the resulting color.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;3.&#160;Running TeX"
- href="ch03.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Chapter&#160;3.&#160;Running
- TeX&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Part&#160;II.&#160;Elements of a Complex
- Document</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch05.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch05.html
deleted file mode 100644
index ac0558358d6..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch05.html
+++ /dev/null
@@ -1,3711 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;5.&#160;Fonts</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="next" href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;6.&#160;Pictures and Figures"
- href="ch06.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.fonts"
- name="chap.fonts"></a>Chapter&#160;5.&#160;Fonts</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>All of the common TeX macro packages use the Computer
- Modern fonts<a id="id2855980" class="indexterm"
- name="id2855980"></a><a id="id2855984" class="indexterm"
- name="id2855984"></a><a id="id2855991" class="indexterm"
- name="id2855991"></a><a id="id2877438" class="indexterm"
- name="id2877438"></a> by default. In fact, the Computer
- Modern fonts are so frequently used in TeX documents that
- some people believe they are <span
- class="emphasis"><em>the</em></span> TeX fonts and that no
- other options are available.</p>
-
- <p>This is not the case. In fact, using different fonts in
- TeX is quite easy. However, many interrelated font issues can
- be quite complicated, and it is possible to do things that
- make your documents print incorrectly (or make them
- unprintable).</p>
-
- <p>This chapter explores all of the issues related to fonts
- and how these issues are resolved by a combination of font
- files, TeX macros, DVI drivers, and careful planning. At a
- high level, it works like this:</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>TeX macros select a font (by assigning
- \font\fontid=fonttfm). The macros may be very simple or
- quite complex (as is the case in LaTeX's New Font
- Selection Scheme).</p>
- </li>
-
- <li>
- <p>TeX loads the metric information from
- <tt>fonttfm.tfm</tt><a id="id2879938" class="indexterm"
- name="id2879938"></a>. Many implementations of TeX look
- for this file in the directories on the
- <tt>TEXFONTS</tt> path. TeX cannot process your
- document if it cannot find the <tt>TFM</tt> file<a
- id="id2879967" class="indexterm"
- name="id2879967"></a>.<sup>[<a id="id2879974"
- name="id2879974"
- href="#ftn.id2879974">53</a>]</sup></p>
- </li>
-
- <li>
- <p>TeX writes a <tt>DVI</tt> file<a id="id2880010"
- class="indexterm" name="id2880010"></a>. The
- <tt>DVI</tt> file contains the name of each font (the
- name of the <tt>TFM</tt> file) and the magnification
- used (magnification is discussed in the section
- &#8220;<a href="ch05.html#sec.issueofsize"
- title="What TeX Needs To Know">the section called
- &#8220;What TeX Needs To Know&#8221;</a>&#8221; later
- in this chapter).</p>
- </li>
-
- <li>
- <p>The DVI driver attempts to locate font files for
- each font used at each magnification. Depending on the
- DVI driver, fonts can come from many places. Many
- drivers consult a list of built-in fonts to see if the
- desired font resides in the printer. Some also consult
- a list of font substitutions. (This can be used to
- substitute existing fonts for fonts that you do not
- have, like Computer Modern Roman in place of Times
- Roman if you don't have Times Roman.)</p>
-
- <p>Assuming that the font is not built-in<a
- id="id2880077" class="indexterm" name="id2880077"></a>
- or replaced by substitution of a built-in font, the DVI
- driver looks for a font file. Most modern DVI drivers
- look for <tt>PK</tt> fonts, although some also look for
- <tt>GF</tt><a id="id2880109" class="indexterm"
- name="id2880109"></a> and <tt>PXL</tt> fonts<a
- id="id2880130" class="indexterm" name="id2880130"></a>
- as well.</p>
-
- <p>The exact location of these files varies. Some
- implementations look in the directories on the
- <tt>TEXFONTS</tt> path, others look in the
- <tt>TEXPKS</tt> or <tt>PKFONTS</tt> paths.</p>
-
- <p>A typical font directory on a unix system is
- <tt>/usr/local/lib/tex/fonts/pk</tt>. The files in this
- directory typically have names of the form
- <tt>tfmname.999pk</tt>; where <span
- class="emphasis"><em>tfmname</em></span> is the name of
- the font and <span class="emphasis"><em>999</em></span>
- is the resolution.</p>
-
- <p>On file systems which have short filenames (for
- example, MS-DOS) a typical font directory is <tt>\bs
- tex\bs fonts\bs 999dpi</tt> (or <tt>\bs tex\bs fonts\bs
- dpi999</tt>).<sup>[<a id="id2880211" name="id2880211"
- href="#ftn.id2880211">54</a>]</sup> The files are then
- simply <tt>tfmname.pk</tt>.</p>
-
- <p>Some DVI drivers employ automatic font generation to
- attempt to create the font if it cannot be found.</p>
- </li>
-
- <li>
- <p>The DVI driver produces output suitable for a
- particular device. This may include one or more forms
- of downloaded fonts as well as requests for built-in
- fonts that are assumed to exist.</p>
- </li>
- </ol>
- </div>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>TeX output isn't printable directly. TeX typesets a
- document in a device-independent fashion; it's the DVI
- driver that actually <span
- class="emphasis"><em>prints</em></span> the document. This
- is important because many of the font issues are really DVI
- driver issues more than TeX issues, and because the
- distinction between TeXing a document and printing a
- document is another layer of complexity that can be a
- source of difficulty.,</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.issueofsize" name="sec.issueofsize"></a>What
- TeX Needs To Know</h2>
- </div>
- </div>
-
- <p>TeX needs remarkably little information about a font.
- Recall from Chapter&#160;<a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a>,
- <span class="emphasis"><em><a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a></em></span>,
- that TeX typesets each page using &#8220;boxes<a
- id="id2880323" class="indexterm" name="id2880323"></a> and
- glue<a id="id2880331" class="indexterm"
- name="id2880331"></a>.&#8221; In order to perform this
- function, TeX needs to know only the size of each character
- (its width, height, and depth)<a id="id2880343"
- class="indexterm" name="id2880343"></a><a id="id2880353"
- class="indexterm" name="id2880353"></a><a id="id2880362"
- class="indexterm" name="id2880362"></a><a id="id2880372"
- class="indexterm" name="id2880372"></a><a id="id2880382"
- class="indexterm" name="id2880382"></a><a id="id2880389"
- class="indexterm" name="id2880389"></a><a id="id2880397"
- class="indexterm" name="id2880397"></a>. In practice, TeX
- fonts contain a little bit more information than simply the
- size of each character. Generally, they contain ligature
- and kerning information as well.</p>
-
- <p><span class="emphasis"><em>Ligatures</em></span><a
- id="id2880416" class="indexterm" name="id2880416"></a> are
- a typographic convention for replacing some letter
- combinations with single symbols. In English, this is done
- solely to improve the appearance of the letter
- combinations. Figure&#160;<a href="ch05.html#fig.filig"
- title="Figure&#160;5.1.&#160;fi as two characters and as a ligature">
- Figure&#160;5.1</a> shows a common ligature in English,
- &#8220;fi.&#8221; Other common ligatures in English are
- &#8220;ff&#8221;, &#8220;fl&#8221;, and the combinations
- &#8220;ffi&#8221; and &#8220;ffl.&#8221; Other languages
- have different ligatures.</p>
-
- <div class="figure">
- <a id="fig.filig" name="fig.filig"></a>
-
- <p class="title">
- <b>Figure&#160;5.1.&#160;&#8220;fi&#8221; as two
- characters and as a ligature</b></p>
-
- <div class="mediaobject">
- <img src="fi-ligs.eps" />
- </div>
- </div>
-
- <p><span class="emphasis"><em>Kerning</em></span><a
- id="id2880500" class="indexterm" name="id2880500"></a> is
- the process of adding or removing small amounts of space
- between characters to improve the appearance of particular
- letter combinations. Although every character has a natural
- width, some combinations of characters give the illusion of
- too much or too little space. Figure&#160;<a
- href="ch05.html#fig.kerning"
- title="Figure&#160;5.2.&#160;We unkerned and kerned">Figure&#160;5.2</a>
- shows a common example in the word &#8220;We.&#8221;</p>
-
- <div class="figure">
- <a id="fig.kerning" name="fig.kerning"></a>
-
- <p class="title">
- <b>Figure&#160;5.2.&#160;&#8220;We&#8221; unkerned and
- kerned</b></p>
-
- <div class="mediaobject">
- <img src="we-we.eps" />
- </div>
- </div>
-
- <p>This is all the information that TeX needs, and it is
- all that is contained in the <tt>TFM</tt> files that TeX
- uses.<sup>[<a id="id2880575" name="id2880575"
- href="#ftn.id2880575">55</a>]</sup></p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2880659"
- name="id2880659"></a>Selecting a Font in TeX</h3>
- </div>
- </div>
-
- <p>TeX's macro language includes a \font primitive for
- loading a font<a id="id2880668" class="indexterm"
- name="id2880668"></a><a id="id2880678" class="indexterm"
- name="id2880678"></a><a id="id2880691" class="indexterm"
- name="id2880691"></a>. This primitive operation
- associates a control sequence<a id="id2880701"
- class="indexterm" name="id2880701"></a> with the metrics
- in a particular <tt>TFM</tt> file. For example, the
- following line associates the control sequence \tinyfont
- with the metrics in <tt>cmr5.tfm</tt> (the Computer
- Modern Roman 5pt font):</p>
-<pre class="screen">
-\font\tinyfont=cmr5
-</pre>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>Remember, only letters can appear in a TeX control
- sequence. You cannot say \font\cmr5=cmr5 because \cmr5
- is not a valid control sequence.</p>
- </div>
-
- <p>The control sequence defined with \font can
- subsequently be used to change the current font. After
- the above command, \tinyfont in your document selects the
- Computer Modern Roman 5pt font as the current font.</p>
-
- <p>In practice, using the primitive operations to select
- fonts has a number of disadvantages. Later in this
- chapter, the worst of these disadvantages is described
- and a better alternative is offered. For simplicity, the
- primitive operations are used in most of the examples in
- this chapter.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2880773"
- name="id2880773"></a>Which Character Is Which?</h3>
- </div>
- </div>
-
- <p>How does TeX know which character<a id="id2880782"
- class="indexterm" name="id2880782"></a> to use when it
- reads a symbol from an input file? The answer is simple:
- TeX considers each font to be an array of characters. It
- uses the numeric ASCII<a id="id2880794" class="indexterm"
- name="id2880794"></a> code of each character to determine
- what element in the array to use.<sup>[<a id="id2880810"
- name="id2880810" href="#ftn.id2880810">56</a>]</sup> This
- is a reasonable and efficient scheme as long as the ASCII
- values of the characters in your input file are the same
- as the metric information that TeX is using.</p>
-
- <p>The section called &#8220;<a
- href="ch05.html#sec.fonts.encodingvec"
- title="Declaring a family">the section called
- &#8220;Declaring a family&#8221;</a>&#8221; in this
- chapter describes how the ordering of characters in a
- font is determined. It also discusses some of the
- problems that can arise when TeX and your printer have
- conflicting information about the arrangement of
- characters in the font. The &#8220;<a
- href="ch05.html#sec.fonts.virtualfonts"
- title="Virtual Fonts">the section called &#8220;Virtual
- Fonts&#8221;</a>&#8221; section describes the TeX
- mechanism for constructing fonts with different
- arrangements of characters.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2880909"
- name="id2880909"></a>The Issue of Size</h2>
- </div>
- </div>
-
- <p>In the purest sense, selecting a font determines only
- what shape<a id="id2880917" class="indexterm"
- name="id2880917"></a><a id="id2880921" class="indexterm"
- name="id2880921"></a> each character will have; it does not
- determine the size<a id="id2880932" class="indexterm"
- name="id2880932"></a><a id="id2880939" class="indexterm"
- name="id2880939"></a> of the font. Unfortunately in
- practice, the issue of shape and size cannot be separated.
- The same shapes <span
- class="emphasis"><em>appear</em></span> to be different at
- different sizes. <span class="emphasis"><em>Optical
- scaling</em></span><a id="id2880960" class="indexterm"
- name="id2880960"></a><a id="id2880967" class="indexterm"
- name="id2880967"></a> uses different designs to make
- letters at different sizes appear to have the same shape.
- Conversly, linear scaling<a id="id2880980"
- class="indexterm" name="id2880980"></a><a id="id2880987"
- class="indexterm" name="id2880987"></a> produces characters
- with exactly the same shape at different sizes, although
- they appear slightly different.</p>
-
- <p>Because the size of an object affects the way that the
- human eye and the brain perceive its shape, a simple linear
- scaling of each character does not produce the most
- aesthetically pleasing results. To overcome this problem,
- TeX uses two different quantities to express the notion of
- size: design size and magnification.</p>
-
- <p><span class="emphasis"><em>Design size</em></span><a
- id="id2881047" class="indexterm" name="id2881047"></a>
- addresses the issue of perception: a font looks most like
- the way it was designed to appear when printed at or close
- to its design size. Furthermore, two fonts with different
- design sizes (say 8pt and 12pt) that are the same typeface
- should <span class="emphasis"><em>appear</em></span>
- identical when printed at 8pt and 12pt, respectively, even
- though the actual shapes may be slightly different. The
- design size of a font is intrinsic to the font itself and
- cannot be changed or influenced by TeX. It is important
- because it has a direct impact on the aesthetics of the
- typeset page.</p>
-
- <p><span class="emphasis"><em>Magnification</em></span><a
- id="id2881075" class="indexterm" name="id2881075"></a>
- addresses the notion of linear scaling. Changing
- magnifications changes the size of each character without
- altering its actual shape. Although, as noted above,
- changing its size may change its <span
- class="emphasis"><em>apparent</em></span> shape. In
- general, you should print fonts as close to their design
- size as possible---in other words, with a magnifcation as
- close to 1.0 as possible. Figure&#160;<a
- href="ch05.html#fig.Rs"
- title="Figure&#160;5.3.&#160;The Computer Modern Roman letter R at 150pt: (a) from a 5pt design; (b) from a 17pt design">
- Figure&#160;5.3</a> demonstrates how different characters
- may look when printed at very large magnifications.</p>
-
- <div class="figure">
- <a id="fig.Rs" name="fig.Rs"></a>
-
- <p class="title"><b>Figure&#160;5.3.&#160;The Computer
- Modern Roman letter &#8220;R&#8221; at 150pt: (a) from a
- 5pt design; (b) from a 17pt design</b></p>
-
- <div class="mediaobject">
- <img src="two-rs.eps" />
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.gettingtfms"
- name="sec.gettingtfms"></a>Expressing Design Size in
- TeX</h3>
- </div>
- </div>
-
- <p>The design size<a id="id2881175" class="indexterm"
- name="id2881175"></a> of a font is an integral part of
- the <tt>TFM</tt> file (because it is intrinsic to the
- font that the <tt>TFM</tt> file<a id="id2881207"
- class="indexterm" name="id2881207"></a> describes). In
- order to select a different design size, you must select
- a different <tt>TFM</tt> file. For example, the Computer
- Modern Roman font is usually distributed at eight design
- sizes: 5, 6, 7, 8, 9, 10, 12, and 17 points. Metrics for
- these sizes are stored in the <tt>TFM</tt> files
- <tt>cmr5.tfm</tt>, <tt>cmr6.tfm</tt>, <tt>cmr7.tfm</tt>,
- $&#8230;$, and <tt>cmr17.tfm</tt>.</p>
-
- <p>Every font that you select has a specific design size,
- even though you may elect to use the font at another
- size.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2881284"
- name="id2881284"></a>Expressing Magnification in
- TeX</h3>
- </div>
- </div>
-
- <p>Magnification<a id="id2881294" class="indexterm"
- name="id2881294"></a> can be expressed either implicitly
- or explicitly in TeX. Implicitly, magnification can be
- expressed by selecting a particular font <tt>at</tt> a
- particular size. For example, the following line defines
- the control sequence \big to be the Computer Modern Roman
- 10pt font <tt>at</tt> a size of 12pt (an implicit
- magnification of 120\%):</p>
-<pre class="screen">
-\font\big=cmr10 at 12pt
-</pre>
-
- <p>Explicit magnification is selected by requesting a
- font <tt>scaled</tt> to a particular extent. For example,
- the following line defines the control sequence \bigger
- to be the Computer Modern Roman 10pt font at a
- magnification of 144\% (in other words, at 14.4pt):</p>
-<pre class="screen">
-\font\bigger=cmr10 scaled 1440
-</pre>
-
- <p>As you can see, TeX expects the <tt>scaled</tt>
- magnification to be ten times the percentage of
- magnification. The magnification that you request must be
- an integer (you can't say <tt>scaled 1440.4</tt>).
- Multiplying the magnification by 10 allows TeX to accept
- fractional percentages like 104.5\%.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2881380"
- name="id2881380"></a>Standard Magnifications</h3>
- </div>
- </div>
-
- <p>TeX provides seven standard magnifications. There are
- several good reasons to use these magnifications whenever
- possible. The most important is that most TeX systems can
- easily print fonts at these sizes. As described later in
- the section &#8220;<a href="ch08.html#sec.printing"
- title="Printing Fonts">the section called &#8220;Printing
- Fonts&#8221;</a>,&#8221; TeX's ability to select any font
- at any magnification does not guarantee that it can be
- printed at that size. By using standard sizes, you
- increase the likelihood that your document will be
- printable on your system and on other TeX systems (if
- portability is an issue). Using standard sizes will also
- give consistency to your documents. If you write many
- documents separately that may eventually be collected
- together (as a collection of short stories or a series of
- technical reports, for example), the internal consistency
- of sizes will make them appear more uniform. Finally, the
- standard sizes have aesthetic characteristics as well.
- Each size is 1.2 times the preceding size. The geometric
- relationship between the sizes is designed to make them
- appear pleasing when mixed together.</p>
-
- <p>The standard sizes can be selected with the \magstep
- control sequence. The standard sizes (or steps) are
- called <span class="emphasis"><em>magsteps</em></span> in
- TeX jargon. The natural size of a font is its \magstep0
- size. The \magstep1 size is 20\% larger. And \magstep2 is
- 20\% larger than that (44\% larger than the original
- design), etc. To select the Computer Modern Roman 10pt
- font at its next largest standard size, use:</p>
-<pre class="screen">
-\font\larger=cmr10 scaled\magstep1
-</pre>
-
- <p>For those occasions when you want a font that is only
- a little bit larger, TeX includes the control sequence
- \magstephalf which is halfway between \magstep0 and
- \magstep1.</p>
-
- <p>Most TeX formats that are based upon Plain TeX define
- seven magsteps: \magstep0, \magstephalf, and \magstep1
- through \magstep5.</p>
-
- <p>By using different design sizes and different standard
- magnifications, you gain access to a very wide range of
- sizes. For example, given the seven standard design sizes
- and seven standard magsteps, it is possible to print
- Computer Modern Roman at any of the following sizes (all
- sizes are in points):</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>5</td>
-
- <td>7.67</td>
-
- <td>9.6</td>
-
- <td>10.95</td>
-
- <td>13.15</td>
-
- <td>16.59</td>
-
- <td>19.91</td>
-
- <td>29.38</td>
- </tr>
-
- <tr>
- <td>5.48</td>
-
- <td>8</td>
-
- <td>9.86</td>
-
- <td>11.52</td>
-
- <td>13.82</td>
-
- <td>17</td>
-
- <td>20.4</td>
-
- <td>29.86</td>
- </tr>
-
- <tr>
- <td>6</td>
-
- <td>8.4</td>
-
- <td>10</td>
-
- <td>12</td>
-
- <td>14.4</td>
-
- <td>17.28</td>
-
- <td>20.74</td>
-
- <td>35.25</td>
- </tr>
-
- <tr>
- <td>6.57</td>
-
- <td>8.64</td>
-
- <td>10.08</td>
-
- <td>12.1</td>
-
- <td>14.52</td>
-
- <td>17.42</td>
-
- <td>22.39</td>
-
- <td>42.3</td>
- </tr>
-
- <tr>
- <td>7</td>
-
- <td>8.76</td>
-
- <td>10.37</td>
-
- <td>12.44</td>
-
- <td>14.93</td>
-
- <td>18.62</td>
-
- <td>24.48</td>
-
- <td>7.2</td>
- </tr>
-
- <tr>
- <td>9</td>
-
- <td>10.8</td>
-
- <td>12.96</td>
-
- <td>15.55</td>
-
- <td>18.66</td>
-
- <td>24.88</td>
-
- <td>&#160;</td>
-
- <td>&#160;</td>
- </tr>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2881671"
- name="id2881671"></a>Where Do TFM Files Come
- From?</h3>
- </div>
- </div>
-
- <p>In order to use <span
- class="emphasis"><em>any</em></span> font in TeX, you
- must have a <tt>TFM</tt> file for it. How you can acquire
- <tt>TFM</tt> files<a id="id2881705" class="indexterm"
- name="id2881705"></a> for the fonts you use depends on
- the kinds of fonts and where they were developed. The
- following list offers suggestions for the most commonly
- used fonts:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">PostScript fonts</span></dt>
-
- <dd>
- <p>Every vendor that supplies PostScript fonts<a
- id="id2881738" class="indexterm"
- name="id2881738"></a><a id="id2881748"
- class="indexterm" name="id2881748"></a> (either as
- font files or built-in to a printer or cartridge)
- should also supply Adobe Font Metric (<tt>AFM</tt>)
- files. <tt>AFM</tt> files provide complete metric
- information about the fonts.<sup>[<a id="id2881782"
- name="id2881782"
- href="#ftn.id2881782">57</a>]</sup> The
- <tt>AFM</tt> files can be converted into
- <tt>TFM</tt> files with the <b>afm2tfm</b> utility
- distributed with <b>dvips</b>.</p>
- </dd>
-
- <dt><span class="term">LaserJet built-in
- fonts</span></dt>
-
- <dd>
- <p>The complete metric information for LaserJet
- built-in fonts<a id="id2881868" class="indexterm"
- name="id2881868"></a> is supplied by
- Hewlett-Packard in &#8220;Tagged Font Metric&#8221;
- files. These are available directly from
- Hewlett-Packard (unfortunately, they are not
- distributed with the printers). The Tagged Font
- Metrics can be converted into TeX <tt>TFM</tt>
- files with <b>hptfm2pl</b>, a free utility written
- by, well, me, actually.</p>
-
- <p>A collection of <tt>TFM</tt> files for the
- standard built-in fonts on the LaserJet III and IV
- printers is available in the CTAN archives in
- <tt>/tex-archive/fonts/ljmetrics</tt>.</p>
- </dd>
-
- <dt><span class="term">LaserJet softfonts</span></dt>
-
- <dd>
- <p>Bitmapped LaserJet softfonts<a id="id2881950"
- class="indexterm" name="id2881950"></a> can be
- converted into TeX fonts with the <b>SFPtoPK</b><a
- id="id2881968" class="indexterm"
- name="id2881968"></a> utility. The resulting font
- includes both TeX <tt>PK</tt> and <tt>TFM</tt>
- files.</p>
-
- <p>Scalable LaserJet softfonts should be
- distributed with Hewlett-Packard Tagged Font Metric
- files. These can be converted into TeX <tt>TFM</tt>
- files with the free utility <b>hptfm2pl</b><a
- id="id2882018" class="indexterm"
- name="id2882018"></a>.</p>
- </dd>
-
- <dt><span class="term">TeX fonts
- (<span>MetaFont</span>)</span></dt>
-
- <dd>
- <p>The MetaFont<a id="id2882052" class="indexterm"
- name="id2882052"></a> program renders TeX
- <tt>MF</tt> files<a id="id2882076"
- class="indexterm" name="id2882076"></a> and
- produces a <tt>TFM</tt> file. Usually it produces a
- <tt>GF</tt> file<a id="id2882115" class="indexterm"
- name="id2882115"></a> as well, but the special mode
- <span class="emphasis"><em>tfmonly</em></span> can
- be used to create just the <tt>TFM</tt>
- file.<sup>[<a id="id2882138" name="id2882138"
- href="#ftn.id2882138">58</a>]</sup> MetaFont modes
- and other aspects of font creation with MetaFont
- are described in Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>,
- <span class="emphasis"><em><a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a></em></span>.</p>
- </dd>
-
- <dt><span class="term">TrueType fonts</span></dt>
-
- <dd>
- <p>Incomplete metrics are frequently<a
- id="id2882219" class="indexterm"
- name="id2882219"></a> distributed in the form of
- Windows' <tt>PFM</tt> files<a id="id2882240"
- class="indexterm" name="id2882240"></a>. Some
- commercial previewers for Windows can extract
- metric information and build a <tt>TFM</tt> file.
- However, at present, I do not know of any free
- utilities which can build TeX metrics from TrueType
- fonts.</p>
- </dd>
- </dl>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="sec.nfss2"
- name="sec.nfss2"></a>The New Font Selection Scheme</h2>
- </div>
- </div>
-
- <p>The New Font Selection Scheme<a id="id2882292"
- class="indexterm" name="id2882292"></a> is a method for
- selecting fonts in Plain TeX and LaTeX. It was introduced
- briefly in the section &#8220;<a
- href="ch04.html#macpack.sec.latexvslatexe"
- title="Installation: Making Format Files">the section
- called &#8220;Installation: Making Format
- Files&#8221;</a>&#8221; of Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.
- This section describes release two of the New Font
- Selection Scheme (known as the NFSS2)<a id="id2882340"
- class="indexterm" name="id2882340"></a> as it exists in the
- LaTeX2e format. Because version one<a id="id2882349"
- class="indexterm" name="id2882349"></a> is now obsolete, it
- is not described.</p>
-
- <p>The NFSS defines a method of font selection used in
- place of TeX's primitive \font command. The problem with
- font selection using \font is that it ties a control
- sequence to a particular font at a particular size, which
- has unpleasant consequences when more than one font is used
- in a document. Consider the definition \font\it=cmti10.
- This associates the control sequence \it with the italic
- Computer Modern font (at 10pt). After this definition, a
- sentence like:</p>
-<pre class="screen">
-This requires <span class="emphasis"><em>emphasis</em></span>.
-</pre>
-
- <p>has the desired result, if Computer Modern Roman at 10pt
- is the font in use when \it is encountered:</p>
-<pre class="screen">
-\fontfamily{cmr}\selectfont
-This requires <span class="emphasis"><em>emphasis</em></span>.
-</pre>
-
- <p>If you are using some other font, perhaps in a chapter
- heading, you get:</p>
-<pre class="screen">
-\fontfamily{cmr}\fontseries{bx}\fontsize{14}{16pt}\selectfont
-This requires {\fontfamily{cmr}\fontseries{m}\fontsize{10}{12pt}\selectfont
-\it emphasis}.
-</pre>
-
- <p>This is almost certainly not what you wanted. The NFSS
- overcomes this difficulty by describing each font with five
- independent parameters: encoding, family, series, shape,
- and size.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">Font encoding</span></dt>
-
- <dd>
- <p>The encoding<a id="id2882449" class="indexterm"
- name="id2882449"></a> parameter identifies the
- encoding vector of the font. Encoding vectors play an
- important role in the selection of characters in a
- font. Encoding vectors are described more thoroughly
- later in this chapter. TeX Text, TeX Math Italic, and
- Adobe Standard are all <span
- class="emphasis"><em>encoding vectors</em></span><a
- id="id2882461" class="indexterm"
- name="id2882461"></a>.</p>
- </dd>
-
- <dt><span class="term">Font family</span></dt>
-
- <dd>
- <p>The family parameter describes the typeface of the
- font<a id="id2882492" class="indexterm"
- name="id2882492"></a>. Computer Modern, Times Roman,
- Helvetica, Galliard, and Gill Sans are all <span
- class="emphasis"><em>families</em></span>.</p>
- </dd>
-
- <dt><span class="term">Font series</span></dt>
-
- <dd>
- <p>Font series<a id="id2882523" class="indexterm"
- name="id2882523"></a> describes the joint notions of
- weight and width. Weight<a id="id2882533"
- class="indexterm" name="id2882533"></a> is a measure
- of how darkly each character is printed, and width<a
- id="id2882543" class="indexterm"
- name="id2882543"></a> is a measure of how wide or
- narrow the font is. Standard abbreviations for weight
- and width are shown in Table&#160;<a
- href="ch05.html#tab.fontshapeww"
- title="Table&#160;5.1.&#160;Standard Weight and Width Designations ">
- Table&#160;5.1</a>. Normal, bold-compressed,
- extrabold-ultraexpanded, and light-medium are all
- examples of font <span
- class="emphasis"><em>series</em></span>.</p>
-
- <div class="table">
- <a id="tab.fontshapeww" name="tab.fontshapeww"></a>
-
- <p class="title"><b>Table&#160;5.1.&#160;Standard
- Weight and Width Designations</b></p>
-
- <table
- summary="Standard Weight and Width Designations "
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\rm\bf Abbr</th>
-
- <th align="left">\bf Weight</th>
-
- <th align="left">\rm\bf Abbr</th>
-
- <th align="left">\bf Width</th>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">ul</td>
-
- <td align="left">Ultra-light</td>
-
- <td align="left">uc</td>
-
- <td align="left">Ultra-condensed</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">el</td>
-
- <td align="left">Extra-light</td>
-
- <td align="left">ec</td>
-
- <td align="left">Extra-condensed</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">l</td>
-
- <td align="left">Light</td>
-
- <td align="left">c</td>
-
- <td align="left">Condensed</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">sl</td>
-
- <td align="left">Semi-light</td>
-
- <td align="left">sc</td>
-
- <td align="left">Semi-condensed</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">m</td>
-
- <td align="left">Medium (normal)</td>
-
- <td align="left">m</td>
-
- <td align="left">Medium</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">sb</td>
-
- <td align="left">Semi-bold</td>
-
- <td align="left">sx</td>
-
- <td align="left">Semi-expanded</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">b</td>
-
- <td align="left">Bold</td>
-
- <td align="left">x</td>
-
- <td align="left">Expanded</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">eb</td>
-
- <td align="left">Extra-bold</td>
-
- <td align="left">ex</td>
-
- <td align="left">Extra-expanded</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">ub</td>
-
- <td align="left">Ultra-bold</td>
-
- <td align="left">ux</td>
-
- <td align="left">Ultra-expanded</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>The general rule for combining weight and width to
- form a series abbreviation is to use the abbreviation
- for weight followed by the abbreviation for width,
- unless one is &#8220;medium,&#8221; in which case it
- is left out. Table&#160;<a
- href="ch05.html#tab.fontshapeex"
- title="Table&#160;5.2.&#160;Weight and Width Are Combined to Form Series ">
- Table&#160;5.2</a> shows how several weight/width
- combinations are used to form the series. The series
- designation for a light-medium font demonstrates that
- a single medium attribute is omitted. If both the
- width and weight are medium, use a single
- &#8220;m&#8221; for the series.</p>
-
- <div class="table">
- <a id="tab.fontshapeex" name="tab.fontshapeex"></a>
-
- <p class="title"><b>Table&#160;5.2.&#160;Weight and
- Width Are Combined to Form Series</b></p>
-
- <table
- summary="Weight and Width Are Combined to Form Series "
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Weight and Width</th>
-
- <th align="left">\bf Series</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">Bold extended</td>
-
- <td align="left">bx</td>
- </tr>
-
- <tr>
- <td align="left">Light medium</td>
-
- <td align="left">l</td>
- </tr>
-
- <tr>
- <td align="left">Medium extra-expanded</td>
-
- <td align="left">ex</td>
- </tr>
-
- <tr>
- <td align="left">Light extra-expanded</td>
-
- <td align="left">lex</td>
- </tr>
-
- <tr>
- <td align="left">Normal (medium, medium)</td>
-
- <td align="left">m</td>
- </tr>
- </tbody>
- </table>
- </div>
- </dd>
-
- <dt><span class="term">Font shape</span></dt>
-
- <dd>
- <p>The shape<a id="id2883001" class="indexterm"
- name="id2883001"></a>, in conjunction with series,
- defines the appearance of the font. Shape generally
- refers to the style of the face. Bold, italic,
- slanted, and outline are all examples of font
- shape.</p>
-
- <p>The standard designations of font shape are shown
- in Table&#160;<a href="ch05.html#tab.fontshapeshape"
- title="Table&#160;5.3.&#160;Standard Abbreviations of Font Shape">
- Table&#160;5.3</a>.</p>
-
- <div class="table">
- <a id="tab.fontshapeshape"
- name="tab.fontshapeshape"></a>
-
- <p class="title"><b>Table&#160;5.3.&#160;Standard
- Abbreviations of Font Shape</b></p>
-
- <table
- summary="Standard Abbreviations of Font Shape"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\rm\bf Abbr.</th>
-
- <th align="left">\bf Shape</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">n</td>
-
- <td align="left">Normal</td>
- </tr>
-
- <tr>
- <td align="left">it</td>
-
- <td align="left">Italic</td>
- </tr>
-
- <tr>
- <td align="left">sl</td>
-
- <td align="left">Slanted</td>
- </tr>
-
- <tr>
- <td align="left">sc</td>
-
- <td align="left">Small caps</td>
- </tr>
-
- <tr>
- <td align="left">u</td>
-
- <td align="left">Upright italics</td>
- </tr>
- </tbody>
- </table>
- </div>
- </dd>
-
- <dt><span class="term">Font size</span></dt>
-
- <dd>
- <p>Font size<a id="id2883162" class="indexterm"
- name="id2883162"></a> defines both the size of the
- characters and the spacing between lines of text in
- that size. The distinction between design size and
- magnification, discussed at length in the first part
- of this chapter, is hidden within the NFSS; you need
- only select the size you want.<sup>[<a id="id2883176"
- name="id2883176"
- href="#ftn.id2883176">59</a>]</sup></p>
-
- <p>The spacing between lines of text is described as
- the (vertical) distance between the baselines of two
- consecutive lines of type. It is usually about 20\%
- larger than the size of the font. For example, a 10pt
- font is usually printed with 12pts between the
- baselines of consecutive lines. The inter-line
- distance that looks best depends on the font and
- other design elements of the document. There really
- isn't a good rule for the value that looks best,
- which is why you have to specify it.</p>
- </dd>
- </dl>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.fonts.defnfss2"
- name="sec.fonts.defnfss2"></a>Selecting Fonts with
- the New Font Selection Scheme</h3>
- </div>
- </div>
-
- <p>One of the most visible differences in the NFSS2 is
- that you are encouraged to change the way you select<a
- id="id2883229" class="indexterm" name="id2883229"></a>
- fonts. The NFSS2 defines nine control sequences<a
- id="id2883241" class="indexterm" name="id2883241"></a>
- for user-level font selection. They are shown in
- Table&#160;<a href="ch05.html#tab.nfss2.userlevel"
- title="Table&#160;5.4.&#160;User-level Font Selection Control Sequences in NFSS2 ">
- Table&#160;5.4</a>.</p>
-
- <div class="table">
- <a id="tab.nfss2.userlevel"
- name="tab.nfss2.userlevel"></a>
-
- <p class="title"><b>Table&#160;5.4.&#160;User-level
- Font Selection Control Sequences in NFSS2</b></p>
-
- <table
- summary="User-level Font Selection Control Sequences in NFSS2 "
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Control Sequence</th>
-
- <th align="left">\bf Resulting Change</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\textrm\verb|{}|</td>
-
- <td align="left">Switch to roman family</td>
- </tr>
-
- <tr>
- <td align="left">\textsf\verb|{}|</td>
-
- <td align="left">Switch to sans-serif family</td>
- </tr>
-
- <tr>
- <td align="left">\texttt\verb|{}|</td>
-
- <td align="left">Switch to typewriter family</td>
- </tr>
-
- <tr>
- <td align="left">\textbf\verb|{}|</td>
-
- <td align="left">Switch to bold face
- weight/width</td>
- </tr>
-
- <tr>
- <td align="left">\textmedium\verb|{}|</td>
-
- <td align="left">Switch to medium
- weight/width</td>
- </tr>
-
- <tr>
- <td align="left">\textit\verb|{}|</td>
-
- <td align="left">Switch to italic shape</td>
- </tr>
-
- <tr>
- <td align="left">\textsl\verb|{}|</td>
-
- <td align="left">Switch to slanted shape</td>
- </tr>
-
- <tr>
- <td align="left">\textsc\verb|{}|</td>
-
- <td align="left">Switch to small-caps shape</td>
- </tr>
-
- <tr>
- <td align="left">\emph\verb|{}|</td>
-
- <td align="left">Switch to emphasized text</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>Instead of using \it, for example, to change to an
- italic font within a group, you should use the \textit
- command with the text as an argument. For example,
- instead of using:</p>
-<pre class="screen">
-This is some <span class="emphasis"><em>italic</em></span> text.
-</pre>
-
- <p>you should use:</p>
-<pre class="screen">
-This is some <span class="emphasis"><em>italic</em></span> text.
-</pre>
-
- <p>The advantage of the new scheme is that these macros
- are much more intelligent than the old ones. Notice that
- I did not specify italic correction () in the second
- case. This is because the \textit macro is able to
- determine if the correction is necessary, and if so,
- inserts it automatically.\ff{If you wish to suppress
- italic correction, use \cs{nocorr} at the end (or
- beginning) of the text.} The macros can also be
- nested.</p>
-
- <p>The NFSS2 allows you to use the old font selection
- macros, so existing documents will not be affected. If
- you want to set several paragraphs in a different font,
- you should continue to use the old selection macros
- because you cannot pass more than one paragraph of text
- to a macro.\ff[2]{It is possible to write macros that
- accept multiple paragraphs of text, but the NFSS2 font
- selection macros do not do so.}</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2883502"
- name="id2883502"></a>Low-level interface to
- NFSS</h4>
- </div>
- </div>
-
- <p>The user-level font selection commands are
- implemented in terms of six low-level commands. At this
- level, you must specify the encoding, family, series,
- shape, and size of the font in order to select it.
- There are six control sequences for selecting a font:
- one each for specifying the font parameters and one for
- actually switching to the new font. This strategy
- allows the parameters to be independent; any parameters
- that you do not explicitly change remain the same as
- the current font.</p>
-
- <p>These six control sequences are:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span
- class="term">\fontencoding{<i><tt>enc</tt></i>}</span></dt>
-
- <dd>
- <p>Selects the encoding scheme
- \textit<tt>enc</tt><a id="id2883556"
- class="indexterm" name="id2883556"></a>. The
- encoding schemes officially supported by the
- NFSS2 are shown in Table&#160;<a
- href="ch05.html#tab.nfss2.encoding"
- title="Table&#160;5.5.&#160;Encoding Schemes Supported by NFSS2">
- Table&#160;5.5</a>.</p>
-
- <div class="table">
- <a id="tab.nfss2.encoding"
- name="tab.nfss2.encoding"></a>
-
- <p class="title">
- <b>Table&#160;5.5.&#160;Encoding Schemes
- Supported by NFSS2</b></p>
-
- <table
- summary="Encoding Schemes Supported by NFSS2"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Encoding</th>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\bf Scheme</td>
-
- <td align="left">\bf Encoding Name</td>
- </tr>
-
- <tr>
- <td align="left">T1</td>
-
- <td align="left">TeX text Cork
- encoding</td>
- </tr>
-
- <tr>
- <td align="left">OT1</td>
-
- <td align="left">Old TeX text encoding
- (the CMR encoding)</td>
- </tr>
-
- <tr>
- <td align="left">OT2</td>
-
- <td align="left">University of Washington
- Cyrillic encoding</td>
- </tr>
-
- <tr>
- <td align="left">OT3</td>
-
- <td align="left">University of Washington
- IPA encoding</td>
- </tr>
-
- <tr>
- <td align="left">OML</td>
-
- <td align="left">TeX math (italic)
- letters</td>
- </tr>
-
- <tr>
- <td align="left">OMS</td>
-
- <td align="left">TeX math symbols</td>
- </tr>
-
- <tr>
- <td align="left">OMX</td>
-
- <td align="left">TeX math extended</td>
- </tr>
-
- <tr>
- <td align="left">U</td>
-
- <td align="left">Unknown encoding</td>
- </tr>
- </tbody>
- </table>
- </div>
- </dd>
-
- <dt><span
- class="term">\fontfamily{<i><tt>fam</tt></i>}</span></dt>
-
- <dd>
- <p>Selects the family \textit<tt>fam</tt>.</p>
- </dd>
-
- <dt><span
- class="term">\fontseries{<i><tt>ser</tt></i>}</span></dt>
-
- <dd>
- <p>Selects the series \textit<tt>ser</tt>.</p>
- </dd>
-
- <dt><span
- class="term">\fontshape{<i><tt>shp</tt></i>}</span></dt>
-
- <dd>
- <p>Selects the shape \textit<tt>shp</tt>.</p>
- </dd>
-
- <dt><span
- class="term">\fontsize{<i><tt>ptsize</tt></i>}{<i><tt>
- bskip</tt></i>}</span></dt>
-
- <dd>
- <p>Selects the font size \textit<tt>ptsize</tt>
- with a distance of \textit<tt>bskip</tt> between
- lines. Note that \textit<tt>ptsize</tt> is a
- simple number, whereas \textit<tt>bskip</tt> is a
- TeX distance and you must specify units after the
- number. Under the NFSS2, \textit<tt>ptsize</tt>
- specifies the <span
- class="emphasis"><em>actual</em></span> size of
- the font,\ff{Under the NFSS1, the
- \textit{\texttt{ptsize}} was simply a label; the
- actual font loaded was the nearest magstep.} but
- the NFSS2 will attempt to find a closest match if
- there is no exact match for the requested size. A
- warning message is issued if the size does not
- exist and a closest match has to be selected. You
- can control the sensitivity of the warning with
- the \fontsubfuzz parameter. It is initially set
- to 0.4pt, meaning that any font within 0.4pt of
- the requested size will be used without issuing a
- warning.</p>
- </dd>
-
- <dt><span class="term">\selectfont</span></dt>
-
- <dd>
- <p>Switches to the font described by the current
- values of encoding, family, series, shape, and
- size.</p>
- </dd>
- </dl>
- </div>
-
- <p>From this description, can you figure out how the
- control sequence <span
- class="emphasis"><em>could</em></span> be defined under
- the NFSS? See this footnote<sup>[<a id="id2855832"
- name="id2855832" href="#ftn.id2855832">60</a>]</sup>
- for the answer.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2855857"
- name="id2855857"></a>Defining Fonts with NFSS2</h3>
- </div>
- </div>
-
- <p>The standard Computer Modern fonts and most PostScript
- fonts can be selected by using the appropriate style
- files or inputting the appropriate macros. However, if
- you have nonstandard fonts or fonts for some other
- device, you can easily add them to the NFSS<a
- id="id2855870" class="indexterm"
- name="id2855870"></a>.</p>
-
- <p>The internal interface to the NFSS has been entirely
- redesigned. The new interface is much cleaner than the
- interface to the NFSS1, but similar in design.</p>
-
- <p>If you are not very familiar with TeX, what follows
- may be a bit confusing; treat this example as a sort of
- &#8220;cookbook recipe&#8221; and substitute the font you
- wish to define for the <tt>logo</tt> font (the
- <tt>logo</tt> font is the typeface used for the MetaFont
- logo).</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.fonts.encodingvec"
- name="sec.fonts.encodingvec"></a>Declaring a
- family</h4>
- </div>
- </div>
-
- <p>In order to add a new typeface, you must declare a
- new font family<a id="id2855932" class="indexterm"
- name="id2855932"></a> with the control sequence
- \DeclareFontFamily. If you are only adding new sizes or
- shapes to an existing family, do not redeclare the
- family.</p>
-
- <p>The parameters to \DeclareFontFamily are the
- encoding, name, and loading options for the family.
- Loading options are any commands that should be
- executed every time this family is selected. For most
- fonts, there are no loading options.<sup>[<a
- id="id2855948" name="id2855948"
- href="#ftn.id2855948">61</a>]</sup></p>
-
- <p>The following declaration creates the <span
- class="emphasis"><em>logo</em></span> family with the
- old TeX encoding and no loading options:</p>
-<pre class="screen">
-\DeclareFontFamily{OT1}{logo}{}
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2884256"
- name="id2884256"></a>Declaring shapes</h4>
- </div>
- </div>
-
- <p>After a family has been created, you must specify
- what font shapes<a id="id2884266" class="indexterm"
- name="id2884266"></a> are available with
- \DeclareFontShape. To make the font usable, you must
- declare at least one font shape for each family.</p>
-
- <p>The general form of a call to \DeclareFontShape
- is:</p>
-<pre class="screen">
-\DeclareFontShape{<i><tt>enc</tt></i>}
- {<i><tt>fam</tt></i>}
- {<i><tt>series</tt></i>}
- {<i><tt>shape</tt></i>}
- {<i><tt>sizes</tt></i>}
- {<i><tt>loading options</tt></i>}
-</pre>
-
- <p>The family <tt><i><tt>fam</tt></i></tt> (with the
- appropriate encoding <tt><i><tt>enc</tt></i></tt>) must
- already have been created with \DeclareFontFamily. The
- <tt><i><tt>series</tt></i></tt> and
- <tt><i><tt>shape</tt></i></tt> parameters identify the
- name of the series and shape. Table&#160;<a
- href="ch05.html#tab.fontshapeex"
- title="Table&#160;5.2.&#160;Weight and Width Are Combined to Form Series ">
- Table&#160;5.2</a> and Table&#160;<a
- href="ch05.html#tab.fontshapeshape"
- title="Table&#160;5.3.&#160;Standard Abbreviations of Font Shape">
- Table&#160;5.3</a> list some common series and shapes.
- The \textit<tt>sizes</tt> parameter is a list of <span
- class="emphasis"><em>font-shape
- declarations</em></span>, described below, and the
- \textit<tt>loading options</tt>, if specified, override
- the loading options for the font family.</p>
-
- <p>Each font-shape declaration indicates how the
- request for a font should be handled. The complete
- syntax for font-shape declarations is described in
- <span class="emphasis"><em>Interface Description of
- NFSS2</em></span>&#160;[<a
- href="bi01.html#nfss2interface">nfss2interface</a>].
- Here we look at three simple cases: substituting
- another font for the one requested, generating the name
- of the <tt>TFM</tt> file for the requested font, and
- identifying a particular <tt>TFM</tt> file for a size
- or range of sizes. Each of these techniques is used in
- the declaration of the medium, normal logo font in
- Example&#160;<a href="ch05.html#ex.logoshape"
- title="Example&#160;5.1.&#160;Font-shape Declaration with NFSS2">
- Example&#160;5.1</a>. There should be no extra spaces
- in the font size parameter. If you spread it over
- multiple lines in your input file, make sure that a
- comment character (\%) appears at the end of each
- line.</p>
-
- <div class="example">
- <a id="ex.logoshape" name="ex.logoshape"></a>
-
- <p class="title"><b>Example&#160;5.1.&#160;Font-shape
- Declaration with NFSS2</b></p>
-<pre class="screen">
-\DeclareFontShape{OT1}{logo}{m}{n}{
- &lt;-8&gt;sub * cmr/m/n
- &lt;8&gt;&lt;9&gt;&lt;10&gt;gen * logo
- &lt;10.95&gt;logo10 at 10.95pt
- &lt;12-&gt;logo10}{}
-</pre>
- </div>
-
- <p>Each font-shape declaration begins with one or more
- size<a id="id2884513" class="indexterm"
- name="id2884513"></a> specifications in angle brackets.
- This indicates either a specific size
- (<tt>&lt;10&gt;</tt> for a 10pt font) or a range of
- sizes (<tt>&lt;8-9&gt;</tt> for any size larger than or
- equal to 8pt and less than 9pt, <tt>&lt;-8&gt;</tt> for
- all sizes less than 8pt, or <tt>&lt;10-&gt;</tt> for
- all sizes larger than or equal to 10pt).</p>
-
- <p>In Example&#160;<a href="ch05.html#ex.logoshape"
- title="Example&#160;5.1.&#160;Font-shape Declaration with NFSS2">
- Example&#160;5.1</a>, the first font-shape declaration
- indicates that font substitution should be performed
- for any request at a size smaller than 8pt. The string
- <tt>cmr/m/n</tt> indicates that medium, normal,
- Computer Modern Roman should be substituted in its
- place. In general, the substitution specifies the
- <tt><i><tt>family</tt></i>/<i><tt>shape</tt></i>/<i><tt>
- series</tt></i></tt> to be substituted.</p>
-
- <p>The second declaration indicates that the name of
- the external font for 8pt, 9pt and 10pt fonts should be
- generated from the string <tt>logo</tt> and the size
- (at 8pt, <tt>logo8</tt> will be used; at 9pt,
- <tt>logo9</tt>; and at 10pt, <tt>logo10</tt>).</p>
-
- <p>The third declaration demonstrates that the font
- specified (<tt>{logo10 at 10.95pt}</tt>) can be any
- valid TeX font selection command. After special
- declarations have been processed (substitution,
- generation, etc.), the remaining declaration text is
- passed to the TeX \font primitive.</p>
-
- <p>The last declaration specifies that <span
- class="emphasis"><em>any</em></span> size larger than
- 12pt is valid. Any size larger than 12pt will use the
- font <tt>logo10</tt>, scaled appropriately. Automatic
- font generation, if it is being used, can take care of
- actually generating the font. Example&#160;<a
- href="ch05.html#ex.logoshape"
- title="Example&#160;5.1.&#160;Font-shape Declaration with NFSS2">
- Example&#160;5.1</a> was constructed to demonstrate
- several features of the font-shape declaration syntax.
- A simpler, more likely declaration for the medium
- normal logo font is shown in Example&#160;<a
- href="ch05.html#ex.logoshape2"
- title="Example&#160;5.2.&#160;Font-shape declaration with NFSS2 (simplified)">
- Example&#160;5.2</a>.</p>
-
- <div class="example">
- <a id="ex.logoshape2" name="ex.logoshape2"></a>
-
- <p class="title"><b>Example&#160;5.2.&#160;Font-shape
- declaration with NFSS2 (simplified)</b></p>
-<pre class="screen">
-\DeclareFontShape{OT1}{logo}{m}{n}{
- &lt;-8&gt;sub * cmr/m/n
- &lt;8-9&gt;logo8
- &lt;9-10&gt;logo9
- &lt;10-&gt;logo10}{}
-</pre>
- </div>
-
- <p>The 8pt design could have been scaled down for sizes
- less than 8pt, but you should try to avoid large
- deviations from the design size. Because the design for
- my book does not require the logo font at sizes less
- than 8pt, substitution was the best choice.<sup>[<a
- id="id2884721" name="id2884721"
- href="#ftn.id2884721">62</a>]</sup></p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2884733"
- name="id2884733"></a>Storing Font Definitions</h3>
- </div>
- </div>
-
- <p>The NFSS will load your font definitions automatically
- if you store them<a id="id2884743" class="indexterm"
- name="id2884743"></a> in <tt>FD</tt> files<a
- id="id2884764" class="indexterm" name="id2884764"></a> in
- a directory where TeX looks for input files. Whenever an
- unknown encoding/family is requested, NFSS attempts to
- load the file <tt>encfamily.fd</tt>. For example, if the
- font declarations described in the preceding sections are
- stored in a file called <tt>OT1logo.fd</tt>, nothing
- special has do be done to use the logo family. The first
- time the logo family is selected, the definitions will be
- read from <tt>OT1logo.fd</tt>.</p>
-
- <p>If you are using LaTeX2e (or LaTeX with the NFSS),
- there must already be a large number of <tt>FD</tt> files
- on your system. For more information about building the
- LaTeX2e format (which includes the NFSS2), consult the
- section &#8220;<a href="ch04.html#sec.buildlatexe"
- title="Building the LaTeX2e format">the section called
- &#8220;Building the LaTeX2e format&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2884863"
- name="id2884863"></a>Changing the Defaults</h3>
- </div>
- </div>
-
- <p>Sometimes you want the fonts that you define to
- replace the standard Computer Modern fonts. This is
- easily accomplished. The NFSS defines control sequences<a
- id="id2884874" class="indexterm" name="id2884874"></a>
- which identify the default fonts. These control sequences
- are listed in Table&#160;<a
- href="ch05.html#tab.nfssdefaults"
- title="Table&#160;5.6.&#160;Default Fonts ">Table&#160;5.6</a>.</p>
-
- <div class="table">
- <a id="tab.nfssdefaults" name="tab.nfssdefaults"></a>
-
- <p class="title"><b>Table&#160;5.6.&#160;Default
- Fonts</b></p>
-
- <table summary="Default Fonts " border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Control Sequence</th>
-
- <th align="left">\bf Font</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\rmdefault</td>
-
- <td align="left">The default normal (roman)
- font</td>
- </tr>
-
- <tr>
- <td align="left">\bfdefault</td>
-
- <td align="left">The default boldface font</td>
- </tr>
-
- <tr>
- <td align="left">\sfdefault</td>
-
- <td align="left">The default sans-serif font</td>
- </tr>
-
- <tr>
- <td align="left">\itdefault</td>
-
- <td align="left">The default italic font</td>
- </tr>
-
- <tr>
- <td align="left">\scdefault</td>
-
- <td align="left">The default caps and small-caps
- font.</td>
- </tr>
-
- <tr>
- <td align="left">\defaultshape</td>
-
- <td align="left">The default shape
- (<tt>n</tt>)</td>
- </tr>
-
- <tr>
- <td align="left">\defaultseries</td>
-
- <td align="left">The default series
- (<tt>m</tt>)</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>If you have defined a new font, perhaps
- <tt>garamond</tt> as I did for this book, you can make it
- the default normal font by changing \rmdefault. In LaTeX,
- the following command makes <tt>garamond</tt> the default
- normal font:</p>
-<pre class="screen">
-\renewcommand{\rmdefault}{garamond}
-</pre>
-
- <p>In Plain TeX, it's written like this:</p>
-<pre class="screen">
-\def\rmdefault{garamond}
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2885098"
- name="id2885098"></a>NFSS Pitfalls</h3>
- </div>
- </div>
-
- <p>Defining your own fonts with the NFSS is
- straightforward, but it is not without its subtleties.
- There are several things going on behind the scenes that
- you must be aware of if you are going to define your own
- fonts.</p>
-
- <p>The first consideration is font substitution. When
- NFSS cannot find a font, it tries to substitute a
- different one. First, it tries to find the font you
- requested in the default shape, then in the default
- series, and finally, in the default family. You can
- change the defaults used by NFSS2 with the
- \DeclareFontSubstitution command:</p>
-<pre class="screen">
-\DeclareFontSubstitution{<span
-class="emphasis"><em>encoding</em></span>}{<span
-class="emphasis"><em>family</em></span>}{<span
-class="emphasis"><em>series</em></span>}{<span
-class="emphasis"><em>shape</em></span>}
-</pre>
-
- <p>You must specify the defaults for each encoding you
- use because the encoding is never substituted.</p>
-
- <p>The next consideration is the use of mathematics<a
- id="id2885156" class="indexterm" name="id2885156"></a><a
- id="id2885166" class="indexterm" name="id2885166"></a>,
- which is typeset using an entirely different set of
- fonts. Even if you don't use any math in your document,
- the NFSS is prepared to function in math-mode at a
- moment's notice. In order to be prepared, it has to know
- what fonts to use. Ordinarily, mathematics is typeset
- using fonts at the same size as the current text font.
- This means that every time you change font sizes for
- text, NFSS changes font sizes for mathematics as
- well.</p>
-
- <p>By default, the NFSS defines math fonts<a
- id="id2885191" class="indexterm" name="id2885191"></a><a
- id="id2885198" class="indexterm" name="id2885198"></a>
- only at the following sizes: 5, 6, 7, 8, 9, 10, 11, 12,
- 14, 17, 20, and 25pt. If you define a new font at a
- different size, 24pt for example, the first time you try
- to use that font, you will get several warning messages
- indicating that <tt>cmr/m/n/24</tt> (Computer Modern
- Roman), <tt>cmm/m/it/24</tt> (Computer Modern Math
- Italic), <tt>cmsy/m/n/24</tt> (Computer Modern Math
- Symbols), and <tt>lasy/m/n/24</tt> (LaTeX Symbols, if
- using LaTeX), are not available. This is very confusing
- because it won't appear that you have selected 24pt
- Computer Modern <span
- class="emphasis"><em>anywhere</em></span> in your
- document.</p>
-
- <p>There are two ways to solve this problem:<sup>[<a
- id="id2885254" name="id2885254"
- href="#ftn.id2885254">63</a>]</sup></p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Redefine the required fonts at the sizes
- requested. This involves copying the definition of
- each of the fonts from NFSS <tt>FD</tt> files<a
- id="id2885284" class="indexterm"
- name="id2885284"></a> and adding new sizes.</p>
- </li>
-
- <li>
- <p>Tell NFSS to use existing math sizes for the new
- text sizes that you define. This option is
- reasonable only if you won't be using any math at
- the new sizes (or the sizes are so close that the
- mathematics doesn't appear disproportional). NFSS
- includes a macro called \DeclareMathSizes for this
- purpose. Insert it directly after the
- \DeclareFontShape command that declares the new
- font sizes. You must call \DeclareMathSizes once
- for each new size. For example, to use the 25pt
- math sizes with 24pt text, insert the following
- control sequence after you define the 24pt
- font:</p>
-<pre class="screen">
-\DeclareMathSizes{25}{24}{20}{17}
-</pre>
-
- <p>The general form of a call to \DeclareMathSizes
- is:</p>
-<pre class="screen">
-\DeclareMathSizes{<span class="emphasis"><em>text-size</em></span>}
- <tt>{</tt><span
-class="emphasis"><em>math-size</em></span><tt>}</tt>
- <tt>{</tt><span
-class="emphasis"><em>script-size</em></span><tt>}</tt>
- <tt>{</tt><span
-class="emphasis"><em>script-script-size</em></span><tt>}</tt>
-</pre>
-
- <p>Where <span
- class="emphasis"><em><tt>math-size</tt></em></span>,
- <span
- class="emphasis"><em><tt>script-size</tt></em></span>,
- and <span
- class="emphasis"><em><tt>script-script-size</tt></em></span>
- are the normal (123), script ($x^{123}$), and
- script-script ($x^{y^{123}}$) math sizes for the
- specified <span
- class="emphasis"><em><tt>text-size</tt></em></span>.</p>
- </li>
- </ul>
- </div>
-
- <p>LaTeX sometimes resets the current font to the
- \rmdefault font. For example, it does this when a \ref is
- going to be printed. This means that the font you define
- as the \rmdefault font should be available in every size
- that you use. This may require redefining the Computer
- Modern Roman font, as described above, if you add a new
- size but leave Computer Modern as the default font.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2885459"
- name="id2885459"></a>PostScript Fonts Under NFSS</h2>
- </div>
- </div>
-
- <p>PostScript fonts<a id="id2885469" class="indexterm"
- name="id2885469"></a><a id="id2885481" class="indexterm"
- name="id2885481"></a> and other scalable font technologies
- like TrueType differ from the way the
- &#8220;standard&#8221; TeX fonts work. They do not separate
- the notions of design size and magnification. Instead,
- PostScript fonts can be rendered at <span
- class="emphasis"><em>any</em></span> size from a single
- design. In daily use, the PostScript fonts under NFSS are
- indistinguishable from non-PostScript fonts. The NFSS
- distribution includes style files for accessing the 35
- standard PostScript fonts.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2885510"
- name="id2885510"></a>Adjustments to Scale</h3>
- </div>
- </div>
-
- <p><a id="id2885518" class="indexterm"
- name="id2885518"></a>Some combinations of PostScript
- fonts, particularly PostScript fonts with Computer Modern
- mathematics, look bad because there is a large
- discrepancy between the apparent sizes of the fonts. For
- example, as a consequence of design, 10pt Helvetica looks
- bigger than 10pt Computer Modern Math Italic. In order to
- correct this problem, you can specify a scaling factor
- when declaring PostScript fonts.<sup>[<a id="id2885536"
- name="id2885536" href="#ftn.id2885536">64</a>]</sup> The
- scaling factor is specified in square brackets at the
- beginning of the font-shape declaration in the
- \DeclareFontShape command.</p>
-
- <p>The easiest way to find an approximation of the
- correct scaling factor is to look at the <span
- class="emphasis"><em>x-height</em></span> of each
- font.<sup>[<a id="id2885557" name="id2885557"
- href="#ftn.id2885557">65</a>]</sup> The x-height is the
- height of a lowercase &#8220;x&#8221; in the font. The
- following macro will print the x-height of a font:</p>
-<pre class="screen">
-\def\showxheight#1{
- \font\fontfoo=#1 at 10pt
- \message{The x-height of #1 at 10pt is \the\fontdimen5\fontfoo}}
-</pre>
-
- <p>The following TeX input will print the x-heights of
- Helvetica and Computer Modern Roman (assuming that your
- Helvetica font is called <tt>phvr</tt>):</p>
-<pre class="screen">
-\input showxheight
-\showxheight{phvr}
-\showxheight{cmr10}
-\bye
-</pre>
-
- <p>On my system, the x-height of Helvetica is 5.23pt and
- the x-height of Computer Modern Roman is 4.30554pt. The
- following font declaration makes Helvetica have the same
- apparent size as Computer Modern Roman:</p>
-<pre class="screen">
-\DeclareFontShape{OT1}{phv}{m}{n}{
- &lt;-&gt; [0.8232] phvr}{}
-</pre>
-
- <p>Compare scaled Helvetica to unscaled Helvetica:</p>
-
- <p>FIXME: Unscaled Helvetica, Computer Modern Roman,
- Scaled Helvetica</p>
-
- <p>Unscaled Helvetica looks much larger than Computer
- Modern, but the scaled Helvetica appears a little too
- small. Experimentation is the only way to find the scale
- that looks best.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2885640"
- name="id2885640"></a>When Things Go Wrong</h2>
- </div>
- </div>
-
- <p>A number of font-related problems can arise<a
- id="id2885650" class="indexterm" name="id2885650"></a>
- which either prevent you from formatting and printing your
- document or cause the output to differ from what you
- anticipated. The following sections describe many common
- problems and their solutions.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2885669"
- name="id2885669"></a>When TeX Complains</h3>
- </div>
- </div>
-
- <p>The first time an error can occur is when TeX is
- processing your document. Some of these errors prevent
- TeX from continuing while others are simply warnings.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><tt>! Font \myfont=xxxxx not
- loadable: Metric (TFM) file not
- found.</tt></span></dt>
-
- <dd>
- <p>This error indicates that TeX tried to process a
- \font control sequence which assigned the font
- <tt>xxxxx</tt> to the control sequence \myfont, but
- TeX could not find a <tt>TFM</tt> file for the font
- <tt>xxxxx</tt>. All the characters from the missing
- font will be blank in the resulting <tt>DVI</tt>
- file.</p>
-
- <p>You cannot process your document until this
- error is corrected, which is a matter of fixing the
- offending \font command if you are using the old
- font selection scheme.</p>
-
- <p>Under the NFSS2, this error occurs if you
- specify an invalid font in the command
- \DeclareFontShape. Examine the font that you were
- attempting to select and make sure that it
- exists.</p>
- </dd>
-
- <dt><span class="term"><tt>Warning Font/shape `x/y/z'
- undefined on input line
- <i><tt>n</tt></i></tt></span></dt>
-
- <dd>
- <p>This is a warning message from the NFSS. It
- indicates that you requested the font family
- <tt>x</tt>, series <tt>y</tt>, and shape
- <tt>z</tt>, but the requested font does not exist.
- This message is followed by another indicating
- which font NFSS chose to substitute in place of the
- one you requested. NFSS substitutes the closest
- possible font to the one you requested. It is
- usually an acceptable replacement.</p>
-
- <p>For example, if you are currently using Computer
- Modern Bold Extended and you select Computer Modern
- Typewriter, the NFSS will report that there is no
- bold-extended-typewriter font and that normal
- typewriter is being substituted in its place.</p>
- </dd>
-
- <dt><span class="term"><tt>! Font x/y/z/999 not
- found.</tt></span></dt>
-
- <dd>
- <p>This is a fatal error from the NFSS. It
- indicates that you selected font family <tt>x</tt>,
- series <tt>y</tt>, shape <tt>z</tt> at a size of
- 999pts and that no such font exists. This error
- occurs when the size 999 is not defined in the
- \DeclareFontShape command for x/y/z.</p>
- </dd>
-
- <dt><span class="term"><tt>Missing character: There
- is no X in font foo!</tt></span></dt>
-
- <dd>
- <p>This is a warning message from TeX. Usually it
- occurs only in the log file. This error occurs when
- you attempt to access a character that does not
- exist in the current font. This can happen if you
- select the wrong font or if the selected font has a
- different encoding vector than anticipated. See the
- section &#8220;<a
- href="ch05.html#sec.fonts.encodingvec"
- title="Declaring a family">the section called
- &#8220;Declaring a family&#8221;</a>&#8221; in this
- chapter for more information.</p>
- </dd>
- </dl>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2885907"
- name="id2885907"></a>When the DVI Driver
- Complains</h3>
- </div>
- </div>
-
- <p>Getting TeX to successfully produce a <tt>DVI</tt>
- file<a id="id2885925" class="indexterm"
- name="id2885925"></a> is only half the battle. The next
- hurdle is getting a DVI driver to print it. Here are some
- of the things that can go wrong:</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2885937"
- name="id2885937"></a>Can't find PK file</h4>
- </div>
- </div>
-
- <p>When a DVI driver complains that it cannot find the
- appropriate <tt>PK</tt> file, there are several things
- that could be wrong.</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>The font is built into the printer.</p>
-
- <p>If the DVI driver complains that it cannot
- find the <tt>PK</tt> file for a built-in font,
- you need to adjust the DVI driver's configuration
- to indicate that the font is built-in. Exactly
- how this is done depends on the DVI driver that
- you are using. For example, if you are using
- <b>dvips</b>, add an entry to the
- <tt>psfonts.map</tt> file<a id="id2886005"
- class="indexterm" name="id2886005"></a>. If you
- are using emTeX, add an entry to the font
- substitution file specified in the configuration
- file. Consult the references for your particular
- DVI driver for more information about using
- built-in fonts.</p>
- </li>
-
- <li>
- <p>The font does not exist on the printer you are
- using.</p>
-
- <p>This is the same problem as the error above
- except that it cannot be fixed. For example, I
- have <tt>TFM</tt> files for many PostScript fonts
- at home because it helps me format bits of
- documentation that I bring home from work without
- error. However, if I try to print one of these
- documents without first changing the fonts, the
- DVI driver complains that it cannot find several
- fonts. There is no way that I can correct this
- because the missing fonts are built-in fonts for
- a printer that I do not have at home. In this
- case, font substitution by the DVI driver may
- allow you to preview (and even print) the
- document, but it won't look very good unless the
- font metrics of the substituted font are very
- close to the metrics for the original.</p>
- </li>
-
- <li>
- <p>Uncommon size or font (no <tt>PK</tt>
- file).</p>
-
- <p>The Computer Modern family contains a number
- of fonts that are very rarely used. If you don't
- keep <tt>PK</tt> files for these fonts around all
- the time and attempt to use one of them (or
- attempt to use a common font at a very unusual
- size), the DVI driver will not be able to find
- the necessary <tt>PK</tt> file. You have to build
- the <tt>PK</tt> file first. Consult
- Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">
- Chapter&#160;11</a> for more information about
- building <tt>PK</tt> files with MetaFont. Also
- consult the section called &#8220;<a
- href="ch05.html#sec.autofont"
- title="Automatic Font Generation by DVI Drivers">the
- section called &#8220;Automatic Font Generation
- by DVI Drivers&#8221;</a>&#8221; later in this
- chapter.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2886152"
- name="id2886152"></a>Accents don't work or the
- wrong characters are printed</h4>
- </div>
- </div>
-
- <p>This problem is usually caused by a bad encoding
- vector. See the section &#8220;<a
- href="ch05.html#sec.fonts.encodingvec"
- title="Declaring a family">the section called
- &#8220;Declaring a family&#8221;</a>&#8221; in this
- chapter for more information.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2886177"
- name="id2886177"></a>Printer prints the right
- characters but the wrong font</h4>
- </div>
- </div>
-
- <p>This is usually an indication that you are trying to
- use a font that does not exist on the printer.
- PostScript printers, for example, substitute Courier
- for any font that does not exist.</p>
-
- <p>Another possibility is that you have configured your
- DVI driver incorrectly. I once told <b>dvips</b> to
- download Galliard when I used Garamond. It took me
- quite a while to find that error. Make sure that the
- printer contains the fonts that you think it does and
- make sure that you are mapping the TeX font names to
- the correct printer fonts.</p>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2886211"
- name="id2886211"></a>Encoding Vectors</h2>
- </div>
- </div>
-
- <p>An encoding vector<a id="id2886220" class="indexterm"
- name="id2886220"></a> describes the order and position of
- characters within a font. The purpose of this section is to
- help you understand the role that encoding vectors play in
- the translation of text from your input file to printed
- output.</p>
-
- <p>Encoding vectors cause a lot of confusion. Whenever the
- characters that you type in your input file are printed
- incorrectly (&#8220;<tt>flight</tt>&#8221; in your input
- file prints out as &#8220;ight&#8221;;
- &#8220;\oe{}vres&#8221; prints out as
- &#8220;\'uvres&#8221;; or &#8220;<tt>---</tt>&#8221; prints
- out as &#8220;-{}-{}-&#8221; instead of &#8220;---&#8221;),
- you've probably encountered some sort of encoding
- problem.</p>
-
- <p>The root of this problem is that the characters in your
- input file are really just numbers between 0 and
- 255.<sup>[<a id="id2886286" name="id2886286"
- href="#ftn.id2886286">66</a>]</sup> The number 65 is
- usually a capital A, but there is nothing intrinsic to the
- value 65 to signify this. In order to display these byte
- values, they have to be translated into symbols.</p>
-
- <p>These problems arise because there are at least four
- different translations occurring between what you type and
- what appears on the printed (or previewed) page:</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>You type some symbols on the keyboard, and they
- are displayed by your editor. The configuration of
- your system determines how these characters appear.
- Sometimes they are from the ISO Latin-1 symbol set,
- sometimes US ASCII, sometimes something else, and
- sometimes it is user configurable. If you confine
- yourself to pure ASCII, you're pretty safe, but
- that's not convenient for languages other than
- English. When you are typing documents in Spanish,
- it's very convenient to be able to type
- &#8220;\&#160;n&#8221; directly in your document.</p>
- </li>
-
- <li>
- <p>TeX reads your input file and translates it into
- an internal encoding (basically ASCII). (The reverse
- translation is performed before TeX prints any output
- to the terminal or the log file.) The translation
- tables used in this step are generally determined
- when the TeX program is compiled, but several modern
- TeXs allow you to modify these tables at runtime.</p>
-
- <p>TeX assumes that fonts use TeX's internal
- encoding. For example, on an IBM mainframe, which
- uses the EBCDIC character set<a id="id2886356"
- class="indexterm" name="id2886356"></a>, TeX
- translates a capital A (EBCDIC 193) into ASCII 65 and
- assumes that position 65 of the metric information
- for the current font contains the information
- (including ligature and kerning information) for a
- capital A.</p>
- </li>
-
- <li>
- <p>If you use control sequences to represent special
- characters (\oe for &#8220;\oe&#8221;, for example),
- the macro package you use is responsible for defining
- those control sequences so they produce the correct
- characters. If the macro package assumes that the
- &#8220;\oe&#8221; character appears at position 247
- of the current font, the output will not be correct
- in a font with a different encoding.</p>
- </li>
-
- <li>
- <p>The DVI driver reads TeX's <tt>DVI</tt> file and
- assumes that the encoding vector of each font used in
- the <tt>DVI</tt> file is the same as the encoding
- vector of the actual fonts in the output device. For
- <tt>PK</tt> fonts, this is probably true (since the
- DVI driver sends the font to the printer), but for
- fonts built into the printer, it is less likely to be
- true.</p>
- </li>
- </ol>
- </div>
-
- <p>You may think of a font as a collection of 1 to 256
- different symbols in a particular order. This is really a
- font plus a particular encoding vector. It is more accurate
- to think of a font as simply a collection of symbols (with
- no particular number or ordering). An encoding vector
- selects which symbols are used and in what order they
- appear. Typically, an encoding vector can contain only 256
- different symbols. It is important to note that changing an
- encoding vector of a font does not simply permute the order
- of the characters in the font, it can change which symbols
- are actually present as well.</p>
-
- <p>Encoding vectors are either implicit or explicit. Most
- fonts have an implicit encoding, but some (for example,
- Adobe Type&#160;1 fonts) contain an explicit, configurable
- encoding. TeX fonts have an implicit encoding. TeX actually
- uses several different encoding vectors (it uses more than
- one because it has both text or body fonts and several
- kinds of math and symbol fonts). The character set tables
- in Appendix&#160;<a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a>,
- <span class="emphasis"><em><a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a></em></span>,
- show the encoding of several different fonts.</p>
-
- <p>\font\mathit=cmmi10 Most macro packages assume that the
- TEX TEXT encoding is being used. For example, Plain TeX
- defines the control sequence \AE as an abbreviation for
- character number 29 in the current font. Even when control
- sequences aren't involved, problems can arise if the output
- font does not have the anticipated encoding. The byte-value
- 34 in your input file is almost always the literal double
- quote character (<tt>"</tt>) and usually prints as a double
- quote (which is probably what your editor displays and
- probably what you expect). If the font encoding is
- something different, the result will not be what you
- expect. For example, if the current font has the TEX MATH
- ITALIC encoding, the result is
- &#8220;{\mathit\char34}&#8221;.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.fonts.virtualfonts"
- name="sec.fonts.virtualfonts"></a>Virtual Fonts</h2>
- </div>
- </div>
-
- <p>Virtual fonts<a id="id2886658" class="indexterm"
- name="id2886658"></a><a id="id2886666" class="indexterm"
- name="id2886666"></a> (stored in <tt>VF</tt> files<a
- id="id2886687" class="indexterm"
- name="id2886687"></a><sup>[<a id="id2886706"
- name="id2886706" href="#ftn.id2886706">67</a>]</sup>) are a
- relatively new addition to the TeX family. When TeX was
- originally defined in 1970, Knuth<a id="id2886736"
- class="indexterm" name="id2886736"></a> chose a character
- encoding that suited his purposes, and very little effort
- was made to parameterize the encoding. (In fact, any TeX
- macro writer can use <span
- class="emphasis"><em>any</em></span> encoding she wants,
- but no general mechanism for identifying the encoding
- exists.<sup>[<a id="id2886754" name="id2886754"
- href="#ftn.id2886754">68</a>]</sup>) Virtual fonts combat
- this problem by allowing the creator to define a virtual
- font in terms of (multiple) characters from one or more
- fonts.</p>
-
- <p>Virtual fonts are used most commonly to change the
- encoding vector of a font. This provides a convenient way
- of mapping different fonts into the required encoding so
- that they are easy to use in TeX. A virtual font consists
- of a <tt>VF</tt> file and a <tt>TFM</tt> file. TeX uses the
- <tt>TFM</tt> file as it would any other.</p>
-
- <p>Figure&#160;<a href="ch05.html#fig.vfdiagram"
- title="Figure&#160;5.4.&#160;How TeX uses a virtual font">Figure&#160;5.4</a>
- shows how a virtual font is used by the TeX system. In this
- case, a virtual font <tt>ctmr</tt> has been created
- combining characters from the fonts <tt>trr0n</tt>,
- <tt>trr6m</tt>, <tt>trr6j</tt>, and <tt>trr10j</tt>.</p>
-
- <div class="figure">
- <a id="fig.vfdiagram" name="fig.vfdiagram"></a>
-
- <p class="title"><b>Figure&#160;5.4.&#160;How TeX uses a
- virtual font</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>The document uses the font <tt>ctmr</tt>. TeX uses the
- font metric information in <tt>ctmr.tfm</tt> to compose the
- <tt>DVI</tt> file. The DVI driver, however, discovers a
- <tt>VF</tt> file named <tt>ctmr</tt>, so it uses the
- instructions in the virtual font to select characters from
- the four built-in fonts. This is a practical example. It
- shows how the HP LaserJet built-in fonts may be accessed
- with the standard TeX text encoding.</p>
-
- <p>In practice, virtual fonts suffer from one limitation: A
- virtual font can only permute the encoding vector; it
- cannot access characters that do not appear in the encoding
- vector of the &#8220;real&#8221; font. For example, an
- Adobe Type&#160;1 font might contain all of the characters
- that appear in the TeX text encoding, but many of them do
- not appear in the standard Adobe encoding vector. A virtual
- font alone cannot remap the characters into the TeX text
- encoding. The encoding vector of the font must also be
- changed. Several PostScript DVI drivers have this
- ability.</p>
-
- <p>Virtual fonts are binary files and are very difficult to
- edit. To make it possible to construct virtual fonts by
- hand, TeX includes standard utilities (<b>VFtoVP</b><a
- id="id2886971" class="indexterm" name="id2886971"></a> and
- <b>VPtoVF</b><a id="id2886985" class="indexterm"
- name="id2886985"></a>) for converting the binary
- <tt>VF</tt> format into a human-readable <tt>VPL</tt>
- format. The <tt>VPL</tt> files are text files that can be
- edited with a text editor.</p>
-
- <p>A complete description of how to create virtual fonts is
- beyond the scope of this book. If you are interested in
- experimenting with virtual fonts, I strongly recommend that
- you examine the <b>fontinst</b> package.<sup>[<a
- id="id2887038" name="id2887038"
- href="#ftn.id2887038">69</a>]</sup> <b>fontinst</b><a
- id="id2887070" class="indexterm" name="id2887070"></a>
- allows you to construct <tt>VPL</tt> files with TeX
- documents. This isn't as strange as it first sounds.
- Virtual font files have to include the metric information
- from <tt>TFM</tt> files for each font that they include.
- Because TeX can easily read this information, and the
- output is a plain text document anyway, TeX is a very
- capable, if somewhat slow, tool.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.autofont" name="sec.autofont"></a>Automatic
- Font Generation by DVI Drivers</h2>
- </div>
- </div>
-
- <p>Recent releases of many popular DVI drivers (\dvips<a
- id="id2887119" class="indexterm" name="id2887119"></a>,
- xdvi<a id="id2887132" class="indexterm"
- name="id2887132"></a>, \SeeTeX<a id="id2887140"
- class="indexterm" name="id2887140"></a>, and emTeX<a
- id="id2887151" class="indexterm" name="id2887151"></a>'s
- DVI drivers, to name a few) include the ability to generate
- missing fonts automatically<a id="id2887162"
- class="indexterm" name="id2887162"></a><a id="id2887174"
- class="indexterm" name="id2887174"></a>. Automatic font
- generation overcomes two problems simultaneously: it
- reduces disk space requirements, and it makes font
- generation easier. Most implementations of TeX are
- distributed with a complete set of Computer Modern fonts at
- seven or more magnifications. This can easily amount to
- several megabytes of disk space (even more if you are using
- other fonts, like the \AmS fonts<a id="id2887193"
- class="indexterm" name="id2887193"></a> from the American
- Mathematical Society<a id="id2887205" class="indexterm"
- name="id2887205"></a>). In practice, you probably use only
- a small subset of these fonts.</p>
-
- <p>One way to combat the disk-space problem is to delete
- all of the TeX fonts on your system and build just the ones
- you actually use. In the days before automatic font
- generation, this would have been quite unpleasant. The
- first time you discovered that you needed a font that you
- did not have, you would have to stop your DVI driver,
- figure out what size was missing, figure out how to get
- MetaFont to build the font that was missing at the
- appropriate resolution, run MetaFont, store the font in the
- right place, and return to your DVI driver. Moments later,
- you might discover that you had to do the whole process
- again for some other font.</p>
-
- <p>Using a driver that provides automatic font generation
- makes it nearly painless to delete fonts and let them be
- built automatically.<sup>[<a id="id2887238"
- name="id2887238" href="#ftn.id2887238">70</a>]</sup> The
- DVI driver determines the resolution required, runs
- MetaFont with the appropriate parameters, stores the font
- in the correct place, and continues processing the document
- uninterrupted.</p>
-
- <p>The down side of automatic font generation is that you
- must keep the MetaFont program around and make available
- the source files for the Computer Modern fonts (and any
- other MetaFont fonts that you use). If you do not already
- have these files on your hard disk, the potential disk
- space savings are somewhat reduced. (MetaFont is discussed
- fully in Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>.)
- Moreover, automatic font generation can only build
- <tt>PK</tt> files<a id="id2887281" class="indexterm"
- name="id2887281"></a>; if <tt>TFM</tt> files are also
- missing, you will have to build those by hand before TeX
- can process your document.<sup>[<a id="id2887312"
- name="id2887312" href="#ftn.id2887312">71</a>]</sup></p>
-
- <p>Another benefit of automatic font generation is that it
- can be used to provide previewers, even non-PostScript
- previewers, with the ability to preview documents that use
- PostScript fonts, provided that you have the Printer Font
- ASCII (<tt>PFA</tt>)<a id="id2887344" class="indexterm"
- name="id2887344"></a> or Printer Font Binary
- (<tt>PFB</tt>)<a id="id2887363" class="indexterm"
- name="id2887363"></a> font sources and Adobe Font Metric
- (<tt>AFM</tt>)<a id="id2887382" class="indexterm"
- name="id2887382"></a> for your PostScript fonts.</p>
-
- <p>The following lines, added to the <tt>MakeTeXPK</tt><a
- id="id2887401" class="indexterm" name="id2887401"></a>
- script distributed with <b>dvips</b>, provide automatic
- font generation for PostScript fonts with <b>ps2pk</b><a
- id="id2887423" class="indexterm" name="id2887423"></a>.
- This is useful even on systems where PostScript printers
- are used for output, because previewers like <b>xdvi</b><a
- id="id2887438" class="indexterm" name="id2887438"></a> also
- use <b>MakeTeXPK</b> to build missing fonts.</p>
-<pre class="screen">
-# Look for a PostScript outline font...
-if [ -r /usr/local/lib/tex/ps/outlines/$NAME.pfa ]
-then
- echo Building TeX font from PostScript outline
- # Hack. If $6 is null, $DESTDIR =&gt; $6 ...
- PStoTeXfont $1 $2 $3 $4 $5 $6 $DESTDIR
- exit 0
-else
- echo Building TeX font from MetaFont outline
-fi
-</pre>
-
- <p>In this example, PostScript fonts are stored in the
- <tt>/usr/local/lib/tex/ps/outlines</tt> directory. You
- should change this directory to something appropriate for
- your system. On a unix system, the <b>PStoTeXfont</b>
- script shown in Example&#160;<a
- href="ch05.html#ex.pstotexfont"
- title="Example&#160;5.3.&#160;The PStoTeXfont script">Example&#160;5.3</a>
- is appropriate.<sup>[<a id="id2887500" name="id2887500"
- href="#ftn.id2887500">72</a>]</sup> A <b>Perl</b> version
- of <b>MakeTeXPK</b> that handles both MetaFont and
- PostScript fonts is shown in Example&#160;<a
- href="apd.html#ex.maketexpk"
- title="Example&#160;D.1.&#160;MakeTeXPK.pl">Example&#160;D.1</a>
- in Appendix&#160;<a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a>,
- <span class="emphasis"><em><a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a></em></span>.</p>
-
- <div class="example">
- <a id="ex.pstotexfont" name="ex.pstotexfont"></a>
-
- <p class="title"><b>Example&#160;5.3.&#160;The
- PStoTeXfont script</b></p>
-<pre class="screen">
-#!/usr/local/bin/bash
-#
-# This script file makes a new TeX font from a PS outline.
-#
-# Parameters are:
-#
-# name dpi bdpi [mag mode destdir]
-#
-# `name' is the name of the font, such as `ptmr'. `dpi'
-# is the resolution the font is needed at. `bdpi' is
-# the base resolution.
-#
-# This script ignores the remaining parameters. They are
-# left here to document the fact that the caller may provide
-# them. They may be provided because the caller thinks
-# MetaFont is going to do the work...
-#
-# Of course, this needs to be set up for your site.
-#
-# TEMPDIR needs to be unique for each process because of the
-# possibility of simultaneous processes running this script.
-
-TEMPDIR=/tmp/temp-tex-PS.$$
-NAME=$1
-DPI=$2
-BDPI=$3
-
-LOCALDIR=/usr/local/lib/mf/fonts
-DESTDIR=$LOCALDIR/pk
-
-BASENAME=$NAME.$DPI
-PFADIR=/usr/local/lib/tex/ps/outlines
-
-# Clean up on normal or abnormal exit
-trap "cd /; rm -rf $TEMPDIR" 0 1 2 15
-
-mkdir $TEMPDIR
-cd $TEMPDIR
-
-# We proceed by making a 10pt font at the resolution
-# requested...
-echo Making ${DPI}dpi version of $NAME.
-ps2pk -X$DPI -P10 -a$PFADIR/$NAME.afm $PFADIR/$NAME.pfa ${BASENAME}pk
-
-mv ${BASENAME}pk $DESTDIR
-
-exit 0
-</pre>
- </div>
-
- <p>A similar script for using automatic font generation
- under emTeX with <b>4DOS</b> is shown in Examples&#160;<a
- href="apd.html#ex.dvidxx"
- title="Example&#160;D.3.&#160;dvidxx.btm">Example&#160;D.3</a>
- and&#160;<a href="apd.html#ex.makepk"
- title="Example&#160;D.4.&#160;makepk.btm">Example&#160;D.4</a>
- in Appendix&#160;<a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a>.
- Several other options are available for performing
- automatic font generation on a number of platforms,
- including a <b>REXX</b> version for OS/2 and a compiled
- program called <b>MKTeXPK</b>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.t1fonts" name="sec.t1fonts"></a>Math Fonts in
- TeX</h2>
- </div>
- </div>
-
- <p>Changing math fonts<a id="id2887679" class="indexterm"
- name="id2887679"></a><a id="id2887686" class="indexterm"
- name="id2887686"></a> is more difficult than changing text
- fonts. In addition to the large number of special symbols
- that must be available, TeX needs a lot more information to
- use the fonts because the characters are combined more
- frequently and in more complex ways. For example, the open
- brace character (\{) in math mode is
- &#8220;extensible;&#8221; this means that it can be as
- large as required. In order for TeX to construct a brace of
- arbitrary size, one of the math fonts (the math extensions
- font) contains four different characters that TeX combines
- to form the brace:</p>
-
- <p>FIXME: brace pieces</p>
-
- <p>Extensible recipes for characters like &#8220;\{&#8221;,
- &#8220;\}&#8221;, &#8220;(&#8221;, and &#8220;)&#8221; are
- examples of additional metric information that must be
- available in math fonts for TeX.</p>
-
- <p>In addition to the Computer Modern math fonts, there are
- really only three other choices at present: the \AmS
- fonts<a id="id2887745" class="indexterm"
- name="id2887745"></a> (MetaFont fonts freely distributed by
- the American Mathematical Society<a id="id2887758"
- class="indexterm" name="id2887758"></a> which extend but do
- not replace the Computer Modern math fonts), the Lucida
- Bright+New Math fonts<a id="id2887768" class="indexterm"
- name="id2887768"></a>, and the MathTime fonts<a
- id="id2887778" class="indexterm" name="id2887778"></a>.
- Lucida Bright and MathTime are both sets of commercial
- PostScript Type&#160;1 fonts.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2887790"
- name="id2887790"></a>Concrete Examples</h2>
- </div>
- </div>
-
- <p>The following sections describe by example how you can
- use several different kinds of fonts in TeX. The tools
- described are generally free and generally available for
- multiple platforms. Where specific commercial tools are
- used, free alternatives are discussed.</p>
-
- <p>The specific tools I mention here are not the only tools
- available nor are they necessarily the best, although I
- hope I've found the best ones. If you have found a
- different and better solution, don't abandon it in favor of
- what I use here. But please do tell me about the method
- that you have found. With every passing day, more free
- software becomes available.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2887816"
- name="id2887816"></a>MetaFont Fonts</h3>
- </div>
- </div>
-
- <p>Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>
- describes how to use MetaFont to create fonts for TeX.<a
- id="id2887825" class="indexterm" name="id2887825"></a><a
- id="id2887847" class="indexterm" name="id2887847"></a> If
- you have MetaFont installed, you can easily create fonts
- that are usable in TeX.</p>
-
- <p>MetaFont reads <tt>MF</tt> files, which are plain text
- files that describe a font analogous to the way TeX reads
- <tt>TEX</tt> files that describe a document.</p>
-
- <p>Appendix&#160;<a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a>,
- <span class="emphasis"><em><a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a></em></span>,
- contains examples of many MetaFont fonts. Consult the
- &#8220;Definitive List of All Fonts Available for
- {MetaFont}&#8221;&#160;[<a
- href="bi01.html#lreq:metafonts">lreq:metafonts</a>] for
- an up-to-date list with availability information.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2887929"
- name="id2887929"></a>PostScript Type 1 Fonts</h3>
- </div>
- </div>
-
- <p>PostScript printers have many PostScript Type&#160;1<a
- id="id2887939" class="indexterm" name="id2887939"></a><a
- id="id2887949" class="indexterm" name="id2887949"></a>
- fonts built in. If you want to use built-in fonts, you
- only need the metric information for them and a
- PostScript DVI driver. The <b>dvips</b> driver is the
- most popular free DVI driver. Several commercial drivers
- are also available.</p>
-
- <p>The metric information should be available in the form
- of Adobe Font Metric (<tt>AFM</tt>) files<a
- id="id2887986" class="indexterm" name="id2887986"></a>
- from the printer vendor or directly from Adobe Systems<a
- id="id2888007" class="indexterm" name="id2888007"></a>,
- Inc. You need a program that will convert <tt>AFM</tt>
- files into <tt>TFM</tt> files<a id="id2888034"
- class="indexterm" name="id2888034"></a>. There are
- several free programs that will do this conversion (one
- is included with <b>dvips</b>), and your DVI driver may
- have included one. In general, if one came with your DVI
- driver, that is the one you should use.</p>
-
- <p>If you want to use PostScript Type&#160;1 fonts on
- non-PostScript devices, like most screen previewers, you
- need the &#8220;sources&#8221; for the fonts that you
- want to use. Many font vendors sell fonts in Adobe
- Type&#160;1 format. In addition, there are many
- Type&#160;1 fonts available on the Internet and on
- bulletin board systems.<sup>[<a id="id2888068"
- name="id2888068" href="#ftn.id2888068">73</a>]</sup></p>
-
- <p>Several companies have made complete, high-quality
- fonts available. They are:</p>
-
- <div class="table">
- <a id="id2888084" name="id2888084"></a>
-
- <p class="title"><b>Table&#160;5.7.&#160;</b></p>
-
- <table summary="" border="1">
- <colgroup>
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">IBM Courier</th>
-
- <th>URW Antiqua</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">Bitstream Courier</td>
-
- <td>URW Grotesk Bold</td>
- </tr>
-
- <tr>
- <td align="left">Bitstream Charter</td>
-
- <td>Nimbus Roman No9</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>Check the license that accompanies these fonts to make
- sure that you can use them legally.</p>
-
- <p>PostScript Type&#160;1 font sources are available in
- Printer Font ASCII (<tt>PFA</tt>)<a id="id2888169"
- class="indexterm" name="id2888169"></a> and Printer Font
- Binary (<tt>PFB</tt>)<a id="id2888188" class="indexterm"
- name="id2888188"></a> formats.<sup>[<a id="id2888196"
- name="id2888196" href="#ftn.id2888196">74</a>]</sup> The
- <tt>PFB</tt> format is more compact, but less portable.
- unix systems usually use <tt>PFA</tt> files, while MS-DOS
- and OS/2 systems use <tt>PFB</tt> files. Several existing
- programs can convert <tt>PFB</tt> files into <tt>PFA</tt>
- files and vice-versa. For the remainder of this section,
- I will consistently refer to PostScript Type&#160;1
- source files as <tt>PFA</tt> files, although you can use
- <tt>PFB</tt> files instead if they are supported on your
- platform.</p>
-
- <p>In addition to the <tt>PFA</tt> files, you will also
- need metric information for the fonts. The metric
- information <span class="emphasis"><em>should</em></span>
- be available in <tt>AFM</tt> format. If you purchased
- fonts from a vendor and did not receive <tt>AFM</tt>
- files, you should complain. Fonts from free sources, like
- Internet archive sites and bulletin board systems
- sometimes include only Printer Font Metric
- (<tt>PFM</tt>)<a id="id2888341" class="indexterm"
- name="id2888341"></a> files. These are Microsoft Windows
- printer metric files, and they do not contain enough
- information to make a <tt>TFM</tt> file.</p>
-
- <p>It is possible to create a <tt>TFM</tt> file from the
- <tt>PFM</tt> file, but the metrics are not particularly
- good. To do this:</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>Convert the <tt>PFM</tt> file into an incomplete
- <tt>AFM</tt> file with the <b>PFM2AFM</b><a
- id="id2888427" class="indexterm"
- name="id2888427"></a> utility.</p>
- </li>
-
- <li>
- <p>Use the <b>PS2PK</b><a id="id2888449"
- class="indexterm" name="id2888449"></a> program to
- make a <tt>PK</tt> file.</p>
- </li>
-
- <li>
- <p>Use <b>PKBBOX</b><a id="id2888481"
- class="indexterm" name="id2888481"></a> to create a
- more complete <tt>AFM</tt> file from the incomplete
- <tt>AFM</tt> file and the <tt>PK</tt> file.</p>
- </li>
- </ol>
- </div>
-
- <p>The <tt>AFM</tt> file manufactured in this way can be
- used to create a <tt>TFM</tt> file. The <tt>PK</tt> file
- can be used by any DVI driver that understands TeX
- <tt>PK</tt> fonts (almost all drivers have this
- ability).</p>
-
- <p>Creating <tt>PK</tt> files does require more disk
- space, but it has the advantage that you can print TeX
- documents which use PostScript Type&#160;1 fonts on
- non-PostScript devices. This includes fast,
- <tt>PK</tt>-based screen previewers like <b>xdvi</b> and
- emTeX's <b>dviscr</b> that do not understand
- PostScript.</p>
-
- <p>Programs like <b>dvipsone</b><a id="id2888617"
- class="indexterm" name="id2888617"></a> and
- <b>dviwindo</b><a id="id2888631" class="indexterm"
- name="id2888631"></a> which run under the Microsoft
- Windows environment can use PostScript fonts directly if
- Adobe Type Manager (ATM)<a id="id2888641"
- class="indexterm" name="id2888641"></a> is installed on
- the system. However, it is still necessary to construct
- the <tt>TFM</tt> files for TeX.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2888662"
- name="id2888662"></a>{Using a new PostScript font
- in TeX (for PostScript printers)}</h4>
- </div>
- </div>
-
- <p>This section presents a step-by-step description of
- how to use a new PostScript font in TeX with a
- PostScript printer or previewer. In this situation, you
- have a PostScript printer, and you use <b>dvips</b> to
- print your documents. This method also allows you to
- preview your documents with <b>Ghostscript</b>.</p>
-
- <p>For either method, you must first obtain the
- PostScript sources for the font that you want to use.
- You <span class="emphasis"><em>must</em></span> have a
- <tt>PFA</tt> or <tt>PFB</tt> file and an <tt>AFM</tt>
- file. As a concrete example, I'll use the &#8220;Nimbus
- Roman 9L Regular&#8221; font. For this font, I obtain
- <tt>unmr.pfa</tt> and <tt>unmr.afm</tt>. These fonts
- are available from the CTAN archives in the directory
- <tt>fonts/urw</tt>.<sup>[<a id="id2888763"
- name="id2888763" href="#ftn.id2888763">75</a>]</sup> In
- order to use the font in TeX, you must create TeX font
- metrics for it using <b>afm2tfm</b><a id="id2888801"
- class="indexterm" name="id2888801"></a> (in particular,
- the version of <b>afm2tfm</b> that comes with
- <b>dvips</b>).</p>
-
- <p>First, however, we must decide what encoding vector
- to use. Frequently, the fonts you obtain use Adobe
- Standard Encoding. The problem with this encoding is
- that it isn't very complete; it leaves out a lot of
- standard TeX characters (like the ligatures
- &#8220;fi&#8221; and &#8220;fl&#8221; as well as many
- accented and international letters). Instead of using
- Adobe Standard Encoding<a id="id2888843"
- class="indexterm" name="id2888843"></a>, I recommend
- using the Cork Encoding<a id="id2888852"
- class="indexterm" name="id2888852"></a>. The Cork
- Encoding has several advantages; it is a superset of
- the original TeX text encoding; it is becoming a new
- standard for TeX; and it is supported by the NFSS2. Of
- course, the Cork Encoding is not suitable for all
- fonts; there's no reason to try to re-encode a symbol
- font into the Cork Encoding---that doesn't even make
- any sense.</p>
-
- <p>Luckily, using the Cork Encoding is no more
- difficult than using whatever encoding the distributed
- font contains. <b>afm2tfm</b> will do all the work. You
- only need to obtain the appropriate encoding file. In
- this case, the file is <tt>ec.enc</tt>, and it is
- distributed with both <b>dvips</b> and NFSS2. Use
- <b>afm2tfm</b> to generate the metrics:</p>
-<pre class="screen">
-\$ {\bf afm2tfm unmr.afm -v unmr.vpl -T ec.enc unmr0.tfm}
-</pre>
-
- <p>This command reads <tt>unmr.afm</tt>, the original
- <tt>AFM</tt> file with an arbitrary encoding, and the
- encoding vector <tt>ec.enc</tt>. It creates the virtual
- font <tt>unmr.vpl</tt> and the <tt>TFM</tt> file
- <tt>unmr0.tfm</tt>.</p>
-
- <p>The relationship between these files is subtle. The
- <tt>AFM</tt> file contains metric information for all
- the possible glyphs<a id="id2888978" class="indexterm"
- name="id2888978"></a> in the font. The encoding file
- establishes the encoding vector---which particular
- characters occur in exactly what order. These two files
- are combined to produce character metric information
- for the specific encoding vector. This information is
- saved in the <tt>TFM</tt> file. This is a
- &#8220;raw&#8221; <tt>TFM</tt> file<a id="id2889015"
- class="indexterm" name="id2889015"></a>.<sup>[<a
- id="id2889026" name="id2889026"
- href="#ftn.id2889026">76</a>]</sup> It does not have
- any ligature or kerning information and <span
- class="emphasis"><em>may</em></span> have a different
- encoding from the virtual font (although, in this case
- it has the same encoding).</p>
-
- <p>The next step is to produce a virtual font from the
- <tt>VPL</tt> file<a id="id2889087" class="indexterm"
- name="id2889087"></a>:</p>
-<pre class="screen">
-\$ {\bf vptovf unmr.vpl unmr.vf unmr.tfm}
-</pre>
-
- <p>This produces a virtual font file, <tt>unmr.vf</tt>,
- and an appropriate <tt>TFM</tt> file. This <tt>TFM</tt>
- file has ligature and kerning information for the
- characters in the font as well as the metrics for the
- individual glyphs.</p>
-
- <p>The names of the virtual font files and the related
- <tt>TFM</tt> files are entirely arbitrary. You can give
- them any names you wish. In the long run, you will
- benefit if you choose a naming scheme that allows you
- to determine which files are which simply by examining
- the names. If you have a lot of fonts, take a look at
- <span class="emphasis"><em>{Filenames for
- Fonts}</em></span>&#160;[<a
- href="bi01.html#tug:filenames-fonts">tug:filenames-fonts</a>].
- It is also available electronically from CTAN in the
- directory <tt>info/filename</tt>.</p>
-
- <p>Now you should install the <tt>VF</tt> and
- <tt>TFM</tt> files in the appropriate directories and
- proceed to use the <tt>unmr</tt> font. TeX will do the
- right thing because the <tt>TFM</tt> file contains the
- appropriate metric information, and the DVI driver will
- do the right thing because it has a virtual font which
- specifies how the characters should be mapped into the
- printer.</p>
-
- <p>Now that TeX is happy, we have the additional
- problem of making the PostScript printer happy. The
- easiest way to do this is to tell <b>dvips</b> to do it
- for us. The <tt>psfonts.map</tt> file used by
- <b>dvips</b> identifies which fonts are built into the
- printer and which fonts need to be downloaded.</p>
-
- <p>Each line in the <tt>psfonts.map</tt> file describes
- how a particular TeX font should be interpreted. The
- simplest lines identify the PostScript name of fonts
- built into the printer. For \linebreak</p>
-
- <p>example, the following line indicates that
- <b>dvips</b><a id="id2889279" class="indexterm"
- name="id2889279"></a> should use the PostScript font
- Times-Roman (which is assumed to be resident in the
- printer) everywhere that the <tt>DVI</tt> file uses the
- font <tt>rptmr</tt>:</p>
-<pre class="screen">
-rptmr Times-Roman
-</pre>
-
- <p>To automatically download a PostScript font<a
- id="id2889318" class="indexterm" name="id2889318"></a>,
- add <tt>&lt;</tt><tt><i><tt>fontfile</tt></i></tt> to
- the corresponding line in the <tt>psfonts.map</tt>
- file. The following entry indicates that the PostScript
- font CharterBT-Roman should be used where
- <tt>rbchr</tt> is used in the document. In addition,
- <b>dvips</b> should download the font from the file
- <tt>/usr/local/lib/fonts/psfonts/bchr.pfa</tt> if it is
- used in the document.</p>
-<pre class="screen">
-rbchr CharterBT-Roman &lt;/usr/local/lib/fonts/psfonts/bchr.pfa
-</pre>
-
- <p>Additional PostScript commands can be added to the
- entry to perform special effects. Some of these are
- described in the documentation for <b>dvips</b>. They
- require a knowledge of PostScript that is beyond the
- scope of this book.</p>
-
- <p>Adding the following line to <tt>psfonts.map</tt>
- will download and use the Nimbus URW font we installed
- above. (It is shown on two lines only because of the
- constraints of the page; you should enter it on one
- line):</p>
-<pre class="screen">
-unmr0 NimbusRomanNo9L-Regular &lt;unmr.pfa
- "ECEncoding ReEncodeFont" &lt;ec.enc
-</pre>
-
- <p>This line identifies the font <tt>unmr0</tt> as the
- NimbusRomanNo9L-Regular PostScript font, re-encoded
- with the ECEncoding described in the file
- <tt>ec.enc</tt>. Because this font is not resident in
- the printer, you must also tell <b>dvips</b> to
- download the font from <tt>unmr.pfa</tt>. If you keep
- encoding files or PostScript fonts (<tt>PFB</tt> or
- <tt>PFA</tt> files) in nonstandard locations, you will
- have to specify the full path of <tt>ec.enc</tt> and/or
- <tt>unmr.pfa</tt>.</p>
-
- <p>Notice that you specify the <span
- class="emphasis"><em>raw</em></span> font in the
- <tt>psfonts.map</tt> file. TeX and <b>dvips</b> will
- use the virtual font to determine which character(s)
- from which raw font(s) should <span
- class="emphasis"><em>actually</em></span> be used to
- print your document. <b>afm2tfm</b> prints the line
- that should be added to the font map file when it is
- finished converting the font, so you don't always have
- to remember which is which.</p>
-
- <p>The <tt>psfonts.map</tt> file (and the encoding and
- font files) are typically stored in a system-default
- location. On unix systems, this is frequently
- <tt>/usr/local/lib/tex/ps</tt>. If you can't (or don't
- want) to change files in this directory, you can use
- your own font map file.</p>
-
- <p>When you run <b>dvips</b>, it loads a initialization
- file (typically <tt>~/.dvipsrc</tt>). If you put the
- following line in that file:</p>
-<pre class="screen">
-p +/home/jdoe/myfonts.map
-</pre>
-
- <p>it extends the system-wide font map using the file
- <tt>/home/jdoe/myfonts.map</tt>, which has the same
- format as the <tt>psfonts.map</tt> file.</p>
-
- <p>If you use the <tt>&lt;font.pfa</tt> syntax in your
- font map file to download PostScript fonts, you may
- discover that <b>dvips</b> is producing very large
- output files (or takes a long time to print, if output
- is going directly to a printer). The reason is that
- <b>dvips</b> is downloading the font at the beginning
- of every document that uses it. If you have a few fonts
- that you use all the time, it may be faster and more
- convenient to download the fonts manually at the
- beginning of the day and then remove the
- <tt>&lt;font.pfa</tt> portion of the font mapping line
- (leave the encoding file, however). This will produce
- smaller output files because <b>dvips</b> will assume
- that the fonts are already downloaded. Of course, the
- trade-off is that your documents will not print
- correctly (because the appropriate fonts are not
- attached to the PostScript file) if you mail them to a
- colleague who doesn't download the same fonts you do,
- or if you forget to download the fonts again after
- someone power-cycles the printer.<sup>[<a
- id="id2889655" name="id2889655"
- href="#ftn.id2889655">77</a>]</sup></p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2889664"
- name="id2889664"></a>{Using a new PostScript font
- in TeX (for non-PostScript devices)}</h4>
- </div>
- </div>
-
- <p>Using PostScript fonts for screen previewing or
- printing on non-PostScript printers is a very different
- process from printing on PostScript devices. You still
- need the <tt>AFM</tt> and <tt>PFA</tt> files.</p>
-
- <p>This time you're going to create <tt>PK</tt> files
- with <b>ps2pk</b><a id="id2889716" class="indexterm"
- name="id2889716"></a>, so virtual fonts are less
- useful. In fact, you have to give the <tt>AFM</tt> file
- the correct encoding in order to get the right
- <tt>PK</tt> file, so we'll avoid virtual fonts
- altogether. Of course, if you need several different
- encodings (perhaps TeX Text, Cork, and Adobe Standard)
- for different documents, you'll be better off with one
- or two raw font files and several virtual fonts, but
- for the moment let's imagine that that is not the
- case.</p>
-
- <p>Example&#160;<a href="apd.html#ex.encafmpl"
- title="Example&#160;D.5.&#160;enc-afm.pl">Example&#160;D.5</a>
- in Appendix&#160;<a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a>,
- <span class="emphasis"><em><a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a></em></span>,
- is a Perl script that changes the encoding vector in an
- <tt>AFM</tt> file to reflect the encoding specified in
- an encoding file (like the ones used in the preceding
- section). This is an important step because
- <b>ps2pk</b> uses the encoding in the <tt>AFM</tt> file
- to determine which glyphs to render.<sup>[<a
- id="id2889816" name="id2889816"
- href="#ftn.id2889816">78</a>]</sup></p>
-
- <p>To install this script, save it in a file called
- <tt>enc-afm.pl</tt> and change the top of the script
- (the <tt>#!</tt> line) to reflect where Perl is
- installed on your system. Users of Perl on non-unix
- systems may have to work a little harder, or simply use
- the syntax <span class="emphasis"><em>{perl
- enc-afm.pl}</em></span> to run the script. unix users
- can create a symbolic link to <tt>enc-afm.pl</tt>
- called <tt>enc-afm</tt>, and mark it as executable.</p>
-
- <p>Using this script, transform <tt>unmr.afm</tt> into
- <tt>unmrX.afm</tt>:</p>
-<pre class="screen">
-\$ <span
-class="bold"><b>enc-afm unmr.afm ec.enc &gt; unmrX.afm</b></span>
-</pre>
-
- <p>Now the <tt>unmrX.afm</tt> file has the Cork
- encoding. We can use this file to create a <tt>TFM</tt>
- file for TeX:</p>
-<pre class="screen">
-\$ <span class="bold"><b>afm2tfm unmrX.afm unmr.tfm</b></span>
-</pre>
-
- <p>This <tt>TFM</tt> file should be moved to the
- directory where you store <tt>TFM</tt> files for
- TeX.</p>
-
- <p>Unlike PostScript fonts on PostScript devices,
- different <tt>PK</tt> files must be created for each
- size required. As a concrete example, let's assume we
- want a 14pt font. The easiest way to create a 14pt font
- with <b>ps2pk</b> is to use the <span
- class="emphasis"><em>-P</em></span> parameter to
- specify the size. Unfortunately, this will cause some
- DVI drivers to complain because <span
- class="emphasis"><em>-P</em></span> sets the design
- size of the <tt>PK</tt> file, and it won't match the
- design size in the <tt>TFM</tt> file. A better solution
- is to determine the resolution you need with the
- following formula:</p>
-
- <p>$$\hbox{resolution} = {{\hbox{base resolution} *
- \hbox{point size}}\over{10}}$$</p>
-
- <p>The factor 10 is used because it is the nominal
- design size of PostScript fonts (at least, that's what
- <b>afm2tfm</b> uses). For example, if we are creating a
- 14pt font for a 300dpi laser printer, the desired
- resolution is $300*14/10 = 420$. Now we can create the
- font:</p>
-<pre class="screen">
-\$ <span
-class="bold"><b>ps2pk -X420 -aunmrX.afm unmr.pfa unmr.420pk</b></span>
-</pre>
-
- <p>This command creates a 420dpi <tt>PK</tt> file using
- the <tt>AFM</tt> file <tt>unmrX.afm</tt>. The font
- source comes from <tt>unmr.pfa</tt>, and the resulting
- <tt>PK</tt> file is called <tt>unmr.pk</tt>. On MS-DOS
- systems, name the output <tt>PK</tt> file
- <tt>unmr.pk</tt> because <tt>unmr.420pk</tt> is not a
- valid filename. Move the resulting <tt>PK</tt> file to
- the appropriate directory. On unix systems, it is
- probably <tt>/usr/local/lib/tex/fonts/pk</tt>; while on
- MS-DOS and other systems, it is probably something like
- <tt>/texfonts/420dpi</tt>.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2890165"
- name="id2890165"></a>HP LaserJet Softfonts</h3>
- </div>
- </div>
-
- <p>Bitmapped HP LaserJet Softfonts<a id="id2890174"
- class="indexterm" name="id2890174"></a> can easily be
- converted into TeX <tt>PK</tt> files with the
- <b>SFPtoPK</b> utility. Then they can be used with almost
- any DVI driver.</p>
-
- <p>Scalable LaserJet Softfonts can be used by TeX if two
- conditions are met: metric information is available, and
- the DVI driver that you are using can access built-in
- printer fonts. Metric information for Scalable LaserJet
- Softfonts distributed by Hewlett-Packard come in the form
- of Tagged Font Metric files. Tagged Font Metric files
- have the extension <tt>TFM</tt>, but they should not be
- confused with TeX <tt>TFM</tt> files. The utility
- <b>hptfm2pl</b> converts Tagged Font Metric files into
- TeX <tt>PL</tt> files (<tt>PL</tt> is a human-readable
- text format of <tt>TFM</tt> files). <tt>PL</tt> files are
- transformed into <tt>TFM</tt> files by the standard TeX
- utility <b>PLtoTF</b>.</p>
-
- <p>To use Scalable LaserJet Softfonts, you must convert
- the metric information into TeX <tt>TFM</tt> files so
- that TeX can use the font, and then you must inform your
- DVI driver that the fonts are built into the printer.
- Before printing your document, download the Scalable
- LaserJet Softfont to your printer. The <b>sfload</b>
- utility that is part of Sfware can download Scalable
- LaserJet Fonts. Many other free and shareware font
- downloading programs exist, too.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2890329"
- name="id2890329"></a>TrueType Fonts</h3>
- </div>
- </div>
-
- <p>At present, TrueType fonts<a id="id2890338"
- class="indexterm" name="id2890338"></a> can be used only
- on systems that have built-in TrueType support (the
- Macintosh and MS-DOS computers running Microsoft Windows
- 3.1 fall into this category). You must use DVI drivers
- that communicate with the printer through the system's
- printer interface.</p>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2879974" name="ftn.id2879974"
- href="#id2879974">53</a>]</sup> {Some fonts may be
- preloaded in the format file. TeX does not need
- <tt>TFM</tt> files for those fonts since the metric
- information is already available.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2880211" name="ftn.id2880211"
- href="#id2880211">54</a>]</sup> {Older DVI drivers may
- still use <tt>PXL</tt> files. They are frequently stored
- in directories with names like <tt>pxl999</tt>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2880575" name="ftn.id2880575"
- href="#id2880575">55</a>]</sup> {Actually, <tt>TFM</tt>
- files contain a little bit more information. The width of
- a space, the amount of stretch and shrink allowed between
- words, the amount of extra space allowed after a
- punctuation mark, and some specialized information used
- only in fonts for mathematics also appear in the
- <tt>TFM</tt> files<a id="id2880604" class="indexterm"
- name="id2880604"></a>. In principle, <tt>TFM</tt> files
- can contain even more information, although they rarely
- do. For a complete, detailed description of the
- information stored in a <tt>TFM</tt> file, consult
- Appendix F of <span class="emphasis"><em>The
- TeXbook</em></span>&#160;[<a
- href="bi01.html#kn:texbook">kn:texbook</a>] and <span
- class="emphasis"><em>{The TF To PL
- Processor}</em></span>&#160;[<a
- href="bi01.html#texware:tftopl">texware:tftopl</a>].}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2880810" name="ftn.id2880810"
- href="#id2880810">56</a>]</sup> {This is true even if
- your computer's natural character set is not ASCII. It is
- the responsibility of the implementor to map the
- computer's natural character set into ASCII.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2881782" name="ftn.id2881782"
- href="#id2881782">57</a>]</sup> {Actually, for math
- fonts, TeX requires several metrics that are not usually
- provided. <b>afm2tfm</b><a id="id2881795"
- class="indexterm" name="id2881795"></a> has options which
- allow you to specify these extra metrics when you convert
- the <tt>AFM</tt> file.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2882138" name="ftn.id2882138"
- href="#id2882138">58</a>]</sup> {If your MetaFont
- distribution does not include a <span
- class="emphasis"><em>tfmonly</em></span> mode, you can
- find one in the <tt>modes.mf</tt> file on CTAN. Consult
- Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>,
- <span class="emphasis"><em><a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a></em></span>,
- for more information.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2883176" name="ftn.id2883176"
- href="#id2883176">59</a>]</sup> {This doesn't mean that
- every size you want is available. See the section
- &#8220;<a href="ch05.html#sec.fonts.defnfss2"
- title="Selecting Fonts with the New Font Selection Scheme">
- the section called &#8220;Selecting Fonts with the New
- Font Selection Scheme&#8221;</a>&#8221; for information
- about defining font sizes in the NFSS.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2855832" name="ftn.id2855832"
- href="#id2855832">60</a>]</sup>
- &#8220;$\backslash$<tt>fontshape{it}</tt>$\backslash$<tt>selectfont</tt>&#8221;</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2855948" name="ftn.id2855948"
- href="#id2855948">61</a>]</sup> {One possible use of
- loading options is to inhibit hyphenation in fixed-width
- fonts intended for use in verbatim material. The loading
- options <tt>{\ hyphenchar\ font=-1}</tt> have this
- effect.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2884721" name="ftn.id2884721"
- href="#id2884721">62</a>]</sup> {The only reason that
- sizes less than 8pt need to be declared at all is that
- marginal notes (used for editorial comments while the
- book was in revision) were set in 5pt, and the logo font
- occasionally turned up in a marginal note.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2885254" name="ftn.id2885254"
- href="#id2885254">63</a>]</sup> {Under earlier versions
- of the NFSS, this problem actually resulted in an error
- rather than a warning. If you wish, you can simply ignore
- the warning; you no longer have to fix the problem.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2885536" name="ftn.id2885536"
- href="#id2885536">64</a>]</sup> {Actually, you can
- declare a scaling factor in any font declaration,
- although it seems to make less sense for non-PostScript
- fonts.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2885557" name="ftn.id2885557"
- href="#id2885557">65</a>]</sup> {Usually, scaling fonts
- to the same x-height makes them look acceptable together,
- but depending on the particular fonts involved, a little
- more or a little less scaling may be required to achieve
- a pleasant balance.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2886286" name="ftn.id2886286"
- href="#id2886286">66</a>]</sup> {In some special versions
- of TeX, notably those for handling languages like
- Japanese, this may be extended to a much larger number,
- but the problem is the same.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2886706" name="ftn.id2886706"
- href="#id2886706">67</a>]</sup> {For a complete
- description, consult <span class="emphasis"><em>{The VP
- To VF Processor}</em></span>&#160;[<a
- href="bi01.html#texware:vptovf">texware:vptovf</a>] and
- <span class="emphasis"><em>{The VF to VP
- Processor}</em></span>&#160;[<a
- href="bi01.html#texware:vftovp">texware:vftovp</a>].}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2886754" name="ftn.id2886754"
- href="#id2886754">68</a>]</sup> {Version 2 of NFSS
- includes &#8220;encoding&#8221; as a parameter in font
- selection. In the long run, this will allow macro writers
- to hide many of these difficulties, dramatically reducing
- the burden currently placed on the user.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2887038" name="ftn.id2887038"
- href="#id2887038">69</a>]</sup> {You can retrieve the
- <b>fontinst</b> package from the CTAN archives in the
- directory <tt>fonts/utilities/fontinst</tt>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2887238" name="ftn.id2887238"
- href="#id2887238">70</a>]</sup> {It's still a bit
- tedious, at least on slow machines, but now you can walk
- away and get a cup of coffee ;-). All the fonts will be
- built automatically.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2887312" name="ftn.id2887312"
- href="#id2887312">71</a>]</sup> {Recent versions of TeX
- derived from the \Web2C package can build <tt>TFM</tt>
- files automatically as well.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2887500" name="ftn.id2887500"
- href="#id2887500">72</a>]</sup> {OK, so not <span
- class="emphasis"><em>every</em></span> example in this
- book is in <b>Perl</b>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2888068" name="ftn.id2888068"
- href="#id2888068">73</a>]</sup> {Before you use these
- &#8220;free&#8221; fonts, be aware that many are of
- questionable legality.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2888196" name="ftn.id2888196"
- href="#id2888196">74</a>]</sup> {PostScript fonts for the
- Macintosh are stored in <tt>PFB</tt> format (essentially)
- in the resource fork of the printer font file. The metric
- information is stored in the screen font, which also
- contains bitmaps for on-screen display.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2888763" name="ftn.id2888763"
- href="#id2888763">75</a>]</sup> {The Nimbus fonts
- actually come with <tt>TFM</tt> and <tt>VF</tt> files
- which makes some of the following steps redundant. But
- because most fonts <span
- class="emphasis"><em>don't</em></span> come with TeX
- metrics, the example is important.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2889026" name="ftn.id2889026"
- href="#id2889026">76</a>]</sup> {Raw <tt>TFM</tt> files
- used to be identified with an &#8220;r&#8221; prefix, but
- recently the trend has turned towards a &#8220;0&#8221;
- suffix. For a more complete discussion of font names,
- consult <span class="emphasis"><em>Filenames for
- Fonts</em></span>&#160;[<a
- href="bi01.html#tug:filenames-fonts">tug:filenames-fonts</a>].}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2889655" name="ftn.id2889655"
- href="#id2889655">77</a>]</sup> {Some spooling software
- will transparently handle these problems (by downloading
- fonts that you forget) if the fonts are available.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2889816" name="ftn.id2889816"
- href="#id2889816">78</a>]</sup> {This step isn't
- necessary when using a PostScript printers because the
- PostScript font always contains all the glyphs. The font
- created by <b>ps2pk</b> will only contain the characters
- in a single encoding.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;6.&#160;Pictures and Figures"
- href="ch06.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Part&#160;II.&#160;Elements
- of a Complex Document&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;6.&#160;Pictures and Figures</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch06.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch06.html
deleted file mode 100644
index a89d17fadf5..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch06.html
+++ /dev/null
@@ -1,3381 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;6.&#160;Pictures and Figures</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts" />
- <link rel="next" href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;5.&#160;Fonts" href="ch05.html"><img
- src="figures/nav-prev.png" alt="Prev" border="0" />
- </a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;7.&#160;International Considerations"
- href="ch07.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.pictures"
- name="chap.pictures"></a>Chapter&#160;6.&#160;Pictures
- and Figures</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>Pictures<a id="id2884175" class="indexterm"
- name="id2884175"></a> and figures<a id="id2884189"
- class="indexterm" name="id2884189"></a> are an important
- component of many documents. This chapter explores how they
- can be incorporated into your TeX documents. There are many
- ways to include pictures and figures in TeX. The most
- important considerations are the type of image<a
- id="id2855783" class="indexterm" name="id2855783"></a>, the
- type of printer you will be using, what platform you are
- using, and how portable the document must be.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.devindrev" name="sec.devindrev"></a>Different
- Kinds of Images</h2>
- </div>
- </div>
-
- <p>Images<a id="id2883926" class="indexterm"
- name="id2883926"></a> come from many, many different
- sources, but they can be divided into two broad classes:
- bitmapped and scalable (or vector). Bitmapped images<a
- id="id2883939" class="indexterm" name="id2883939"></a><a
- id="id2883949" class="indexterm" name="id2883949"></a> are
- produced whenever an image is scanned from a drawing,
- photograph, or other printed work. They are also produced
- by most simple paint programs. Scalable images<a
- id="id2883964" class="indexterm" name="id2883964"></a><a
- id="id2883971" class="indexterm" name="id2883971"></a><a
- id="id2883981" class="indexterm" name="id2883981"></a> are
- produced by some more sophisticated drawing programs, many
- commercial sources, and some other applications. Both
- classes have advantages and disadvantages.</p>
-
- <p>Files that contain graphic images usually end with an
- extension<a id="id2890375" class="indexterm"
- name="id2890375"></a> that identifies the format of the
- image. The extension is a common and convenient nickname
- for the image format. In this chapter, I refer to graphic
- image formats by their extension (for example, GIF images
- or XBM images) without explanation. I do this partly
- because it is easy, but also because it is the most common
- way of referring to them, and you don't really need to know
- anything about the image formats to use them. If your DVI
- driver understands PCX images, you just need a PCX image;
- you don't have to have a detailed understanding of the
- format (thank goodness). If you want to know more, refer to
- the filename extension glossary in Appendix&#160;<a
- href="apa.html"
- title="Appendix&#160;A.&#160;Filename Extension Summary">Appendix&#160;A</a>,
- which will help you identify each of the formats discussed
- in this chapter.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2890411"
- name="id2890411"></a>Bitmapped Images</h3>
- </div>
- </div>
-
- <p>Photographs<a id="id2890419" class="indexterm"
- name="id2890419"></a> and images with a lot of subtle
- detail are almost always stored as bitmaps. Scanners
- always produce bitmapped images<a id="id2890430"
- class="indexterm" name="id2890430"></a>. Some bitmap
- images can be converted into scalable formats. High-end
- graphic packages like \product{CorelDRAW}<a
- id="id2890443" class="indexterm" name="id2890443"></a>
- and \product{\idx{Adobe Illustrator}} can do this, but
- most cannot. The exceptions are line drawings and other
- very high contrast images. Bitmaps are also
- &#8220;cheap&#8221; to print. Neither the computer nor
- the printer must do very much work to print a
- black-and-white bitmap image. (Color bitmap images must
- be dithered before they can be printed, but that's a
- separate consideration because it need be done only once,
- not every time the image is printed.) Bitmapped images
- are also easy to convert from one format to another.</p>
-
- <p>Unfortunately, bitmap images are very
- device-dependent. They are stored as a two-dimensional
- array of dots, which gives them a fixed resolution. A
- $3\times5$-inch bitmap image that prints correctly on
- your 300dpi laser printer will only be a
- $\frac{3}{4}\times1\frac{1}{4}$-inch picture if you make
- your final copy on a 1200dpi photo-typesetter.</p>
-
- <p>Bitmap images also require considerable memory and
- disk space to store. The $3\times5$ image described above
- requires more than 150Kb of memory (if it is
- uncompressed).</p>
-
- <p>A final consideration is that bitmap images do not
- scale very well. Enlarging or reducing the image requires
- either removing some dots (causing a loss of detail) or
- inserting extra dots (frequently giving slanted lines a
- very jagged appearance). Rescaling images by exact
- integer amounts (doubling or tripling its size, for
- example, but not making it 2$\frac{1}{2}$ times as large)
- works reasonably well (except for jagged edges). Shaded
- regions, which are composed of a regular pattern of black
- and white dots, are frequently disrupted by irregular
- &#8220;blotching&#8221; if non-integral scaling is
- used.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2884033"
- name="id2884033"></a>Scalable Images</h3>
- </div>
- </div>
-
- <p>Many graphic images can be represented more compactly
- as a collection of lines, curves, and other discrete
- elements. Images of this type are called <span
- class="emphasis"><em>scalable</em></span> or <span
- class="emphasis"><em>vector</em></span> images<a
- id="id2884054" class="indexterm" name="id2884054"></a><a
- id="id2884061" class="indexterm" name="id2884061"></a>.
- Instead of storing every pixel in a rectangular array,
- vector images store the encoded instructions for
- &#8220;drawing&#8221; the image. This provides a compact
- representation. A circle, no matter how large, can be
- represented with just a few data points: the position of
- the center, the radius, the width and color of the line
- that forms the circle, and the pattern that fills the
- circle. It is also easy to change the size of the image;
- if you halve every measurement, the image is drawn at one
- half the size with minimal loss of detail.</p>
-
- <p>One drawback of scalable images is that they require
- considerable computational power to render. Every printer
- ultimately prints the page as a large bitmap; the print
- engine has to translate the lines, curves, and fills of a
- scalable image into a bitmap before this is
- possible.<sup>[<a id="id2884093" name="id2884093"
- href="#ftn.id2884093">79</a>]</sup> Previewing scalable
- images requires translating them into bitmaps to display
- them. This can be a noticeably slow process unless you
- have a very fast computer.</p>
-
- <p>The other significant drawback of scalable images is
- that they are difficult to translate from one format to
- another. For example, to translate a PostScript image<a
- id="id2884111" class="indexterm" name="id2884111"></a>
- into something that can be printed on a non-PostScript
- printer, you have to have a program that understands all
- of the commands in the PostScript file. A bitmap
- conversion, on the other hand, doesn't require any
- understanding of graphics commands; it simply has to know
- how to rearrange the bits in the array. What it boils
- down to is this: it's a lot easier to write a translation
- program to &#8220;reverse the order of all the bits in
- each byte in each row&#8221; than it is to write one that
- can &#8220;draw the bezier curve with these three control
- points using a dashed, light-blue line $\frac{1}{8}$ of
- an inch wide.&#8221;</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2884144"
- name="id2884144"></a>Device Independence Revisited</h2>
- </div>
- </div>
-
- <p>Pictures<a id="id2890779" class="indexterm"
- name="id2890779"></a> and figures<a id="id2890791"
- class="indexterm" name="id2890791"></a> are a foreign
- concept to TeX. Remember, TeX cares only about building
- pages out of boxes and glue. TeX's notion of a picture is
- frequently nothing more than &#8220;something special goes
- here (I don't know what) and it's 5 inches wide, 2 inches
- high, and 1 inch deep.&#8221; This is device independence,
- of a sort, but many of the easiest ways to include pictures
- and figures in TeX do rely on features of a specific DVI
- driver or a specific kind of printer. If document
- portability is an issue, consider carefully before you
- select a particular way of including pictures and
- figures.</p>
-
- <p>On the bright side, most DVI drivers<a id="id2890822"
- class="indexterm" name="id2890822"></a> provide some
- mechanism for incorporating pictures and figures. As long
- as it is possible to convert the images from the format
- originally used to a format that another DVI driver
- understands, document portability can be achieved. For
- example, it is possible to print PostScript figures on a
- non-PostScript device if they are first converted into
- another format with <b>Ghostscript</b> or some other
- PostScript interpreter. Unfortunately, it is usually
- inconvenient to convert pictures from one format to
- another, and some conversions may distort the images a
- little bit (or a lot).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.ptexpic" name="sec.ptexpic"></a>Using Only
- TeX</h2>
- </div>
- </div>
-
- <p>This section describes picture and figure environments
- that don't use any external programs. Graphics created in
- this way are entirely device-independent and can be printed
- with any DVI driver.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2890867"
- name="id2890867"></a>Plain TeX</h3>
- </div>
- </div>
-
- <p>Plain TeX<a id="id2890880" class="indexterm"
- name="id2890880"></a><a id="id2890893" class="indexterm"
- name="id2890893"></a><a id="id2890906" class="indexterm"
- name="id2890906"></a> has no built-in provision for
- creating pictures or figures. It is possible to do simple
- diagrams and graphs by writing macros that place
- individual points on the page. Figure&#160;<a
- href="ch06.html#fig.plaintex"
- title="Figure&#160;6.1.&#160;An example diagram in Plain TeX">
- Figure&#160;6.1</a> shows several data points plotted in
- Plain TeX. The input was derived from macros presented in
- Appendix D of <span class="emphasis"><em>The
- TeXbook</em></span>&#160;[<a
- href="bi01.html#kn:texbook">kn:texbook</a>]; it is shown
- in Example&#160;<a href="ch06.html#ex.plaintexm"
- title="Example&#160;6.1.&#160;The Input for the Plain TeX Diagram">
- Example&#160;6.1</a>.</p>
-
- <div class="figure">
- <a id="fig.plaintex" name="fig.plaintex"></a>
-
- <p class="title"><b>Figure&#160;6.1.&#160;An example
- diagram in Plain TeX</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <div class="example">
- <a id="ex.plaintexm" name="ex.plaintexm"></a>
-
- <p class="title"><b>Example&#160;6.1.&#160;The Input
- for the Plain TeX Diagram</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="tex.06.01.tex"></a>
-</pre>
- </div>
-
- <p>With special-purpose fonts, it is possible to make
- more complex figures in Plain TeX. However, LaTeX
- provides a <tt>picture</tt> environment which greatly
- simplifies the process.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.pictures.latex"
- name="sec.pictures.latex"></a>LaTeX</h3>
- </div>
- </div>
-
- <p>The <tt>picture</tt> environment in LaTeX<a
- id="id2891050" class="indexterm" name="id2891050"></a><a
- id="id2891064" class="indexterm" name="id2891064"></a><a
- id="id2891076" class="indexterm" name="id2891076"></a> is
- implemented on top of the kinds of primitive operations
- shown in Example&#160;<a href="ch06.html#ex.plaintexm"
- title="Example&#160;6.1.&#160;The Input for the Plain TeX Diagram">
- Example&#160;6.1</a>. Working in the <tt>picture</tt>
- environment is a lot like working on graph paper: you
- begin by specifing how big the graph paper is and the
- distance between lines on the paper (the lines aren't
- really there; they're just used for reference), and then
- inside the <tt>picture</tt> environment, you put <span
- class="emphasis"><em>picture elements</em></span> down on
- the page at the intersections of the lines on the
- grid.</p>
-
- <p>LaTeX provides picture elements for text, boxes, solid
- and empty circles, lines, and arrows. Lines and arrows
- can be drawn at angles, but they are formed by taking
- characters from a special set of fonts so there is a
- limited number of angles available. The advantage of
- using special fonts to draw the lines is that it is
- relatively efficient.</p>
-
- <p>Figure&#160;<a href="ch06.html#fig.latexpic"
- title="Figure&#160;6.2.&#160;A parallelogram in LaTeX">Figure&#160;6.2</a>
- is a simple figure drawn with LaTeX's <tt>picture</tt>
- environment. The LaTeX input for this environment is
- shown in Example&#160;<a href="ch06.html#ex.latexpicsrc"
- title="Example&#160;6.2.&#160;The LaTeX Input for ">Example&#160;6.2</a>.</p>
-
- <div class="figure">
- <a id="fig.latexpic" name="fig.latexpic"></a>
-
- <p class="title"><b>Figure&#160;6.2.&#160;A
- parallelogram in LaTeX</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <div class="example">
- <a id="ex.latexpicsrc" name="ex.latexpicsrc"></a>
-
- <p class="title"><b>Example&#160;6.2.&#160;The LaTeX
- Input for <a href="ch06.html#fig.latexpic"
- title="Figure&#160;6.2.&#160;A parallelogram in LaTeX">Figure&#160;6.2</a></b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="tex.06.02.tex"></a>
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.Fig"
- name="sec.Fig"></a>The epic and eepic styles</h4>
- </div>
- </div>
-
- <p>Constructing diagrams using <tt>picture</tt>
- primitives is very tedious because each element of the
- picture has to be placed individually. The <span
- class="emphasis"><em>epic</em></span> style extends
- LaTeX's picture environment by adding several
- higher-level commands for picture construction. These
- commands allow you to draw solid, dotted, and dashed
- lines with arbitrary slopes, create matrices and grids
- with a single command, join several independently
- placed elements together, and read a list of points
- from an external file.</p>
-
- <p>The diagrams produced by <tt>epic.sty</tt><a
- id="id2891283" class="indexterm" name="id2891283"></a>
- are still limited by the fonts available to LaTeX. The
- <tt>eepic.sty</tt><a id="id2891298" class="indexterm"
- name="id2891298"></a> extends <tt>epic.sty</tt> by
- using \special commands to construct the more complex
- figure elements. The \special commands are the same as
- those used by <tt>tpic</tt> (see the &#8220;<a
- href="ch06.html#sec.tpic" title="MetaFont">the section
- called &#8220;MetaFont&#8221;</a>&#8221; section in
- this chapter) and are supported by many DVI
- drivers.</p>
-
- <p>Figure&#160;<a href="ch06.html#fig.epic"
- title="Figure&#160;6.3.&#160;A figure created with (a) epic, and (b) eepic">
- Figure&#160;6.3</a> shows a figure constructed with the
- <span class="emphasis"><em>epic</em></span> macros.
- Figure&#160;<a href="ch06.html#fig.epic"
- title="Figure&#160;6.3.&#160;A figure created with (a) epic, and (b) eepic">
- Figure&#160;6.3</a> (a) uses <tt>epic.sty</tt>, and (b)
- uses <tt>eepic.sty</tt>. Notice that <tt>eepic.sty</tt>
- provides circles of arbitrary size and smooth lines at
- any angle. The end points of the radial lines in this
- figure were calculated by another program and read from
- a data file by <span
- class="emphasis"><em>epic</em></span>. The source for
- these figures is shown in Example&#160;<a
- href="ch06.html#ex.epicsrc"
- title="Example&#160;6.3.&#160;The epic Input for ">Example&#160;6.3</a>
- (both diagrams were created with the same source).</p>
-
- <div class="example">
- <a id="ex.epicsrc" name="ex.epicsrc"></a>
-
- <p class="title"><b>Example&#160;6.3.&#160;The epic
- Input for <a href="ch06.html#fig.epic"
- title="Figure&#160;6.3.&#160;A figure created with (a) epic, and (b) eepic">
- Figure&#160;6.3</a></b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="tex.06.03.tex"></a>
-</pre>
- </div>
-
- <div class="figure">
- <a id="fig.epic" name="fig.epic"></a>
-
- <p class="title"><b>Figure&#160;6.3.&#160;A figure
- created with (a) epic, and (b) eepic</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2891474"
- name="id2891474"></a>The bezier style</h4>
- </div>
- </div>
-
- <p>The <span class="emphasis"><em>bezier</em></span>
- style<a id="id2891487" class="indexterm"
- name="id2891487"></a> allows you to construct curved
- lines in the LaTeX picture environment. An example is
- shown in Figure&#160;<a href="ch06.html#fig.bezier"
- title="Figure&#160;6.4.&#160;Several bezier curves created with the LaTeX bezier style">
- Figure&#160;6.4</a>. Its source is shown in
- Example&#160;<a href="ch06.html#ex.beziersrc"
- title="Example&#160;6.4.&#160;The Input for ">Example&#160;6.4</a>.
- The grid in this example was created with <span
- class="emphasis"><em>epic</em></span> for
- convenience.</p>
-
- <div class="example">
- <a id="ex.beziersrc" name="ex.beziersrc"></a>
-
- <p class="title"><b>Example&#160;6.4.&#160;The Input
- for <a href="ch06.html#fig.bezier"
- title="Figure&#160;6.4.&#160;Several bezier curves created with the LaTeX bezier style">
- Figure&#160;6.4</a></b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="tex.06.04.tex"></a>
-</pre>
- </div>
-
- <div class="figure">
- <a id="fig.bezier" name="fig.bezier"></a>
-
- <p class="title"><b>Figure&#160;6.4.&#160;Several
- bezier curves created with the LaTeX bezier
- style</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2891594"
- name="id2891594"></a>Other styles</h4>
- </div>
- </div>
-
- <p>In addition to these styles, there are several other
- style files for doing particular types of drawing.
- Styles exist for drawing logical circuit diagrams, bar
- charts, trees, and more.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2891609"
- name="id2891609"></a>Other approaches</h4>
- </div>
- </div>
-
- <p>Because constructing LaTeX drawing by hand is
- tedious, several programs have been written that allow
- you to construct diagrams visually and then produce the
- appropriate <tt>picture</tt> environments
- automatically. The <b>texcad</b><a id="id2891633"
- class="indexterm" name="id2891633"></a> program
- distributed with emTeX<a id="id2891642"
- class="indexterm" name="id2891642"></a> is one such
- program. A similar program called <b>xtexcad</b><a
- id="id2891659" class="indexterm" name="id2891659"></a>
- runs under X11 on some platforms, and there is a Fig
- translator for the LaTeX <tt>picture</tt> environment.
- (For more information about Fig, see the &#8220;<a
- href="ch06.html#sec.Fig"
- title="The epic and eepic styles">the section called
- &#8220;The epic and eepic styles&#8221;</a>&#8221;
- section later in this chapter.)</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2891692"
- name="id2891692"></a>PiCTeX</h3>
- </div>
- </div>
-
- <p>PiCTeX<a id="id2891701" class="indexterm"
- name="id2891701"></a><a id="id2891712" class="indexterm"
- name="id2891712"></a> is a macro package that you can
- load on top of Plain TeX or LaTeX.<sup>[<a id="id2891727"
- name="id2891727" href="#ftn.id2891727">80</a>]</sup> It
- does an amazing job of plotting mathematical functions<a
- id="id2891735" class="indexterm" name="id2891735"></a>
- and two-dimensional graphs directly in TeX. An example of
- PiCTeX (taken from <span class="emphasis"><em>The PiCTeX
- Manual</em></span>&#160;[<a
- href="bi01.html#mw:pictex">mw:pictex</a>]) is shown in
- Figure&#160;<a href="ch06.html#fig.pictex"
- title="Figure&#160;6.5.&#160;Sample diagrams using PiCTeX">
- Figure&#160;6.5</a>. The source for this figure is shown
- in Example&#160;<a href="ch06.html#ex.pictexsrc"
- title="Example&#160;6.5.&#160;PiCTeX Input for ">Example&#160;6.5</a>.</p>
-
- <div class="figure">
- <a id="fig.pictex" name="fig.pictex"></a>
-
- <p class="title"><b>Figure&#160;6.5.&#160;Sample
- diagrams using PiCTeX</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <div class="example">
- <a id="ex.pictexsrc" name="ex.pictexsrc"></a>
-
- <p class="title"><b>Example&#160;6.5.&#160;PiCTeX Input
- for <a href="ch06.html#fig.pictex"
- title="Figure&#160;6.5.&#160;Sample diagrams using PiCTeX">
- Figure&#160;6.5</a></b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="tex.06.05.tex"></a>
-</pre>
- </div>
-
- <p>The primary drawback of PiCTeX is that it requires a
- considerable amount of memory to use. Even relatively
- simple looking graphs require a big TeX to plot with
- PiCTeX. PiCTeX also produces very, very large
- <tt>DVI</tt> files (the graphs are drawn by interpreting
- and plotting each pixel individually). This usually
- results in very large output files from the DVI driver,
- and some printers may have difficulty printing your
- documents.</p>
-
- <p>The PiCTeX macros are freely available, but the manual
- is not. You can purchase the manual directly from the
- author of PiCTeX or from the TeX User's Group.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2891884"
- name="id2891884"></a>XYPic</h3>
- </div>
- </div>
-
- <p><b>XYPic</b><a id="id2891897" class="indexterm"
- name="id2891897"></a><a id="id2891907" class="indexterm"
- name="id2891907"></a> is another add-on macro package for
- TeX, LaTeX, and other formats. It provides considerably
- more flexibility than the LaTeX picture environment
- without resorting to the resource-expensive strategy of
- PiCTeX.</p>
-
- <p><b>XYPic</b> provides many more arrows than LaTeX
- (including curved and self-pointing forms), a wider
- variety of dashed and dotted lines, provision for lines
- that bend and go around \linebreak</p>
-
- <p>other picture elements, and annotations for lines and
- arrows. It seems especially well suited to typesetting
- commutative diagrams, simple state-transition diagrams,
- and complex annotated matrices.</p>
-
- <p>The syntax used in <b>XYPic</b> diagrams is not as
- straightforward as LaTeX's picture environment. An
- example of a complex <b>XYPic</b> diagram is shown in
- Figure&#160;<a href="ch06.html#fig.xypic"
- title="Figure&#160;6.6.&#160;An XYPic diagram">Figure&#160;6.6</a>.
- The corresponding source is shown in Example&#160;<a
- href="ch06.html#ex.xypicsrc"
- title="Example&#160;6.6.&#160;The XYPic Input for ">Example&#160;6.6</a>.</p>
-
- <div class="figure">
- <a id="fig.xypic" name="fig.xypic"></a>
-
- <p class="title"><b>Figure&#160;6.6.&#160;An XYPic
- diagram</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <div class="example">
- <a id="ex.xypicsrc" name="ex.xypicsrc"></a>
-
- <p class="title"><b>Example&#160;6.6.&#160;The XYPic
- Input for <a href="ch06.html#fig.xypic"
- title="Figure&#160;6.6.&#160;An XYPic diagram">Figure&#160;6.6</a></b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="tex.06.06.tex"></a>
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2892057"
- name="id2892057"></a>DraTeX</h3>
- </div>
- </div>
-
- <p>DraTeX<a id="id2892066" class="indexterm"
- name="id2892066"></a><a id="id2892077" class="indexterm"
- name="id2892077"></a> is a macro package that can be
- loaded on top of Plain TeX or LaTeX and provides many
- sophisticated drawing features. An example is shown in
- Figure&#160;<a href="ch06.html#fig.dratex"
- title="Figure&#160;6.7.&#160;An DraTeX diagram">Figure&#160;6.7</a>.
- The source is in Example&#160;<a
- href="ch06.html#ex.dratexsrc"
- title="Example&#160;6.7.&#160;The DraTeX Input for ">Example&#160;6.7</a>.</p>
-
- <div class="figure">
- <a id="fig.dratex" name="fig.dratex"></a>
-
- <p class="title"><b>Figure&#160;6.7.&#160;An DraTeX
- diagram</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <div class="example">
- <a id="ex.dratexsrc" name="ex.dratexsrc"></a>
-
- <p class="title"><b>Example&#160;6.7.&#160;The DraTeX
- Input for <a href="ch06.html#fig.dratex"
- title="Figure&#160;6.7.&#160;An DraTeX diagram">Figure&#160;6.7</a></b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="tex.06.07.tex"></a>
-</pre>
- </div>
-
- <p>DraTeX offers a wide variety of low-level drawing
- commands: straight lines at arbitrary angles, circles of
- any size, bezier curves, rectangular or polar coordinate
- systems, perspective for three-dimensional figures,
- user-definable shading patterns, clipping, repetition,
- and user-definable drawing objects and commands. A
- supporting package, AlDraTeX<a id="id2892187"
- class="indexterm" name="id2892187"></a>, provides
- high-level drawing commands for pie charts, XY charts,
- bar charts, spread diagrams, grid diagrams, trees, and
- diagram annotations (arrows, edges, labels).</p>
-
- <p>Although it is a flexible and portable solution,
- beware that complex figures may require considerable time
- to compute and will almost certainly require a big TeX.
- The resulting <tt>DVI</tt> files tend to be large as
- well.</p>
-
- <p>DraTeX and AlDraTeX are described in <span
- class="emphasis"><em>TeX &amp; LaTeX: Drawing and
- Literate Programming</em></span>&#160;[<a
- href="bi01.html#eg:dratex">eg:dratex</a>].</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2892246"
- name="id2892246"></a>Using a Little Help</h2>
- </div>
- </div>
-
- <p>On most platforms, if you have TeX, MetaFont<a
- id="id2892255" class="indexterm" name="id2892255"></a> is
- available. Because MetaFont was designed for drawing, it
- has much better support for pictures and figures than TeX.
- There are three utilities that allow you to combine TeX and
- MetaFont to create pictures: <b>MFPic</b> and
- <b>Fig2MF</b>.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2892297"
- name="id2892297"></a>MFPic</h3>
- </div>
- </div>
-
- <p><b>MFPic</b>'s <tt>picture</tt> environment and
- LaTeX's <tt>picture</tt> environment are implemented very
- differently. The commands in <b>MFPic</b> don't attempt
- to typeset your diagram with special fonts; instead, they
- write MetaFont commands to another file. This file must
- be processed with MetaFont before your document can be
- viewed.</p>
-
- <p>Because MetaFont is used to draw the actual diagram,
- the <b>MFPic</b> macros are much more flexible than the
- LaTeX picture creation commands. <b>MFPic</b> macros
- provide lines (at any angle), rectangles, polygons,
- circles (of any size), ellipses, cyclic and acyclic
- curves, arcs, and wedges (all empty, shaded, or
- filled).</p>
-
- <p>Unlike <b>Fig2MF</b>, described below, <b>MFPic</b>
- can plot user-specified functions (parametrically or
- directly, using polygonal or bezier interpolation).</p>
-
- <p>Finally, because <b>MFPic</b> works so directly with
- TeX, it can include labels and captions in the figure as
- well as allowing &#8220;MetaFont hackers&#8221; to insert
- MetaFont code directly.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2892403"
- name="id2892403"></a>Fig2MF</h3>
- </div>
- </div>
-
- <p>The &#8220;Fig&#8221; in <b>Fig2MF</b><a
- id="id2892422" class="indexterm" name="id2892422"></a>
- stands for the Fig graphics code (in this case, Fig
- version 2.1). Fig is a device-independent way of
- representing figures. Like TeX <tt>DVI</tt> files, Fig
- graphics<a id="id2892446" class="indexterm"
- name="id2892446"></a> are always translated into a
- device-dependent form before they are printed.
- <b>Fig2MF</b> translates Fig graphics into MetaFont code,
- which can be rendered into a font that is usable by TeX
- on any platform.</p>
-
- <p>At present, there are a few limitations on
- <b>Fig2MF</b>: text objects are ignored, and arrowed and
- non-solid line styles are not supported. The advantage of
- <b>Fig2MF</b> is that very good interactive drawing
- programs, like <b>xfig</b>, can be used to create
- figures.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.tpic"
- name="sec.tpic"></a>MetaFont</h3>
- </div>
- </div>
-
- <p>If the idea of programming directly in MetaFont<a
- id="id2892507" class="indexterm" name="id2892507"></a> is
- appealing to you, start by reading &#8220;Simple Drawings
- in MetaFont&#8221;&#160;[<a
- href="bi01.html#zw:simple">zw:simple</a>]. This is a
- short document (freely available) that describes how
- simple drawings can easily be rendered directly in
- MetaFont.</p>
-
- <p>In order to use MetaFont creatively, <span
- class="emphasis"><em>The \MF{}book</em></span>&#160;[<a
- href="bi01.html#kn:mfbook">kn:mfbook</a>] is really a
- necessity, but you can get a feel for the picture
- creation process in MetaFont without it.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2892560"
- name="id2892560"></a>Using a Little More Help</h2>
- </div>
- </div>
-
- <p>A couple of TeX macro packages combine the convenience
- of using only TeX commands to produce pictures and figures
- with the power of PostScript<a id="id2892571"
- class="indexterm" name="id2892571"></a><a id="id2892581"
- class="indexterm" name="id2892581"></a>. Using these macros
- makes your documents less portable because they rely on a
- PostScript printer or PostScript interpreter to be
- printed.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.pictures.pstricks"
- name="sec.pictures.pstricks"></a>PSTricks</h2>
- </div>
- </div>
-
- <p>The PSTricks<a id="id2892610" class="indexterm"
- name="id2892610"></a><a id="id2892620" class="indexterm"
- name="id2892620"></a> macro package is a TeX-PostScript
- hybrid. The advantage of this approach is that PSTricks is
- able to provide much wider functionality than the preceding
- packages without leaving TeX. The disadvantage is that it
- makes your documents dependent on a PostScript printer.</p>
-
- <p>One of the neatest features of PSTricks is the ability
- to interact with other TeX objects. You can add PostScript
- annotations (curved lines, labels, etc.) to the entries in
- a table, for example, or point to other elements on the
- page.</p>
-
- <p>In addition to allowing you to insert essentially
- arbitrary PostScript commands directly into your document,
- PSTricks provides TeX macros for most common picture
- elements including: commands for curved and straight lines
- (at arbitrary angles), a wide variety of arrow heads and
- tails, pattern-filled regions, regular and irregular
- polygonal shapes, text scaling and rotation, and grids.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2892664"
- name="id2892664"></a>TeXdraw</h2>
- </div>
- </div>
-
- <p>TeXdraw, like \product{\PSTricks}, provides support for
- pictures and figures by relying on a PostScript back
- end.</p>
-
- <p>TeXdraw<a id="id2892679" class="indexterm"
- name="id2892679"></a><a id="id2892688" class="indexterm"
- name="id2892688"></a> is organized into a toolbox of simple
- routines from which more complex commands can be
- constructed. The TeXdraw manual&#160;[<a
- href="bi01.html#pk:texdraw">pk:texdraw</a>] includes
- several examples of how complex commands can be built from
- toolbox routines.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2892716"
- name="id2892716"></a>tpic</h2>
- </div>
- </div>
-
- <p>The &#8220;pic&#8221;<a id="id2892728" class="indexterm"
- name="id2892728"></a> drawing language was designed for
- <b>troff</b> documents. The <b>tpic</b><a id="id2892749"
- class="indexterm" name="id2892749"></a><a id="id2892756"
- class="indexterm" name="id2892756"></a><a id="id2892766"
- class="indexterm" name="id2892766"></a> program interprets
- pic drawings and produces TeX output to render them. The
- output relies on a set of \special commands, which must be
- implemented by the DVI driver to actually produce the
- output. The <b>tpic</b> \specials are implemented by many
- DVI drivers.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.scaleformat" name="sec.scaleformat"></a>Using a
- Lot of Help</h2>
- </div>
- </div>
-
- <p>Although many nice effects can be achieved directly in
- TeX or with MetaFont, you will probably want to include
- some other form of image (e.g., an encapsulated PostScript
- figure or a scanned photograph) in a TeX document
- eventually.</p>
-
- <p>There are a myriad of choices when this occurs. To a
- large extent, the options available depend on the kind of
- printer you have, which DVI drivers you use, and to what
- extent you are willing to sacrifice device
- independence.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2892815"
- name="id2892815"></a>Electronic Cut-and-paste</h3>
- </div>
- </div>
-
- <p>Documents<a id="id2892828" class="indexterm"
- name="id2892828"></a> that require complex graphics may
- be difficult to produce as a single TeX document. You may
- exceed the memory limitations of your version of TeX if
- you try to put too many figures on a given page, or you
- may wish to include graphics from incompatible macro
- packages (suppose you are using the Lollipop format for
- example, and you want to include a LaTeX
- <tt>picture</tt>).</p>
-
- <p>You can always leave blank space in your document,
- print the graphic on a separate page, and then combine
- the two pages with scissors, glue, and a photocopy
- machine. However, there are many times when this is
- inappropriate (not to mention the aesthetic sensibilities
- it may disturb).</p>
-
- <p>Another solution is to use a program that can perform
- cut-and-paste operations on the output files before they
- are printed. If you use Plain TeX or LamSTeX, one option
- is <b>DVIpaste</b><a id="id2892877" class="indexterm"
- name="id2892877"></a>. <b>DVIpaste</b> can insert parts
- of one <tt>DVI</tt> file into another. It is part of the
- LamSTeX distribution. The documentation for
- <b>DVIpaste</b> contains a good example of its use.
- Unfortunately, <b>DVIpaste</b> relies on macros that are
- incompatible with most other macro packages.</p>
-
- <p>Some DVI drivers like <b>dvimsp</b><a id="id2892928"
- class="indexterm" name="id2892928"></a>,<sup>[<a
- id="id2892937" name="id2892937"
- href="#ftn.id2892937">81</a>]</sup> which comes with
- emTeX, can translate <tt>DVI</tt> files into bitmapped
- images that can then be incorporated into your document
- directly. Figures&#160;<a href="ch04.html#fig.caffeine"
- title="Figure&#160;4.11.&#160;Caffeine by ChemTeX">Figure&#160;4.11</a>,
- <a href="ch04.html#fig.lithium"
- title="Figure&#160;4.13.&#160;A lithium cation rendered by ChemStruct">
- Figure&#160;4.13</a>, and &#160;<a
- href="ch04.html#fig.mozart"
- title="Figure&#160;4.15.&#160;A little Mozart&#8230;">Figure&#160;4.15</a>
- in Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>,
- were inserted into this book using <b>dvidot</b><a
- id="id2893022" class="indexterm"
- name="id2893022"></a>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2893032"
- name="id2893032"></a>Scalable Image Formats</h3>
- </div>
- </div>
-
- <p>Several of the most commonly encountered scalable
- image formats are PostScript (usually encapsulated)<a
- id="id2893044" class="indexterm" name="id2893044"></a><a
- id="id2893054" class="indexterm" name="id2893054"></a>,
- HPGL (Hewlett-Packard's<a id="id2893063"
- class="indexterm" name="id2893063"></a> Plotter
- language), DXF (Autocad's vector format)<a id="id2893072"
- class="indexterm" name="id2893072"></a>, and the Fig
- graphics<a id="id2893081" class="indexterm"
- name="id2893081"></a> language. PostScript and HPGL are
- used by specific printers and plotters, DXF files are
- created by many computer-aided design programs, and Fig
- is a graphic language understood by several free editing
- tools---it is always converted into something else before
- it is printed. Many programs that can edit scalable
- images have their own vendor-specific formats. Luckily,
- these programs can usually produce PostScript or HPGL
- output as well.</p>
-
- <p>PostScript images are the most commonly encountered
- scalable images. Drawing packages that output PostScript
- generally produce <span class="emphasis"><em>encapsulated
- PostScript</em></span> (EPS)<a id="id2893109"
- class="indexterm" name="id2893109"></a><a id="id2893117"
- class="indexterm" name="id2893117"></a>. Similarly, most
- PostScript clip-art is distributed in EPS format.
- Encapsulated PostScript is a subset of the PostScript
- language. One of the most important features of EPS
- images is a <span class="emphasis"><em>bounding
- box</em></span><a id="id2893135" class="indexterm"
- name="id2893135"></a><a id="id2893145" class="indexterm"
- name="id2893145"></a>. The bounding box identifies the
- size of the EPS image. This information is used to
- determine the scaling factor required to get an image of
- the correct size.</p>
-
- <p>Generic PostScript can sometimes be converted into
- encapsulated PostScript. For example, the
- <b>ps2epsi</b><a id="id2893170" class="indexterm"
- name="id2893170"></a> program that comes with
- <b>Ghostscript</b><a id="id2893185" class="indexterm"
- name="id2893185"></a> attempts to convert generic
- PostScript into encapsulated PostScript.</p>
-
- <p>Some software produces reasonable PostScript figures,
- but fails to include the bounding box. For those
- situations, the <b>bbfig</b><a id="id2893206"
- class="indexterm" name="id2893206"></a> program that
- comes with <b>dvips</b> may help. <b>bbfig</b> uses the
- printer to calculate a bounding box that you can insert
- into the figure. After you have printed the figure, you
- can construct a bounding box by hand, if necessary
- (sometimes <b>bbfig</b> gets confused). Simply measure
- the height and width of the figure and its position on
- the page (measured from the bottom-left corner). The
- bounding box is a rectangle measured from the lower-left
- corner of the figure to the upper-right corner. An
- example is shown in Figure&#160;<a
- href="ch06.html#fig.epsbox"
- title="Figure&#160;6.8.&#160;A PostScript bounding box example">
- Figure&#160;6.8</a>.</p>
-
- <div class="figure">
- <a id="fig.epsbox" name="fig.epsbox"></a>
-
- <p class="title"><b>Figure&#160;6.8.&#160;A PostScript
- bounding box example</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>The bounding box is measured in PostScript points.
- There are 72 PostScript points to the inch, so the image
- in Figure&#160;<a href="ch06.html#fig.epsbox"
- title="Figure&#160;6.8.&#160;A PostScript bounding box example">
- Figure&#160;6.8</a> has the following bounding box:</p>
-
- <div class="informalexample">
- <p>&lt;!-- %BoundingBox: 115.2 180 468 626.4 --&gt;</p>
- </div>
-
- <p>If you are printing your document on a PostScript
- printer, you will find that PostScript images are easy to
- handle; every PostScript DVI driver that I have seen
- allows you to incorporate encapsulated PostScript with
- one or more \special commands. The section &#8220;<a
- href="ch06.html#sec.incps"
- title="Bitmapped Image Formats">the section called
- &#8220;Bitmapped Image Formats&#8221;</a>&#8221; later in
- this chapter describes two ways of incorporating
- encapsulated PostScript images into Plain TeX or LaTeX
- documents for printing on a PostScript printer.</p>
-
- <p>PostScript output on non-PostScript devices is much
- more difficult, although it can be achieved with a
- PostScript interpreter like <b>Ghostscript</b>.<sup>[<a
- id="id2893346" name="id2893346"
- href="#ftn.id2893346">82</a>]</sup> For a detailed
- description of how PostScript images can be converted
- into another format with <b>Ghostscript</b>, see the
- &#8220;<a href="ch06.html#sec.gs"
- title="Image Magick">the section called &#8220;Image
- Magick&#8221;</a>&#8221; section later in this
- chapter.</p>
-
- <p>Hewlett-Packard HPGL<a id="id2893388"
- class="indexterm" name="id2893388"></a> is the plotter
- language developed by HP for its line of pen-based
- plotting devices. Many computer-aided design and drafting
- programs can produce HPGL. In addition to plotters, the
- HP LaserJet III and more recent HP LaserJet printers also
- understand HPGL. On an HP LaserJet III or later model
- printer, you can print HPGL directly if your DVI driver
- allows you to include printer-specific data. This ability
- was introduced in version 1.4t of the emTeX
- <b>dvihplj</b><a id="id2893402" class="indexterm"
- name="id2893402"></a> driver.</p>
-
- <p>If your DVI driver does not support printer-specific
- files or your printer does not understand HPGL, there are
- at least two conversion programs (<b>hp2xx</b><a
- id="id2893432" class="indexterm" name="id2893432"></a>
- and <b>hp2ps</b><a id="id2893446" class="indexterm"
- name="id2893446"></a>) that may be able to convert your
- HPGL drawings into another form you can use.</p>
-
- <p>The Fig graphics language was designed to represent
- pictures and figures in an easy to interpret and portable
- manner. The <b>Fig</b><a id="id2893467" class="indexterm"
- name="id2893467"></a> and <b>xfig</b><a id="id2893481"
- class="indexterm" name="id2893481"></a> drawing programs
- work with Fig graphics<a id="id2893490" class="indexterm"
- name="id2893490"></a>. Several other programs, like
- <b>gnuplot</b><a id="id2893505" class="indexterm"
- name="id2893505"></a>, can also produce Fig graphics. See
- the &#8220;<a href="ch06.html#sec.Fig"
- title="The epic and eepic styles">the section called
- &#8220;The epic and eepic styles&#8221;</a>&#8221;
- section for more information.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.incps"
- name="sec.incps"></a>Bitmapped Image Formats</h3>
- </div>
- </div>
-
- <p>Including bitmapped images<a id="id2893540"
- class="indexterm" name="id2893540"></a> is easier than
- including scalable images because no real interpretation
- of commands is necessary. Over the years, lots of
- different ways have been developed for including
- bitmapped images in TeX documents. Since the development
- of the <b>bm2font</b> program, most of these methods have
- become obsolete. As a result, this section examines only
- a few methods.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2893563"
- name="id2893563"></a>DVI driver {\ttbackslash
- special}</h4>
- </div>
- </div>
-
- <p>The first method is DVI driver-specific: if your DVI
- driver includes a \special command for including
- bitmapped graphic images, you can simply use that
- command. The disadvantage of using a DVI driver
- \special is that it makes the document less portable.
- Instead of being printable with any DVI driver, it now
- requires a DVI driver that recognizes a particular
- \special command. Note also that some DVI drivers do
- not handle color images very well; you may need to
- convert the image to black and white first. (Many
- programs described in the &#8220;<a
- href="ch06.html#sec.picconv"
- title="Manipulating Images">the section called
- &#8220;Manipulating Images&#8221;</a>&#8221; section
- later in this chapter can perform this operation.)</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2893598"
- name="id2893598"></a>bm2font</h4>
- </div>
- </div>
-
- <p>On most platforms, <b>bm2font</b><a id="id2893612"
- class="indexterm" name="id2893612"></a> provides an
- ideal solution for including bitmapped images. This
- program translates bitmapped images into <tt>PK</tt><a
- id="id2893630" class="indexterm" name="id2893630"></a>
- fonts and produces a snippet of TeX code that can be
- used to print the image in your document. Because most
- DVI drivers can use <tt>PK</tt> fonts, a high degree of
- portability is maintained. Some portability is still
- lost since the bitmapped image has a fixed resolution,
- but that is a consequence of using the bitmapped image,
- not <b>bm2font</b>. All of the bitmap images in this
- book were included with the <b>bm2font</b> program.</p>
-
- <p>This book is a good example of an instance where
- portability is required. I could easily have included
- the graphics with the \special command of the DVI
- driver that I use most frequently (<b>dvihplj</b>), but
- then I couldn't have produced pages suitable for final
- publication.</p>
-
- <p><b>bm2font</b> can read a number of common graphic
- image formats including <tt>GIF</tt><a id="id2893714"
- class="indexterm" name="id2893714"></a>, Windows
- <tt>BMP</tt><a id="id2893731" class="indexterm"
- name="id2893731"></a>, and <tt>PCX</tt><a
- id="id2893753" class="indexterm" name="id2893753"></a>.
- It can translate color images into black and white
- using a number of dithering<a id="id2893763"
- class="indexterm" name="id2893763"></a> methods, and it
- can scale the image to a specific size (although
- scaling bitmap images is not usually very
- effective).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2893776"
- name="id2893776"></a>pbmtopk</h4>
- </div>
- </div>
-
- <p>The <b>pbmtopk</b><a id="id2893790"
- class="indexterm" name="id2893790"></a> program
- provides a solution similar to <b>bm2font</b>. Because
- <b>pbmtopk</b><a id="id2893812" class="indexterm"
- name="id2893812"></a> is a smaller program, it may be
- easier to port to other systems. The <b>pbmtopk</b>
- distribution includes <b>pktopbm</b><a id="id2893834"
- class="indexterm" name="id2893834"></a>, which can
- translate <tt>PK</tt> files back into <tt>PBM</tt><a
- id="id2893860" class="indexterm" name="id2893860"></a>
- bitmaps.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2893872"
- name="id2893872"></a>Inserting PostScript Images into
- TeX</h3>
- </div>
- </div>
-
- <p>If you are using Plain TeX or LaTeX and printing your
- documents on a PostScript printer<a id="id2893883"
- class="indexterm" name="id2893883"></a>, there are
- several (essentially equivalent) style files that you can
- use to include your figures.</p>
-
- <p>One is <tt>epsfig.sty</tt><a id="id2893906"
- class="indexterm" name="id2893906"></a>, which can be
- used as a LaTeX style option or be inserted directly into
- Plain TeX documents with \input.<sup>[<a id="id2893914"
- name="id2893914" href="#ftn.id2893914">83</a>]</sup> The
- <tt>epsfig</tt> style option is supported by LaTeX2e as
- well.</p>
-
- <p>After the style file is loaded, you can use the macro
- \epsfig to include your figure. The complete syntax for
- \epsfig is:</p>
-<pre class="screen">
- \epsfig{figure=, height=, width=, rheight=, rwidth=,
- bbllx=, bblly=, bburx=, bbury=,
- clip=, angle=, silent=}
-</pre>
-
- <p>In practice, only a few of these options are commonly
- used. Here is a description of each:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><tt>figure=</tt></span></dt>
-
- <dd>
- <p>Identifies the name of the file containing the
- PostScript figure. This option is required.</p>
- </dd>
-
- <dt><span class="term"><tt>height=,
- width=</tt></span></dt>
-
- <dd>
- <p>Specify the height and width of the figure. If
- only one is specified, the other will be scaled
- automatically to keep the proportions of the
- original figure. If both are given, the figure will
- be scaled (anamorphically) to the requested
- size.</p>
- </dd>
-
- <dt><span class="term"><tt>rheight=,
- rwidth=</tt></span></dt>
-
- <dd>
- <p>Provide the &#8220;reserved&#8221; height and
- width of the figure. This is how big the TeX box
- that encloses the figure will be. By default, the
- box is as big as the figure.</p>
- </dd>
-
- <dt><span class="term"><tt>bbllx=, bblly=, bburx=,
- bbury=</tt></span></dt>
-
- <dd>
- <p>Specify the bounding box<a id="id2894103"
- class="indexterm" name="id2894103"></a> of the
- figure. If not specified (it usually isn't), the
- bounding box is read from the PostScript
- figure.</p>
- </dd>
-
- <dt><span class="term"><tt>clip=</tt></span></dt>
-
- <dd>
- <p>Indicates whether or not the figure should be
- &#8220;clipped&#8221; at its bounding box. Clipping
- prevents lines in the figure from extending beyond
- the bounding box.</p>
- </dd>
-
- <dt><span class="term"><tt>angle=</tt></span></dt>
-
- <dd>
- <p>Allows you to specify that the figure should be
- rotated. Always specify the angle of rotation in
- degrees. The figure is always rotated
- counter-clockwise.</p>
- </dd>
-
- <dt><span class="term"><tt>silent=</tt></span></dt>
-
- <dd>
- <p>Turns off informative messages printed by the
- macros as the figure is processed.</p>
- </dd>
- </dl>
- </div>
-
- <p>The parameters to the \epsfig macro have to obey TeX's
- strict parsing rules. In particular, you must not put
- spaces around the equal sign in any option. The
- <tt>clip=</tt> and <tt>silent=</tt> options have no
- values, but you must include the equal sign anyway.</p>
-
- <p>For example, Figure&#160;<a
- href="ch06.html#fig.psfigure"
- title="Figure&#160;6.9.&#160;An example of an encapsulated figure">
- Figure&#160;6.9</a> was inserted by \epsfig using the
- following commands:</p>
-<pre class="screen">
-\begin{figure}
- \epsfig{figure=figs/sample.eps}
- \caption{An example of an encapsulated figure.}
- \label{fig.psfigure}
-\end{figure}
-</pre>
- <a id="id2894252" class="indexterm" name="id2894252"></a>
-
- <div class="figure">
- <a id="fig.psfigure" name="fig.psfigure"></a>
-
- <p class="title"><b>Figure&#160;6.9.&#160;An example of
- an encapsulated figure</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>Figure&#160;<a href="ch06.html#fig.psfigurerot"
- title="Figure&#160;6.10.&#160;Another example of an encapsulated figure (resized and rotated)">
- Figure&#160;6.10</a> demonstrates a few of other
- <tt>epsfig</tt> options:</p>
-<pre class="screen">
-\begin{figure}
- \epsfig{figure=figs/sample.eps,width=6cm,angle=45}
- \caption{Another example of an encapsulated figure
- (resized and rotated)}
- \label{fig.psfigurerot}
-\end{figure}
-</pre>
- <a id="id2894324" class="indexterm" name="id2894324"></a>
-
- <div class="figure">
- <a id="fig.psfigurerot" name="fig.psfigurerot"></a>
-
- <p class="title"><b>Figure&#160;6.10.&#160;Another
- example of an encapsulated figure (resized and
- rotated)</b></p>
-
- <div class="mediaobject">
- <img src="figs/tex.06.09.eps" />
- </div>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.picconv" name="sec.picconv"></a>Manipulating
- Images</h2>
- </div>
- </div>
-
- <p>There are literally dozens of software packages
- available for manipulating graphic images<a id="id2894380"
- class="indexterm" name="id2894380"></a>. The discussion
- that follows focuses on a small handful of these programs.
- The programs selected are representative of the kinds of
- tools available, but this is by no means an endorsement
- that these are the best tools. Table&#160;<a
- href="ch06.html#tab.manipover"
- title="Table&#160;6.1.&#160;Graphics Manipulation Packages">
- Table&#160;6.1</a> summarizes the programs described in
- this section.</p>
-
- <p>If you cannot find any way of converting a particular
- image, remember that you may be able to display the image
- and capture it with another program that can save the image
- in a more tractable format.</p>
-
- <div class="table">
- <a id="tab.manipover" name="tab.manipover"></a>
-
- <p class="title"><b>Table&#160;6.1.&#160;Graphics
- Manipulation Packages</b></p>
-
- <table summary="Graphics Manipulation Packages"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Program</th>
-
- <th align="left">\bf Platforms</th>
-
- <th align="left">\bf Cost</th>
-
- <th align="left">\bf Purpose</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">Image Magick</td>
-
- <td align="left">unix</td>
-
- <td align="left">Free</td>
-
- <td align="left">Display, manipulate, convert and
- capture images</td>
- </tr>
-
- <tr>
- <td align="left">PBMplus</td>
-
- <td align="left">All</td>
-
- <td align="left">Free</td>
-
- <td align="left">Convert and manipulate images</td>
- </tr>
-
- <tr>
- <td align="left">xv</td>
-
- <td align="left">unix</td>
-
- <td align="left">SW${}^1$</td>
-
- <td align="left">Display, manipulate, convert and
- capture images</td>
- </tr>
-
- <tr>
- <td align="left">xloadimage</td>
-
- <td align="left">unix</td>
-
- <td align="left">Free</td>
-
- <td align="left">Display images</td>
- </tr>
-
- <tr>
- <td align="left">Image Alchemy</td>
-
- <td align="left">MS-DOS${}^2$</td>
-
- <td align="left">SW</td>
-
- <td align="left">Convert images</td>
- </tr>
-
- <tr>
- <td align="left">ColorView</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">SW</td>
-
- <td align="left">Convert images</td>
- </tr>
-
- <tr>
- <td align="left">Jpeg4</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">SW</td>
-
- <td align="left">Convert images</td>
- </tr>
-
- <tr>
- <td align="left">pmjpeg</td>
-
- <td align="left">OS/2</td>
-
- <td align="left">SW</td>
-
- <td align="left">Display and convert images</td>
- </tr>
-
- <tr>
- <td align="left">txt2pcx</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">SW</td>
-
- <td align="left">Translate text into graphic image
- format</td>
- </tr>
-
- <tr>
- <td align="left">Ghostscript</td>
-
- <td align="left">All</td>
-
- <td align="left">Free</td>
-
- <td align="left">Convert PostScript to other
- formats</td>
- </tr>
-
- <tr>
- <td align="left">GoScript</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">\$\$${}^3$</td>
-
- <td align="left">Convert PostScript to other
- formats</td>
- </tr>
-
- <tr>
- <td align="left">hp2xx</td>
-
- <td align="left">unix</td>
-
- <td align="left">Free</td>
-
- <td align="left">Convert HPGL to other formats</td>
- </tr>
-
- <tr>
- <td align="left">\multicolumn{4}{l}{ ${}^1$\vrule
- height11pt width0pt\tiny Shareware: &#8220;Try
- before you buy,&#8221; but not free.}</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\multicolumn{4}{l}{ ${}^2$\tiny
- Also available for Sun workstations; see
- documentation.}</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.gs"
- name="sec.gs"></a>Image Magick</h3>
- </div>
- </div>
-
- <p><b>Image Magick<a id="id2894787" class="indexterm"
- name="id2894787"></a></b> is a collection of eight
- programs for manipulating images. These programs work
- with MIFF files<a id="id2894797" class="indexterm"
- name="id2894797"></a> by default. MIFF is the
- &#8220;machine-independent file format&#8221; developed
- by the package's author. If you are going to manipulate
- images with these tools, the author recommends converting
- them to MIFF format first. The <b>convert</b> program
- reads and writes a large number of image formats, so
- conversion to and from MIFF format is
- straightforward.</p>
-
- <p><b>Image Magick</b> requires the Independent JPEG
- Group<a id="id2894834" class="indexterm"
- name="id2894834"></a>'s JPEG library in order to
- manipulate JPEG images. Similarly, Sam Leffler<a
- id="id2894844" class="indexterm" name="id2894844"></a>'s
- TIFF software library is required to manipulate TIFF<a
- id="id2894854" class="indexterm" name="id2894854"></a>
- images. Both of these are compile-time options. If you
- did not build <b>Image Magick</b>, you may not be able to
- manipulate JPEG or TIFF images. To manipulate PostScript
- images, <b>Ghostscript</b> must be available.</p>
-
- <p>The programs described below are the <b>Image
- Magick</b> tools that allow you to manipulate images in
- ways that may be necessary or useful for creating
- printable images. Other tools, like <b>animate</b><a
- id="id2894899" class="indexterm" name="id2894899"></a>,
- included in the <b>Image Magick</b> distribution, aren't
- described here because they have no bearing on
- printability.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><b>display</b></span></dt>
-
- <dd>
- <p>This program<a id="id2894938" class="indexterm"
- name="id2894938"></a> allows you to preview images
- on an X11 display. The number of colors in the
- image is reduced to match the number of colors of
- your display, if necessary. Program options allow
- you to specify a variety of image-processing
- operations on the image (noise reduction, scaling,
- manipulation of the color map, etc.).</p>
-
- <p>Conversion to MIFF format, as recommended above,
- isn't necessary for simply displaying the
- image.</p>
- </dd>
-
- <dt><span class="term"><b>import</b></span></dt>
-
- <dd>
- <p>This program<a id="id2894981" class="indexterm"
- name="id2894981"></a> allows you to capture visible
- portions of an X11 display. You can capture any
- visible window, the entire display, or any
- rectangular portion of the display. <b>import</b>
- can save the image in any format recognized by
- <b>convert</b>.</p>
- </dd>
-
- <dt><span class="term"><b>convert</b></span></dt>
-
- <dd>
- <p>As the name implies, this utility<a
- id="id2895033" class="indexterm"
- name="id2895033"></a> converts images between
- graphics formats. The following standard formats
- are recognized:</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>MIFF</td>
-
- <td>BMP</td>
-
- <td>CMYK</td>
-
- <td>EPS</td>
-
- <td>FAX</td>
-
- <td>GIF</td>
-
- <td>IRIS</td>
-
- <td>JPEG</td>
-
- <td>PICT</td>
-
- <td>PNM</td>
- </tr>
-
- <tr>
- <td>PS</td>
-
- <td>RGB</td>
-
- <td>RLE</td>
-
- <td>SUN</td>
-
- <td>TGA</td>
-
- <td>TEXT</td>
-
- <td>TIFF</td>
-
- <td>XBM</td>
-
- <td>XWD</td>
-
- <td>&#160;</td>
- </tr>
- </table>
-
- <p>Additionally, a few less-standard formats are
- recognized. A complete list is available in the
- manual page for <b>convert</b>.</p>
- </dd>
-
- <dt><span class="term"><b>combine</b></span></dt>
-
- <dd>
- <p>This program combines<a id="id2895167"
- class="indexterm" name="id2895167"></a> two images
- by blending them together. The result varies
- tremendously, depending on the kind of blending
- used. Simple overlaps, various kinds of cutouts,
- and more complex color blendings are possible.</p>
- </dd>
-
- <dt><span class="term"><b>montage</b></span></dt>
-
- <dd>
- <p>Unlike <b>combine</b>, <b>montage</b><a
- id="id2895217" class="indexterm"
- name="id2895217"></a> combines multiple images by
- <span class="emphasis"><em>tiling<a id="id2895229"
- class="indexterm"
- name="id2895229"></a></em></span>. (The images are
- laid next to each other rather than on top of each
- other.) Optionally, the image name can appear below
- each tile.</p>
- </dd>
-
- <dt><span class="term"><b>mogrify</b></span></dt>
-
- <dd>
- <p><b>mogrify</b><a id="id2895268"
- class="indexterm" name="id2895268"></a> is used to
- transform an image (or series of images). You can
- specify alternate color maps in a variety of ways,
- as well as dithering<a id="id2895280"
- class="indexterm" name="id2895280"></a> and error
- correcting transformations. The images can also be
- rolled, rotated, rescaled, and sheared. (Shearing<a
- id="id2895290" class="indexterm"
- name="id2895290"></a> transforms a rectangle into a
- parallelogram by shifting the X or Y axis.)</p>
- </dd>
- </dl>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2895306"
- name="id2895306"></a>PBMplus</h3>
- </div>
- </div>
-
- <p>The <b>PBMplus<a id="id2895320" class="indexterm"
- name="id2895320"></a></b> package is a large collection
- of image translation programs. This package was written
- originally for unix, but has since been ported to MS-DOS
- and OS/2.</p>
-
- <p><b>PBMplus</b> defines three file formats<a
- id="id2895342" class="indexterm" name="id2895342"></a><a
- id="id2895350" class="indexterm" name="id2895350"></a><a
- id="id2895357" class="indexterm"
- name="id2895357"></a>:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>PBM---The Portable Bitmap format for black and
- white images</p>
- </li>
-
- <li>
- <p>PGM---The Portable Graymap format for grayscaled
- images</p>
- </li>
-
- <li>
- <p>PPM---The Portable Pixmap format for color
- images</p>
- </li>
- </ul>
- </div>
- <br />
- <br />
-
- <p>Translation from one format to another is accomplished
- by translating into the appropriate portable format
- first, and then translating the portable bitmap into the
- destination format.</p>
-
- <p>The following image formats are supported by the
- PBMPlus tools:</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>Abekas YUV bytes</td>
-
- <td>MGR bitmaps</td>
- </tr>
-
- <tr>
- <td>Andrew Toolkit raster objects</td>
-
- <td>MTV or PRT ray traced images</td>
- </tr>
-
- <tr>
- <td>Atari Degas .pi1 images</td>
-
- <td>MacPaint files</td>
- </tr>
-
- <tr>
- <td>Atari Degas .pi3 files</td>
-
- <td>Macintosh PICT files</td>
- </tr>
-
- <tr>
- <td>Atari Spectrum files</td>
-
- <td>PCX files</td>
- </tr>
-
- <tr>
- <td>AutoCAD slides</td>
-
- <td>PostScript &#8220;images&#8221;</td>
- </tr>
-
- <tr>
- <td>Bennet Yee &#8220;faces&#8221;</td>
-
- <td>QRT ray tracer files</td>
- </tr>
-
- <tr>
- <td>CMU window manager bitmaps</td>
-
- <td>Raw grayscale bytes</td>
- </tr>
-
- <tr>
- <td>Doodle brush files</td>
-
- <td>Raw RGB bytes</td>
- </tr>
-
- <tr>
- <td>FITS files</td>
-
- <td>Sun icons</td>
- </tr>
-
- <tr>
- <td>GIF files</td>
-
- <td>Sun rasterfiles</td>
- </tr>
-
- <tr>
- <td>Gould scanner files</td>
-
- <td>TIFF images</td>
- </tr>
-
- <tr>
- <td>Group 3 faxes</td>
-
- <td>TrueVision Targa files</td>
- </tr>
-
- <tr>
- <td>HIPS files</td>
-
- <td>Usenix FaceSaver(tm) images</td>
- </tr>
-
- <tr>
- <td>HP PaintJet files</td>
-
- <td>X10/X11 window dumps</td>
- </tr>
-
- <tr>
- <td>IFF ILBM files</td>
-
- <td>X11 pixmaps</td>
- </tr>
-
- <tr>
- <td>IMG (GEM) images</td>
-
- <td>XBM files</td>
- </tr>
-
- <tr>
- <td>Img-whatnot files</td>
-
- <td>Xim file</td>
- </tr>
-
- <tr>
- <td>Lisp Machine bitmaps</td>
-
- <td>&#160;</td>
- </tr>
- </table>
-
- <p>The <b>PBMplus</b> tools translate the image into the
- appropriate portable format (PBM, PGM, or PPM) depending
- on the nature of the image. Similarly, the tools can all
- work with &#8220;lower&#8221; formats. (PPM tools can
- work with PGM and PBM files, and PGM tools can work with
- PBM files.) For example, there is no
- &#8220;<b>pbmtopcx</b>,&#8221; however the
- <b>ppmtopcx</b><a id="id2895625" class="indexterm"
- name="id2895625"></a> tool will create a black and white
- PCX file if you use a PBM file as the input. Once
- converted into a portable format, the image can be
- translated back into (almost) any of the supported
- formats.</p>
-
- <p>In addition to image conversion, the PBMPlus tools
- include programs to perform a wide variety of image
- manipulations.</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>Apply Conway's rules of life</td>
-
- <td>Create a blank image</td>
- </tr>
-
- <tr>
- <td>Create a mask bitmap</td>
-
- <td>Reduce/enlarge an image</td>
- </tr>
-
- <tr>
- <td>Convert text into a bitmap</td>
-
- <td>Create a UPC bitmap</td>
- </tr>
-
- <tr>
- <td>Bentleyize a greymap</td>
-
- <td>Apply edge-detection</td>
- </tr>
-
- <tr>
- <td>Apply edge-enhancement</td>
-
- <td>Generate a histogram</td>
- </tr>
-
- <tr>
- <td>Normalize contrast</td>
-
- <td>Apply an &#8220;oil-painting&#8221; filter</td>
- </tr>
-
- <tr>
- <td>Create a &#8220;ramp&#8221;</td>
-
- <td>Generate textural features</td>
- </tr>
-
- <tr>
- <td>Perform bitwise arithmetic</td>
-
- <td>Perform MxN convolution</td>
- </tr>
-
- <tr>
- <td>Crop an image</td>
-
- <td>Cut/Paste rectangles</td>
- </tr>
-
- <tr>
- <td>Color-reduce</td>
-
- <td>Flip/rotate</td>
- </tr>
-
- <tr>
- <td>Apply gamma-correction</td>
-
- <td>Build a visual index</td>
- </tr>
-
- <tr>
- <td>Invert an image</td>
-
- <td>Add a border to an image</td>
- </tr>
-
- <tr>
- <td>Scale an image</td>
-
- <td>Shear an image</td>
- </tr>
-
- <tr>
- <td>Smooth an image</td>
-
- <td>Build a tiled image</td>
- </tr>
-
- <tr>
- <td>Colorize a graymap</td>
-
- <td>Dither color images</td>
- </tr>
-
- <tr>
- <td>Create fractal terrain</td>
-
- <td>Apply Laplacian-relief filter</td>
- </tr>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2895807"
- name="id2895807"></a>xv</h3>
- </div>
- </div>
-
- <p><b>xv</b><a id="id2895821" class="indexterm"
- name="id2895821"></a> is an interactive image
- viewing/converting tool that runs on X11 servers
- (including MS-DOS implementations of X11 such as
- Desqview/X).</p>
-
- <p>You can view GIF<a id="id2895837" class="indexterm"
- name="id2895837"></a>, PBM<a id="id2895845"
- class="indexterm" name="id2895845"></a>, XBM<a
- id="id2895854" class="indexterm" name="id2895854"></a>,
- Sun rasterfile<a id="id2895863" class="indexterm"
- name="id2895863"></a>, JPEG<a id="id2895871"
- class="indexterm" name="id2895871"></a>, and TIFF<a
- id="id2895880" class="indexterm" name="id2895880"></a>
- images. You can save any image in one of those formats or
- in encapsulated PostScript. In addition, you can capture
- any visible portion of the X11 server window
- interactively with <b>xv</b>.</p>
-
- <p>Like most of the tools described here, <b>xv</b>
- includes a number of image manipulation tools (cropping,
- scaling, editing the color map, etc.). If you try to view
- an image that is larger than your display, <b>xv</b>
- automatically scales it to fit. I find that <b>xv</b>'s
- interactive nature makes it easier to use for image
- manipulation than the command-driven tools.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2895932"
- name="id2895932"></a>xloadimage</h3>
- </div>
- </div>
-
- <p>The <b>xloadimage</b><a id="id2895946"
- class="indexterm" name="id2895946"></a> program is
- another X11 picture display tool. Like <b>xv</b> and
- <b>Image Magick</b>'s <b>display</b>, it has a number of
- picture manipulation options (although they are not
- interactive).</p>
-
- <p>One advantage of <b>xloadimage</b> is that it does not
- rescale images that are too large to fit within the
- display. Instead, it places them in a scrollable window.
- I find this behavior superior to <b>xv</b>'s solution of
- rescaling a very large image even though you are
- interested only in a small section of it.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2896003"
- name="id2896003"></a>Image Alchemy</h3>
- </div>
- </div>
-
- <p><b>Image Alchemy</b><a id="id2896018"
- class="indexterm" name="id2896018"></a> is a shareware
- tool for converting graphic images between various
- formats. Although the manual mentions a version for Sun
- workstations, I have only seen the MS-DOS version.</p>
-
- <p>Note that the unregistered shareware version of this
- program will only convert images which are 640$\times$480
- pixels or smaller.</p>
-
- <p>The following is a list of the graphic formats
- recognized by version 1.5 of <b>Image Alchemy</b>:</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>ADEX</td>
-
- <td>PCPAINT/Pictor Page Format</td>
- </tr>
-
- <tr>
- <td>Autologic</td>
-
- <td>PCX</td>
- </tr>
-
- <tr>
- <td>Binary Information Files (BIF)</td>
-
- <td>Portable BitMap (PBM)</td>
- </tr>
-
- <tr>
- <td>Encapsulated PostScript (EPS)</td>
-
- <td>Q0</td>
- </tr>
-
- <tr>
- <td>Erdas LAN/GIS</td>
-
- <td>QDV</td>
- </tr>
-
- <tr>
- <td>Freedom of the Press</td>
-
- <td>QRT</td>
- </tr>
-
- <tr>
- <td>GEM VDI Image File</td>
-
- <td>Scodl</td>
- </tr>
-
- <tr>
- <td>GIF</td>
-
- <td>Silicon Graphics Image</td>
- </tr>
-
- <tr>
- <td>HP Printer Command Language (PCL)</td>
-
- <td>Stork</td>
- </tr>
-
- <tr>
- <td>HP Raster Transfer Language (RTL)</td>
-
- <td>Sun Raster</td>
- </tr>
-
- <tr>
- <td>HSI JPEG</td>
-
- <td>TIFF</td>
- </tr>
-
- <tr>
- <td>HSI Palette</td>
-
- <td>Targa</td>
- </tr>
-
- <tr>
- <td>HSI Raw</td>
-
- <td>Utah Raster Toolkit (RLE)</td>
- </tr>
-
- <tr>
- <td>IFF/ILBM</td>
-
- <td>Vivid</td>
- </tr>
-
- <tr>
- <td>JPEG/JFIF</td>
-
- <td>Windows Bitmap (BMP)</td>
- </tr>
-
- <tr>
- <td>Jovian VI</td>
-
- <td>WordPerfect Graphic File</td>
- </tr>
-
- <tr>
- <td>Macintosh PICT/PICT2</td>
-
- <td>XBM</td>
- </tr>
-
- <tr>
- <td>MTV Ray Tracer</td>
-
- <td>XWD</td>
- </tr>
- </table>
-
- <p><b>Image Alchemy</b> can also perform a number of
- image manipulations like rescaling, cropping, and color
- map changes.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2896234"
- name="id2896234"></a>ColorView</h3>
- </div>
- </div>
-
- <p><b>ColorView<a id="id2896248" class="indexterm"
- name="id2896248"></a></b> is a shareware MS-DOS program
- for displaying and converting graphic images. Although
- designed to work with VESA SuperVGA adapters,
- <b>ColorView</b> can also work with plain VGA adapters.
- It does require a 80286 or a more powerful processor.</p>
-
- <p><b>ColorView</b> can read JPEG<a id="id2896279"
- class="indexterm" name="id2896279"></a>, GIF (87 and
- 89)<a id="id2896288" class="indexterm"
- name="id2896288"></a>, BMP<a id="id2896296"
- class="indexterm" name="id2896296"></a>, and RLE<a
- id="id2896310" class="indexterm" name="id2896310"></a>
- images. It can write GIF (87), 8-bit BMP, 24-bit BMP,
- JPEG, and RLE images. It can perform image translation
- without displaying the images, so a VGA or SuperVGA
- adapter is not required for translation.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2896325"
- name="id2896325"></a>Jpeg4</h3>
- </div>
- </div>
-
- <p>This<a id="id2896334" class="indexterm"
- name="id2896334"></a> is the Independent JPEG Group<a
- id="id2896343" class="indexterm" name="id2896343"></a>'s
- JPEG Software. The compression tool can convert GIF<a
- id="id2896353" class="indexterm" name="id2896353"></a>,
- PPM<a id="id2896361" class="indexterm"
- name="id2896361"></a>, and Targa (TGA)<a id="id2896370"
- class="indexterm" name="id2896370"></a> images into
- JPEG<a id="id2896379" class="indexterm"
- name="id2896379"></a> format. The decompression tool
- converts JPEG images into GIF, PPM (or PGM<a
- id="id2896389" class="indexterm" name="id2896389"></a>),
- or Targa formats.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2896400"
- name="id2896400"></a>pmjpeg</h3>
- </div>
- </div>
-
- <p>The <b>pmjpeg</b><a id="id2896415" class="indexterm"
- name="id2896415"></a> program is an OS/2 2.x program that
- can read and display JPEG<a id="id2896424"
- class="indexterm" name="id2896424"></a>, TIFF<a
- id="id2896433" class="indexterm" name="id2896433"></a>,
- Targa<a id="id2896441" class="indexterm"
- name="id2896441"></a>, GIF<a id="id2896450"
- class="indexterm" name="id2896450"></a>, PCX<a
- id="id2896459" class="indexterm" name="id2896459"></a>,
- and Windows<a id="id2896467" class="indexterm"
- name="id2896467"></a> or OS/2 BMP<a id="id2896482"
- class="indexterm" name="id2896482"></a> images. In
- addition, <b>pmjpeg</b> can write images in any of these
- formats except Windows BMP. <b>pmjpeg</b> can also
- capture all or part of the desktop. Some of the other
- features of <b>pmjpeg</b> are color map editing, contrast
- enhancement, image cropping, scaling, rotation, batch
- translation of images into JPEG format, cyclic slideshow
- presentations, and the ability to reduce an image to the
- system palette colors.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2896523"
- name="id2896523"></a>txt2pcx</h3>
- </div>
- </div>
-
- <p><b>txt2pcx</b><a id="id2896537" class="indexterm"
- name="id2896537"></a> is a memory-resident MS-DOS utility
- that captures text-mode screens as PCX graphic images.
- See the discussion of screen capturing in the &#8220;<a
- href="ch06.html#sec.screendump" title="GoScript">the
- section called &#8220;GoScript&#8221;</a>&#8221; section
- of this chapter for more information about why this is
- sometimes desirable.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2896564"
- name="id2896564"></a>Ghostscript</h3>
- </div>
- </div>
-
- <p><b>Ghostscript</b><a id="id2896577" class="indexterm"
- name="id2896577"></a> is distributed by the Free Software
- Foundation (FSF)<a id="id2896586" class="indexterm"
- name="id2896586"></a>. It is one of the few freely
- available programs that can convert PostScript images
- into other formats.</p>
-
- <p><b>Ghostscript</b> is a (mostly) complete PostScript<a
- id="id2896608" class="indexterm" name="id2896608"></a>
- interpreter. Converting an entire page of PostScript into
- another format is straightforward with
- <b>Ghostscript</b>. The following example converts the
- PostScript file <tt>file.ps</tt> into a monochrome GIF<a
- id="id2896637" class="indexterm" name="id2896637"></a>
- image called <tt>image1.gif</tt>:</p>
-<pre class="screen">
-\$ <span
-class="bold"><b>gs -r300 -sDEVICE=gifmono -sOutputFile=image1.gif file.ps</b></span>
-
-</pre>
- <br />
- <br />
-
- <p>The parameter <span
- class="emphasis"><em>-r300</em></span> indicates that
- <b>Ghostscript</b> should generate output at a resolution
- of 300dpi. This controls the size of the bitmap. If you
- plan to print the resulting bitmap, you should specify
- the same resolution as your printer. If <tt>file.ps</tt>
- contains more than one page, you can use a <tt>&lt;!--
- d</tt> in the output file's name to identify how multiple
- pages --&gt; should be handled. For example, if
- <tt>file.ps</tt> contains three pages, the following
- command will extract the first page into
- <tt>image1.gif</tt>, the second page into
- <tt>image2.gif</tt>, and the third page into
- <tt>image3.gif</tt>:<sup>[<a id="id2896732"
- name="id2896732" href="#ftn.id2896732">84</a>]</sup></p>
-<pre class="screen">
-\$ <span
-class="bold"><b>gs -r300 -sDEVICE=gifmono -sOutputFile=image\%d.gif file.ps</b></span>
-
-</pre>
- \vskip-\baselineskip <br />
- <br />
-
- <p>For incorporating images into TeX, it is more common
- to convert an encapsulated PostScript (EPS)<a
- id="id2896761" class="indexterm" name="id2896761"></a><a
- id="id2896769" class="indexterm" name="id2896769"></a><a
- id="id2896779" class="indexterm" name="id2896779"></a>
- image into a bitmapped format than it is to convert
- entire pages. Encapsulated PostScript is described
- earlier in this chapter in the section &#8220;<a
- href="ch06.html#sec.scaleformat"
- title="Using a Lot of Help">the section called
- &#8220;Using a Lot of Help&#8221;</a>.&#8221; It is
- slightly more difficult to convert encapsulated
- PostScript because of the bounding box<a id="id2896806"
- class="indexterm" name="id2896806"></a>. To convert this
- into a bitmap of exactly the right size, you have to tell
- <b>Ghostscript</b> to move the image to the upper-left
- corner of the page (where <b>Ghostscript</b> always
- begins its conversion) and tell it how big the image is
- in pixels.</p>
-
- <p>The following steps are necessary to produce exactly
- the right size bitmap of the encapsulated PostScript
- figure:</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>Find the size of the bounding box. Examine the
- PostScript file using a text editor. Find the line
- that begins with <tt>&lt;!-- % BoundingBox:</tt>
- --&gt; followed by four numbers. Those numbers are
- the lower-left x-coordinate (llx), the lower-left
- y-coordinate (lly), the upper-right x-coordinate
- (urx), and the upper-right y-coordinate (ury),
- respectively.</p>
- </li>
-
- <li>
- <p>Create another file called <tt>trans.ps</tt>
- that contains the single line:</p>
-<pre class="screen">
-<span class="emphasis"><em>llx</em></span> neg <span
-class="emphasis"><em>lly</em></span> neg translate
-</pre>
- </li>
-
- <li>
- <p>Calculate the width of the bounding box:
- $width_{bb} = urx - llx$.</p>
- </li>
-
- <li>
- <p>The width you have just calculated is the width
- at 72dpi. To convert this to the resolution that
- you will be using, multiply by the resolution and
- divide by 72. For example, if you will be printing
- at 300dpi and the width of the bounding box
- $width_{bb}$ is 216, the width at 300dpi, <span
- class="emphasis"><em>width</em></span>, is $(216
- \times 300) \div 72 = 900$.</p>
- </li>
-
- <li>
- <p>Calculate the corrected height in an analogous
- manner using $height_{bb} = ury - lly$ as a
- starting point. For example, if $height_{bb} =
- 360$, the height you get at 300dpi is 1500.</p>
- </li>
-
- <li>
- <p>Finally, run <b>Ghostscript</b> using the <span
- class="emphasis"><em>-g</em></span> parameter to
- select the image size ($width \times height$). For
- example, to translate the EPS file <tt>card.ps</tt>
- into the GIF file <tt>card.gif</tt> at 300dpi
- assuming the height and width calculated above,
- run:</p>
-<pre class="screen">
-\$ <span
-class="bold"><b>{gs -r300 -g900x1500 -sDEVICE=gifmono {\bs}
- -sOutputFile=card.gif trans.ps card.ps}</b></span>
-
-</pre>
- </li>
- </ol>
- </div>
-
- <p>The <span class="emphasis"><em>Perl</em></span> script
- shown in Example&#160;<a href="ch06.html#ex.gseps"
- title="Example&#160;6.8.&#160;Converting Encapsulated PostScript to a Bitmap with Ghostscript">
- Example&#160;6.8</a> automates this process.</p>
-
- <div class="example">
- <a id="ex.gseps" name="ex.gseps"></a>
-
- <p class="title"><b>Example&#160;6.8.&#160;Converting
- Encapsulated PostScript to a Bitmap with
- Ghostscript</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="gs-eps.pl"></a>
-</pre>
- </div>
-
- <p>The primary disadvantage of <b>Ghostscript</b> is that
- the selection of free PostScript fonts is quite limited.
- The only freely available fonts are: IBM Courier,
- Bitstream Courier, Bitstream Charter, Adobe Utopia, URW
- Antiqua, URW Grotesk Bold, Nimbus Roman No9, and Nimbus
- Sans. Unless you have the PostScript sources for other
- fonts used in your figures (<tt>PFA</tt> or <tt>PFB</tt>
- and <tt>AFM</tt> files), <b>Ghostscript</b> will use
- crude approximations of the desired font.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.screendump"
- name="sec.screendump"></a>GoScript</h3>
- </div>
- </div>
-
- <p><b>GoScript</b><a id="id2897134" class="indexterm"
- name="id2897134"></a> is a commercial PostScript<a
- id="id2897143" class="indexterm" name="id2897143"></a>
- interpreter sold by LaserGo, Inc.<a id="id2897155"
- class="indexterm" name="id2897155"></a> <b>GoScript</b>
- is available for MS-DOS systems only. A special version
- is available for Microsoft Windows.</p>
-
- <p>The primary advantage of a commercial interpreter is
- that it comes with more high-quality fonts. The
- <b>GoScript</b> program comes with &#8220;clones&#8221;
- of the 13 standard PostScript fonts:</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>Times Roman</td>
-
- <td>Times Italic</td>
- </tr>
-
- <tr>
- <td>Times Bold</td>
-
- <td>Times Bold Italic</td>
- </tr>
-
- <tr>
- <td>Helvetica</td>
-
- <td>Helvetica Oblique</td>
- </tr>
-
- <tr>
- <td>Helvetica Bold</td>
-
- <td>Helvetica Bold Oblique</td>
- </tr>
-
- <tr>
- <td>Courier</td>
-
- <td>Courier Oblique</td>
- </tr>
-
- <tr>
- <td>Courier Bold</td>
-
- <td>Courier Bold Oblique</td>
- </tr>
-
- <tr>
- <td>Symbol</td>
-
- <td>&#160;</td>
- </tr>
- </table>
-
- <p>The <b>GoScript Plus</b> program includes clones of
- all 35 standard fonts (the standard 13 plus AvantGarde,
- Bookman, Helvetica-Narrow, New Century Schoolbook,
- Palatino in four styles, Zapf Chancery Italic, and Zapf
- Dingbats). For MS-DOS users, this program has the
- additional advantage of being quite a bit faster than
- <b>Ghostscript</b>.</p>
-
- <p>Although <b>GoScript</b> can use any PostScript
- Type&#160;1 or Type&#160;3 font, the fonts supplied with
- <b>GoScript</b> are not in a standard PostScript format,
- so they cannot be used with other applications.</p>
-
- <p>On a 300dpi LaserJet printer, <b>GoScript</b> did not
- seem to align the baseline of bitmapped PostScript fonts
- with great accuracy. This is unfortunate, because the
- Computer Modern fonts created with MetaFont for TeX are
- bitmapped.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2897312"
- name="id2897312"></a>hp2xx</h3>
- </div>
- </div>
-
- <p><b>hp2xx</b><a id="id2897329" class="indexterm"
- name="id2897329"></a> converts scalable images in HPGL<a
- id="id2897338" class="indexterm" name="id2897338"></a>
- into other formats. HPGL is Hewlett-Packard's command
- language for controlling pen-based plotters. (HP's
- LaserJet series of printers, starting with the LaserJet
- III, also understand HPGL.)</p>
-
- <p>Many computer-aided drafting packages can save
- diagrams in HPGL format. Other software that works with
- scalable images is likely to be able to save in HPGL
- format as well. Because HPGL support is uncommon in
- printers, you will probably have to convert HPGL diagrams
- into another format to include them in your TeX
- documents. <b>hp2xx</b> output comes in three flavors:
- scalable graphics, TeX commands, and bitmapped
- graphics.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">Scalable graphics</span></dt>
-
- <dd>
- <p>The supported scalable graphics formats are
- encapsulated PostScript and MetaFont source
- code.</p>
- </dd>
-
- <dt><span class="term">TeX commands</span></dt>
-
- <dd>
- <p>HPGL drawings composed of mostly straight lines
- can be rendered in TeX. <b>hp2xx</b>'s TeX output
- is designed for either the emTeX DVI drivers (it
- relies on \special commands to draw lines at
- arbitrary angles) or the <span
- class="emphasis"><em>epic</em></span> macros (which
- also use \special commands that must be supported
- by your DVI driver).</p>
- </dd>
-
- <dt><span class="term">Bitmapped graphics</span></dt>
-
- <dd>
- <p>Bitmaps can be produced in PBM<a id="id2897448"
- class="indexterm" name="id2897448"></a>, PCX<a
- id="id2897457" class="indexterm"
- name="id2897457"></a>, or PCL<a id="id2897465"
- class="indexterm" name="id2897465"></a> (HP
- LaserJet bitmap) formats. You can select image size
- and resolution to produce a bitmap that will print
- at the correct size for your printer.</p>
- </dd>
- </dl>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2897483"
- name="id2897483"></a>Image Editors</h2>
- </div>
- </div>
-
- <p>Although many images<a id="id2897492" class="indexterm"
- name="id2897492"></a><a id="id2897500" class="indexterm"
- name="id2897500"></a> are available on the Net and
- commercially, it is very likely that you will want to
- create your own pictures and diagrams for some of the
- documents that you write. A few common drawing tools are
- described below. Table&#160;<a
- href="ch06.html#tab.drawingtools"
- title="Table&#160;6.2.&#160;Graphics Editing Packages">Table&#160;6.2</a>
- summarizes the packages discussed here. There are many more
- commercial packages for image editing---so many, in fact,
- that I'm not going to make any effort to describe them
- here.</p>
-
- <div class="table">
- <a id="tab.drawingtools" name="tab.drawingtools"></a>
-
- <p class="title"><b>Table&#160;6.2.&#160;Graphics Editing
- Packages</b></p>
-
- <table summary="Graphics Editing Packages" border="1">
- <colgroup>
- <col align="left" />
- <col align="center" />
- <col align="center" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">Program</th>
-
- <th align="center">Platforms</th>
-
- <th align="center">Cost</th>
-
- <th align="left">Purpose</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">xfig</td>
-
- <td align="center">unix</td>
-
- <td align="center">free</td>
-
- <td align="left">Edit scalable Fig drawings</td>
- </tr>
-
- <tr>
- <td align="left">idraw</td>
-
- <td align="center">unix</td>
-
- <td align="center">free</td>
-
- <td align="left">Edit encapsulated PostScript
- images</td>
- </tr>
-
- <tr>
- <td align="left">tgif</td>
-
- <td align="center">unix</td>
-
- <td align="center">free</td>
-
- <td align="left">Edit scalable drawings</td>
- </tr>
-
- <tr>
- <td align="left">pixmap</td>
-
- <td align="center">unix</td>
-
- <td align="center">free</td>
-
- <td align="left">Edit X11 XBM and XPM files</td>
- </tr>
-
- <tr>
- <td align="left">texcad</td>
-
- <td align="center">MS-DOS</td>
-
- <td align="center">free</td>
-
- <td align="left">Edit LaTeX picture
- environments</td>
- </tr>
-
- <tr>
- <td align="left">xtexcad</td>
-
- <td align="center">unix</td>
-
- <td align="center">free</td>
-
- <td align="left">An X11 implementation of
- <b>texcad</b></td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2897734"
- name="id2897734"></a>xfig</h3>
- </div>
- </div>
-
- <p><b>xfig</b><a id="id2897747" class="indexterm"
- name="id2897747"></a> is an editing tool for scalable
- images stored in the Fig format, described in the
- &#8220;<a href="ch06.html#sec.Fig"
- title="The epic and eepic styles">the section called
- &#8220;The epic and eepic styles&#8221;</a>&#8221;
- section of this chapter. An example of a drawing being
- constructed with <b>xfig</b> is shown in Figure&#160;<a
- href="ch06.html#fig.sd-xfig"
- title="Figure&#160;6.11.&#160;Editing an image with xfig">
- Figure&#160;6.11</a>.</p>
-
- <div class="figure">
- <a id="fig.sd-xfig" name="fig.sd-xfig"></a>
-
- <p class="title"><b>Figure&#160;6.11.&#160;Editing an
- image with xfig</b></p>
-
- <div class="mediaobject">
- <img src="tex.06.11.eps" />
- </div>
- </div>
-
- <p>The objects in Fig are arcs, circles, open and closed
- splines, ellipses, regular and irregular polygons,
- polylines, boxes, arc-boxes (boxes with rounded corners),
- text, and encapsulated PostScript. Compound objects can
- be constructed by binding these objects together.</p>
-
- <p>As a consequence of Fig's device independence, it can
- be translated into a number of different output formats.
- A completed Fig drawing can be rendered in PostScript,
- PiCTeX, \linebreak</p>
-
- <p>LaTeX's <tt>picture</tt> environment, MetaFont, or any
- of the pic, epic, eepic, box, eepicemu and \special
- environments. Figures can also be saved as X11 bitmaps.
- Not all of the output formats support all of the features
- of Fig. For example, arbitrarily sloped lines are not
- supported by the LaTeX <tt>picture</tt> environment, and
- encapsulated PostScript makes sense only for PostScript
- output.</p>
-
- <p><b>xfig</b> supports rotation, flipping, scaling, and
- duplication of objects. However, it imposes some
- limitations on the figures that you create. Objects that
- contain boxes, arc-boxes, circles, or ellipses can be
- rotated only in 90 degree increments. Text objects cannot
- be flipped over.</p>
-
- <p>When objects are placed on the &#8220;canvas,&#8221;
- you can elect to have <b>xfig</b> restrict their
- placement to $\frac{1}{16}$, $\frac{1}{4}$, or
- $\frac{1}{2}$-inch intervals. Restricted placement makes
- alignment of a large number of objects easier.
- Unrestricted placement is also allowed, and there is an
- alignment operator that can center (vertically and
- horizontally) any number of objects. A nonprinting grid
- is available in several sizes, independent of the
- restriction on object placement. In a similar way,
- <b>xfig</b> can be instructed to draw sloped lines within
- specific limits (for example, only allowing lines at
- slopes supported by LaTeX's <tt>picture</tt>
- environment). Precise numeric-coordinate placement of
- individual objects is also supported.</p>
-
- <p><b>xfig</b> provides access to the standard 35
- PostScript fonts as well as the standard LaTeX fonts.
- Eight-bit input, allowing access to international
- symbols, is also provided.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2897932"
- name="id2897932"></a>idraw</h3>
- </div>
- </div>
-
- <p><b>idraw</b><a id="id2897946" class="indexterm"
- name="id2897946"></a>, the InterViews drawing editor, is
- an X Windows application for editing encapsulated
- PostScript figures. Figure&#160;<a
- href="ch06.html#fig.sd-idraw"
- title="Figure&#160;6.12.&#160;Editing an image with idraw">
- Figure&#160;6.12</a> shows a drawing constructed with
- <b>idraw</b>.</p>
-
- <div class="figure">
- <a id="fig.sd-idraw" name="fig.sd-idraw"></a>
-
- <p class="title"><b>Figure&#160;6.12.&#160;Editing an
- image with idraw</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>The objects in <b>idraw</b> are lines, ellipses, open
- and closed splines, irregular polygons, polylines,
- rectangles, and text. Compound objects can be constructed
- by gluing these objects together. Fonts, brushes, and
- patterns can be customized and extended with X-defaults.
- <b>idraw</b> supports the full complement of rotation,
- flip, scale, and duplicate operations with or without
- grid lines and optional gravity.</p>
-
- <p>Unfortunately, the &#8220;gravity&#8221; option, which
- allows you to create horizontally and vertically aligned
- objects, is not preserved when a file is saved. It is
- very difficult to recover the alignment of a file when it
- has been saved and reloaded.</p>
-
- <p>Graphics in TIFF, encapsulated PostScript, X11 bitmap
- format, and Unidraw format can be imported into
- <b>idraw</b> figures.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2898057"
- name="id2898057"></a>tgif</h3>
- </div>
- </div>
-
- <p><b>tgif</b><a id="id2898071" class="indexterm"
- name="id2898071"></a>, like <b>xfig</b> and <b>idraw</b>,
- is an editor for scalable drawings. The
- &#8220;gif\,&#8221; in <b>tgif</b> has nothing to do with
- the bitmap GIF format. The captured screen in
- Figure&#160;<a href="ch06.html#fig.sd-tgif"
- title="Figure&#160;6.13.&#160;Editing an image with tgif">
- Figure&#160;6.13</a> shows a drawing being constructed
- with <b>tgif</b>.</p>
-
- <div class="figure">
- <a id="fig.sd-tgif" name="fig.sd-tgif"></a>
-
- <p class="title"><b>Figure&#160;6.13.&#160;Editing an
- image with tgif</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p><b>tgif</b> stores objects as a set of Prolog
- &#8220;facts.&#8221; Several programs are provided for
- interpretation of <b>tgif</b> objects outside of
- <b>tgif</b>. Only four output types are built into
- <b>tgif</b>: PostScript<a id="id2898193"
- class="indexterm" name="id2898193"></a>, encapsulated
- PostScript (EPS)<a id="id2898202" class="indexterm"
- name="id2898202"></a>, X11 bitmaps<a id="id2898211"
- class="indexterm" name="id2898211"></a>, and X11
- pixmaps.</p>
-
- <p><b>tgif</b> has a number of interesting features
- including the ability to design hierarchical drawings in
- either a &#8220;top down&#8221; or &#8220;bottom
- up&#8221; manner, and the separation of an object's <span
- class="emphasis"><em>representation</em></span> from its
- <span class="emphasis"><em>instantiation</em></span>. In
- addition, arbitrary text-based attributes can be attached
- to each object. <b>tgif</b> uses these attributes in a
- number of ways, such as the execution of system commands
- based upon object attributes.</p>
-
- <p>The objects supported by <b>tgif</b> are arcs,
- ellipses, rectangles, rounded-corner rectangles,
- polylines, polygons, open and closed splines, text, X11
- bitmaps, some forms of X11 pixmaps, and encapsulated
- PostScript. These objects can be grouped together.</p>
-
- <p><b>tgif</b> supports only five fonts (Times, Courier,
- Helvetica, New Century Schoolbook, and Symbol) at a few
- fixed sizes. The fill patterns, line styles, text-styles,
- and other attributes are similarly fixed (although more
- generous in number).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2898297"
- name="id2898297"></a>bitmap/pixmap</h3>
- </div>
- </div>
-
- <p><b>bitmap</b><a id="id2898311" class="indexterm"
- name="id2898311"></a> and <b>pixmap</b><a id="id2898325"
- class="indexterm" name="id2898325"></a> are standard
- tools distributed with the X11 Window System. The
- <b>pixmap</b> tool provides a superset of the functions
- in <b>bitmap</b>, including support for color images. An
- example of the <b>bitmap</b> program editing a small X
- icon is shown in Figure&#160;<a
- href="ch06.html#fig.xbitmap"
- title="Figure&#160;6.14.&#160;An example of bitmap editing an icon">
- Figure&#160;6.14</a>.</p>
-
- <div class="figure">
- <a id="fig.xbitmap" name="fig.xbitmap"></a>
-
- <p class="title"><b>Figure&#160;6.14.&#160;An example
- of bitmap editing an icon</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2898403"
- name="id2898403"></a>Other Bitmap Editors</h3>
- </div>
- </div>
-
- <p>Free or inexpensive bitmap editors<a id="id2898413"
- class="indexterm" name="id2898413"></a> are available for
- almost every computer system. The selection of a
- particular package depends in large part on what kinds of
- diagrams you need to create.</p>
-
- <p>The primary disadvantage of bitmap editing is that it
- is difficult to create bitmaps large enough to be used at
- printer resolution. Even a &#8220;full screen&#8221;
- image on a high-resolution monitor is only a couple of
- inches across (at best) on a laser printer.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2898442"
- name="id2898442"></a>texcad/xtexcad</h3>
- </div>
- </div>
-
- <p><b>texcad</b><a id="id2898456" class="indexterm"
- name="id2898456"></a> is an MS-DOS program (distributed
- with emTeX) for editing LaTeX <tt>picture</tt>
- environments. <b>xtexcad</b><a id="id2898478"
- class="indexterm" name="id2898478"></a> is a similar
- program that runs under the X11 Window system.</p>
-
- <p>The LaTeX <tt>picture</tt> environment suffers from
- two limitations: it can only draw relatively simple
- diagrams, and it is very difficult to use. <b>texcad</b>
- and <b>xtexcad</b> remove the second limitation. With one
- of these programs, the LaTeX <tt>picture</tt> environment
- becomes a viable option for many diagrams.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2898527"
- name="id2898527"></a>Screen Dumps</h2>
- </div>
- </div>
-
- <p>If you are writing a document that describes a computer
- program, it is frequently desirable to include an image of
- the running program (a captured screen or screen dump<a
- id="id2898539" class="indexterm" name="id2898539"></a>) in
- the document. There are several ways that this can be
- accomplished<a id="id2898549" class="indexterm"
- name="id2898549"></a><a id="id2898556" class="indexterm"
- name="id2898556"></a><a id="id2898563" class="indexterm"
- name="id2898563"></a><a id="id2898570" class="indexterm"
- name="id2898570"></a><a id="id2898577" class="indexterm"
- name="id2898577"></a><a id="id2898584" class="indexterm"
- name="id2898584"></a><a id="id2898591" class="indexterm"
- name="id2898591"></a><a id="id2898598" class="indexterm"
- name="id2898598"></a>:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p><b>Screen Thief</b> for MS-DOS</p>
- </li>
-
- <li>
- <p><b>GrabIt</b> for Microsoft Windows</p>
- </li>
-
- <li>
- <p><b>xv</b>, <b>Image Magick</b>, or <b>xwd</b> for
- X11 workstations</p>
- </li>
-
- <li>
- <p><b>PM-Cam</b>, <b>Nikon II</b>, or <b>pmjpeg</b>
- for OS/2</p>
- </li>
- </ul>
- </div>
-
- <p>The captured screen may be in a graphics format that is
- directly usable by your DVI driver or by <b>bm2font</b>. If
- not, one or more of the conversion programs described in
- &#8220;<a href="ch06.html#sec.picconv"
- title="Manipulating Images">the section called
- &#8220;Manipulating Images&#8221;</a>&#8221; earlier in
- this chapter will help you convert it into a usable
- format.</p>
-
- <p>The most common output devices for TeX are laser
- printers with a resolution of 300dpi or higher. By
- contrast, the resolution of a typical display is around
- 80dpi. This discrepancy may require you to enlarge the
- bitmap image to make it legible in your document. For
- example, a 640x480 bitmap image is only about two inches
- wide when printed at 300dpi. In color images, <span
- class="emphasis"><em>dithering<a id="id2898740"
- class="indexterm" name="id2898740"></a></em></span>, which
- increases the number of dots used to represent each pixel
- in the original image, has a natural enlarging effect on
- the image, and this reduces the magnitude of the problem.
- However, some scaling may still be necessary.</p>
-
- <p>If the screen you want to include is only text (this
- includes IBM's line-drawing characters and other symbols),
- you can include it as a special &#8220;verbatim&#8221;
- environment if you have an appropriate font. The advantages
- of this method are that the actual screen text can be
- incorporated directly into your document (making the
- document more portable and easier to distribute, if that is
- a concern), and that the resulting document is small and
- easy to print. The disadvantage of this approach is that
- information about color is lost. If parts of the on-screen
- text appear in different colors for highlighting, using a
- pure-text approach may not produce acceptable results. For
- example, compare Figure&#160;<a
- href="ch06.html#fig.textshot"
- title="Figure&#160;6.15.&#160;A text mode screen dump.">Figure&#160;6.15</a>
- with the results in Figure&#160;<a
- href="ch02.html#fig.melatexcmp"
- title="Figure&#160;2.2.&#160;LaTeX as a compiler in Multi-Edit">
- Figure&#160;2.2</a> in Chapter&#160;<a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a>,
- <span class="emphasis"><em><a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a></em></span>.</p>
-
- <div class="figure">
- <a id="fig.textshot" name="fig.textshot"></a>
-
- <p class="title"><b>Figure&#160;6.15.&#160;A text mode
- screen dump.</b></p>
-
- <div class="literallayout">
- <p>\screendump{metext}</p>
- </div>
- </div>
-
- <p>To insert pure-text screen captures, you have to have a
- font with exactly the same encoding as the text on the
- screen (for more information about font encodings, see the
- section &#8220;<a href="ch05.html#sec.fonts.encodingvec"
- title="Declaring a family">the section called
- &#8220;Declaring a family&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>).
- On MS-DOS and OS/2 PCs, this is sometimes a problem because
- the IBM line drawing characters do not appear in most
- fonts. Several commercial fonts provide the appropriate
- character set, but so do the freely available IBM Courier
- fonts (distributed by IBM for the X11 Consortium). The IBM
- Courier fonts are PostScript Type&#160;1 fonts. If you need
- TeX <tt>PK</tt> fonts, use the <b>ps2pk</b> program as
- described in the section called &#8220;<a
- href="ch05.html#sec.t1fonts" title="Math Fonts in TeX">the
- section called &#8220;Math Fonts in TeX&#8221;</a>&#8221;
- in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>.</p>
-
- <p>To use the IBM Courier fonts to print captured screens,
- you will need <tt>AFM</tt> files<a id="id2898938"
- class="indexterm" name="id2898938"></a> that have the
- correct encoding vector. <tt>AFM</tt> files with the IBM
- OEM character set encoding are available from the CTAN
- archives in the directory <tt>fonts/courier</tt>.</p>
-
- <p>After the appropriate font is available, you are almost
- ready to reproduce a captured screen. One problem remains:
- TeX cannot \input binary files. Because screen dumps
- frequently contain characters from outside the normal ASCII
- range, they must be considered binary in this context. To
- overcome this difficulty, it is necessary to process the
- screen dump and convert it into a text file. The
- <b>Perl</b> script in Example&#160;<a
- href="apd.html#ex.txt2verb"
- title="Example&#160;D.8.&#160;txt2verb.pl">Example&#160;D.8</a>
- in Appendix&#160;<a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a>,
- <span class="emphasis"><em><a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a></em></span>,
- will perform this conversion.</p>
-
- <p>After conversion, the TeX code shown in Example&#160;<a
- href="ch06.html#ex.texscreencapt"
- title="Example&#160;6.9.&#160;Script for Inserting a Captured Text Screen">
- Example&#160;6.9</a> will insert the screen. This code will
- work in both Plain TeX and LaTeX. Similar code can be
- written for other formats. Figure&#160;<a
- href="ch06.html#fig.textshot"
- title="Figure&#160;6.15.&#160;A text mode screen dump.">Figure&#160;6.15</a>
- was produced with this code.</p>
-
- <div class="example">
- <a id="ex.texscreencapt" name="ex.texscreencapt"></a>
-
- <p class="title"><b>Example&#160;6.9.&#160;Script for
- Inserting a Captured Text Screen</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad"
-href="screendump.sty"></a>
-</pre>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2884093" name="ftn.id2884093"
- href="#id2884093">79</a>]</sup> {Some devices, most
- notably plotters, don't work this way. They really draw
- lines and curves with physical pens.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2891727" name="ftn.id2891727"
- href="#id2891727">80</a>]</sup> And probably any other
- format derived from Plain TeX.</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2892937" name="ftn.id2892937"
- href="#id2892937">81</a>]</sup> {<b>dvimsp</b> has been
- replaced by <b>dvidot</b> in the beta test
- distributions.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2893346" name="ftn.id2893346"
- href="#id2893346">82</a>]</sup> {In fairness, the degree
- of difficulty depends on the platform you work on. Some
- systems, like the Amiga, have very good support for
- PostScript output, even on non-PostScript devices.
- Alternatively, if you have a fast computer, the extra
- translation through <b>Ghostscript</b> may be quite
- painless.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2893914" name="ftn.id2893914"
- href="#id2893914">83</a>]</sup> {The <tt>epsfig.sty</tt>
- style relies on <tt>epsf.tex</tt><a id="id2893934"
- class="indexterm" name="id2893934"></a> to provide
- low-level support for including EPS images. The
- <tt>epsf.tex</tt> file is part of the <b>dvips</b>
- distribution.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2896732" name="ftn.id2896732"
- href="#id2896732">84</a>]</sup> {Under MS-DOS and OS/2,
- remember that the command processor performs variable
- substitution with the percent sign. Use two consecutive
- percent signs.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;5.&#160;Fonts" href="ch05.html"><img
- src="figures/nav-prev.png" alt="Prev" border="0" />
- </a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;7.&#160;International Considerations"
- href="ch07.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;5.&#160;Fonts&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;7.&#160;International
- Considerations</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch07.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch07.html
deleted file mode 100644
index 0b39091b781..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch07.html
+++ /dev/null
@@ -1,2409 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;7.&#160;International
- Considerations</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures" />
- <link rel="next" href="ch08.html"
- title="Chapter&#160;8.&#160;Printing" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;6.&#160;Pictures and Figures"
- href="ch06.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;8.&#160;Printing"
- href="ch08.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.foreign"
- name="chap.foreign"></a>Chapter&#160;7.&#160;International
- Considerations</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>Although the standard TeX macro packages and the Computer
- Modern fonts were designed to typeset documents written
- primarily in English, TeX enjoys widespread international
- use<a id="id2890702" class="indexterm"
- name="id2890702"></a><a id="id2890737" class="indexterm"
- name="id2890737"></a><a id="id2890746" class="indexterm"
- name="id2890746"></a>.</p>
-
- <p>From a technical standpoint, languages can be divided into
- two categories: those that are &#8220;like English&#8221;
- (meaning that they use a relatively small number of
- characters and are typeset horizontally, left to right) and
- those that are not. German, French, and Russian are all
- &#8220;like English&#8221; in this sense. Hebrew, Chinese,
- and Japanese are not (Hebrew<a id="id2890473"
- class="indexterm" name="id2890473"></a> is typeset right to
- left, and Chinese<a id="id2890482" class="indexterm"
- name="id2890482"></a> and Japanese<a id="id2890491"
- class="indexterm" name="id2890491"></a> use thousands of
- characters).<sup>[<a id="id2890500" name="id2890500"
- href="#ftn.id2890500">85</a>]</sup></p>
-
- <p>This chapter explores some of the issues that arise when
- TeX is used to typeset languages other than English. For
- simplicity, we'll look at languages like English first, and
- then describe some environments for typesetting much more
- complex languages.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.for.printing"
- name="sec.for.printing"></a>Typesetting in Any
- Language</h2>
- </div>
- </div>
-
- <p>In order to typeset<a id="id2899108" class="indexterm"
- name="id2899108"></a> any language with TeX, three things
- have to happen:</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>TeX has to read the input file and perform the
- correct mapping from the input file's character set
- to its internal representation of each character. The
- character set used in the input file will vary
- depending upon the language. For instance, if you're
- writing a document in French<a id="id2899141"
- class="indexterm" name="id2899141"></a>, it is as
- natural to use &#8220;é&#8221; in your input file as
- it is to use any other letter.</p>
- </li>
-
- <li>
- <p>TeX has to typeset the document according to the
- rules of the language being used. Naturally, this
- means that there must be some way of declaring what
- language is being used, and appropriate macros have
- to exist to embody the rules of that language. Users
- familiar only with English may not recognize the
- importance of language-specific rules because English
- has so few rules. Other languages have many. In
- German<a id="id2899172" class="indexterm"
- name="id2899172"></a>, for example, if the consonants
- &#8220;ck&#8221; in a word are broken by a hyphen,
- the &#8220;c&#8221; becomes a &#8220;k&#8221;
- (&#8220;k-k&#8221;). In French<a id="id2899199"
- class="indexterm" name="id2899199"></a>, small
- amounts of extra space are placed around various
- punctuation marks.</p>
-
- <p>A good reference manual for internationalization
- is <span class="emphasis"><em>{Software
- Internationalization and Localization: An
- Introduction}</em></span>&#160;[<a
- href="bi01.html#eu:international">eu:international</a>].</p>
- </li>
-
- <li>
- <p>The <tt>DVI</tt> file that results from
- typesetting the document must be printed correctly.
- In other words, all of the accented characters and
- symbols used by the language must be available (or
- constructed) for previewing and printing.</p>
- </li>
- </ol>
- </div>
-
- <p>Early attempts to write documents in languages other
- than English were hampered by several limitations in the
- TeX program. In particular, fonts were limited to 128
- characters, and only a single set of hyphenation patterns
- could be loaded (effectively preventing multilingual
- documents from being hyphenated correctly). These technical
- problems were corrected in TeX version 3.x (first released
- in 1990). The remaining difficulties---mostly a lack of
- standardization and the need to develop relevant
- language-specific macros---are being addressed by the TUG<a
- id="id2899266" class="indexterm" name="id2899266"></a>
- Technical Working Group on Multiple Language Coordination
- (TWGMLC)<a id="id2899280" class="indexterm"
- name="id2899280"></a>.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2899289"
- name="id2899289"></a>Reading Input Files</h3>
- </div>
- </div>
-
- <p>The first point to consider when typesetting is that
- every input file is written in some character set. For
- example, because this book is written in English and I
- work in the United States, the source code for this book
- is written in 7-bit ASCII<a id="id2899303"
- class="indexterm" name="id2899303"></a>. If this book
- were written in another language, a different character
- set, perhaps ISO Latin1, would be more appropriate.</p>
-
- <p>When TeX reads your input file, characters like
- &#8220;é&#8221; and &#8220;\guillemet&#8221; have to be
- translated into a form that TeX can use. For example,
- &#8220;é&#8221; should be translated into é and, if the
- DC fonts are in use, &#8220;\guillemet&#8221; should be
- translated into character 19; otherwise, if the DC
- fonts<a id="id2899343" class="indexterm"
- name="id2899343"></a> are not in use,
- &#8220;\guillemet&#8221; should be translated into
- <tt>$&lt;&lt;$</tt> which will give the approximate
- result. The DC fonts are discussed in the section called
- &#8220;<a href="ch07.html#sec.for.printing"
- title="Typesetting in Any Language">the section called
- &#8220;Typesetting in Any Language&#8221;</a>,&#8221;
- later in this chapter.</p>
-
- <p>It is always possible to access characters from
- another symbol set by using a control sequence<a
- id="id2899384" class="indexterm" name="id2899384"></a>.
- Table&#160;<a href="ch07.html#tab.accentedchar"
- title="Table&#160;7.1.&#160;Standard Control Sequences for Symbols from Other Character Sets">
- Table&#160;7.1</a> shows the standard TeX control
- sequences for accessing accented characters and
- characters from other alphabets.<sup>[<a id="id2899397"
- name="id2899397" href="#ftn.id2899397">86</a>]</sup></p>
-
- <div class="table">
- <a id="tab.accentedchar" name="tab.accentedchar"></a>
-
- <p class="title"><b>Table&#160;7.1.&#160;Standard
- Control Sequences for Symbols from Other Character
- Sets</b></p>
-
- <table
- summary="Standard Control Sequences for Symbols from Other Character Sets"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Control</th>
-
- <th align="left">&#160;</th>
-
- <th align="left">\bf Control</th>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\bf Sequence</td>
-
- <td align="left">\bf Symbol</td>
-
- <td align="left">\bf Sequence</td>
-
- <td align="left">\bf Symbol</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\`e</td>
-
- <td align="left">\`e</td>
-
- <td align="left">\oe</td>
-
- <td align="left">\oe</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\'e</td>
-
- <td align="left">é</td>
-
- <td align="left">\ae</td>
-
- <td align="left">\ae</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\"e</td>
-
- <td align="left">\"e</td>
-
- <td align="left">\o</td>
-
- <td align="left">\o</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\u{e}</td>
-
- <td align="left">\u{e}</td>
-
- <td align="left">\aa</td>
-
- <td align="left">\aa</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\.e</td>
-
- <td align="left">\.e</td>
-
- <td align="left">\l</td>
-
- <td align="left">\l</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\t{ee}</td>
-
- <td align="left">\t{ee}</td>
-
- <td align="left">\OE</td>
-
- <td align="left">\OE</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\d{e}</td>
-
- <td align="left">\d{e}</td>
-
- <td align="left">\AE</td>
-
- <td align="left">\AE</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\H{e}</td>
-
- <td align="left">
- {\fontfamily{cmr}\selectfont\H{e}}</td>
-
- <td align="left">\O</td>
-
- <td align="left">\O</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\^e</td>
-
- <td align="left">\^e</td>
-
- <td align="left">\AA</td>
-
- <td align="left">\char'302</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\v{e}</td>
-
- <td align="left">\v{e}</td>
-
- <td align="left">\L</td>
-
- <td align="left">\L</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\=e</td>
-
- <td align="left">\=e</td>
-
- <td align="left"><tt>?`</tt></td>
-
- <td align="left">?`</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\&amp;nbsp;e</td>
-
- <td align="left">\&#160;e</td>
-
- <td align="left"><tt>!`</tt></td>
-
- <td align="left">!`</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\c{e}</td>
-
- <td align="left">\c{e}</td>
-
- <td align="left">\ss</td>
-
- <td align="left">\ss</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\b{e}</td>
-
- <td align="left">\b{e}</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>Table&#160;<a href="ch07.html#tab.newaccentedchar"
- title="Table&#160;7.2.&#160;New Control Sequences Proposed by TWGMLC">
- Table&#160;7.2</a> shows new control sequences proposed
- by the TWGMLC for characters not available in standard
- TeX and LaTeX distributions.<sup>[<a id="id2899840"
- name="id2899840" href="#ftn.id2899840">87</a>]</sup></p>
-
- <div class="table">
- <a id="tab.newaccentedchar"
- name="tab.newaccentedchar"></a>
-
- <p class="title"><b>Table&#160;7.2.&#160;New Control
- Sequences Proposed by TWGMLC</b></p>
-
- <table
- summary="New Control Sequences Proposed by TWGMLC"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="center" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\multicolumn{2}{l|}{\bf Control
- Sequences}</th>
-
- <th align="center">\bf Symbols</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left"><tt>,,</tt></td>
-
- <td align="center"><tt>''</tt></td>
-
- <td align="left">\dcr\char18 \ \char16</td>
-
- <td>German quotations
- ({\dcr\char18}G\"ansef\"u\ss{}chen{\dcr\char16})</td>
- </tr>
-
- <tr>
- <td align="left">French quotations
- (guillemets)</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\dh</td>
-
- <td align="center">\DH</td>
-
- <td align="left">\dcr\char240 \ \char208</td>
-
- <td>Icelandic eth</td>
- </tr>
-
- <tr>
- <td align="left">\dj</td>
-
- <td align="center">\DJ</td>
-
- <td align="left">\dcr\char158 \ \char208</td>
-
- <td>Serbocroation dj</td>
- </tr>
-
- <tr>
- <td align="left">\ng</td>
-
- <td align="center">\NG</td>
-
- <td align="left">\dcr\char173 \ \char141</td>
-
- <td>Sami ng</td>
- </tr>
-
- <tr>
- <td align="left">\th</td>
-
- <td align="center">\TH</td>
-
- <td align="left">\dcr\char254 \ \char222</td>
-
- <td>Icelandic thorn</td>
- </tr>
-
- <tr>
- <td align="left"><tt>\k e</tt></td>
-
- <td align="center">&#160;</td>
-
- <td align="left">\dcr\char166</td>
-
- <td>Polish ogonek subscript</td>
- </tr>
-
- <tr>
- <td align="left"><tt>\r u</tt></td>
-
- <td align="center">&#160;</td>
-
- <td align="left">\dcr\char183</td>
-
- <td>Czech circle accent</td>
- </tr>
-
- <tr>
- <td align="left">\v{d}</td>
-
- <td align="center">\V{D}</td>
-
- <td align="left">\dcr\char164 \ \char132</td>
-
- <td>Czech d and D with ha\v{c}ek</td>
- </tr>
-
- <tr>
- <td align="left">\v{l}</td>
-
- <td align="center">\V{l}</td>
-
- <td align="left">\dcr\char169 \ \char137</td>
-
- <td>Slovakian l and L with ha\v{c}ek</td>
- </tr>
-
- <tr>
- <td align="left">\v{t}</td>
-
- <td align="center">\V{T}</td>
-
- <td align="left">\dcr\char180 \ \char148</td>
-
- <td>Czech t and T with ha\v{c}ek</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>The only technical problem associated with using
- language-specific character sets in your input files is
- that you must have some way of telling TeX to perform the
- appropriate substitutions. One method is to use a special
- style file like <tt>isolatin1</tt>.<sup>[<a
- id="id2900193" name="id2900193"
- href="#ftn.id2900193">88</a>]</sup> This style uses
- &#8220;active characters&#8221; to map the ISO Latin1
- input character set to TeX's representation. It could be
- adapted to other character sets as well. Another
- possibility is to rely on system-dependent extensions to
- TeX. For example, emTeX provides extensive support for
- &#8220;code pages,&#8221; which address this problem.</p>
-
- <p>The only other problem created by using different
- input character sets is one of compatibility. If you
- write files using the ISO Latin1 character set and send
- them to someone who uses a different character set, the
- file will appear to be incorrect.<sup>[<a id="id2900241"
- name="id2900241" href="#ftn.id2900241">89</a>]</sup></p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2900256"
- name="id2900256"></a>Appearances can be
- deceiving</h4>
- </div>
- </div>
-
- <p>A document stored on disk is really just a file
- containing a series of characters, each represented by
- a unique numerical value. For an editor to display a
- document, each numerical value must be translated into
- a visual representation of the character. Frequently
- this translation is performed by the operating system
- or computer hardware. In an analogous way, each numeric
- value must be translated into a printable character
- when the document is typeset.</p>
-
- <p>Figure&#160;<a href="ch07.html#fig.charmap"
- title="Figure&#160;7.1.&#160;Character mapping example">
- Figure&#160;7.1</a> shows how this translation is
- performed for display by the operating system and for
- printing by TeX (using the <tt>isolatin1</tt> style,
- for example). This figure shows the disparity that
- occurs if the two translation tables are not the
- same.</p>
-
- <div class="figure">
- <a id="fig.charmap" name="fig.charmap"></a>
-
- <p class="title"><b>Figure&#160;7.1.&#160;Character
- mapping example</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>How can this arise? Well, suppose, for example, that
- a colleague is writing a document in French<a
- id="id2900326" class="indexterm" name="id2900326"></a>.
- He has a TeXnical problem that he would like me to
- investigate. I agree to take a look, and he sends the
- file to me. My colleage is using the ISO Latin1
- character set in his input file because it contains
- many symbols that are convenient for writing French
- (including the guillemets). I receive the file and edit
- it on my PC. The file that I see displayed looks like
- gibberish. That's because I'm using the IBM OEM
- encoding on my PC, which is sufficient for English. All
- of the special characters in the ISO Latin1 character
- set appear incorrect. Bewildered, I TeX and preview the
- document to see what it's supposed to look like. To my
- surprise, the previewed document looks fine.</p>
-
- <p>In this case, I can correct the problem by changing
- the &#8220;code page&#8221; used on my PC or by
- translating the input file with a program like GNU
- <b>recode</b><a id="id2900364" class="indexterm"
- name="id2900364"></a>.<sup>[<a id="id2900372"
- name="id2900372"
- href="#ftn.id2900372">90</a>]</sup></p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2900395"
- name="id2900395"></a>Changing the Rules</h3>
- </div>
- </div>
-
- <p>In order to select languages, the TWGMLC has proposed
- a set of language switching macros. These are shown in
- Table&#160;<a href="ch07.html#tab.langswitch"
- title="Table&#160;7.3.&#160;Language Switch Macros Proposed by TUG">
- Table&#160;7.3</a>.<sup>[<a id="id2900417"
- name="id2900417" href="#ftn.id2900417">91</a>]</sup></p>
-
- <p>Selecting a language has three effects:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>It establishes the correct hyphenation
- environment<a id="id2900456" class="indexterm"
- name="id2900456"></a>.</p>
-
- <p>Language-specific hyphenation patterns are
- loaded, if necessary, and correct values for the
- minimum length of a hyphenated word fragment are
- set.</p>
-
- <p>At the time of this writing, hyphenation
- patterns are already available, or under
- development, for Armenian, Bulgarian, Cambodian,
- Catalan, Croation, Czech, Danish, Dutch, English
- (U.K. and U.S.), Esperanto, Estonian, Finnish,
- French, German, Greek (both modern and ancient),
- Hungarian, Icelandic, Italian, Kirundi, Latin,
- Lithuanian, Norwegian, Polish, Portuguese, Russian,
- Slovak, Swahili, Swedish, Yiddish, and Yoruba.</p>
- </li>
-
- <li>
- <p>It loads the correct fonts and special
- characters.</p>
-
- <p>Even languages which use the same alphabet may
- have different fonts<a id="id2900507"
- class="indexterm" name="id2900507"></a><a
- id="id2900517" class="indexterm"
- name="id2900517"></a><a id="id2900527"
- class="indexterm" name="id2900527"></a> in order to
- provide specific features of the language. For
- example, the &#8220;fi&#8221; ligature<a
- id="id2900547" class="indexterm"
- name="id2900547"></a> makes sense only when
- typesetting English, and the \th and \TH macros
- make sense only when typesetting languages that
- need &#8220;{\dcr\char254}&#8221; and
- &#8220;{\dcr\char222}.&#8221;</p>
-
- <div class="table">
- <a id="tab.langswitch" name="tab.langswitch"></a>
-
- <p class="title"><b>Table&#160;7.3.&#160;Language
- Switch Macros Proposed by TUG</b></p>
-
- <table
- summary="Language Switch Macros Proposed by TUG"
- border="1">
- <colgroup>
- <col align="center" />
- <col align="left" />
- <col align="center" />
- <col align="left" />
- <col align="center" />
- <col align="left" />
- <col align="center" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="center">Macro Switch</th>
-
- <th align="left">Language</th>
-
- <th align="center">Macro Switch</th>
-
- <th align="left">Language</th>
-
- <th align="center">Macro Switch</th>
-
- <th align="left">Language</th>
-
- <th align="center">Macro Switch</th>
-
- <th align="left">Language</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="center">AB</td>
-
- <td align="left">Abkhazian</td>
-
- <td align="center">FY</td>
-
- <td align="left">Frisian</td>
-
- <td align="center">MG</td>
-
- <td align="left">Malagasy</td>
-
- <td align="center">SB</td>
-
- <td align="left">Sorbian</td>
- </tr>
-
- <tr>
- <td align="center">OM</td>
-
- <td align="left">Afan Oromo</td>
-
- <td align="center">GL</td>
-
- <td align="left">Galician</td>
-
- <td align="center">ML</td>
-
- <td align="left">Malayalam</td>
-
- <td align="center">ES</td>
-
- <td align="left">Spanish</td>
- </tr>
-
- <tr>
- <td align="center">FF</td>
-
- <td align="left">Afar</td>
-
- <td align="center">KA</td>
-
- <td align="left">Georgian</td>
-
- <td align="center">MS</td>
-
- <td align="left">Malay</td>
-
- <td align="center">SU</td>
-
- <td align="left">Sudanese</td>
- </tr>
-
- <tr>
- <td align="center">AF</td>
-
- <td align="left">Afrikaans</td>
-
- <td align="center">DE</td>
-
- <td align="left">German</td>
-
- <td align="center">MT</td>
-
- <td align="left">Maltese</td>
-
- <td align="center">SW</td>
-
- <td align="left">Swahili</td>
- </tr>
-
- <tr>
- <td align="center">SQ</td>
-
- <td align="left">Albanian</td>
-
- <td align="center">EL</td>
-
- <td align="left">Greek</td>
-
- <td align="center">MI</td>
-
- <td align="left">Maori</td>
-
- <td align="center">SV</td>
-
- <td align="left">Swedish</td>
- </tr>
-
- <tr>
- <td align="center">AM</td>
-
- <td align="left">Amharic</td>
-
- <td align="center">KL</td>
-
- <td align="left">Greenlandic</td>
-
- <td align="center">MR</td>
-
- <td align="left">Marathi</td>
-
- <td align="center">TL</td>
-
- <td align="left">Tagalog</td>
- </tr>
-
- <tr>
- <td align="center">AR</td>
-
- <td align="left">Arabic</td>
-
- <td align="center">GN</td>
-
- <td align="left">Guarani</td>
-
- <td align="center">MO</td>
-
- <td align="left">Moldavian</td>
-
- <td align="center">TG</td>
-
- <td align="left">Tajik</td>
- </tr>
-
- <tr>
- <td align="center">HY</td>
-
- <td align="left">Armenian</td>
-
- <td align="center">GU</td>
-
- <td align="left">Gujarati</td>
-
- <td align="center">NA</td>
-
- <td align="left">Nauru</td>
-
- <td align="center">TA</td>
-
- <td align="left">Tamil</td>
- </tr>
-
- <tr>
- <td align="center">AS</td>
-
- <td align="left">Assamese</td>
-
- <td align="center">HA</td>
-
- <td align="left">Hausa</td>
-
- <td align="center">NE</td>
-
- <td align="left">Nepali</td>
-
- <td align="center">TT</td>
-
- <td align="left">Tatar</td>
- </tr>
-
- <tr>
- <td align="center">AY</td>
-
- <td align="left">Aymara</td>
-
- <td align="center">HE</td>
-
- <td align="left">Hebrew</td>
-
- <td align="center">NO</td>
-
- <td align="left">Norwegian</td>
-
- <td align="center">TE</td>
-
- <td align="left">Telugu</td>
- </tr>
-
- <tr>
- <td align="center">AZ</td>
-
- <td align="left">Azerbaijani</td>
-
- <td align="center">HI</td>
-
- <td align="left">Hindi</td>
-
- <td align="center">OC</td>
-
- <td align="left">Occitan</td>
-
- <td align="center">TY</td>
-
- <td align="left">Thai</td>
- </tr>
-
- <tr>
- <td align="center">BA</td>
-
- <td align="left">Bashkir</td>
-
- <td align="center">HU</td>
-
- <td align="left">Hungarian</td>
-
- <td align="center">OR</td>
-
- <td align="left">Oriya</td>
-
- <td align="center">BO</td>
-
- <td align="left">Tibetan</td>
- </tr>
-
- <tr>
- <td align="center">EU</td>
-
- <td align="left">Basque</td>
-
- <td align="center">IS</td>
-
- <td align="left">Icelandic</td>
-
- <td align="center">PS</td>
-
- <td align="left">Pashto</td>
-
- <td align="center">TI</td>
-
- <td align="left">Tigrinya</td>
- </tr>
-
- <tr>
- <td align="center">BN</td>
-
- <td align="left">Bengali</td>
-
- <td align="center">ID</td>
-
- <td align="left">Indonesian</td>
-
- <td align="center">FA</td>
-
- <td align="left">Persian</td>
-
- <td align="center">TO</td>
-
- <td align="left">Tonda</td>
- </tr>
-
- <tr>
- <td align="center">DZ</td>
-
- <td align="left">Bhutani</td>
-
- <td align="center">IA</td>
-
- <td align="left">Interlingua</td>
-
- <td align="center">PL</td>
-
- <td align="left">Polish</td>
-
- <td align="center">TS</td>
-
- <td align="left">Tsonga</td>
- </tr>
-
- <tr>
- <td align="center">BH</td>
-
- <td align="left">Bihari</td>
-
- <td align="center">IE</td>
-
- <td align="left">Interlingue</td>
-
- <td align="center">PT</td>
-
- <td align="left">Portuguese</td>
-
- <td align="center">TR</td>
-
- <td align="left">Turkish</td>
- </tr>
-
- <tr>
- <td align="center">BI</td>
-
- <td align="left">Bislama</td>
-
- <td align="center">IU</td>
-
- <td align="left">Inuktitut</td>
-
- <td align="center">PA</td>
-
- <td align="left">Punjabi</td>
-
- <td align="center">TK</td>
-
- <td align="left">Turkmen</td>
- </tr>
-
- <tr>
- <td align="center">BR</td>
-
- <td align="left">Breton</td>
-
- <td align="center">IK</td>
-
- <td align="left">Inupiak</td>
-
- <td align="center">QU</td>
-
- <td align="left">Quechua</td>
-
- <td align="center">TW</td>
-
- <td align="left">Twi</td>
- </tr>
-
- <tr>
- <td align="center">BG</td>
-
- <td align="left">Bulgarian</td>
-
- <td align="center">GA</td>
-
- <td align="left">Irish</td>
-
- <td align="center">RM</td>
-
- <td align="left">Rhaeto-Roman</td>
-
- <td align="center">GB</td>
-
- <td align="left">U.K. English</td>
- </tr>
-
- <tr>
- <td align="center">MY</td>
-
- <td align="left">Burmese</td>
-
- <td align="center">IT</td>
-
- <td align="left">Italian</td>
-
- <td align="center">RO</td>
-
- <td align="left">Romanian</td>
-
- <td align="center">US</td>
-
- <td align="left">U.S. English</td>
- </tr>
-
- <tr>
- <td align="center">BE</td>
-
- <td align="left">Byelorussian</td>
-
- <td align="center">JA</td>
-
- <td align="left">Japanese</td>
-
- <td align="center">RU</td>
-
- <td align="left">Russian</td>
-
- <td align="center">UG</td>
-
- <td align="left">Uigur</td>
- </tr>
-
- <tr>
- <td align="center">KM</td>
-
- <td align="left">Cambodian</td>
-
- <td align="center">JW</td>
-
- <td align="left">Javanese</td>
-
- <td align="center">SE</td>
-
- <td align="left">Sami</td>
-
- <td align="center">UK</td>
-
- <td align="left">Ukrainian</td>
- </tr>
-
- <tr>
- <td align="center">CA</td>
-
- <td align="left">Catalan</td>
-
- <td align="center">KN</td>
-
- <td align="left">Kannada</td>
-
- <td align="center">SM</td>
-
- <td align="left">Samoan</td>
-
- <td align="center">UR</td>
-
- <td align="left">Urdu</td>
- </tr>
-
- <tr>
- <td align="center">ZH</td>
-
- <td align="left">Chinese</td>
-
- <td align="center">KS</td>
-
- <td align="left">Kashmiri</td>
-
- <td align="center">SG</td>
-
- <td align="left">Sangho</td>
-
- <td align="center">UZ</td>
-
- <td align="left">Uzbek</td>
- </tr>
-
- <tr>
- <td align="center">CO</td>
-
- <td align="left">Corsican</td>
-
- <td align="center">KK</td>
-
- <td align="left">Kazakh</td>
-
- <td align="center">GD</td>
-
- <td align="left">Scots Gaelic</td>
-
- <td align="center">VI</td>
-
- <td align="left">Vietnamese</td>
- </tr>
-
- <tr>
- <td align="center">HR</td>
-
- <td align="left">Croatian</td>
-
- <td align="center">RW</td>
-
- <td align="left">Kinyarwanda</td>
-
- <td align="center">SR</td>
-
- <td align="left">Serbian</td>
-
- <td align="center">VO</td>
-
- <td align="left">Volapuk</td>
- </tr>
-
- <tr>
- <td align="center">CS</td>
-
- <td align="left">Czech</td>
-
- <td align="center">KY</td>
-
- <td align="left">Kirghiz</td>
-
- <td align="center">ST</td>
-
- <td align="left">Sesotho</td>
-
- <td align="center">CY</td>
-
- <td align="left">Welsh</td>
- </tr>
-
- <tr>
- <td align="center">DA</td>
-
- <td align="left">Danish</td>
-
- <td align="center">RN</td>
-
- <td align="left">Kirundi</td>
-
- <td align="center">TN</td>
-
- <td align="left">Setswana</td>
-
- <td align="center">WO</td>
-
- <td align="left">Wolof</td>
- </tr>
-
- <tr>
- <td align="center">NL</td>
-
- <td align="left">Dutch</td>
-
- <td align="center">KO</td>
-
- <td align="left">Korean</td>
-
- <td align="center">SN</td>
-
- <td align="left">Shona</td>
-
- <td align="center">XH</td>
-
- <td align="left">Xhosa</td>
- </tr>
-
- <tr>
- <td align="center">EO</td>
-
- <td align="left">Esperanto</td>
-
- <td align="center">KU</td>
-
- <td align="left">Kurdish</td>
-
- <td align="center">SD</td>
-
- <td align="left">Sindhi</td>
-
- <td align="center">YI</td>
-
- <td align="left">Yiddish</td>
- </tr>
-
- <tr>
- <td align="center">ET</td>
-
- <td align="left">Estonian</td>
-
- <td align="center">LO</td>
-
- <td align="left">Laothian</td>
-
- <td align="center">SI</td>
-
- <td align="left">Singhalese</td>
-
- <td align="center">YO</td>
-
- <td align="left">Yoruba</td>
- </tr>
-
- <tr>
- <td align="center">FO</td>
-
- <td align="left">Faroese</td>
-
- <td align="center">LV</td>
-
- <td align="left">Latvian</td>
-
- <td align="center">SS</td>
-
- <td align="left">Siswati</td>
-
- <td align="center">ZA</td>
-
- <td align="left">Zhuang</td>
- </tr>
-
- <tr>
- <td align="center">FJ</td>
-
- <td align="left">Fiji</td>
-
- <td align="center">LN</td>
-
- <td align="left">Lingala</td>
-
- <td align="center">SK</td>
-
- <td align="left">Slovak</td>
-
- <td align="center">ZU</td>
-
- <td align="left">Zulu</td>
- </tr>
-
- <tr>
- <td align="center">FI</td>
-
- <td align="left">Finnish</td>
-
- <td align="center">LT</td>
-
- <td align="left">Lithuanian</td>
-
- <td align="center">SL</td>
-
- <td align="left">Slovenian</td>
-
- <td align="center">FR</td>
-
- <td align="left">French</td>
- </tr>
-
- <tr>
- <td align="center">MK</td>
-
- <td align="left">Macedonian</td>
-
- <td align="center">SO</td>
-
- <td align="left">Somali</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
- </li>
-
- <li>
- <p>It defines special primitive operations, if
- appropriate.</p>
-
- <p>For example, right-to-left typesetting
- primitives are necessary only for languages like
- Hebrew<a id="id2901991" class="indexterm"
- name="id2901991"></a> which are typeset
- right-to-left.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2902005"
- name="id2902005"></a>Printing the Result</h3>
- </div>
- </div>
-
- <p>The Computer Modern Fonts<a id="id2902014"
- class="indexterm" name="id2902014"></a> are insufficient
- for typesetting languages other than English. In order to
- overcome this difficulty, the TeX User's Group has
- extended the Computer Modern encoding vector and
- established a new standard.</p>
-
- <p>The new standard fonts are known variously as the Cork
- fonts<a id="id2902035" class="indexterm"
- name="id2902035"></a><a id="id2902042" class="indexterm"
- name="id2902042"></a>, the DC fonts<a id="id2902053"
- class="indexterm" name="id2902053"></a><a id="id2902060"
- class="indexterm" name="id2902060"></a>, and the EC
- fonts<a id="id2902072" class="indexterm"
- name="id2902072"></a><a id="id2902079" class="indexterm"
- name="id2902079"></a>. These are all synonymous. The new
- standard was created following discussions at the TeX
- User's Group meeting in Cork, Ireland in 1990, hence the
- name Cork. The MetaFont fonts<a id="id2902090"
- class="indexterm" name="id2902090"></a><a id="id2902104"
- class="indexterm" name="id2902104"></a>, which embody
- this encoding, will eventually become the EC fonts. The
- current versions, available now, are still being refined
- (in the sense that some of the letter forms are being
- refined; the encoding will not change). These are called
- the DC fonts.</p>
-
- <p>There is a distinction between the standard encoding
- vector and the MetaFont fonts that replace Computer
- Modern. Therefore, I will refer to the standard encoding
- as the &#8220;Cork Encoding<a id="id2902133"
- class="indexterm" name="id2902133"></a>&#8221; and to the
- MetaFont fonts as the &#8220;DC fonts&#8221;.<sup>[<a
- id="id2902146" name="id2902146"
- href="#ftn.id2902146">92</a>]</sup></p>
-
- <p>At the time of this writing, the DC fonts are not a
- complete superset of Computer Modern because the DC Math
- fonts have not yet been released. (The DC fonts<a
- id="id2902163" class="indexterm" name="id2902163"></a><a
- id="id2902173" class="indexterm" name="id2902173"></a>
- will contain the upper-case Greek<a id="id2902185"
- class="indexterm" name="id2902185"></a> alphabet, which
- is currently missing from the DC fonts.) When the DC Math
- fonts are released, the DC fonts will be a complete
- superset of Computer Modern. The only apparent difference
- will be that the accents on the DC fonts are not at
- exactly the same height as the accented characters
- constructed with the \accent primitive using Computer
- Modern.<sup>[<a id="id2902200" name="id2902200"
- href="#ftn.id2902200">93</a>]</sup></p>
-
- <p>The Cork Encoding is shown in Table&#160;<a
- href="apb.html#tab.font.corkencoding"
- title="Table&#160;B.3.&#160;The Cork Font Encoding">Table&#160;B.3</a>
- in Appendix&#160;<a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a>,
- <span class="emphasis"><em><a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a></em></span>.
- There are 255 symbols in this vector with one blank for
- special purposes. Unlike the Computer Modern fonts, which
- have different encoding vectors in some typefaces
- (Computer Modern Roman is not the same as Computer Modern
- Typewriter, for example), all of the DC fonts have the
- same encoding vector.</p>
-
- <p>Several people have commented that the Cork Encoding
- suffers from a &#8220;design error&#8221; because it
- places characters in positions 0-31, which are frequently
- inaccessible in other applications, and because it places
- a nonstandard character at position 32, where a space
- usually occurs. This is not a design error. Bear in mind
- that the DC fonts are designed to be TeX output fonts.
- Font creators, working in other environments (for
- example, TrueType or PostScript) are free to divide the
- Cork Encoding into two separate font files and provide a
- virtual font for TeX that establishes the correct
- encoding. The motivation for putting as many symbols as
- possible in a single font is that TeX cannot kern<a
- id="id2902271" class="indexterm" name="id2902271"></a>
- across fonts.</p>
-
- <p>This is not meant to imply that the DC fonts should
- always be virtual<a id="id2902285" class="indexterm"
- name="id2902285"></a><a id="id2902295" class="indexterm"
- name="id2902295"></a><a id="id2902302" class="indexterm"
- name="id2902302"></a>. In fact, the DC fonts should be
- the &#8220;real&#8221; fonts upon which virtual fonts are
- based. A virtual Computer Modern font based upon the real
- DC fonts is infinitely preferable to a virtual DC font
- built on Computer Modern because:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>You need a &#8220;real&#8221; font to make
- virtual fonts, and the Computer Modern fonts don't
- contain enough <span
- class="emphasis"><em>real</em></span>
- characters.</p>
- </li>
-
- <li>
- <p>Expressing accented characters in MetaFont is
- much better than building accents inside a virtual
- font. The virtual font has less information to work
- with (it has only boxes).</p>
- </li>
-
- <li>
- <p>Different languages use accents at different
- heights. A simple &#8220;patch&#8221; to the
- MetaFont code for a real font with accents is far
- superior to introducing another set of virtual
- fonts for every language.</p>
- </li>
- </ul>
- </div>
-
- <p>From a purely practical point of view, the correct way
- to deal with these and related problems is to use the
- babel style files.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="sec.babel"
- name="sec.babel"></a>The Babel Styles</h2>
- </div>
- </div>
-
- <p>The babel styles<a id="id2902395" class="indexterm"
- name="id2902395"></a><a id="id2902402" class="indexterm"
- name="id2902402"></a> are a collection of style files for
- LaTeX that provide features for typesetting in many
- languages. The babel styles are compatible with Plain TeX
- and all versions of LaTeX. (In particular, they are being
- adopted as the standard multilingual styles in LaTeX2e and
- will be the standard in LaTeX3 when it is released.)</p>
-
- <p>To date, babel styles exist for Catalan, Croatian,
- Cyrillic, Czech, Danish, Dutch, English, Esperanto,
- Finnish, French, Galician, German, Italian, Hungarian,
- Norwegian, Polish, Portuguese, Romanian, Russian, Slovak,
- Slovenian, Spanish, Swedish, and Turkish, as well as
- several dialects (American as a dialect of English, for
- example).</p>
-
- <p>Example&#160;<a href="ch07.html#ex.usinglangs"
- title="Example&#160;7.1.&#160;{A Sample Multilingual Document Using English and French}">
- Example&#160;7.1</a> shows the skeletal structure of a
- document using the English and French styles. Within the
- document, the \selectlanguage control sequence is used to
- switch between languages.<sup>[<a id="id2890568"
- name="id2890568" href="#ftn.id2890568">94</a>]</sup> The
- language that is in effect by default is determined when
- the format file is created.</p>
-
- <div class="example">
- <a id="ex.usinglangs" name="ex.usinglangs"></a>
-
- <p class="title"><b>Example&#160;7.1.&#160;{A Sample
- Multilingual Document Using English and French}</b></p>
-<pre class="screen">
-\documentstyle[english,francais]{article}
-\begin{document}
-This is a document which uses both English and
-French. \selectlanguage{french} Mais, je ne parle plus
-fran\c{c}ais. \selectlanguage{english} So I won't try
-to make this example very long.
-\end{document}
-</pre>
- </div>
-
- <p>Selecting a language automatically has the following
- effects:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>It selects hyphenation patterns<a id="id2890625"
- class="indexterm" name="id2890625"></a> for the
- language. This means that paragraphs of text will be
- hyphenated according to the conventions of the
- language in use.<sup>[<a id="id2890639"
- name="id2890639" href="#ftn.id2890639">95</a>]</sup>
- Switching hyphenation patterns is possible only if
- the format file being used by TeX contains
- hyphenation rules for language<a id="id2890550"
- class="indexterm" name="id2890550"></a>.</p>
- </li>
-
- <li>
- <p>It automatically translates the names of all the
- document elements into the selected language. For
- example, if you insert the \tableofcontents when
- French<a id="id2890670" class="indexterm"
- name="id2890670"></a> is the selected language, the
- table of contents will be called the &#8220;Table des
- mati\`eres&#8221; instead of &#8220;Table of
- Contents.&#8221;</p>
- </li>
-
- <li>
- <p>It alters the format of the date produced by the
- \today macro to fit the conventions of the selected
- language. In American, \today is &#8220;January 30,
- 1994&#8221;; in English it is &#8220;30th January
- 1994&#8221;; and in French it is &#8220;30 janvier
- 1994.&#8221;<a id="id2902752" class="indexterm"
- name="id2902752"></a></p>
- </li>
-
- <li>
- <p>It defines particular typing shortcuts to make
- writing the selected language more convenient for the
- typist. For example, the French<a id="id2902772"
- class="indexterm" name="id2902772"></a> style makes
- several punctuation characters into macros so that
- extra space is automatically inserted before them
- according to French typographic conventions<a
- id="id2902783" class="indexterm"
- name="id2902783"></a>.</p>
- </li>
- </ul>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.babelfmt"
- name="sec.babelfmt"></a>Building Multilingual Babel
- Formats</h3>
- </div>
- </div>
-
- <p>Building a multilingual format file<a id="id2902810"
- class="indexterm" name="id2902810"></a> is very much like
- building a format<a id="id2902819" class="indexterm"
- name="id2902819"></a> for a single language. The only
- difference is that instead of loading a single set of
- hyphenation patterns (generally from a file called
- <tt>hyphen.tex</tt>), you will need hyphenation patterns
- for each language that you want to use. These can be
- obtained from the CTAN archives in the directory
- <tt>tex-archive/language/hyphenation</tt>.</p>
-
- <p>If you have a file called <tt>hyphen.tex</tt> on your
- system, rename it. This file is distributed as part of
- the standard TeX distribution and contains American
- English hyphenation patterns, so <tt>ushyphen.tex</tt> is
- an appropriate name.</p>
-
- <p>Next, create a file called <tt>language.dat</tt> that
- contains one line for each language you want to use. Each
- line should list the language name and the file
- containing hyphenation patterns for that language. For
- example, an appropriate <tt>language.dat</tt> file for
- the format used to typeset Example&#160;<a
- href="ch07.html#ex.usinglangs"
- title="Example&#160;7.1.&#160;{A Sample Multilingual Document Using English and French}">
- Example&#160;7.1</a> might contain these lines:</p>
-<pre class="screen">
-english ehyphen.tex
-francais fr8hyph.tex
-</pre>
-
- <p>Now, proceed to construct the format file using
- iniTeX<a id="id2902920" class="indexterm"
- name="id2902920"></a> according to the instructions
- distributed with the format or by following the
- suggestions in Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.
- When iniTeX complains that it cannot find
- <tt>hyphen.tex</tt>, provide the alternate name
- <tt>babel.hyphen</tt>. This will use
- <tt>language.dat</tt> to load the appropriate hyphenation
- patterns and associate them with the languages you
- specified.</p>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>The first language that you list in
- <tt>language.dat</tt> will be the default language for
- the format file that you create.</p>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.asciijtex" name="sec.asciijtex"></a>TeX
- Pitfalls</h2>
- </div>
- </div>
-
- <p>TeX 3.x, the Cork Encoding<a id="id2903012"
- class="indexterm" name="id2903012"></a>, and
- language-specific macro files are not &#8220;magic
- bullets&#8221; that can solve all of the problems that
- arise in typesetting multilingual documents or writing
- macros that are useful in all language contexts. Some of
- the deficiencies are really insoluble without changing the
- TeX program in ways that are not allowed by Knuth. Two such
- problems are mentioned here:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>The \uppercase and \lowercase primitives are
- problematic.</p>
-
- <p>There is a strict one-to-one mapping between
- lowercase and uppercase letters in TeX.
- Unfortunately, accented letters may require different
- mappings. Consider these examples:</p>
-<pre class="screen">
-&lt;para&gt; \begin{tabular}{lll}
- &lt;literal&gt;\"I with two dots&lt;/literal&gt; &amp; \"I with two dots &amp; What you typed \\
- &lt;literal&gt;\"i with two dots&lt;/literal&gt; &amp; \"i with two dots &amp; Result of \lowercase \\
- &lt;literal&gt;\"\i with two dots&lt;/literal&gt; &amp; \"\i with two dots &amp; Correct lowercase
- \end{tabular}
-</pre>
-
- <p>Because no information about the accent is known,
- the result of passing your text to the \lowercase
- primitive is not correct.</p>
-
- <p>This problem can be minimized by using an input
- character set which contains the accented letters
- that you need. This allows you to establish the
- appropriate one-to-one relationships.</p>
-
- <p>Some of the characters chosen for the Cork
- encoding were driven by this weakness as well. The
- only reason that &#8220;{\dcr\char"DF}&#8221; is a
- glyph is so that it can be the \uppercase character
- for &#8220;{\dcr\char"FF}.&#8221;</p>
-
- <p>TeX doesn't distinguish between a dash used in a
- compound word (for example,
- &#8220;wish-fulfillment&#8221;) and a dash used for
- hyphenation.</p>
-
- <p>This distinction isn't necessary in English
- because English doesn't have any end-of-word
- ligatures<a id="id2903112" class="indexterm"
- name="id2903112"></a>. Imagine a language where
- &#8220;sh&#8221; should become &#8220;x&#8221; at the
- end of a word.<sup>[<a id="id2903130"
- name="id2903130" href="#ftn.id2903130">96</a>]</sup>
- A compound word like &#8220;push-ready&#8221; should
- be typeset &#8220;pux-ready&#8221; whereas a word
- like &#8220;pushover&#8221; should remain
- &#8220;push-over&#8221; if it is hyphenated across a
- line break.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2903161"
- name="id2903161"></a>Very Complex Languages</h2>
- </div>
- </div>
-
- <p>The following sections describe TeX packages
- (collections of macros, fonts, and other files) that allow
- you to typeset languages very different from English.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2903174"
- name="id2903174"></a>Japanese</h3>
- </div>
- </div>
-
- <p>Typesetting Japanese<a id="id2903183"
- class="indexterm" name="id2903183"></a> involves solving
- several problems. The first is the task of entering
- Japanese text with an editor. There are many editors on
- many platforms that can handle Japanese input. Although
- there are also established ways to romanize Japanese text
- so that it can be displayed on terminals that do not
- provide support for Japanese input, these are bound to be
- inconvenient for anyone seriously writing in Japanese. If
- you are in a position to edit Japanese text, you are
- probably already aware of several good editors.</p>
-
- <p>The second problem is that typesetting Japanese with
- TeX requires many, many fonts. The fact that a single
- font can hold no more than 256 symbols means that dozens
- (perhaps hundreds) of fonts are required to represent all
- of the myriad symbols used in everyday Japanese writing.
- There are some hard-coded limits on the number of fonts
- that a single TeX document can use, and it is possible to
- bump into them pretty quickly when typesetting a language
- like Japanese.</p>
-
- <p>Another problem is printing the output. Assembling a
- collection of fonts that contain high-quality glyphs for
- all of the necessary characters is a time consuming and
- potentially expensive task. At present, the
- freely-available fonts are of relatively low quality.</p>
-
- <p>A complete discussion of these issues, and many others
- can be found in <span class="emphasis"><em>Understanding
- Japanese Information Processing</em></span>&#160;[<a
- href="bi01.html#kl:japinfoproc">kl:japinfoproc</a>].</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2903244"
- name="id2903244"></a>ASCII Nihongo TeX</h4>
- </div>
- </div>
-
- <p>ASCII Nihongo TeX<a id="id2903253" class="indexterm"
- name="id2903253"></a><a id="id2903264"
- class="indexterm" name="id2903264"></a> (also known as
- \jtex<a id="id2903278" class="indexterm"
- name="id2903278"></a>) is a complete, Japanized version
- of TeX. Instead of trying to shoehorn Japanese into
- traditional TeX programs, all of the programs have been
- modified to accept files containing standard Japanese
- text (two bytes per character). This section describes
- the ASCII Corporation<a id="id2903294"
- class="indexterm" name="id2903294"></a>'s version of
- \jtex. See the section called &#8220;<a
- href="ch07.html#sec.nttjtex" title="NTT \jtex">the
- section called &#8220;NTT \jtex&#8221;</a>&#8221; for
- information about NTT's version of \jtex. You can get
- the ASCII version of \jtex from
- <tt>ftp.ascii.co.jp</tt> (133.152.1.1).</p>
-
- <p>ASCII Nihongo TeX is based on TeX 2.9 and can read
- input files coded with JIS, Shift-JIS, EUC, and KUTEN.
- The <tt>DVI</tt> files produced by ASCII \jtex are not
- standard <tt>DVI</tt> files. In order to support the
- large character set for Japanese writing, the
- <tt>DVI</tt> files use commands that are not output by
- standard TeX, so many drivers do not support them. You
- cannot process <tt>DVI</tt> files produced by ASCII
- \jtex with most standard DVI drivers.</p>
-
- <p>Release notes with version 1.7 of \jtex indicate
- that it will be the last public release of \jtex.
- Another product, called pTeX (for Publishing TeX) may
- be released at some time in the future. One advantage
- of pTeX will be the ability to typeset vertically.</p>
-
- <p>The primary disadvantage of the \jtex system is that
- there are no freely-available fonts for it. The authors
- assume that you will be using fonts resident in your
- printer. You may be able to purchase Japanese fonts
- from some font vendors, although I've seen no detailed
- instructions for using them with \jtex. Other, albeit
- more minor, disadvantages are the need to build and
- maintain an entire parallel TeX distribution and the
- fact that standard <tt>DVI</tt> drivers cannot process
- \jtex <tt>DVI</tt> files.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.nttjtex"
- name="sec.nttjtex"></a>NTT \jtex</h4>
- </div>
- </div>
-
- <p>\jtex\index{NTT jtex@NTT \jtex}<a id="id2903430"
- class="indexterm" name="id2903430"></a> is a complete,
- Japanized version of TeX. Instead of trying to shoehorn
- Japanese into traditional TeX programs, all of the
- programs have been modified to accept files containing
- standard Japanese text (two bytes per character). This
- section describes NTT's version of \jtex. See the
- section called &#8220;<a href="ch07.html#sec.asciijtex"
- title="TeX Pitfalls">the section called &#8220;TeX
- Pitfalls&#8221;</a>&#8221; for information about ASCII
- Corporation's version of \jtex. You can get the NTT
- version of \jtex from <tt>ftp.math.metro-u.ac.jp</tt>
- (133.86.76.25)</p>
-
- <p>NTT \jtex is based on TeX 3.14 and can read input
- files coded with JIS, Shift-JIS, and EUC. In addition
- to support for commercial Japanese fonts, NTT \jtex
- includes a set of fonts generated from 24x24 dot
- bitmaps (JIS C-6234). Unlike ASCII \jtex, NTT produces
- standard <tt>DVI</tt> files.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2903490"
- name="id2903490"></a>Poor Man's Japanese TeX</h4>
- </div>
- </div>
-
- <p>Poor Man's Japanese TeX (\,\pmj)<a id="id2903500"
- class="indexterm" name="id2903500"></a><a
- id="id2903512" class="indexterm" name="id2903512"></a>
- is a freely-available Japanese typesetting system that
- sits on top of standard TeX. The Japanese sections of
- the input file must use the Shift-JIS encoding; a
- conversion program is supplied to convert JIS encoded
- input files into Shift-JIS. If you use another
- encoding, such as EUC<a id="id2903531"
- class="indexterm" name="id2903531"></a>, you will have
- to find some way to convert it into Shift-JIS before
- you can use \pmj.</p>
-
- <p>\pmj solves the font problem in a clever way:
- MetaFont outlines for Japanese characters are
- mechanically produced from freely-available bitmaps.
- This results in relatively low quality characters, but
- at least they're free!</p>
-
- <p>The Paulownia Court, the opening passage from the
- 800-year-old novel <span class="emphasis"><em>The Tale
- of the Genji</em></span>, is shown in Figure&#160;<a
- href="ch07.html#fig.pmj"
- title="Figure&#160;7.2.&#160;Poor Man's Japanese">Figure&#160;7.2</a>.
- This sample was typeset by \pmj.</p>
-
- <div class="figure">
- <a id="fig.pmj" name="fig.pmj"></a>
-
- <p class="title"><b>Figure&#160;7.2.&#160;Poor Man's
- Japanese</b></p>
-
- <div class="mediaobject">
- <img src="pgenji.eps" />
- </div>
- </div>
-
- <p>The \pmj documentation lists the following
- advantages and disadvantages:</p>
-
- <p>\pmj Advantages</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>It is available now.</p>
- </li>
-
- <li>
- <p>It is free.</p>
- </li>
-
- <li>
- <p>It works with standard TeX.</p>
- </li>
-
- <li>
- <p>It is device independent, but has relatively
- poor quality fonts. The relative lack of quality
- is magnified by higher resolution output devices,
- unfortunately.</p>
- </li>
-
- <li>
- <p>It uses a set of free fonts mechanically
- produced from bitmaps.</p>
- </li>
- </ul>
- </div>
-
- <p>\pmj Disadvantages</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>It is somewhat crude and unlikely to be
- improved upon to any great extent.</p>
- </li>
-
- <li>
- <p>It uses low quality fonts.</p>
- </li>
-
- <li>
- <p>It requires a large number of fonts and as a
- result, lots of disk space.</p>
- </li>
-
- <li>
- <p>It provides no access to slanted, bold, or
- other Japanese type-styles.</p>
- </li>
-
- <li>
- <p>It cannot typeset vertically.</p>
- </li>
-
- <li>
- <p>It may take days to build the required
- fonts.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2903726"
- name="id2903726"></a>\jemtex</h4>
- </div>
- </div>
-
- <p>\jemtex<a id="id2903735" class="indexterm"
- name="id2903735"></a><a id="id2903745"
- class="indexterm" name="id2903745"></a> is a lot like
- \pmj; it uses fonts constructed from a collection of
- 24x24 dot bitmaps. The \jemtex font maker includes a
- number of options for tailoring the appearance of the
- characters.</p>
-
- <p>A sample of Japanese typeset with \jemtex is shown
- in Figure&#160;<a href="ch07.html#fig.jemtex"
- title="Figure&#160;7.3.&#160;\jemtex sample">Figure&#160;7.3</a>.</p>
-
- <div class="figure">
- <a id="fig.jemtex" name="fig.jemtex"></a>
-
- <p class="title"><b>Figure&#160;7.3.&#160;\jemtex
- sample</b></p>
-
- <div class="mediaobject">
- <img src="jgenji.eps" />
- </div>
- </div>
-
- <p>\jemtex takes a very different approach to
- processing Japanese text. Instead of providing TeX
- macros to interpret two-byte Japanese symbols in the
- input file, \jemtex provides a preprocessor which
- translates the Japanese input into equivalent TeX
- input. The preprocessor understands EUC<a
- id="id2903810" class="indexterm" name="id2903810"></a>
- and Shift-JIS input files.</p>
-
- <p>Using a preprocessor has several advantages:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>TeX can process the files very quickly.
- Because the input files are not edited by hand,
- they are designed to be processed quickly by TeX
- rather than by human eyes.</p>
- </li>
-
- <li>
- <p>Only the fonts that are actually used must be
- loaded. A system like \pmj must load all of the
- Japanese fonts because it does not know which
- ones will actually be used. \jemtex knows exactly
- which fonts are required for each document.</p>
- </li>
-
- <li>
- <p>The preprocessor can handle subtle spacing
- issues automatically.</p>
- </li>
-
- <li>
- <p>The preprocessor can provide discretionary
- hyphens for TeX, thereby allowing TeX to
- hyphenate Japanese correctly.</p>
- </li>
- </ul>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2903882"
- name="id2903882"></a>Chinese</h3>
- </div>
- </div>
-
- <p>The general problems that apply to Japanese
- typesetting also apply to Chinese.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2903893"
- name="id2903893"></a>Poor Man's Chinese TeX</h4>
- </div>
- </div>
-
- <p>Poor Man's Chinese TeX (\pmc)<a id="id2903902"
- class="indexterm" name="id2903902"></a> <a
- id="id2903916" class="indexterm" name="id2903916"></a>
- <a id="id2903924" class="indexterm"
- name="id2903924"></a> <a id="id2903939"
- class="indexterm" name="id2903939"></a> is closely
- related to \pmj. The Chinese input files should be
- encoded with 8-bit GB encoding (GB 2312-80). If you use
- another encoding, you will have to convert it into the
- 8-bit GB encoding before you can use \pmc.</p>
-
- <p>The \pmc package uses the same technique as \pmj to
- construct Chinese fonts. The relative advantages and
- disadvantages of \pmj apply equally to \pmc.</p>
-
- <p>Two sets of Chinese characters are available:
- traditional and simplified.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2903985"
- name="id2903985"></a>Arabic</h3>
- </div>
- </div>
-
- <p>Typesetting in Arabic<a id="id2904001"
- class="indexterm" name="id2904001"></a> can be
- accomplished with the \arabTeX<a id="id2904010"
- class="indexterm" name="id2904010"></a> package. \arabTeX
- includes a complete set of fonts and macros for producing
- documents in Persian, Arabic, and related scripts. An
- example of Arabic is shown in Figure&#160;<a
- href="ch07.html#fig.flang.arab"
- title="Figure&#160;7.4.&#160;Arabic text typeset with ArabTeX">
- Figure&#160;7.4</a> on page&#160;<a
- href="ch07.html#fig.flang.arab"
- title="Figure&#160;7.4.&#160;Arabic text typeset with ArabTeX">
- Figure&#160;7.4</a>.</p>
-
- <div class="figure">
- <a id="fig.flang.arab" name="fig.flang.arab"></a>
-
- <p class="title"><b>Figure&#160;7.4.&#160;Arabic text
- typeset with ArabTeX</b></p>
-
- <div class="mediaobject">
- <img src="arab.eps" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2904076"
- name="id2904076"></a>Hebrew</h3>
- </div>
- </div>
-
- <p>Typesetting left-to-right Hebrew<a id="id2904085"
- class="indexterm" name="id2904085"></a> (or occasional
- Hebrew words in an English document) is relatively easy.
- The required fonts and TeX macros are available from
- \path|noa.huji.ac.il| and on the CTAN archives in
- <tt>language/hebrew</tt>.<sup>[<a id="id2904109"
- name="id2904109" href="#ftn.id2904109">97</a>]</sup></p>
-
- <p>Typesetting right-to-left Hebrew is more complicated.
- First, you will need an editor that handles right-to-left
- text entry, preferably one that displays Hebrew text.</p>
-
- <p>After you have constructed a document that uses
- right-to-left Hebrew, you will need a special version of
- TeX, called \XeT<a id="id2904128" class="indexterm"
- name="id2904128"></a>, to process it. \XeT is a version
- of TeX that understands right-to-left typesetting.</p>
-
- <p>Early versions of \XeT, called TeX-\XeT<a
- id="id2904148" class="indexterm" name="id2904148"></a>,
- produced nonstandard <tt>DVI</tt> files called
- <tt>IVD</tt> files<a id="id2904178" class="indexterm"
- name="id2904178"></a>. If you use TeX-\XeT, a special
- program called <b>ivd2dvi</b><a id="id2904204"
- class="indexterm" name="id2904204"></a> must be used to
- translate the <tt>IVD</tt> files into <tt>DVI</tt> files
- before they can be printed. More recently, \XeT has been
- reimplemented to produce standard <tt>DVI</tt> files. The
- new version is called TeX\hbox{-{}-}\XeT<a id="id2904243"
- class="indexterm" name="id2904243"></a>.<sup>[<a
- id="id2904255" name="id2904255"
- href="#ftn.id2904255">98</a>]</sup> They are functionally
- identical. You can get unix and PC versions of \XeT from
- \path|noa.huji.ac.il|. An example of Hebrew is shown in
- Figure&#160;<a href="ch07.html#fig.hebrew"
- title="Figure&#160;7.5.&#160;Hebrew">Figure&#160;7.5</a>
- on page&#160;<a href="ch07.html#fig.hebrew"
- title="Figure&#160;7.5.&#160;Hebrew">Figure&#160;7.5</a>.</p>
-
- <div class="figure">
- <a id="fig.hebrew" name="fig.hebrew"></a>
-
- <p class="title">
- <b>Figure&#160;7.5.&#160;Hebrew</b></p>
-
- <div class="mediaobject">
- <img src="hebrew-sample.eps" />
- </div>
- </div>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2890500" name="ftn.id2890500"
- href="#id2890500">85</a>]</sup> {Chinese and Japanese are
- also typeset vertically. At present, TeX does not support
- vertical typesetting, although there is at least one
- effort underway to provide that feature. See the section
- called &#8220;<a href="ch07.html#sec.asciijtex"
- title="TeX Pitfalls">the section called &#8220;TeX
- Pitfalls&#8221;</a>&#8221; for more information on
- vertical typesetting.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2899397" name="ftn.id2899397"
- href="#id2899397">86</a>]</sup> {The accent macros are
- shown with a lower case e; naturally, any letter that
- needs to be accented can be used in place of the e.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2899840" name="ftn.id2899840"
- href="#id2899840">87</a>]</sup> {These characters are
- available in the DC fonts and were not previously
- available in standard TeX.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2900193" name="ftn.id2900193"
- href="#id2900193">88</a>]</sup> {<tt>isolatin1.sty</tt>
- is available from the CTAN archives in
- <tt>macros/latex/contrib/misc/</tt>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2900241" name="ftn.id2900241"
- href="#id2900241">89</a>]</sup> {If you use electronic
- mail to send files that use any characters other than the
- printable subset of 7-bit ASCII (space through tilde),
- you are bound to run into problems. You can combat this
- problem by using a wrapper (like uuencoding or MIME
- messages) when you send the mail, but those tools are
- outside the scope of this book. Ask your system
- administrator for more assistance with sending binary
- mail.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2900372" name="ftn.id2900372"
- href="#id2900372">90</a>]</sup> {<b>recode</b> is
- available from <tt>prep.ai.mit.edu</tt> and other places
- where GNU software is archived.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2900417" name="ftn.id2900417"
- href="#id2900417">91</a>]</sup> {These are
- &#8220;low-level&#8221; macros. A higher-level interface
- will be provided for each language. See the section
- called &#8220;<a href="ch07.html#sec.babel"
- title="The Babel Styles">the section called &#8220;The
- Babel Styles&#8221;</a>&#8221; later in this chapter for
- more information.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2902146" name="ftn.id2902146"
- href="#id2902146">92</a>]</sup> {Because the &#8220;EC
- fonts&#8221; don't exist yet, I won't mention them
- again.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2902200" name="ftn.id2902200"
- href="#id2902200">93</a>]</sup> {Actually, the issue of
- accents is a difficult one. Different languages which
- have the same letters do not always place accents at the
- same height. This is yet another problem that will have
- to be resolved.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2890568" name="ftn.id2890568"
- href="#id2890568">94</a>]</sup> {Another control
- sequence, <tt>\ iflanguage</tt>, is provided so that you
- can write macros which are sensitive to the language in
- use when they are expanded.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2890639" name="ftn.id2890639"
- href="#id2890639">95</a>]</sup> {Paragraphs that contain
- multiple languages will be hyphenated according to the
- rules of the language in effect when the paragraph
- ends.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2903130" name="ftn.id2903130"
- href="#id2903130">96</a>]</sup> {This is a concocted
- example; to my knowledge, it doesn't actually appear in
- any language.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2904109" name="ftn.id2904109"
- href="#id2904109">97</a>]</sup> {At the time of this
- writing, the material at \path|noa.huji.ac.il| is more
- up-to-date than the material in the CTAN archives.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2904255" name="ftn.id2904255"
- href="#id2904255">98</a>]</sup> {Yes, the only difference
- between the names really is the number of hyphens!}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;6.&#160;Pictures and Figures"
- href="ch06.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;8.&#160;Printing"
- href="ch08.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;6.&#160;Pictures and Figures&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;8.&#160;Printing</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch08.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch08.html
deleted file mode 100644
index 8144b2cb503..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch08.html
+++ /dev/null
@@ -1,2376 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;8.&#160;Printing</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations" />
- <link rel="next" href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;7.&#160;International Considerations"
- href="ch07.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;9.&#160;Previewing"
- href="ch09.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.printing"
- name="chap.printing"></a>Chapter&#160;8.&#160;Printing</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p><a id="id2902696" class="indexterm"
- name="id2902696"></a><a id="id2902703" class="indexterm"
- name="id2902703"></a> The emphasis in this book so far has
- been on getting TeX to process a document that contains all
- the desired typographic elements without error. The result of
- this effort is a <tt>DVI</tt> file<a id="id2902726"
- class="indexterm" name="id2902726"></a>.</p>
-
- <p>The next step is translating the <tt>DVI</tt> file into a
- printed document<a id="id2902441" class="indexterm"
- name="id2902441"></a>. That is the focus of this chapter.
- Usually, you want to preview a document before you print it,
- but in many ways previewers are just a special kind of
- printer. The two do differ significantly, however, so we will
- discuss them separately. (Chapter&#160;<a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- <span class="emphasis"><em><a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a></em></span>,
- describes previewers.)</p>
-
- <p>This chapter explores the issues related to printing a DVI
- file. There are sections concerning the printing of fonts,
- the printing of pictures and figures, and descriptions of
- several kinds of drivers you can use to print TeX
- documents.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.printing" name="sec.printing"></a>Printing
- Fonts</h2>
- </div>
- </div>
-
- <p>If you have <a id="id2902499" class="indexterm"
- name="id2902499"></a><a id="id2902509" class="indexterm"
- name="id2902509"></a> a <tt>TFM</tt> file for a font, you
- can use that font in TeX. In fact, you can use that font at
- an arbitrary magnification in TeX, which means that you can
- use Courier at 13.4pt as easily as Computer Modern Roman at
- 10pt. Unfortunately, this ease of use does not imply that
- the resulting <tt>DVI</tt> file will be easy to print. It
- doesn't even imply that it will be possible to print the
- document. For example, if you request Courier at 13.4pt,
- but it is available in your printer only at 10pt and 12pt
- (and you have no other source for Courier), there is no way
- to print your document without distortion.</p>
-
- <p>This section discusses the issues involved in getting
- the desired fonts to print from your DVI file. Both
- bitmapped and scalable fonts are considered, as well as
- fonts built into the printer. You will also gain a better
- understanding of why some documents do not print, and learn
- alternatives that may enable you to print your
- documents.</p>
-
- <p>Every font can be classified in two broad, independent
- ways: internal versus external, and scalable versus
- bitmapped. Each class of fonts has some advantages and some
- unique problems. In general, there are more restrictions on
- built-in fonts than on external fonts, and more
- restrictions on bitmapped fonts than on scalable fonts.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.bitfonts"
- name="sec.bitfonts"></a>Built-in Fonts</h3>
- </div>
- </div>
-
- <p>Built-in fonts<a id="id2904394" class="indexterm"
- name="id2904394"></a>, whether scalable or bitmapped,
- pose two problems. First, you must obtain the appropriate
- <tt>TFM</tt> files<a id="id2904419" class="indexterm"
- name="id2904419"></a>. Usually, the metric information
- has to be supplied by the vendor and then translated into
- TeX <tt>TFM</tt> format using a conversion tool. No
- vendor that I am aware of distributes TeX metric<a
- id="id2904441" class="indexterm" name="id2904441"></a>
- information directly. The section called &#8220;<a
- href="ch05.html#sec.gettingtfms"
- title="Expressing Design Size in TeX">the section called
- &#8220;Expressing Design Size in TeX&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>,
- describes several options for obtaining metric
- information for built-in fonts.</p>
-
- <p>The second problem is that the DVI driver you are
- using must &#8220;know&#8221; somehow that the
- <tt>TFM</tt> file corresponds to one of the printer's
- internal fonts. When the DVI driver examines the
- <tt>DVI</tt> file, the only information available about
- each font is the name of the <tt>TFM</tt> file that
- describes its metrics. The most common way DVI drivers
- handle this problem is with a font translation file or a
- font substitution file.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2904532"
- name="id2904532"></a>Font substitution in
- emTeX</h4>
- </div>
- </div>
-
- <p>emTeX's DVI driver reads a user-specified font
- substitution file<a id="id2904540" class="indexterm"
- name="id2904540"></a> before processing the
- <tt>DVI</tt> file. A line like the following in the
- font substitution file informs the <b>dvihplj</b><a
- id="id2904572" class="indexterm" name="id2904572"></a>
- driver that <tt>lpr1610u</tt> is an internal font and
- describes the LaserJet control sequence required to
- select it:</p>
-
- <div class="informalexample">
- <div class="literallayout">
- <p>
- lpr1610u&#160;300&#160;=&gt;&#160;pcl:&#160;10U&#160;s0P&#160;s16.66H&#160;s8.5V&#160;s0S&#160;s0B&#160;s0T</p>
- </div>
- </div>
-
- <p>Other substitutions are also possible. For example,
- if you work with documents that come from other systems
- that allow long filenames, you can substitute the long
- names for shorter filenames that are legal under
- MS-DOS. The following line in a font substitution file
- tells emTeX that the font &#8220;<tt>tmsrmn</tt>&#8221;
- should be used anywhere that a <tt>DVI</tt> file uses
- the font &#8220;<tt>Times-Roman</tt>&#8221;:</p>
-
- <div class="informalexample">
- <div class="literallayout">
- <p>Times-Roman&#160;-&gt;&#160;tmsrmn</p>
- </div>
- </div>
-
- <p>You can use even more sophisticated substitutions,
- including pattern matching, for example. Consult <span
- class="emphasis"><em>The {emTeX} DVI Driver
- Manual</em></span>&#160;[<a
- href="bi01.html#em:dvidrv">em:dvidrv</a>] for more
- information.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2904676"
- name="id2904676"></a>Font substitution in
- \dvips</h4>
- </div>
- </div>
-
- <p>The <b>dvips</b><a id="id2904690" class="indexterm"
- name="id2904690"></a> program, which translates
- <tt>DVI</tt> files into PostScript, also reads a font
- substitution file before processing a <tt>DVI</tt>
- file. In addition to identifying which fonts are built
- into the printer, the substitution file can also
- instruct <b>dvips</b> to download PostScript fonts that
- are not resident in your printer if they are used in a
- document.</p>
-
- <p><b>dvips</b> has a system-wide font substitution
- file called <tt>psfonts.map</tt><a id="id2904749"
- class="indexterm" name="id2904749"></a>. This file is
- distributed with <b>dvips</b> and can be customized by
- your system administrator. You can tell <b>dvips</b> to
- load a personal font substitution file by using the
- <span class="emphasis"><em>p</em></span> command in
- <b>dvips</b>'s initialization file (called
- <tt>.dvipsrc</tt> in your home directory on unix
- systems). Consult the <b>dvips</b> documentation for
- more information about setting up an initialization
- file.</p>
-
- <p>The following lines in a font substitution file
- indicate that the font <tt>grbk</tt> (which is the name
- of the <tt>TFM</tt> file) corresponds to the built-in
- printer font Garamond-Book. The <tt>TFM</tt> file
- <tt>hlvcd</tt> corresponds to the printer font
- Helvetica-Condensed. Helvetica-Condensed is not built
- into the printer but is stored in the file
- <tt>/home/walsh/fonts/helvcd.pfb</tt>. If
- <tt>hlvcd</tt> is used in a document, <b>dvips</b> will
- download <tt>helvcd.pfb</tt> automatically when it
- converts the document.</p>
-<pre class="screen">
-grbk Garamond-Book
-hlvcd Helvetica-Condensed &lt;/home/walsh/fonts/helvcd.pfb
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2904885"
- name="id2904885"></a>Font substitution in other
- drivers</h4>
- </div>
- </div>
-
- <p>Other DVI drivers, particularly those written for
- operating environments like Microsoft Windows that
- provide a standard interface to printers, may leave the
- distinction between built-in and external fonts up to
- the operating environment. If this is the case, you
- must use the tools provided by the operating system to
- support the printers and fonts that you require.</p>
-
- <p>If your DVI driver does use a font substitution
- file, make sure that the translations specified
- actually exist. The DVI driver cannot practically
- determine if the font you have specified as built into
- the printer really exists or not. If it doesn't, you
- won't get the output you expect, and the DVI driver
- will not be able to diagnose the problem.</p>
-
- <p>The most significant disadvantage of using built-in
- fonts is that they are not usually available for
- on-screen previewing of your document. Some form of
- font substitution has to be employed to preview a
- document. Sometimes this reduces the utility of
- on-screen previewing. Chapter&#160;<a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- <span class="emphasis"><em><a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a></em></span>,
- discusses this issue in more detail.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2904946"
- name="id2904946"></a>External Fonts</h3>
- </div>
- </div>
-
- <p>External fonts<a id="id2904955" class="indexterm"
- name="id2904955"></a>, those that aren't built into the
- printer, pose a different set of problems. First, they
- have to be available to the DVI driver, and they have to
- be represented in a manner that the DVI driver
- understands. For the vast majority of DVI drivers, this
- means that the fonts must be stored in files on your hard
- disk in <tt>PK</tt> format. The <tt>PK</tt><a
- id="id2904990" class="indexterm" name="id2904990"></a>
- files contain a compressed, bitmapped rendering of the
- font at a particular resolution. For more information
- about <tt>PK</tt> files and other bitmapped-font issues,
- see &#8220;<a href="ch08.html#sec.bitfonts"
- title="Built-in Fonts">the section called &#8220;Built-in
- Fonts&#8221;</a>&#8221; later in this chapter.</p>
-
- <p>Most DVI drivers locate fonts by searching in the
- directories contained in an environment variable or in
- some system-dependent locations.</p>
-
- <p>Once the fonts are available, the DVI driver has two
- options for using them: it can download them to the
- printer, or it can send them as bitmapped graphic images.
- Most laser printers can accept downloadable fonts,
- although they may require additional memory to accept
- large numbers of fonts. In either case, the printable
- files are generally larger and print more slowly than
- documents that use the printer's built-in fonts. Of
- course, using external fonts does give you far more
- flexibility than using only built-in fonts.</p>
-
- <p>Unlike a missing internal font, if you attempt to use
- an external font that is not available, your DVI driver
- will be able to detect the problem and may be able to
- substitute another font or compensate in some other
- way.</p>
-
- <div class="sidebar">
- <p class="title"><b>Increasing Printing Speed</b></p>
-
- <p>How can you increase printing speed<a id="id2905074"
- class="indexterm" name="id2905074"></a> if you
- frequently print, on a laser printer, documents that
- use a small number of external fonts (for example,
- several sizes of Computer Modern)? A handy trick is to
- download the fonts manually and then tell the DVI
- driver that the fonts are built-in.</p>
-
- <p>Suppose you use the 7pt, 10pt, and 12pt sizes of
- Computer Modern Roman, and the 12pt and 14pt sizes of
- Computer Modern Bold Extended in most of your
- documents. If you are printing on an HP LaserJet
- printer with emTeX's <b>dvihplj</b>, you could convert
- the relevant <tt>PK</tt> files into HP LaserJet
- softfonts with <b>PKtoSFP</b><a id="id2905121"
- class="indexterm" name="id2905121"></a> (see the
- discussion of bitmapped fonts in the next section to
- determine which <tt>PK</tt> files are relevant). Then
- download them to the printer every morning with a
- utility like <b>Sfload</b><a id="id2905150"
- class="indexterm" name="id2905150"></a>. <b>Sfload</b>
- is part of the <b>Sfware</b><a id="id2905171"
- class="indexterm" name="id2905171"></a> package.
- (Disclaimer: I wrote <b>Sfware</b> so I'm partial to
- it. There are many other programs that can download
- softfonts.) In the font-substitution file for
- <b>dvihplj</b><a id="id2905194" class="indexterm"
- name="id2905194"></a>, simply indicate that those fonts
- are built-in, and <b>dvihplj</b> will no longer
- download them for each document. This can significantly
- decrease the amount of data that must be sent to the
- printer for each document.</p>
-
- <p>Beware, however, that if you fail to download the
- fonts, you will get very badly garbled output when you
- print a document.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2905223"
- name="id2905223"></a>Bitmapped Fonts</h3>
- </div>
- </div>
-
- <p>Each character in a bitmapped font is represented by a
- rectangular array of dots. Some of the dots in this array
- are &#8220;on,&#8221; and some are &#8220;off.&#8221;
- When the dots are printed very close together, they
- provide the illusion of a solid character. Bitmapped
- fonts are common in the TeX community because all of the
- fonts created by MetaFont are printed in bitmapped
- form.</p>
-
- <p>The notion of magnification discussed in the section
- called &#8220;<a href="ch05.html#sec.issueofsize"
- title="What TeX Needs To Know">the section called
- &#8220;What TeX Needs To Know&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a> is
- interpreted as an issue of resolution when dealing with
- bitmapped fonts.</p>
-
- <p>Resolution<a id="id2905279" class="indexterm"
- name="id2905279"></a> is used in a slightly
- counter-intuitive way by DVI drivers. Generally,
- resolution is described as a feature of a device that
- affects the <span
- class="emphasis"><em>appearance</em></span> of images
- printed on that device and not their <span
- class="emphasis"><em>size</em></span>. For example, in
- comparing two drawings in which one was printed on 150dpi
- dot-matrix printer and the other was printed on a 300dpi
- laser printer, I might say, &#8220;the laser printed page
- looks better because it was printed at a higher
- resolution.&#8221;</p>
-
- <p>That's true, but what isn't usually stated explicitly
- is that the comparison is between a 150dpi drawing
- rendered at 150dpi and a 300dpi drawing rendered at
- 300dpi. This is the situation shown in Figure&#160;<a
- href="ch08.html#fig.reschange"
- title="Figure&#160;8.1.&#160;Resolution of the bitmap and the device changed simultaneously">
- Figure&#160;8.1</a> where a 4dpi image is printed at 4dpi
- next to an 8dpi image printed at 8dpi.</p>
-
- <div class="figure">
- <a id="fig.reschange" name="fig.reschange"></a>
-
- <p class="title"><b>Figure&#160;8.1.&#160;Resolution of
- the bitmap and the device changed
- simultaneously</b></p>
-<pre class="screen">
- \input{ft-resch.fig}
-</pre>
- </div>
-
- <p>What if the resolution of the printer were held
- constant? That's the situation shown in Figure&#160;<a
- href="ch08.html#fig.sizechange"
- title="Figure&#160;8.2.&#160;Resolution of the bitmap changed while device held constant">
- Figure&#160;8.2</a>. The 4dpi image printed at 4dpi is
- shown next to the 8dpi image printed at 4dpi. The result
- is that the size of the image is doubled.</p>
-
- <div class="figure">
- <a id="fig.sizechange" name="fig.sizechange"></a>
-
- <p class="title"><b>Figure&#160;8.2.&#160;Resolution of
- the bitmap changed while device held constant</b></p>
-<pre class="screen">
- \input{ft-sizch.fig}
-</pre>
- </div>
-
- <p>This is the technique that DVI drivers use to print a
- larger magnification of the same font; they print a
- version of the font designed for a correspondingly
- higher-resolution device. The same technique is used to
- print at smaller magnifications.</p>
-
- <p>Most DVI drivers use bitmapped fonts stored in
- <tt>PK</tt> files<a id="id2905416" class="indexterm"
- name="id2905416"></a>. The <tt>PK</tt> format is a highly
- compressed binary format.<sup>[<a id="id2905446"
- name="id2905446" href="#ftn.id2905446">99</a>]</sup> Two
- other bitmapped font formats (sometimes accepted by DVI
- drivers) are associated with TeX: <tt>GF</tt><a
- id="id2905494" class="indexterm" name="id2905494"></a>
- and <tt>PXL</tt> files<a id="id2905511" class="indexterm"
- name="id2905511"></a>. The <tt>GF</tt> format is a very
- flat, uncompressed bitmap format produced by several
- utility programs, including MetaFont. The <b>GFtoPK<a
- id="id2905547" class="indexterm"
- name="id2905547"></a></b> program converts <tt>GF</tt>
- files into <tt>PK</tt> files. The <tt>PXL</tt> format<a
- id="id2905584" class="indexterm" name="id2905584"></a> is
- an uncompressed bitmap format; it has been superseded by
- the <tt>PK</tt> format (which achieves better
- compression) and is completely obsolete. If you still
- have <tt>PXL</tt> files, you should convert them to
- <tt>PK</tt> format with the <b>PXtoPK</b><a
- id="id2905640" class="indexterm" name="id2905640"></a>
- utility. If you are using a DVI driver that still
- requires <tt>PXL</tt> files, you should find out about an
- upgrade; the program is obsolete.</p>
-
- <p>The fact that DVI drivers use different resolutions of
- the same font file to obtain different magnifications
- introduces a naming problem. How can the DVI driver
- distinguish between <tt>cmr12.pk</tt> at 300dpi and
- <tt>cmr12.pk</tt> at 360dpi (or any other
- resolution)?</p>
-
- <p>On unix systems, this problem is usually resolved by
- putting the resolution in the filename in front of the
- extension <span class="emphasis"><em>pk</em></span>. For
- example, <tt>cmr12.300pk</tt> is <tt>cmr12</tt> at 300dpi
- while <tt>cmr12.360pk</tt> is <tt>cmr12</tt> at
- 360dpi.</p>
-
- <p>On many other systems, where the operating system
- imposes limits on the length of filenames, a solution is
- achieved by storing the fonts in different
- subdirectories. On MS-DOS, for example, the 300dpi
- version of <tt>cmr12</tt> might be stored in <span
- class="emphasis"><em>\bs texfonts\bs 300dpi\bs
- cmr12.pk</em></span> while the 360dpi version is stored
- in <span class="emphasis"><em>\bs texfonts\bs 360dpi\bs
- cmr12.pk</em></span>.</p>
-
- <p>In either case, you should obey the conventions
- specified by your DVI driver to assure that the DVI
- driver can find the fonts. One common solution to the
- problem of finding fonts is to use an environment
- variable to list the directories where <tt>PK</tt> files
- occur. For example, on a unix system, the environment
- variable <tt>TEXPKS</tt> might hold a list of directories
- separated by colons:<sup>[<a id="id2905773"
- name="id2905773" href="#ftn.id2905773">100</a>]</sup></p>
-<pre class="screen">
-TEXPKS=/usr/local/lib/tex/fonts:/usr/local/lib/tex/fonts/pk: /usr/local/lib/mf/fonts:/usr/local/lib/mf/fonts/pk
-</pre>
-
- <p>Under MS-DOS, the environment variable
- <tt>DVIDRVFONTS</tt> might hold a list of directories
- separated by semicolons:</p>
-<pre class="screen">
-DVIDRVFONTS=C:\TEXFONTS;C:\MYFONTS
-</pre>
-
- <p>The format of the environment variable and how it is
- created or modified is determined by the operating
- environment that you are using. The name of the
- environment variable differs according to the DVI
- driver.</p>
-
- <p>To recap, TeX works with <span
- class="emphasis"><em>magnifications</em></span><a
- id="id2905827" class="indexterm" name="id2905827"></a><a
- id="id2905837" class="indexterm" name="id2905837"></a> of
- abstract, scalable measurements; DVI drivers work with
- <span class="emphasis"><em>resolutions</em></span> of
- fixed, bitmapped images.</p>
-
- <p>To convert a magnification into a resolution, multiply
- the resolution of your output device by the
- magnification. A font at a magnification of 120\% on a
- 300dpi laser printer has a resolution of 360dpi.</p>
-
- <p>To convert a resolution into a magnification, divide
- the font resolution by the resolution of the printer. A
- 420dpi font on a 300dpi laser printer has a magnification
- of 140\%.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2905872"
- name="id2905872"></a>Scalable Fonts</h3>
- </div>
- </div>
-
- <p>Although scalable fonts<a id="id2905881"
- class="indexterm" name="id2905881"></a> used to be very
- uncommon, the proliferation of PostScript printers and
- products like Adobe Type Manager (not to mention built-in
- support for TrueType fonts in Apple System 7.0 and
- Microsoft Windows 3.1) have made these fonts very common.
- It is important to remember that scalable fonts are
- ultimately converted into bitmapped fonts. All printers
- eventually treat the page as a very large bitmap and
- either do or do not deposit a small amount of ink in each
- position in the bitmap.</p>
-
- <p>Most DVI drivers leave the work of performing this
- rasterization to someone else. If you are not using a
- PostScript printer, you probably rely on some other piece
- of software to do the work. Adobe Type Manager and
- built-in support for TrueType are the most common
- software solutions. Some printers, like the LaserJet III,
- have built-in scalable fonts as well, even though they
- are not PostScript printers.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2905916"
- name="id2905916"></a>Font Printing Pitfalls</h3>
- </div>
- </div>
-
- <p>Sometimes you need a font at a size that is not
- available. Because scalable fonts are available at any
- size, this is a problem only with bitmapped fonts<a
- id="id2905928" class="indexterm" name="id2905928"></a><a
- id="id2905940" class="indexterm" name="id2905940"></a>.
- Remember that MetaFont creates bitmapped fonts, but they
- can be scaled because the <tt>MF</tt> source for the font
- is not a bitmap. You can't scale the <tt>PK</tt> file,
- but you can generate a new <tt>PK</tt> file at the size
- you need. In order to do this, you must have MetaFont
- installed, and you must have the <tt>MF</tt> source for
- the font. Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>,
- <span class="emphasis"><em><a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a></em></span>,
- describes how to create a MetaFont font at any size.</p>
-
- <p>If the font isn't a MetaFont font, or you don't have
- the <tt>MF</tt> source, you may still be able to scale
- the font. However, you should be aware before you try
- that the result may be unacceptable. Scaling bitmapped
- fonts causes ugly, jagged edges if the font is scaled
- larger, and loss of detail if it is scaled smaller. Small
- changes in size are sometimes manageable.</p>
-
- <p>The <b>dvips</b> driver will scale bitmapped fonts if
- it cannot find or build the requested font.
- Alternatively, the <b>sffx</b><a id="id2906056"
- class="indexterm" name="id2906056"></a> program can scale
- HP LaserJet softfonts. I don't know of any other scaling
- options.</p>
-
- <p>Non-scalable fonts that are built into the printer
- cannot be scaled at all. If you need to have a built-in
- font at an unavailable size, you will have to substitute
- another font in place of the built-in one.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2906078"
- name="id2906078"></a>Printing Pictures and Figures</h2>
- </div>
- </div>
-
- <p>Pictures<a id="id2906087" class="indexterm"
- name="id2906087"></a><a id="id2906097" class="indexterm"
- name="id2906097"></a> and figures<a id="id2906108"
- class="indexterm" name="id2906108"></a><a id="id2906118"
- class="indexterm" name="id2906118"></a> are frequently the
- least portable elements of a document. Chapter&#160;<a
- href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a>,
- <span class="emphasis"><em><a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a></em></span>,
- describes many of the options that are available for
- including pictures and figures in a document.</p>
-
- <p>If the method used is supported by the DVI driver and
- printer that you use, pictures and figures are
- transparently printed. They are even less difficult to
- print than fonts. On the other hand, if you are attempting
- to print a document which incorporates pictures and figures
- using a method not supported by your DVI driver or printer,
- it may be exceptionally difficult to print the
- document.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2906166"
- name="id2906166"></a>Unsolvable Problems</h3>
- </div>
- </div>
-
- <p><tt>DVI</tt> files are not always
- &#8220;complete&#8221; with respect to pictures and
- figures. Many documents use \special commands to access
- DVI driver or printer-specific features in order to
- include pictures and figures. These \specials may have
- just the name of an external file that contains the
- graphic image to be included. For example, using the
- emTeX drivers, I can include a bitmapped graphic image
- with the command \special\verb|{em:graph spslogo}|. When
- emTeX's DVI drivers process this command, the graphic
- image in the file <tt>spslogo.pcx</tt> is included in the
- output. If I transmit this <tt>DVI</tt> file to another
- computer but forget to transmit the file
- <tt>spslogo.pcx</tt>, there is no way to print the
- <tt>DVI</tt> file with the SPS logo.</p>
-
- <p>At first, it may seem that a good solution to the
- problem described above would be to include the actual
- data for the image in the \special command. But to do
- that, TeX would have to process the image data, defeating
- the purpose of the \special mechanism. The \special
- mechanism is better because it is open ended---it can
- handle new types of graphics, for example, without
- changing TeX.</p>
-
- <p>The second, essentially unsolvable, problem involves
- <tt>DVI</tt> files containing \special commands that have
- embedded data. For example, one set of picture drawing
- \special commands are the <tt>tpic</tt> \specials. If
- your DVI driver does not understand these commands, there
- is no practical way to extract them from the <tt>DVI</tt>
- file in order to convert them into a format your DVI
- driver understands. There may not even be a practical way
- of extracting them from the TeX document to construct a
- printable image. You simply can't print that document
- with the <tt>tpic</tt> figures intact.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2906292"
- name="id2906292"></a>Solvable Problems</h3>
- </div>
- </div>
-
- <p>If you have a document that includes an external
- picture or figure using a method that your DVI driver or
- printer does not understand, and you have the file that
- contains the graphic image and the TeX source for the
- document, you may be able to print it.</p>
-
- <p>The section called &#8220;<a
- href="ch06.html#sec.picconv"
- title="Manipulating Images">the section called
- &#8220;Manipulating Images&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a>,
- lists a wide variety of picture conversion tools that may
- allow you to convert the image into a printable form. For
- example, if the document in question uses a \special
- command to include a <tt>PCX</tt> graphic image, but your
- DVI driver only understands the Macintosh <tt>PICT</tt>
- format, you could use the <b>PBMplus</b><a id="id2906359"
- class="indexterm" name="id2906359"></a> utilities to
- convert the <tt>PCX</tt> image into <tt>PICT</tt>
- format.</p>
-
- <p>A conversion that might frequently be necessary if you
- work on both PostScript and non-PostScript printers is
- conversion from encapsulated PostScript to a bitmap
- format. This is a translation that <b>Ghostscript</b> or
- some other PostScript interpreter can perform.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2906405"
- name="id2906405"></a>Pictures Using Only TeX</h3>
- </div>
- </div>
-
- <p>Device-independent pictures created using only TeX
- pose no particular printing problems. These include the
- LaTeX <tt>picture</tt> environment, as well as the PiCTeX
- and <b>XYPic</b> macro packages.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2906432"
- name="id2906432"></a>MetaFont Figures</h3>
- </div>
- </div>
-
- <p>Pictures<a id="id2906441" class="indexterm"
- name="id2906441"></a><a id="id2906454" class="indexterm"
- name="id2906454"></a> created with MetaFont (using
- <b>MFPic</b>, <b>Fig2MF</b>, or MetaFont directly) are
- really MetaFont fonts. As a result, they can be created
- for almost any raster output device.<sup>[<a
- id="id2906483" name="id2906483"
- href="#ftn.id2906483">101</a>]</sup> As long as MetaFont
- is available and the figures aren't too large, they pose
- no problems. Very large images may break some DVI drivers
- or may not be printable on some output devices.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2906500"
- name="id2906500"></a>Scalable Images</h3>
- </div>
- </div>
-
- <p>Scalable formats<a id="id2906509" class="indexterm"
- name="id2906509"></a>, primarily PostScript and HPGL, are
- difficult to convert to other printing technologies.
- However, the <b>Ghostscript</b><a id="id2906527"
- class="indexterm" name="id2906527"></a> program is one
- option for PostScript figures, and <b>hp2xx</b><a
- id="id2906542" class="indexterm" name="id2906542"></a>
- can convert a subset of HPGL commands into other
- formats.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2906554"
- name="id2906554"></a>Bitmap Images</h3>
- </div>
- </div>
-
- <p>Bitmap images<a id="id2906563" class="indexterm"
- name="id2906563"></a> are generally the easiest to
- convert from one format to another, but there is another
- issue that is more difficult to deal with---resolution.
- Printing a bitmap image at 1200dpi if the original is
- only 300dpi is not easy.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2906581"
- name="id2906581"></a>Selected Drivers</h2>
- </div>
- </div>
-
- <p>Table&#160;<a href="ch08.html#tab.drivers"
- title="Table&#160;8.1.&#160;Common DVI Drivers">Table&#160;8.1</a>
- lists a number of common DVI drivers<a id="id2906602"
- class="indexterm" name="id2906602"></a><a id="id2906609"
- class="indexterm" name="id2906609"></a> used to print TeX
- documents (as opposed to previewing them). These drivers
- are discussed in more detail in this section. The list of
- drivers described here is nowhere near complete. The
- presence or absence of a particular driver from this list
- is not intended as a reflection on the quality of the
- driver. I tried to select a representative set of free and
- commercial drivers. Drivers for other printers usually
- offer similar features.</p>
-
- <div class="table">
- <a id="tab.drivers" name="tab.drivers"></a>
-
- <p class="title"><b>Table&#160;8.1.&#160;Common DVI
- Drivers</b></p>
-
- <table summary="Common DVI Drivers" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf DVI driver</th>
-
- <th align="left">\bf Supplier</th>
-
- <th align="left">\bf System</th>
-
- <th align="left">\bf Printers</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left"><b>dvihplj</b></td>
-
- <td align="left">Free (emTeX)</td>
-
- <td align="left">&#160;</td>
-
- <td align="left">HP LaserJet compatible</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvidot</b></td>
-
- <td align="left">Free (emTeX)</td>
-
- <td align="left">MS-DOS+OS/2</td>
-
- <td align="left">Most dot matrix</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvipcx</b></td>
-
- <td align="left">Free (emTeX)</td>
-
- <td align="left">&#160;</td>
-
- <td align="left"><tt>PCX</tt> graphic images</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvilj2</b></td>
-
- <td align="left">Free (<span
- class="emphasis"><em>dvi2xx</em></span>)</td>
-
- <td align="left">Most</td>
-
- <td align="left">HP LaserJet compatible</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvips</b></td>
-
- <td align="left">Free (<span
- class="emphasis"><em>dvips</em></span>)</td>
-
- <td align="left">Most</td>
-
- <td align="left">PostScript</td>
- </tr>
-
- <tr>
- <td align="left"><b>DVILASER/HP</b></td>
-
- <td align="left">ArborText</td>
-
- <td align="left">MS-DOS, Unix</td>
-
- <td align="left">HP LaserJet compatible</td>
- </tr>
-
- <tr>
- <td align="left"><b>DVILASER/PS</b></td>
-
- <td align="left">ArborText</td>
-
- <td align="left">MS-DOS, Unix</td>
-
- <td align="left">PostScript</td>
- </tr>
-
- <tr>
- <td align="left"><b>PTI Laser/HP</b></td>
-
- <td align="left">Personal TeX</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">HP LaserJet compatible</td>
- </tr>
-
- <tr>
- <td align="left"><b>PTI Laser/PS</b></td>
-
- <td align="left">Personal TeX</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">PostScript</td>
- </tr>
-
- <tr>
- <td align="left"><b>PTI Jet</b></td>
-
- <td align="left">Personal TeX</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">HP DeskJet compatible</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvipsone</b></td>
-
- <td align="left">Y&amp;Y</td>
-
- <td align="left">MS-DOS</td>
-
- <td align="left">PostScript</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2906990"
- name="id2906990"></a>emTeX Drivers</h3>
- </div>
- </div>
-
- <p>The emTeX<a id="id2906999" class="indexterm"
- name="id2906999"></a> distribution includes three DVI
- drivers: <b>dvihplj</b><a id="id2907020"
- class="indexterm" name="id2907020"></a> for printing on
- HP LaserJet, DeskJet, PaintJet, QuietJet printers (as
- well as the Kyocera laser printer), <b>dvidot</b><a
- id="id2907035" class="indexterm" name="id2907035"></a>
- for printing on a wide variety of dot-matrix printers,
- and <b>dvipcx</b><a id="id2907050" class="indexterm"
- name="id2907050"></a> for translating DVI files into
- <tt>PCX</tt> graphics images (for faxing, for example).
- The printers that <b>dvidot</b> supports are listed
- below. If your dot-matrix printer isn't listed, detailed
- instructions in the emTeX documentation will probably
- allow you to construct an appropriate parameter file.</p>
-
- <table class="simplelist" border="0"
- summary="Simple list">
- <tr>
- <td>Apple Imagewriter</td>
-
- <td>IBM Proprinter 4202</td>
- </tr>
-
- <tr>
- <td>C.ITOH 8510A</td>
-
- <td>IBM Proprinter 4207</td>
- </tr>
-
- <tr>
- <td>Canon Bubble Jet BJ-10e</td>
-
- <td>IBM Proprinter 4208</td>
- </tr>
-
- <tr>
- <td>EPSON FX and RX series</td>
-
- <td>NEC P6, Panasonic KX-P1124</td>
- </tr>
-
- <tr>
- <td>EPSON LQ series</td>
-
- <td>NEC P7</td>
- </tr>
-
- <tr>
- <td>IBM Proprinter 4201</td>
-
- <td>Tandy DMP-130</td>
- </tr>
- </table>
-
- <p>All of the emTeX drivers support several \special
- commands for including bitmapped graphics and lines at
- any angle.</p>
-
- <p>The Computer Modern fonts in <tt>PK</tt> format occupy
- several directories and considerable space on disk. To
- minimize the impact of keeping several magnifications of
- fonts around, the emTeX drivers introduced the concept of
- <span class="emphasis"><em>font libraries</em></span>.
- Font libraries<a id="id2907170" class="indexterm"
- name="id2907170"></a> are single files that contain many,
- many <tt>PK</tt> fonts<a id="id2907189" class="indexterm"
- name="id2907189"></a><a id="id2907208" class="indexterm"
- name="id2907208"></a>. The fonts distributed with emTeX
- are distributed in font library format. The
- <b>fontlib</b> program, distributed with emTeX, allows
- you to create and maintain font libraries of your
- own.</p>
-
- <p>The emTeX drivers support automatic font generation
- starting with version 1.4S. This is accomplished by a
- second program, <b>dvidrv</b><a id="id2907239"
- class="indexterm" name="id2907239"></a>, that runs the
- DVI driver and then <b>MFjob</b><a id="id2907254"
- class="indexterm" name="id2907254"></a>, if required, to
- build the fonts. The relationship between these
- components is shown in Figure&#160;<a
- href="ch08.html#fig.emdvi"
- title="Figure&#160;8.3.&#160;Previewing and printing with emTeX">
- Figure&#160;8.3</a>.</p>
-
- <div class="figure">
- <a id="fig.emdvi" name="fig.emdvi"></a>
-
- <p class="title"><b>Figure&#160;8.3.&#160;Previewing
- and printing with emTeX</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>Starting with version 1.4t,<sup>[<a id="id2907302"
- name="id2907302" href="#ftn.id2907302">102</a>]</sup>
- emTeX's <b>dvihplj</b> supports 600dpi fonts (for the
- LaserJet 4 series) and built-in printer fonts.</p>
-
- <p>The following list of features highlights some of the
- capabilities of the emTeX drivers:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Printing of a range of pages</p>
- </li>
-
- <li>
- <p>Printing of multiple copies (with or without
- collating)</p>
- </li>
-
- <li>
- <p>Reverse ordering of pages</p>
- </li>
-
- <li>
- <p>Selection of duplex printing</p>
- </li>
-
- <li>
- <p>Ability to scale <tt>PK</tt> files to the
- requested size if an appropriate <tt>PK</tt> file
- is unavailable. This may result in poorer output
- quality due to distortion, but that's not emTeX's
- fault.</p>
- </li>
-
- <li>
- <p>Extremely flexible support for printing booklets
- and &#8220;n-up&#8221; arrangements of pages</p>
- </li>
-
- <li>
- <p>Selection of paper size and dimensions (margins,
- etc.)</p>
- </li>
-
- <li>
- <p>Transformations (rotation by a multiple of 90
- degrees)</p>
- </li>
-
- <li>
- <p>Changes in magnification and resolution of
- output</p>
- </li>
-
- <li>
- <p>Support for font libraries</p>
- </li>
-
- <li>
- <p>Support for font compression in printers with
- that feature</p>
- </li>
-
- <li>
- <p>Ability to download each page as a large bitmap
- (to overcome font limitations in some printers)</p>
- </li>
-
- <li>
- <p>Support for automatic font generation</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2907474"
- name="id2907474"></a>dvilj2</h3>
- </div>
- </div>
-
- <p><b>dvilj2</b><a id="id2907487" class="indexterm"
- name="id2907487"></a> is a free driver for the HP
- LaserJet Series II printer. It is part of the
- <b>dvi2xx</b> distribution, which also includes drivers
- for the HP LaserJet Series IIP and III printers, as well
- as a driver for the IBM 3812 page printer.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2907508"
- name="id2907508"></a>dvips</h3>
- </div>
- </div>
-
- <p><b>dvips</b><a id="id2907521" class="indexterm"
- name="id2907521"></a> is one of the most popular
- PostScript <tt>DVI</tt> drivers. It is available for
- unix, MS-DOS, and OS/2 platforms. It may also be
- available on other platforms because the source code is
- freely available. <b>dvips</b> supports a wide range of
- \special commands for controlling the PostScript output,
- including pictures and figures and raw PostScript
- code.</p>
-
- <p>The following list of features highlights some of
- <b>dvips</b>'s capabilities:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Inclusion of printer-specific prologue files</p>
- </li>
-
- <li>
- <p>Support for compressed PostScript pictures and
- figures</p>
- </li>
-
- <li>
- <p>Automatic creation of pseudo-bold and
- pseudo-italic fonts</p>
- </li>
-
- <li>
- <p>Ability to run as a filter</p>
- </li>
-
- <li>
- <p>Automatic splitting of documents into sections
- to prevent out-of-memory errors on the printer</p>
- </li>
-
- <li>
- <p>Printing of crop marks</p>
- </li>
-
- <li>
- <p>Printing of a range of pages (by physical sheet
- or TeX page number)</p>
- </li>
-
- <li>
- <p>Selection of manual-feed on the printer</p>
- </li>
-
- <li>
- <p>Limit on number of output pages</p>
- </li>
-
- <li>
- <p>Reverse order of pages</p>
- </li>
-
- <li>
- <p>Selection of paper type</p>
- </li>
-
- <li>
- <p>Changes in magnification of the output</p>
- </li>
-
- <li>
- <p>Printing of odd/even pages only</p>
- </li>
-
- <li>
- <p>Printing of multiple copies (with or without
- collating)</p>
- </li>
-
- <li>
- <p>Stripping of comments (to avoid printer/spooler
- bugs)</p>
- </li>
-
- <li>
- <p>Moving of printed image left/right or up/down
- page</p>
- </li>
-
- <li>
- <p>Compression of fonts before downloading</p>
- </li>
- </ul>
- </div>
-
- <p>An option to the <b>dvips</b> driver can be used to
- indicate which printer the output is destined for. This
- allows many printer-specific options (resolution, paper
- sizes, etc.) to be specified in a configuration file,
- removing from the user the burden of remembering
- them.</p>
-
- <p>Automatic font generation is supported by
- <b>dvips</b>, as described above. <b>dvipsk</b><a
- id="id2907755" class="indexterm" name="id2907755"></a>, a
- modified version of <b>dvips</b>, also supports a
- font-searching mechanism that greatly simplifies the task
- of specifying which directories contain font files. If
- any directory specification in the font path ends with
- two slashes, <b>dvips</b> searches that directory and all
- of its subdirectories for the font files. This allows you
- to create a font directory structure like the one shown
- here:</p>
-<pre class="screen">
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>/<span
-class="emphasis"><em>typeface</em></span>
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>/<span
-class="emphasis"><em>typeface</em></span>/src
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>/<span
-class="emphasis"><em>typeface</em></span>/tfm
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>/<span
-class="emphasis"><em>typeface</em></span>/vf
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>/<span
-class="emphasis"><em>typeface</em></span>/vpl
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>/<span
-class="emphasis"><em>typeface</em></span>/glyphs
-/usr/local/lib/tex/fonts/<span
-class="emphasis"><em>supplier</em></span>/<span
-class="emphasis"><em>typeface</em></span>/glyphs/pk
-</pre>
-
- <p>This arrangement is advantageous because it organizes
- your fonts and simplifies maintenance of the directories
- that contain them. If <tt>/usr/local/lib/tex/fonts//</tt>
- is in the font search path, <b>dvips</b> will search
- through all of the font directories for the files that it
- needs. For example, it might find the <tt>TFM</tt> file
- for <tt>cmr10</tt> in
- <tt>/usr/local/lib/tex/fonts/free/cm/tfm</tt>. The
- directory
- <tt>/usr/local/lib/tex/fonts/adobe/garamond/glyphs/type1</tt>
- is the location for the PostScript source of the
- Garamond-Italic font.</p>
-
- <p>The <b>dvips</b> distribution includes the
- <b>afm2tfm</b><a id="id2907929" class="indexterm"
- name="id2907929"></a> program for creating TeX font
- metrics from Adobe <tt>AFM</tt> files<a id="id2907948"
- class="indexterm" name="id2907948"></a>. This version of
- <b>afm2tfm</b> can perform several useful tasks such as
- automatically creating appropriate virtual fonts (for
- mapping TeX font encodings to PostScript encodings) or
- changing the encoding of the PostScript font.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.pr.dvilaserhp"
- name="sec.pr.dvilaserhp"></a>DVILASER/HP</h3>
- </div>
- </div>
-
- <p>ArborText<a id="id2907992" class="indexterm"
- name="id2907992"></a>'s \dvilaserhp<a id="id2908001"
- class="indexterm" name="id2908001"></a> DVI driver
- translates TeX <tt>DVI</tt> files into a format that can
- be printed on HP LaserJet printers. These drivers are
- available for both MS-DOS and supported unix
- workstations. The following discussion is based on
- experiences with \dvilaserhp version 5.3.3, the MS-DOS
- implementation of ArborText's HP LaserJet driver.</p>
-
- <p>\dvilaserhp functions in the way you would expect,
- generating LaserJet printable documents from TeX
- <tt>DVI</tt> files. It also has many special features.
- Some of the more interesting features are summarized
- below. \dvilaserhp can print documents using <tt>PK</tt>
- files, HP LaserJet softfonts, and built-in fonts
- (including fonts from cartridges).</p>
-
- <p>ArborText supplies a complete set of Computer Modern
- fonts in <tt>PK</tt> format. Recent releases of
- \dvilaserhp can use the virtual fonts introduced in TeX
- version 3.0.</p>
-
- <p>ArborText's \dvilaserhp DVI driver provides the
- following features:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Selectable number of copies</p>
- </li>
-
- <li>
- <p>Optional reverse ordering of pages</p>
- </li>
-
- <li>
- <p>Selectable manual-feed</p>
- </li>
-
- <li>
- <p>Portrait or landscape orientation</p>
- </li>
-
- <li>
- <p>Selectable page size</p>
- </li>
-
- <li>
- <p>Ability to scale <tt>PK</tt> files to the
- requested size if an appropriate <tt>PK</tt> file
- is unavailable. This may result in poorer output
- quality due to distortion, but that's not
- \dvilaserhp's fault.<sup>[<a id="id2908153"
- name="id2908153"
- href="#ftn.id2908153">103</a>]</sup></p>
- </li>
-
- <li>
- <p>Page movement and reordering options (for
- printing multiple pages on a single sheet of paper,
- for example)</p>
- </li>
-
- <li>
- <p>Configurable font substitution</p>
- </li>
-
- <li>
- <p>Support for LaserJet &#8220;overlays.&#8221;
- \dvilaserhp recognizes \special commands for
- inserting raw HP LaserJet format documents and
- inserting HP LaserJet overlays<sup>[<a
- id="id2908216" name="id2908216"
- href="#ftn.id2908216">104</a>]</sup></p>
- </li>
-
- <li>
- <p>An interactive mode (useful for printing only
- selected pages from a document without re-running
- \dvilaserhp many times or when many options are
- going to be used)</p>
- </li>
-
- <li>
- <p>Selectable paper tray</p>
- </li>
- </ul>
- </div>
-
- <p>Many other utilities come with \dvilaserhp; they are
- summarized in Table&#160;<a
- href="ch08.html#tab.dvilaserhp.util"
- title="Table&#160;8.2.&#160;Other \protect\dvilaserhp Utilities">
- Table&#160;8.2</a>.<a id="id2908263" class="indexterm"
- name="id2908263"></a><a id="id2908269" class="indexterm"
- name="id2908269"></a><a id="id2908276" class="indexterm"
- name="id2908276"></a><a id="id2908283" class="indexterm"
- name="id2908283"></a> <a id="id2908292" class="indexterm"
- name="id2908292"></a><a id="id2908299" class="indexterm"
- name="id2908299"></a><a id="id2908306" class="indexterm"
- name="id2908306"></a><a id="id2908313" class="indexterm"
- name="id2908313"></a><a id="id2908320" class="indexterm"
- name="id2908320"></a> <a id="id2908328" class="indexterm"
- name="id2908328"></a><a id="id2908335" class="indexterm"
- name="id2908335"></a><a id="id2908342" class="indexterm"
- name="id2908342"></a>\index{VPtoVF}{\def\x{${}^1$}</p>
-
- <div class="table">
- <a id="tab.dvilaserhp.util"
- name="tab.dvilaserhp.util"></a>
-
- <p class="title"><b>Table&#160;8.2.&#160;Other
- \protect\dvilaserhp Utilities</b></p>
-
- <table summary="Other \protect\dvilaserhp Utilities"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Utility</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it aftovp</td>
-
- <td align="left">Converts <tt>VPL</tt> from
- <tt>AFM</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it gftopk\,\x</td>
-
- <td align="left">Converts <tt>GF</tt> files into
- <tt>PK</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it hpformat</td>
-
- <td align="left">A print formatter for ASCII
- files</td>
- </tr>
-
- <tr>
- <td align="left">\it packpxl</td>
-
- <td align="left">Creates packed (byte-aligned)
- <tt>PXL</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it painthp</td>
-
- <td align="left">Converts MacPaint files into HP
- LaserJet format</td>
- </tr>
-
- <tr>
- <td align="left">\it pcltopk\,\x</td>
-
- <td align="left">Converts HP LaserJet softfonts
- into <tt>PK</tt>/<tt>TFM</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it pktopx\,\x</td>
-
- <td align="left">Converts <tt>PK</tt> files into
- <tt>PXL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it pxtopk\,\x</td>
-
- <td align="left">Converts <tt>PXL</tt> files into
- <tt>PK</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it spr</td>
-
- <td align="left">A serial-line print spooler</td>
- </tr>
-
- <tr>
- <td align="left">\it tftovp</td>
-
- <td align="left">Converts <tt>VPL</tt> from
- <tt>TFM</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it unpkpxl</td>
-
- <td align="left">Creates standard, word-aligned
- <tt>PXL</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it vftovp\,\x</td>
-
- <td align="left">Converts <tt>VF</tt> files into
- <tt>VPL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it vptovf\,\,\x</td>
-
- <td align="left">Converts <tt>VPL</tt> files into
- <tt>VF</tt> files</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>ArborText recently released <b>DVILASER/HP3 drivers<a
- id="id2908752" class="indexterm"
- name="id2908752"></a></b> for the HP LaserJet III and IV
- printers. In addition to the features described above,
- <b>DVILASER/HP3</b> supports more complex documents,
- compressed font downloading, 600dpi and duplex printing,
- paper tray and output bin selection, and the ability to
- include TIFF images via a \special command.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.pr.dvilaserps"
- name="sec.pr.dvilaserps"></a>DVILASER/PS</h3>
- </div>
- </div>
-
- <p>ArborText<a id="id2908789" class="indexterm"
- name="id2908789"></a>'s \dvilaserps<a id="id2908797"
- class="indexterm" name="id2908797"></a> DVI driver
- translates TeX <tt>DVI</tt> files into PostScript. These
- drivers are available for both MS-DOS and supported unix
- workstations. The following discussion is based on
- experiences with \dvilaserps version 6.3.5, the MS-DOS
- implementation of ArborText's PostScript driver.</p>
-
- <p>PostScript DVI drivers are more flexible than many
- other DVI drivers because PostScript is a very powerful
- page description language. Some of \dvilaserps's more
- interesting features are summarized below. \dvilaserps
- can print documents using <tt>PK</tt> files, downloadable
- PostScript fonts, and built-in fonts. ArborText supplies
- <tt>TFM</tt> files for many built-in PostScript fonts.
- Recent releases of \dvilaserps can use the virtual fonts
- introduced in TeX version 3.0.</p>
-
- <p>ArborText's \dvilaserps DVI driver provides the
- following features:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Options for loading custom PostScript prologue
- code</p>
- </li>
-
- <li>
- <p>Ability to be used as a filter (sends PostScript
- code to standard output)</p>
- </li>
-
- <li>
- <p>Selectable number of copies</p>
- </li>
-
- <li>
- <p>Optional reverse ordering of pages</p>
- </li>
-
- <li>
- <p>Portrait or landscape orientation</p>
- </li>
-
- <li>
- <p>Selectable page size</p>
- </li>
-
- <li>
- <p>Ability to scale <tt>PK</tt> files to the
- requested size if an appropriate <tt>PK</tt> file
- is unavailable. This may result in poorer output
- quality due to distortion, but that's not
- \dvilaserps's fault.</p>
- </li>
-
- <li>
- <p>Page movement and reordering options (for
- printing multiple pages on a single sheet of paper,
- for example)</p>
- </li>
-
- <li>
- <p>Selectable paper tray</p>
- </li>
-
- <li>
- <p>Configurable font substitution</p>
- </li>
-
- <li>
- <p>Support for LaserJet &#8220;overlays&#8221;</p>
- </li>
-
- <li>
- <p>An interactive mode (useful for printing only
- selected pages from a document without re-running
- \dvilaserps many times or when many options are
- going to be used)</p>
- </li>
-
- <li>
- <p>Ability to download <tt>PK</tt> files
- permanently, speeding printing of future
- documents</p>
- </li>
-
- <li>
- <p>Document, page, or encapsulated PostScript
- document structuring options</p>
- </li>
-
- <li>
- <p>Optional clipping of characters that fall
- outside the normally printable page area</p>
- </li>
- </ul>
- </div>
-
- <p>Many other utilities come with \dvilaserps. They are
- summarized in<a id="id2909044" class="indexterm"
- name="id2909044"></a><a id="id2909051" class="indexterm"
- name="id2909051"></a><a id="id2909058" class="indexterm"
- name="id2909058"></a><a id="id2909065" class="indexterm"
- name="id2909065"></a> <a id="id2909073" class="indexterm"
- name="id2909073"></a><a id="id2909080" class="indexterm"
- name="id2909080"></a><a id="id2909087" class="indexterm"
- name="id2909087"></a><a id="id2909094" class="indexterm"
- name="id2909094"></a><a id="id2909102" class="indexterm"
- name="id2909102"></a> <a id="id2909110" class="indexterm"
- name="id2909110"></a><a id="id2909117" class="indexterm"
- name="id2909117"></a><a id="id2909124" class="indexterm"
- name="id2909124"></a><a id="id2909131" class="indexterm"
- name="id2909131"></a> <a id="id2909140" class="indexterm"
- name="id2909140"></a><a id="id2909147" class="indexterm"
- name="id2909147"></a> Table&#160;<a
- href="ch08.html#tab.dvilaserps.util"
- title="Table&#160;8.3.&#160;Other \protect\dvilaserps Utilities">
- Table&#160;8.3</a>.</p>
-
- <div class="table">
- <a id="tab.dvilaserps.util"
- name="tab.dvilaserps.util"></a>
-
- <p class="title"><b>Table&#160;8.3.&#160;Other
- \protect\dvilaserps Utilities</b></p>
-
- <table summary="Other \protect\dvilaserps Utilities"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Utility</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it afmtopl</td>
-
- <td align="left">Converts <tt>AFM</tt> files into
- unmapped <tt>PL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it afmtoplm</td>
-
- <td align="left">Converts <tt>AFM</tt> files into
- mapped <tt>PL</tt> files\y</td>
- </tr>
-
- <tr>
- <td align="left">\it aftovp</td>
-
- <td align="left">Converts <tt>VPL</tt> from
- <tt>AFM</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it gftopk\,\x</td>
-
- <td align="left">Converts <tt>GF</tt> files into
- <tt>PK</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it packpxl</td>
-
- <td align="left">Creates packed (byte-aligned)
- <tt>PXL</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it pktopx\,\x</td>
-
- <td align="left">Converts <tt>PK</tt> files into
- <tt>PXL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it pltotf\,\,\x</td>
-
- <td align="left">Converts <tt>PL</tt> files into
- <tt>TFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it psformat</td>
-
- <td align="left">A print formatter for ASCII
- files</td>
- </tr>
-
- <tr>
- <td align="left">\it pxtopk\,\x</td>
-
- <td align="left">Converts <tt>PXL</tt> files into
- <tt>PK</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it spr</td>
-
- <td align="left">A serial-line print spooler</td>
- </tr>
-
- <tr>
- <td align="left">\it tftopl\,\x</td>
-
- <td align="left">Converts <tt>TFM</tt> files into
- <tt>PL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it tftovp</td>
-
- <td align="left">Converts <tt>VPL</tt> from
- <tt>TFM</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it unpkpxl</td>
-
- <td align="left">Creates standard, word-aligned
- <tt>PXL</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it vftovp\,\x</td>
-
- <td align="left">Converts <tt>VF</tt> files into
- <tt>VPL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it vptovf\,\,\x</td>
-
- <td align="left">Converts <tt>VPL</tt> files into
- <tt>VF</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\multicolumn{2}{l}{ ${}^1$\vrule
- height11pt width0pt\tiny A standard, or otherwise
- freely available, utility.}</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>\dvilaserps recognizes \special commands for inserting
- raw PostScript files and commands, encapsulated
- PostScript files, and automatic page overlays (which can
- be selectively enabled and disabled). Other \special
- commands allow you to set most of the \dvilaserps
- command-line options directly in the document, rotate any
- TeX &#8220;box&#8221; to any angle, and print change
- bars. For LaTeX users, ArborText includes a plug-in
- replacement for LaTeX's picture environments that uses
- PostScript instead of special fonts to draw each
- figure.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2909658"
- name="id2909658"></a>PTI Laser/HP and PTI Jet</h3>
- </div>
- </div>
-
- <p><b>PTI Laser/HP</b><a id="id2909683" class="indexterm"
- name="id2909683"></a> and <b>PTI Jet</b><a id="id2909696"
- class="indexterm" name="id2909696"></a> are distributed
- together by Personal TeX, Inc.<a id="id2909706"
- class="indexterm" name="id2909706"></a> <b>PTI
- Laser/HP</b> is an HP LaserJet driver. <b>PTI Jet</b> is
- a DeskJet driver. The <b>PTI Jet</b> driver works with a
- standard DeskJet printer; no additional options or memory
- are required. The <b>PTI Laser/HP</b> driver is for HP
- LaserJet II and III series printers. A separate program,
- <b>PTI Laser/HP4</b>, is sold for LaserJet 4 series
- printers (to support 600dpi fonts, for example).</p>
-
- <p>The following features are available in these
- drivers:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Support for font substitution</p>
- </li>
-
- <li>
- <p>Support for built-in fonts</p>
- </li>
-
- <li>
- <p>Printing multiple copies of each page</p>
- </li>
-
- <li>
- <p>Setting page size</p>
- </li>
-
- <li>
- <p>Printing in landscape mode</p>
- </li>
-
- <li>
- <p>Selecting magnification</p>
- </li>
-
- <li>
- <p>Ability to print a range of pages (by physical
- sheet or TeX page number)</p>
- </li>
-
- <li>
- <p>Reversing order of pages</p>
- </li>
-
- <li>
- <p>Ability to move the page image left/right or
- up/down the page</p>
- </li>
-
- <li>
- <p>Support for 256 character fonts</p>
- </li>
- </ul>
- </div>
-
- <p><b>PTI Laser/HP</b> offers the following additional
- features, which are not supported by <b>PTI Jet</b>:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Ability to reserve printer font ID numbers</p>
- </li>
-
- <li>
- <p>A utility program, <b>sftopk</b>, for converting
- HP LaserJet softfonts into TeX <tt>PK</tt>
- fonts</p>
- </li>
-
- <li>
- <p>Support for directly including HP LaserJet
- printer commands via the \special mechanism in
- TeX</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2909924"
- name="id2909924"></a>PTI Laser/PS</h3>
- </div>
- </div>
-
- <p><b>PTI Laser/PS</b><a id="id2909938" class="indexterm"
- name="id2909938"></a> is Personal TeX's PostScript DVI
- driver. In addition to the DVI driver, the <b>PTI
- Laser/PS</b> package includes utilities for spooling
- output to a serially-connected printer and converting
- <tt>AFM</tt> files into <tt>TFM</tt> files.</p>
-
- <p>Some of <b>PTI Laser/PS</b>'s more interesting options
- are summarized below.</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Ability to select different printer
- resolutions</p>
- </li>
-
- <li>
- <p>Selectable number of copies</p>
- </li>
-
- <li>
- <p>Configurable font substitution</p>
- </li>
-
- <li>
- <p>Selectable page size</p>
- </li>
-
- <li>
- <p>An interactive mode for selecting options and
- reacting to errors (characters that fall off the
- page, missing fonts, etc.)</p>
- </li>
-
- <li>
- <p>Portrait or landscape orientation</p>
- </li>
-
- <li>
- <p>Selectable TeX magnification</p>
- </li>
-
- <li>
- <p>Option files for storing frequently used
- options.</p>
- </li>
-
- <li>
- <p>Selectable output filename</p>
- </li>
-
- <li>
- <p>Options to select individual pages or ranges of
- pages by TeX page number or physical sheet
- number</p>
- </li>
-
- <li>
- <p>Optional reverse ordering of pages</p>
- </li>
-
- <li>
- <p>Adjustable page offset (adjusts the position of
- the printed page on the physical page)</p>
- </li>
-
- <li>
- <p>Support for 256-character fonts</p>
- </li>
-
- <li>
- <p>Special support for the eccentricities of the
- Apple LaserWriter printer</p>
- </li>
- </ul>
- </div>
-
- <p><b>PTI Laser/PS</b> recognizes a \special command for
- inserting raw PostScript files into the printed document.
- The horizontal and vertical size of the inserted image
- can be changed.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2910137"
- name="id2910137"></a>dvipsone</h3>
- </div>
- </div>
-
- <p><b>dvipsone</b><a id="id2910149" class="indexterm"
- name="id2910149"></a> is a commercial PostScript driver
- for MS-DOS distributed by Y&amp;Y Inc.<a id="id2910159"
- class="indexterm" name="id2910159"></a> It produces
- PostScript output from a TeX <tt>DVI</tt> file.
- <b>dvipsone</b> is designed for a
- &#8220;bitmap-free&#8221; environment. This makes
- <b>dvipsone</b> almost unique among <tt>DVI</tt> drivers
- because it <span class="emphasis"><em>cannot</em></span>
- use standard <tt>PK</tt> fonts. To use <b>dvipsone</b>,
- you must have PostScript fonts for every font that you
- use (or the font must be built into the printer).<sup>[<a
- id="id2910231" name="id2910231"
- href="#ftn.id2910231">105</a>]</sup> Y&amp;Y sells a
- complete set of Computer Modern fonts in Adobe
- Type&#160;1 format.</p>
-
- <p><b>dvipsone</b> has a rich set of features:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Printing multiple <tt>DVI</tt> files with a
- single command</p>
- </li>
-
- <li>
- <p>Printing pages in reverse order</p>
- </li>
-
- <li>
- <p>Printing only odd or even pages</p>
- </li>
-
- <li>
- <p>Ability to force output to conform to EPS
- standards</p>
- </li>
-
- <li>
- <p>Assumption that all requested fonts are
- printer-resident</p>
- </li>
-
- <li>
- <p>Insertion of verbatim PostScript</p>
- </li>
-
- <li>
- <p>Printing a range of pages</p>
- </li>
-
- <li>
- <p>Resizing of the output</p>
- </li>
-
- <li>
- <p>Rotation of output by arbitrary angle</p>
- </li>
-
- <li>
- <p>Shifting output left/right or up/down</p>
- </li>
-
- <li>
- <p>Printing arbitrary number of copies</p>
- </li>
-
- <li>
- <p>Selection of paper type (letter, landscape,
- legal, etc.)</p>
- </li>
-
- <li>
- <p>Insertion of user-specified PostScript
- prologue</p>
- </li>
-
- <li>
- <p>Conservation of memory by downloading partial
- fonts</p>
- </li>
-
- <li>
- <p>Remapping of the font encoding on-the-fly</p>
- </li>
-
- <li>
- <p>Support for ten different styles of \special
- commands for including encapsulated PostScript
- images</p>
- </li>
- </ul>
- </div>
-
- <p>Perhaps the most interesting feature of the
- <b>dvipsone</b> driver is its ability to download partial
- PostScript fonts. Y&amp;Y claim that partial font
- downloading is a feature unique to <b>dvipsone</b>. A
- moderately complex TeX document may use twenty or more
- fonts and each font is typically between 20K and 30K.
- This means that the DVI driver downloads roughly 500K of
- font data for the document. In addition to requiring
- considerable printer memory, all that font data increases
- the amount of time that it takes to send your document to
- the printer. The partial font downloading feature of
- <b>dvipsone</b> means that only the characters that are
- actually used in your document are sent to the printer.
- The ability to download partial fonts can result in a
- substantially smaller PostScript file.</p>
-
- <p>Several other utilities are distributed with
- <b>dvipsone</b>. They are summarized in <a id="id2910495"
- class="indexterm" name="id2910495"></a><a id="id2910502"
- class="indexterm" name="id2910502"></a><a id="id2910510"
- class="indexterm" name="id2910510"></a><a id="id2910517"
- class="indexterm" name="id2910517"></a> <a id="id2910525"
- class="indexterm" name="id2910525"></a><a id="id2910532"
- class="indexterm" name="id2910532"></a><a id="id2910539"
- class="indexterm" name="id2910539"></a> Table&#160;<a
- href="ch08.html#tab.dvipsone.util"
- title="Table&#160;8.4.&#160;Other dvipsone Utilities">Table&#160;8.4</a>.</p>
-
- <div class="table">
- <a id="tab.dvipsone.util" name="tab.dvipsone.util"></a>
-
- <p class="title"><b>Table&#160;8.4.&#160;Other dvipsone
- Utilities</b></p>
-
- <table summary="Other dvipsone Utilities" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left"><span>\bf Utility</span></th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left"><tt>download</tt></td>
-
- <td align="left">Robust font-downloading program
- for PostScript fonts</td>
- </tr>
-
- <tr>
- <td align="left"><tt>afmtotfm</tt>\,\x</td>
-
- <td align="left">Converts <tt>AFM</tt> files into
- <tt>TFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left"><tt>tfmtoafm</tt></td>
-
- <td align="left">Converts <tt>TFM</tt> files into
- <tt>AFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left"><tt>pfatopfb</tt>\,\x</td>
-
- <td align="left">Convert <tt>PFA</tt> files into
- <tt>PFB</tt> files</td>
- </tr>
-
- <tr>
- <td align="left"><tt>pfbtopfa</tt>\,\x</td>
-
- <td align="left">Convert <tt>PFB</tt> files into
- <tt>PFA</tt> files</td>
- </tr>
-
- <tr>
- <td align="left"><tt>twoup</tt></td>
-
- <td align="left">Reorders pages in a PostScript
- file</td>
- </tr>
-
- <tr>
- <td align="left"><tt>pktops</tt></td>
-
- <td align="left">Provides access to <tt>PK</tt>
- fonts for <b>dvipsone</b></td>
- </tr>
- </tbody>
- </table>
- </div>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2905446" name="ftn.id2905446"
- href="#id2905446">99</a>]</sup> {For a complete, detailed
- description of the <tt>PK</tt> and <tt>GF</tt> formats,
- consult <span class="emphasis"><em>The GF to PK
- Processor</em></span>&#160;[<a
- href="bi01.html#mfware:gftopk">mfware:gftopk</a>].}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2905773" name="ftn.id2905773"
- href="#id2905773">100</a>]</sup> {A backslash is used
- here to escape the end of the first line. This is a
- standard way to continue a line in most unix shells.
- Naturally, you can simply enter it as one line in your
- editor, if you prefer.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2906483" name="ftn.id2906483"
- href="#id2906483">101</a>]</sup> {Because figures are
- frequently much larger than individual characters,
- MetaFont may have difficulty with large figures at very
- high resolutions.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2907302" name="ftn.id2907302"
- href="#id2907302">102</a>]</sup> {In alpha-testing at the
- time of this writing.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2908153" name="ftn.id2908153"
- href="#id2908153">103</a>]</sup> {The scaling uses the
- next larger-sized <tt>PK</tt> file, and ArborText claims
- that this results in good quality over a large range of
- point sizes without providing <tt>PK</tt> files for every
- exact size.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2908216" name="ftn.id2908216"
- href="#id2908216">104</a>]</sup> {Consult your HP
- LaserJet reference manual for more information about
- overlays.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2910231" name="ftn.id2910231"
- href="#id2910231">105</a>]</sup> {The <b>dvipsone</b>
- distribution includes a utility which can convert
- <tt>PK</tt> fonts into bitmapped PostScript fonts. This
- program translates a <tt>PK</tt> file into an Adobe
- Type&#160;3 font. Once in Type&#160;3 format,
- <b>dvipsone</b> can use the font. Using Type&#160;3 fonts
- created in this way adds resolution-dependence to your
- PostScript file.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;7.&#160;International Considerations"
- href="ch07.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;9.&#160;Previewing"
- href="ch09.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;7.&#160;International
- Considerations&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;9.&#160;Previewing</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch09.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch09.html
deleted file mode 100644
index 641c668e9dc..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch09.html
+++ /dev/null
@@ -1,1550 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;9.&#160;Previewing</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="ch08.html"
- title="Chapter&#160;8.&#160;Printing" />
- <link rel="next" href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;8.&#160;Printing"
- href="ch08.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;10.&#160;Online Documentation"
- href="ch10.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.preview"
- name="chap.preview"></a>Chapter&#160;9.&#160;Previewing</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p><a id="id2902540" class="indexterm"
- name="id2902540"></a><a id="id2902547" class="indexterm"
- name="id2902547"></a>Because TeX is not interactive, most TeX
- documents are developed iteratively. After adding a
- significant amount of text or changing the format of a
- document, you'll want to see what the document looks like.
- Then you can add more text or try different formats. Then,
- it's helpful to see it again $&#8230;$</p>
-
- <p>You could print the document, but that's wasteful and slow
- (not to mention environmentally unfriendly). This is where
- screen previewers enter the picture. They allow you to look
- at your document on a video display.</p>
-
- <p>Accurate previewing is more difficult than printing your
- document for several reasons. Screen displays are much more
- diverse than printers (previewing on a PC is very different
- from previewing on a workstation running X11 even though
- printing to a LaserJet printer is essentially the same from
- both places). Also, it's very difficult to preview documents
- that use printer-specific features. For example, if you use a
- PostScript figure in your document, it will be very easy to
- print on a PostScript printer, but on most platforms it is
- much more difficult to preview that document on the screen
- (two exceptions are the Amiga and NeXT which have integrated
- support for displaying PostScript images).</p>
-
- <p>In the following sections I'll explore options for
- previewing on several platforms. The X Window System is
- usually associated with unix workstations, but several PC
- implementations (running under both MS-DOS and OS/2) are now
- available. The X11 previewers described here may be available
- for those systems, but I haven't seen them.
- <b>Ghostscript</b> is another previewing option that is
- available on several platforms so it is described in its own
- section.</p>
-
- <p>Table&#160;<a href="ch09.html#tab.previewers"
- title="Table&#160;9.1.&#160;Common Previewers">Table&#160;9.1</a>
- summarizes the previewers described here.</p>
-
- <div class="table">
- <a id="tab.previewers" name="tab.previewers"></a>
-
- <p class="title"><b>Table&#160;9.1.&#160;Common
- Previewers</b></p>
-
- <table summary="Common Previewers" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="center" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Previewer</th>
-
- <th align="left">\bf Supplier</th>
-
- <th align="center">\bf OS</th>
-
- <th align="left">\bf Comments</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\program{xdvi}</td>
-
- <td align="left">Free (xdvi)</td>
-
- <td align="center">Unix/DesqView</td>
-
- <td align="left">X11</td>
- </tr>
-
- <tr>
- <td align="left"><b>\XTeX</b></td>
-
- <td align="left">Free (\XTeX)</td>
-
- <td align="center">Unix</td>
-
- <td align="left">X11</td>
- </tr>
-
- <tr>
- <td align="left"><b>Ghostscript</b></td>
-
- <td align="left">Free (gs)</td>
-
- <td align="center">most</td>
-
- <td align="left">PostScript</td>
- </tr>
-
- <tr>
- <td align="left"><b>Ghostview</b></td>
-
- <td align="left">Free (Ghostview)</td>
-
- <td align="center">Unix, Windows</td>
-
- <td align="left">PostScript</td>
- </tr>
-
- <tr>
- <td align="left"><b>dviscr</b></td>
-
- <td align="left">Free (emTeX)</td>
-
- <td align="center">MS-DOS, OS/2</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvipm</b></td>
-
- <td align="left">Free (emTeX)</td>
-
- <td align="center">OS/2</td>
-
- <td align="left">Presentation Manager</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvivga</b></td>
-
- <td align="left">Free (dvivga)</td>
-
- <td align="center">MS-DOS</td>
-
- <td align="left">EGA/VGA</td>
- </tr>
-
- <tr>
- <td align="left"><b>TeX Preview</b></td>
-
- <td align="left">ArborText</td>
-
- <td align="center">MS-DOS, Unix</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvideo</b></td>
-
- <td align="left">Kinch Software</td>
-
- <td align="center">MS-DOS</td>
-
- <td align="left">EGA</td>
- </tr>
-
- <tr>
- <td align="left"><b>PTI View</b></td>
-
- <td align="left">Personal TeX</td>
-
- <td align="center">MS-DOS</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvimswin</b></td>
-
- <td align="left">Free (dvimswin)</td>
-
- <td align="center">MS-DOS</td>
-
- <td align="left">Windows</td>
- </tr>
-
- <tr>
- <td align="left"><b>dviwin</b></td>
-
- <td align="left">Free (dviwin)</td>
-
- <td align="center">MS-DOS</td>
-
- <td align="left">Windows</td>
- </tr>
-
- <tr>
- <td align="left"><b>wdviwin</b></td>
-
- <td align="left">Kinch Software</td>
-
- <td align="center">MS-DOS</td>
-
- <td align="left">Windows</td>
- </tr>
-
- <tr>
- <td align="left"><b>DVIWindo</b></td>
-
- <td align="left">Y&amp;Y</td>
-
- <td align="center">MS-DOS</td>
-
- <td align="left">Windows</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvi2tty</b></td>
-
- <td align="left">Free (dvi2tty)</td>
-
- <td align="center">Most</td>
-
- <td align="left">ASCII</td>
- </tr>
-
- <tr>
- <td align="left"><b>dvigt/dvitovdu</b></td>
-
- <td align="left">Free</td>
-
- <td align="center">Most</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left"><b>crudetype</b></td>
-
- <td align="left">Free</td>
-
- <td align="center">VMS</td>
-
- <td align="left">ASCII</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.ghostscript"
- name="sec.ghostscript"></a>Previewing Under X11</h2>
- </div>
- </div>
-
- <p><a id="id2911438" class="indexterm"
- name="id2911438"></a><a id="id2911448" class="indexterm"
- name="id2911448"></a>The three most common X11 previewers
- are <b>xdvi</b>, \XTeX, and <b>Ghostview</b> (really a
- PostScript previewer). <b>Ghostview</b> runs on top of
- <b>Ghostscript</b> and is described in the &#8220;<a
- href="ch09.html#sec.ghostscript"
- title="Previewing Under X11">the section called
- &#8220;Previewing Under X11&#8221;</a>&#8221; section of
- this chapter.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2911502"
- name="id2911502"></a>Previewing with xdvi</h3>
- </div>
- </div>
-
- <p>You can retrieve <b>xdvi</b><a id="id2911516"
- class="indexterm" name="id2911516"></a> from the CTAN
- archives in the directory <tt>dviware/xdvi</tt>.</p>
-
- <p>Figure&#160;<a href="ch09.html#fig.xdvi"
- title="Figure&#160;9.1.&#160;How Previewing with xdvi Works">
- Figure&#160;9.1</a> shows the preview process under xdvi.
- <b>xdvi</b> reads the <tt>DVI</tt> file and loads the
- <tt>PK</tt> files<a id="id2911583" class="indexterm"
- name="id2911583"></a> for any fonts that are required. If
- xdvi cannot find a requested font, it will run
- \MakeTeXPK<a id="id2911608" class="indexterm"
- name="id2911608"></a> to create the font. \MakeTeXPK is a
- shell script (or a batch file called <tt>maketexp</tt><a
- id="id2911623" class="indexterm" name="id2911623"></a>
- under MS-DOS) that tries to use MetaFont or
- <b>ps2pk</b><a id="id2911637" class="indexterm"
- name="id2911637"></a> to build the font.</p>
-
- <div class="figure">
- <a id="fig.xdvi" name="fig.xdvi"></a>
-
- <p class="title"><b>Figure&#160;9.1.&#160;How
- Previewing with xdvi Works</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>After forming each page, xdvi passes it off to the X11
- Window Manager to be displayed. Previewing under xdvi is
- shown in Figure&#160;<a href="ch09.html#fig.preview.xdvi"
- title="Figure&#160;9.2.&#160;Previewing with xdvi">Figure&#160;9.2</a>.</p>
-
- <div class="figure">
- <a id="fig.preview.xdvi" name="fig.preview.xdvi"></a>
-
- <p class="title"><b>Figure&#160;9.2.&#160;Previewing
- with xdvi</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>Screen resolution is typically much lower than printer
- resolution. Because xdvi uses the <tt>PK</tt> files at
- printer resolution, it must scale them before using them
- for display purposes. The scaling process allows xdvi to
- use <span
- class="emphasis"><em>anti-aliasing</em></span><a
- id="id2911760" class="indexterm" name="id2911760"></a> to
- improve image quality on color displays. Anti-aliasing is
- a technique used to improve the appearance of scaled
- images by using colored pixels around the edges of the
- image to provide the illusion of partial pixels. This can
- dramatically improve the readability of the displayed
- text. If the \ps font files are available, xdvi can
- display documents that use \ps fonts; otherwise, it
- performs font substitution.</p>
-
- <p>A recent addition to xdvi is the ability to preview
- documents that include PostScript figures. The figures
- are rendered behind the scenes by <b>Ghostscript</b> and
- displayed by xdvi. In my opinion, this addition really
- makes xdvi one of the finest X11 previewers available. It
- is fast, uses printer fonts, has anti-aliasing for superb
- readability on color displays, and can include PostScript
- figures.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2911812"
- name="id2911812"></a>Previewing with \xtex</h3>
- </div>
- </div>
-
- <p>The \xtex previewer<a id="id2911822" class="indexterm"
- name="id2911822"></a><a id="id2911832" class="indexterm"
- name="id2911832"></a> is very similar to xdvi. The
- primary difference is that \xtex uses X11 fonts for
- display. This means that \xtex must build fonts at the
- appropriate resolution. After the fonts have been built,
- \xtex is typically a very fast previewer.</p>
-
- <p>You can retrieve \xtex from the CTAN archives in the
- directory <tt>dviware/xtex</tt>.</p>
-
- <div class="figure">
- <a id="fig.xtex" name="fig.xtex"></a>
-
- <p class="title"><b>Figure&#160;9.3.&#160;How
- Previewing with xtex Works</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>Figure&#160;<a href="ch09.html#fig.xtex"
- title="Figure&#160;9.3.&#160;How Previewing with xtex Works">
- Figure&#160;9.3</a> shows the preview process under
- \xtex. Like xdvi, \xtex uses the \MakeTeXPK program to
- build <tt>PK</tt> files for fonts that are unavailable.
- Additionally, \xtex uses the \TeXtoXfont shell script, or
- batch file, to convert <tt>PK</tt> fonts into X11 display
- fonts.</p>
-
- <p>The \xtex previewer relies on the X11 Window Manager
- to build the display. However, if \ps figures are present
- in your document, \xtex will attempt to display them.
- When \xtex is built, you can specify that \ghostscript or
- another \ps interpreter be used to handle \ps
- figures.</p>
-
- <p>An example of \xtex's display is shown in
- Figure&#160;<a href="ch09.html#fig.preview.xtex"
- title="Figure&#160;9.4.&#160;Previewing with xtex">Figure&#160;9.4</a>.</p>
-
- <div class="figure">
- <a id="fig.preview.xtex" name="fig.preview.xtex"></a>
-
- <p class="title"><b>Figure&#160;9.4.&#160;Previewing
- with xtex</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2912002"
- name="id2912002"></a>Previewing with Ghostscript</h2>
- </div>
- </div>
-
- <p>Previewing with <b>Ghostscript</b> <a id="id2912018"
- class="indexterm" name="id2912018"></a><a id="id2912028"
- class="indexterm" name="id2912028"></a> is quite different
- from previewing with xdvi and \xtex. Most previewers
- process the <tt>DVI</tt> file to build the display.
- \ghostscript is a general-purpose program for displaying
- \ps files. Under X11, an additional program called
- \ghostview provides more sophisticated control of
- previewing.</p>
-
- <p><b>Ghostscript</b> and <b>Ghostview</b><a id="id2912074"
- class="indexterm" name="id2912074"></a> are products of the
- Free Software Foundation (FSF)<a id="id2912083"
- class="indexterm" name="id2912083"></a>. You can retrieve
- them from the GNU archives on <tt>prep.ai.mit.edu</tt> in
- the directory <tt>/pub/gnu</tt> or from any mirror of those
- archives.</p>
-
- <p><b>Ghostscript</b> reads and interprets the \ps file
- created by a program such as \dvips. It provides its own
- means of handling font substitution if the appropriate
- fonts are unavailable. Because \dvips converts the TeX
- <tt>DVI</tt> file into \ps, \ghostscript can display all of
- the elements of the document including \ps figures and
- other PostScript printer-specific commands.</p>
-
- <p>An example of <b>Ghostview</b>'s display is shown in
- Figure&#160;<a href="ch09.html#fig.preview.ghostview"
- title="Figure&#160;9.5.&#160;Previewing with Ghostview">Figure&#160;9.5</a>.</p>
-
- <div class="figure">
- <a id="fig.preview.ghostview"
- name="fig.preview.ghostview"></a>
-
- <p class="title"><b>Figure&#160;9.5.&#160;Previewing with
- Ghostview</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2912205"
- name="id2912205"></a>Previewing with emTeX</h2>
- </div>
- </div>
-
- <p>Figure&#160;<a href="ch08.html#fig.emdvi"
- title="Figure&#160;8.3.&#160;Previewing and printing with emTeX">
- Figure&#160;8.3</a> in Chapter&#160;<a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a>,
- <span class="emphasis"><em><a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a></em></span>,
- shows the relationship between the various components
- involved when processing a <tt>DVI</tt> file with emTeX<a
- id="id2912253" class="indexterm" name="id2912253"></a><a
- id="id2912265" class="indexterm" name="id2912265"></a>.
- Previewing and printing are very similar operations with
- emTeX. To preview, you use the <b>dviscr</b><a
- id="id2912285" class="indexterm" name="id2912285"></a>
- driver, and the result is displayed on the screen. To
- print, use one of the other DVI drivers, and the result is
- a file that can be sent directly to your printer.
- Chapter&#160;<a href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">Chapter&#160;13</a>,
- <span class="emphasis"><em><a href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">Chapter&#160;13</a></em></span>,
- discusses emTeX in more detail.</p>
-
- <p><b>dvidrv</b> runs the appropriate DVI driver:
- <b>dviscr</b> for previewing, <b>dvihplj</b><a
- id="id2912340" class="indexterm" name="id2912340"></a> for
- printing to an HP LaserJet printer, or <b>dvidot</b><a
- id="id2912355" class="indexterm" name="id2912355"></a> for
- printing to other dot matrix printers.</p>
-
- <p>The DVI driver reads the <tt>DVI</tt> file and loads
- fonts from <tt>PK</tt> files<a id="id2912388"
- class="indexterm" name="id2912388"></a> or <tt>FLI</tt>
- font libraries<a id="id2912417" class="indexterm"
- name="id2912417"></a>. If your document uses graphics, they
- are loaded from <tt>PCX</tt><a id="id2912445"
- class="indexterm" name="id2912445"></a> or <tt>MSP</tt>
- files<a id="id2912463" class="indexterm"
- name="id2912463"></a>.</p>
-
- <p>If your document uses a font that is not available, the
- DVI driver writes the commands necessary to build the font
- to the <tt>MFJ</tt> file<a id="id2912487" class="indexterm"
- name="id2912487"></a>.<sup>[<a id="id2912496"
- name="id2912496" href="#ftn.id2912496">106</a>]</sup>
- Before performing font substitution, the driver will ask if
- you wish to build the missing fonts. If you elect to build
- them, the DVI driver stops and returns control to the
- <b>dvidrv</b><a id="id2912513" class="indexterm"
- name="id2912513"></a> program.</p>
-
- <p><b>dvidrv</b> notices that the DVI driver stopped
- because of missing fonts and runs <b>MFjob<a id="id2912538"
- class="indexterm" name="id2912538"></a></b> to build them.
- After building the fonts, the previewer is run again to
- display the document.</p>
-
- <p>The <b>dvidrv</b> program is quite simple. With some
- care, it can be replaced by a batch file that does more
- work.<sup>[<a id="id2912560" name="id2912560"
- href="#ftn.id2912560">107</a>]</sup> For example, I have
- replaced <b>dvidrv</b> with a <b>4DOS<a id="id2912587"
- class="indexterm" name="id2912587"></a></b> batch file
- called <b>dvidxx</b> that can automatically build \ps fonts
- by calling <b>ps2pk</b> in addition to building MetaFont
- fonts with <b>MFjob</b>. The <b>dvidxx</b> batch file is
- printed in Example&#160;<a href="apd.html#ex.dvidxx"
- title="Example&#160;D.3.&#160;dvidxx.btm">Example&#160;D.3</a>
- in Appendix&#160;<a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a>,
- <span class="emphasis"><em><a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a></em></span>.</p>
-
- <p>A full-screen preview with <b>dviscr</b> is shown in
- Figure&#160;<a href="ch09.html#fig.preview.dviscr"
- title="Figure&#160;9.6.&#160;Previewing with emTeX's dviscr">
- Figure&#160;9.6</a>.</p>
-
- <div class="figure">
- <a id="fig.preview.dviscr" name="fig.preview.dviscr"></a>
-
- <p class="title"><b>Figure&#160;9.6.&#160;Previewing with
- emTeX's dviscr</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>Under OS/2, the <b>dvipm</b><a id="id2912715"
- class="indexterm" name="id2912715"></a> previewer offers
- more power. A sample <b>dvipm</b> display is shown in
- Figure&#160;<a href="ch09.html#fig.preview.dvipm"
- title="Figure&#160;9.7.&#160;Previewing with emTeX's dvipm">
- Figure&#160;9.7</a> later in this chapter.</p>
-
- <div class="figure">
- <a id="fig.preview.dvipm" name="fig.preview.dvipm"></a>
-
- <p class="title"><b>Figure&#160;9.7.&#160;Previewing with
- emTeX's dvipm</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>The <b>dviscr</b> and <b>dvipm</b> previewers use <span
- class="emphasis"><em>anti-aliasing<a id="id2912793"
- class="indexterm" name="id2912793"></a></em></span> to
- obtain better image quality on a color display. However,
- this translates into a poorer quality image when captured
- for display in a black-and-white book.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2912806"
- name="id2912806"></a>Previewing with dvivga</h2>
- </div>
- </div>
-
- <p><b>dvivga</b><a id="id2912819" class="indexterm"
- name="id2912819"></a><a id="id2912827" class="indexterm"
- name="id2912827"></a> is an MS-DOS previewer for EGA and
- VGA displays. You can retrieve <b>dvivga</b> (and a
- complete set of the Computer Modern fonts in <tt>PK</tt>
- format) from the CTAN archives in the directory
- <tt>dviware/dvivga</tt>. <b>dvivga</b> requires <tt>PK</tt>
- fonts at screen-resolutions (around 100dpi); that is why a
- special set of fonts is provided. If you are using a
- dot-matrix printer with a similar resolution, the special
- fonts may already be installed on your system.</p>
-
- <p><b>dvivga</b> does not support any \special commands for
- including pictures or figures, but it does support
- configurable font-substitution for fonts that are
- unavailable.</p>
-
- <p>Figure&#160;<a href="ch09.html#fig.dvivga.vga"
- title="Figure&#160;9.8.&#160;Previewing with dvivga">Figure&#160;9.8</a>
- shows a preview of the sample document from Chapter&#160;<a
- href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>.
- This image is from a VGA display.</p>
-
- <div class="figure">
- <a id="fig.dvivga.vga" name="fig.dvivga.vga"></a>
-
- <p class="title"><b>Figure&#160;9.8.&#160;Previewing with
- dvivga</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.arb.preview" name="sec.arb.preview"></a>TeX
- Preview</h2>
- </div>
- </div>
-
- <p><b>TeX Preview</b>\index{TeX Preview previewing@TeX
- Preview previewing}<a id="id2912979" class="indexterm"
- name="id2912979"></a> is the ArborText<a id="id2912993"
- class="indexterm" name="id2912993"></a> <tt>DVI</tt>
- previewer for MS-DOS. A similar previewer is available for
- unix workstations running the X Window System (versions for
- Motif and Open Look environments are also available). The
- following discussion is based on experiences with <b>TeX
- Preview</b> version 6.1.2, the MS-DOS implementation of
- ArborText's TeX previewer.</p>
-
- <p><b>TeX Preview</b> supports a wide range of graphics
- adapters, including EGA, VGA, and Hercules adapters as well
- as the Olivetti Monochrome Graphics adapter, the Tecmar
- Graphics Master, the Genius VHR Full Page Display Monitor,
- the ETAP Neftis Monitor, the Toshiba 3100, and the AT&amp;T
- PC6300 display.</p>
-
- <p>Figure&#160;<a href="ch09.html#fig.tpre.vga"
- title="Figure&#160;9.9.&#160;Previewing with ArborText's Previewer">
- Figure&#160;9.9</a> shows a preview of the sample document
- from Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.
- This image is from a VGA display. Three additional features
- of the driver, not exercised in this example, are the
- ability to scale fonts to any size, display rulers and
- bitmapped graphics, and a &#8220;two-up&#8221; mode for
- viewing two pages at a time.</p>
-
- <div class="figure">
- <a id="fig.tpre.vga" name="fig.tpre.vga"></a>
-
- <p class="title"><b>Figure&#160;9.9.&#160;Previewing with
- ArborText's Previewer</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>When <b>TeX Preview</b> is displaying a <tt>DVI</tt>
- file, you can move around the page and between pages; you
- can change the magnification, search for text in the
- <tt>DVI</tt> file, show the attributes of the character
- under the cursor (font, dimensions, magnification, etc.),
- and switch to another file. A configuration file allows you
- to specify a wide range of options to control how <b>TeX
- Preview</b> appears when it starts up.</p>
-
- <p>ArborText supplies a full set of Computer Modern Roman
- <tt>PK</tt> files at screen resolutions as well as a
- complete set of Times Roman and Helvetica fonts at screen
- resolutions. The additional PostScript fonts are derived
- from official Adobe sources and allow you to preview
- documents that will be printed on PostScript printers
- (provided that they use only Times, Helvetica, and Computer
- Modern fonts). They are designed specifically to work with
- <tt>TFM</tt> files provided with <b>DVILASER/PS</b>,
- ArborText's PostScript DVI driver.</p>
-
- <p>If you want to use additional fonts, for example the
- \AmS-fonts or Computer Modern fonts at unusual sizes, you
- may wish to generate <tt>PK</tt> files at the appropriate
- resolutions. <b>TeX Preview</b> will perform font
- substitution for missing fonts (you can control what
- substitutions are made) and can use the <tt>DVI</tt> driver
- metric information, so generating additional fonts is not
- necessary.</p>
-
- <p><b>TeX Preview</b> understands the virtual font
- mechanisms introduced in TeX version 3.0. Several
- additional utilities provided with <b>TeX Preview</b> allow
- you to construct virtual fonts. These utilities are
- summarized in Table&#160;<a href="ch09.html#tab.tpre.utils"
- title="Table&#160;9.2.&#160;TeX Preview Utilities">Table&#160;9.2</a><a
- id="id2913251" class="indexterm" name="id2913251"></a><a
- id="id2913268" class="indexterm" name="id2913268"></a><a
- id="id2913275" class="indexterm" name="id2913275"></a> <a
- id="id2913283" class="indexterm" name="id2913283"></a><a
- id="id2913290" class="indexterm" name="id2913290"></a><a
- id="id2913297" class="indexterm" name="id2913297"></a><a
- id="id2913304" class="indexterm" name="id2913304"></a><a
- id="id2913311" class="indexterm" name="id2913311"></a> <a
- id="id2913320" class="indexterm" name="id2913320"></a>.</p>
-
- <div class="table">
- <a id="tab.tpre.utils" name="tab.tpre.utils"></a>
-
- <p class="title"><b>Table&#160;9.2.&#160;TeX Preview
- Utilities</b></p>
-
- <table summary="TeX Preview Utilities" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Utility</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it aftovp</td>
-
- <td align="left">Converts <tt>VPL</tt> from
- <tt>AFM</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it gftopk\,\x</td>
-
- <td align="left">Converts <tt>GF</tt> files into
- <tt>PK</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it packpxl</td>
-
- <td align="left">Creates packed (byte-aligned)
- <tt>PXL</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it pktopx\,\x</td>
-
- <td align="left">Converts <tt>PK</tt> files into
- <tt>PXL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it pxtopk\,\x</td>
-
- <td align="left">Converts <tt>PXL</tt> files into
- <tt>PK</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it tftovp</td>
-
- <td align="left">Converts <tt>VPL</tt> from
- <tt>TFM</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it unpkpxl</td>
-
- <td align="left">Creates standard, word-aligned
- <tt>PXL</tt> file</td>
- </tr>
-
- <tr>
- <td align="left">\it vftovp\,\x</td>
-
- <td align="left">Converts <tt>VF</tt> files into
- <tt>VPL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it vptovf\,\x</td>
-
- <td align="left">Converts <tt>VPL</tt> files into
- <tt>VF</tt> files</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>ArborText's <b>TeX Preview</b> program recognizes
- \special commands for drawing change bars and for rotating
- <span class="emphasis"><em>any</em></span> TeX
- &#8220;box&#8221; through a multiple of 90 degrees. These
- are the same \special commands recognized by other
- ArborText DVI drivers.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2913678"
- name="id2913678"></a>dvideo</h2>
- </div>
- </div>
-
- <p>The MS-DOS based EGA previewer <b>dvideo</b><a
- id="id2913692" class="indexterm" name="id2913692"></a><a
- id="id2913700" class="indexterm" name="id2913700"></a> is
- distributed as part of the TurboTeX<a id="id2913713"
- class="indexterm" name="id2913713"></a> distribution by the
- Kinch Computer Company<a id="id2913726" class="indexterm"
- name="id2913726"></a>. TurboTeX is described more
- completely in the section called &#8220;<a
- href="ch14.html#sec.com.turbo"
- title="µTeX by ArborText">the section called &#8220;µTeX by
- ArborText&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a>,
- <span class="emphasis"><em><a href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a></em></span>.
- TurboTeX also includes a Microsoft Windows previewer.</p>
-
- <p>Figure&#160;<a href="ch09.html#fig.ttexd.ega"
- title="Figure&#160;9.10.&#160;Previewing with TurboTeX dvideo (using limited selection of fonts)">
- Figure&#160;9.10</a> shows a <b>dvideo</b> preview of the
- sample document from Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>.</p>
-
- <div class="figure">
- <a id="fig.ttexd.ega" name="fig.ttexd.ega"></a>
-
- <p class="title"><b>Figure&#160;9.10.&#160;Previewing
- with TurboTeX dvideo (using limited selection of
- fonts)</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>The preview displayed here uses the default set of fonts
- distributed with TurboTeX. This does not include several of
- the large sizes used by this example. In practice, you will
- have to purchase or build many fonts before you can use
- TurboTeX.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2913841"
- name="id2913841"></a>PTI View</h2>
- </div>
- </div>
-
- <p><b>PTI View</b><a id="id2913854" class="indexterm"
- name="id2913854"></a> <a id="id2913866" class="indexterm"
- name="id2913866"></a> is the MS-DOS previewer that comes
- with PCTeX, distributed by Personal TeX, Inc.<a
- id="id2913876" class="indexterm" name="id2913876"></a>
- PCTeX is described in the section called &#8220;<a
- href="ch14.html#sec.pctex" title="PCTeX">the section called
- &#8220;PCTeX&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a>,
- <span class="emphasis"><em><a href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a></em></span>.</p>
-
- <p>Figure&#160;<a href="ch09.html#fig.ptipreview"
- title="Figure&#160;9.11.&#160;Previewing with Personal TeX's Previewer">
- Figure&#160;9.11</a> shows a <b>PTI View</b> preview of the
- sample document from Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>.</p>
-
- <div class="figure">
- <a id="fig.ptipreview" name="fig.ptipreview"></a>
-
- <p class="title"><b>Figure&#160;9.11.&#160;Previewing
- with Personal TeX's Previewer</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p><b>PTI View</b> is distributed with a complete set of
- the Computer Modern fonts in <tt>PK</tt> format (<b>PTI
- View</b> can use the same <tt>PK</tt> fonts as your
- printer, regardless of the printer's resolution). It can
- display the preview in many video modes, including several
- high-resolution super VGA modes.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2914028"
- name="id2914028"></a>Previewing Under Windows</h2>
- </div>
- </div>
-
- <p>Most MS-DOS previewers are inappropriate for previewing
- in Windows<a id="id2914039" class="indexterm"
- name="id2914039"></a><a id="id2914049" class="indexterm"
- name="id2914049"></a> because they assume that they can
- control the entire display. Recently, several commercial
- and free previewers for Windows have become available. They
- are described in this section.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2914065"
- name="id2914065"></a>dvimswin</h3>
- </div>
- </div>
-
- <p>The <b>dvimswin</b><a id="id2914079" class="indexterm"
- name="id2914079"></a><a id="id2914089" class="indexterm"
- name="id2914089"></a> previewer is a Windows version of
- <b>dvivga</b>. It uses the same screen-resolution fonts
- for displaying your <tt>DVI</tt> file and offers
- font-substitution for missing fonts.</p>
-
- <p>You can retrieve <b>dvimswin</b> from the CTAN
- archives in the directory <tt>dviware/dvimswin</tt>. The
- <b>dvimswin</b> previewer is shown in Figure&#160;<a
- href="ch09.html#fig.preview.dvimswin"
- title="Figure&#160;9.12.&#160;Previewing with dvimswin">Figure&#160;9.12</a>.</p>
-
- <div class="figure">
- <a id="fig.preview.dvimswin"
- name="fig.preview.dvimswin"></a>
-
- <p class="title"><b>Figure&#160;9.12.&#160;Previewing
- with dvimswin</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2914192"
- name="id2914192"></a>dviwin</h3>
- </div>
- </div>
-
- <p>The <b>dviwin</b><a id="id2914207" class="indexterm"
- name="id2914207"></a><a id="id2914214" class="indexterm"
- name="id2914214"></a> previewer is another free Microsoft
- Windows previewer. <b>dviwin</b> can use either screen or
- printer resolution fonts to display your <tt>DVI</tt>
- file. You can retrieve <b>dviwin</b> from the CTAN
- archives in the directory <tt>dviware/dviwin</tt>.</p>
-
- <p>What makes <b>dviwin</b> unique is its support for
- \special commands. <b>dviwin</b> understands \special
- commands for including pictures and figures, as well as
- the emTeX and <tt>tpic</tt> drawing primitives.</p>
-
- <p><b>dviwin</b> has built-in support for <tt>PCX</tt><a
- id="id2914309" class="indexterm" name="id2914309"></a>,
- <tt>BMP</tt><a id="id2914326" class="indexterm"
- name="id2914326"></a>, and <tt>MSP</tt><a id="id2914348"
- class="indexterm" name="id2914348"></a> graphic formats.
- Additionally, it can use any graphics filter installed in
- your Windows environment. Many commercial programs
- include additional filters to handle the images that they
- construct. <b>dviwin</b> also supports emTeX font
- libraries<a id="id2914367" class="indexterm"
- name="id2914367"></a> and customizable automatic font
- generation. By using <b>dviwin</b>, you can print your
- <tt>DVI</tt> files on any Microsoft Windows-supported
- printer. The <b>dviwin</b> previewer is shown in
- Figure&#160;<a href="ch09.html#fig.preview.dviwin"
- title="Figure&#160;9.13.&#160;Previewing with dviwin">Figure&#160;9.13</a>.</p>
-
- <div class="figure">
- <a id="fig.preview.dviwin"
- name="fig.preview.dviwin"></a>
-
- <p class="title"><b>Figure&#160;9.13.&#160;Previewing
- with dviwin</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>The <b>dviwin</b> distribution includes two additional
- utilities: <b>clipmeta</b><a id="id2914464"
- class="indexterm" name="id2914464"></a> for creating
- <tt>MSP</tt> graphic files from any image captured in the
- Windows clipboard, and <b>wbr</b>,<a id="id2914491"
- class="indexterm" name="id2914491"></a> a text-file
- browser.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2914502"
- name="id2914502"></a>wdviwin</h3>
- </div>
- </div>
-
- <p>As mentioned above, the TurboTeX<a id="id2914510"
- class="indexterm" name="id2914510"></a> package includes
- a Windows DVI driver, <b>wdviwin</b><a id="id2914528"
- class="indexterm" name="id2914528"></a><a id="id2914536"
- class="indexterm" name="id2914536"></a>, distributed by
- the Kinch Computer Company<a id="id2914548"
- class="indexterm" name="id2914548"></a>. Sample output
- from this previewer is shown in Figure&#160;<a
- href="ch09.html#fig.preview.wttpreview"
- title="Figure&#160;9.14.&#160;Previewing with TurboTeX's wdviwin">
- Figure&#160;9.14</a>. This sample shows the status
- window, the preview window, and a few of the available
- tools.</p>
-
- <div class="figure">
- <a id="fig.preview.wttpreview"
- name="fig.preview.wttpreview"></a>
-
- <p class="title"><b>Figure&#160;9.14.&#160;Previewing
- with TurboTeX's wdviwin</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2914603"
- name="id2914603"></a>DVIWindo</h3>
- </div>
- </div>
-
- <p>The <b>DVIWindo</b><a id="id2914617" class="indexterm"
- name="id2914617"></a><a id="id2914627" class="indexterm"
- name="id2914627"></a> previewer by Y&amp;Y<a
- id="id2914641" class="indexterm" name="id2914641"></a> is
- unique among the previewers used here. <b>DVIWindo</b>
- has no support for <tt>PK</tt> fonts; it relies entirely
- on scalable fonts<a id="id2914671" class="indexterm"
- name="id2914671"></a> provided by Microsoft Windows.
- (This means either PostScript Type&#160;1 fonts rendered
- by <b>Adobe Type Manager</b><a id="id2914689"
- class="indexterm" name="id2914689"></a> or built-in
- TrueType font <a id="id2914698" class="indexterm"
- name="id2914698"></a> support.) As a result, to use the
- <b>DVIWindo</b> previewer, you must purchase the Computer
- Modern fonts in TrueType or Adobe Type&#160;1 format (or
- not use them at all).</p>
-
- <p>The <b>DVIWindo</b> previewer is shown in
- Figure&#160;<a href="ch09.html#fig.preview.dviwindo"
- title="Figure&#160;9.15.&#160;Previewing with Y&amp;Y's DVIWindo">
- Figure&#160;9.15</a>. The pull-down menu shown in this
- image is the &#8220;TeX Menu,&#8221; a new feature of
- <b>DVIWindo</b> 1.1. This menu, which can be customized
- to include any programs you wish, allows <b>DVIWindo</b>
- to function as a TeX shell. Once <b>DVIWindo</b> is
- running, you can edit files and format documents with TeX
- directly from this menu.</p>
-
- <div class="figure">
- <a id="fig.preview.dviwindo"
- name="fig.preview.dviwindo"></a>
-
- <p class="title"><b>Figure&#160;9.15.&#160;Previewing
- with Y&amp;Y's DVIWindo</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p>The real advantage of using scalable fonts is that you
- can resize the image in arbitrary ways.<sup>[<a
- id="id2914807" name="id2914807"
- href="#ftn.id2914807">108</a>]</sup> For example,
- Figure&#160;<a href="ch09.html#fig.preview.dviwindo2"
- title="Figure&#160;9.16.&#160;DVIWindo preview much enlarged">
- Figure&#160;9.16</a> shows a much-enlarged version of the
- same page. Similar enlargement with non-scalable fonts
- would require that the <tt>PK</tt> fonts exist at very
- high-resolutions (occupying considerable disk space) or
- produce very jagged output. The jaggedness of the image
- shown here is the result of magnifying the captured
- screen image, not the previewer. Several useful
- information boxes are also shown in these images.</p>
-
- <div class="figure">
- <a id="fig.preview.dviwindo2"
- name="fig.preview.dviwindo2"></a>
-
- <p class="title"><b>Figure&#160;9.16.&#160;DVIWindo
- preview much enlarged</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p><b>DVIWindo</b> has several other interesting
- features:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Portions of a document may be copied into the
- Windows clipboard and then pasted into other
- applications. This allows you to construct complex
- mathematics in TeX, for example, and paste them
- into another Windows application. The pasted
- material will appear as a single graphical object
- that can be moved, resized, and cropped. The
- material is not rendered as a bitmap, so it can be
- resized without loss of quality!</p>
- </li>
-
- <li>
- <p>TIFF images are displayed in the document. If
- you use <b>dvipsone</b> (Y&amp;Y's PostScript
- printer driver) and create both TIFF and EPS
- (encapsulated PostScript) versions of an image,
- <b>DVIWindo</b> will automatically display the TIFF
- image, and <b>dvipsone</b> will automatically print
- the EPS image.</p>
- </li>
-
- <li>
- <p>Colored text and rules can be incorporated into
- a document with \special commands.</p>
- </li>
-
- <li>
- <p>You can create &#8220;hypertext&#8221; buttons
- in your document. Selecting a button (an area of
- text or a rule) automatically moves you to a
- destination marker in the document. These buttons
- are only meaningful to <b>DVIWindo</b>, but they do
- allow you to move around quickly in a document
- while you are writing it. Of course, they could
- also be very handy if you use <tt>DVI</tt> files
- for online documentation.</p>
- </li>
- </ul>
- </div>
-
- <p>In addition to the <b>DVIWindo</b> executable, several
- programs are provided to help you work with PostScript
- fonts under Windows. They are summarized in Table&#160;<a
- href="ch09.html#tab.dviwindo"
- title="Table&#160;9.3.&#160;DVIWindo Utilities">Table&#160;9.3</a>.</p>
-
- <div class="table">
- <a id="tab.dviwindo" name="tab.dviwindo"></a>
-
- <p class="title"><b>Table&#160;9.3.&#160;DVIWindo
- Utilities</b></p>
-
- <table summary="DVIWindo Utilities" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Utility</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it pfatopfb\,\x</td>
-
- <td align="left">Convert <tt>PFA</tt> files into
- <tt>PFB</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it pfbtopfa\,\x</td>
-
- <td align="left">Convert <tt>PFB</tt> files into
- <tt>PFA</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it tifftags</td>
-
- <td align="left">Show the tags used in a
- <tt>TIFF</tt> image</td>
- </tr>
-
- <tr>
- <td align="left">\it reencode</td>
-
- <td align="left">Change the encoding of a
- PostScript font</td>
- </tr>
-
- <tr>
- <td align="left">\it afmtotfm\,\x</td>
-
- <td align="left">Convert <tt>AFM</tt> files into
- <tt>TFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it tfmtoafm</td>
-
- <td align="left">Convert <tt>TFM</tt> files into
- <tt>AFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it afmtopfm</td>
-
- <td align="left">Convert <tt>AFM</tt> files into
- <tt>PFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it pfmtoafm</td>
-
- <td align="left">Convert <tt>PFM</tt> files into
- <tt>AFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it safeseac</td>
-
- <td align="left">Circumvents problem with
- accented letters in PS fonts under Windows</td>
- </tr>
-
- <tr>
- <td align="left">\it cleanup</td>
-
- <td align="left">Removes inactive Windows from
- the desktop</td>
- </tr>
-
- <tr>
- <td align="left">\it sysseg</td>
-
- <td align="left">Displays information about
- Windows system memory</td>
- </tr>
- </tbody>
- </table>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.preview.tty"
- name="sec.preview.tty"></a>Previewing on a TTY</h2>
- </div>
- </div>
-
- <p><a id="id2915365" class="indexterm"
- name="id2915365"></a>Graphical workstations and personal
- computers with graphics capabilities are a natural
- environment for previewing TeX output. Unfortunately, they
- aren't always available. This section describes several
- previewers that work in less sophisticated
- environments.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2915377"
- name="id2915377"></a>dvi2tty</h3>
- </div>
- </div>
-
- <p>The <b>dvi2tty</b> program<a id="id2915398"
- class="indexterm" name="id2915398"></a><a id="id2915408"
- class="indexterm" name="id2915408"></a> attempts to
- convert TeX output into ASCII text. This program is
- designed to provide an approximation of troff<a
- id="id2915421" class="indexterm" name="id2915421"></a>'s
- <b>nroff</b><a id="id2915435" class="indexterm"
- name="id2915435"></a> processor. To get the best results,
- you will have to reformat your document using a limited
- subset of TeX's capabilities. A LaTeX style file is
- included for this purpose. You can retrieve
- <b>dvi2tty</b> from the CTAN archives in the directory
- <tt>dviware/dvi2tty</tt>.</p>
-
- <p>The output from <b>dvi2tty</b> is imperfect in many
- ways, but it can provide a workable ASCII document. I
- used it to produce plain ASCII documentation in my
- <b>Sfware</b><a id="id2915485" class="indexterm"
- name="id2915485"></a> package, for example.
- <b>dvi2tty</b> also provides a quick-and-dirty method of
- applying some standard text processing tools, like
- <b>grep</b><a id="id2915508" class="indexterm"
- name="id2915508"></a>, to TeX output.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2915519"
- name="id2915519"></a>dvgt/dvitovdu</h3>
- </div>
- </div>
-
- <p><a id="id2915526" class="indexterm"
- name="id2915526"></a><a id="id2915533" class="indexterm"
- name="id2915533"></a><a id="id2915540" class="indexterm"
- name="id2915540"></a>These programs share a common
- history. As a result, they offer an overlapping set of
- features. The most recent work has been done on the
- <b>dvgt</b> processor. You can retrieve <b>dvgt</b> from
- the CTAN archives in the directory
- <tt>dviware/dvgt</tt>.</p>
-
- <p>Unlike <b>dvi2tty</b>, which is a conversion program,
- <b>dvgt</b> is an interactive previewer. One very neat
- feature of <b>dvgt</b> is its ability to preview TeX
- output on a number of graphics terminals, including
- Tektronix 4010, VT240, VT640, Gigi, Regis, VIS500,
- VIS550, VIS603, and VIS630 terminals. The importance of
- this feature is that many versions of <b>Kermit</b><a
- id="id2915617" class="indexterm" name="id2915617"></a>
- and <b>NCSA Telnet</b><a id="id2915631" class="indexterm"
- name="id2915631"></a> (and possibly other communications
- programs) support one of these terminal types. This means
- that you can preview documents even when you are away
- from your workstation, by using dial-up access with
- either a graphics terminal or plain ASCII.</p>
-
- <p>Even when output is limited to plain ASCII,
- <b>dvgt</b> attempts to make its output resemble the
- printed page. To do this, it frequently drops characters
- out of the middle of words and performs other
- space-saving abbreviations. The result is a crude, but
- workable preview, on a plain ASCII terminal.</p>
-
- <p>Figure&#160;<a href="ch09.html#fig.dvgttek"
- title="Figure&#160;9.17.&#160;Previewing with dvgt under Tektronix 4010 emulation">
- Figure&#160;9.17</a> shows an example of <b>dvgt</b>
- display in tek4010 emulation. This is a somewhat
- contrived example since the emulation is being performed
- by an xterm.</p>
-
- <div class="figure">
- <a id="fig.dvgttek" name="fig.dvgttek"></a>
-
- <p class="title"><b>Figure&#160;9.17.&#160;Previewing
- with dvgt under Tektronix 4010 emulation</b></p>
-
- <div class="mediaobject">
- <img src="FIXME:" />
- </div>
- </div>
-
- <p><b>dvitovdu</b> is an older version of the program. It
- is available in source code form in both C and Pascal.
- You can retrieve <b>dvitovdu</b> from the CTAN archives
- in the directory <tt>dviware/dvitovdu</tt>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2915747"
- name="id2915747"></a>crudetype</h3>
- </div>
- </div>
-
- <p><b>crudetype</b><a id="id2915760" class="indexterm"
- name="id2915760"></a><a id="id2915770" class="indexterm"
- name="id2915770"></a> is another plain-ASCII previewer.
- It provides features similar to <b>dvgt</b> and
- <b>dvitovdu</b>. It is written in <span
- class="sc">Web</span>, but it cannot be translated to C
- with the <b>web2c</b> conversion tool (so you will have
- to have a Pascal compiler).</p>
-
- <p>The <b>crudetype</b> program was written with VMS in
- mind, although it may be portable to other systems. You
- can retrieve <b>crudetype</b> from the CTAN archives in
- the directory <tt>dviware/crudetype</tt>.</p>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2912496" name="ftn.id2912496"
- href="#id2912496">106</a>]</sup> {Some setup is required
- to obtain this functionality. By default, the driver asks
- for the name of a font to substitute in place of the
- missing font.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2912560" name="ftn.id2912560"
- href="#id2912560">107</a>]</sup> {Particularly in
- networked environments where <b>dvidrv</b> assures that
- temporary filenames won't collide between users.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2914807" name="ftn.id2914807"
- href="#id2914807">108</a>]</sup> {Most previewers support
- resizing, but they are generally limited to the
- resolutions for which <tt>PK</tt> fonts are
- available.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;8.&#160;Printing"
- href="ch08.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;10.&#160;Online Documentation"
- href="ch10.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;8.&#160;Printing&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;10.&#160;Online Documentation</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch10.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch10.html
deleted file mode 100644
index 9eea2211c0b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch10.html
+++ /dev/null
@@ -1,782 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;10.&#160;Online Documentation</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing" />
- <link rel="next" href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;9.&#160;Previewing"
- href="ch09.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;11.&#160;Introducing MetaFont"
- href="ch11.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.online"
- name="chap.online"></a>Chapter&#160;10.&#160;Online
- Documentation</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>Some common kinds of documentation---for example, manuals
- for computer programs---present a unique challenge to the
- author. In many cases, it would be nice to be able to provide
- online documentation<a id="id2910943" class="indexterm"
- name="id2910943"></a><a id="id2910951" class="indexterm"
- name="id2910951"></a> in addition to a typeset manual.</p>
-
- <p>One option is to maintain two different documents: one for
- publication and one for online access. This is difficult to
- maintain and is prone to error. As the documentation evolves,
- it is almost inevitable that some changes to one document
- will not be implemented in the other.</p>
-
- <p>Another option is to include only very limited formatting
- information in the document designed for publication so that
- it is easy to &#8220;strip out&#8221; the formatting commands
- and produce an online manual. The unfortunate side effect of
- this approach is that the resulting typeset documentation
- doesn't have a very professional appearance.</p>
-
- <p>With care, TeX can be the basis for a middle-ground
- approach to this problem.<sup>[<a id="id2910836"
- name="id2910836" href="#ftn.id2910836">109</a>]</sup> If you
- are starting a new documentation project, TeXinfo<a
- id="id2910846" class="indexterm" name="id2910846"></a> and
- LameTeX<a id="id2910856" class="indexterm"
- name="id2910856"></a> provide two alternatives for the
- production of typeset and online documentation from the same
- source. \LaTeX2HTML<a id="id2910870" class="indexterm"
- name="id2910870"></a> and \LaTeX2hy<a id="id2910881"
- class="indexterm" name="id2910881"></a> provide alternatives
- that may be suitable for existing documentation.</p>
-
- <p>You'll find that the best results occur when you plan
- ahead: if you know that you need both typeset and ASCII
- documentation, try to use tools that will make the task
- easier. But, even if you try to plan ahead, it's not uncommon
- to find out after the fact that you need or want ASCII
- documentation. If you don't have the TeX sources, you'll just
- have to take the best results you can get with one of the
- tools described later in this chapter and do whatever
- hand-editing is required.</p>
-
- <p>If you have the TeX sources for a document, here are some
- guidelines that can help improve the quality of the
- conversion to plain ASCII:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Redefine all font commands to use \tt. This makes
- TeX work with a fixed-width font. You will probably get
- many, many overfull and underfull box messages. This
- can't be helped. Setting \tolerance and \hbadness to
- large values (10000 with TeX 2.x or 100000 with TeX
- 3.x, for example) will reduce the number of
- warnings.</p>
-
- <p>Similarly, redefine all the commands that change
- font size to select the same size (probably 10pt or
- 12pt will work best, but larger values may be better if
- you have wide margins).</p>
- </li>
-
- <li>
- <p>Don't use any special fonts---no <tt>picture</tt>
- environments in LaTeX, for example. Take out rules,
- too.</p>
- </li>
-
- <li>
- <p>Use \raggedright. There's no point in trying to line
- up the right margin.</p>
- </li>
-
- <li>
- <p>Remove or redefine all mathematics to avoid the use
- of math-mode. It won't work; don't ask TeX to try.</p>
- </li>
-
- <li>
- <p>Remove all tables (\halign in Plain TeX,
- <tt>tabular</tt> environments in LaTeX).</p>
- </li>
-
- <li>
- <p>Remove floating environments; this may help.</p>
- </li>
-
- <li>
- <p>Depending on your level of expertise and the number
- of documents that you have to convert, redefine
- footnotes and other environments to give you more
- marginal improvements.</p>
- </li>
- </ul>
- </div>
-
- <p>The <tt>ascii.sty</tt> style<a id="id2916135"
- class="indexterm" name="id2916135"></a> for LaTeX
- encapsulates many of these rules for you.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2916146"
- name="id2916146"></a>Something Is Lost</h2>
- </div>
- </div>
-
- <p>Many things that can easily be represented on paper
- cannot be represented in plain ASCII. One reason for this
- is that plain ASCII output is not proportionally spaced.
- Also, in ASCII you can move up or down only by rows, and
- left or right only by columns; you can't move down &#8220;3
- points&#8221; on a terminal to typeset a subscript, for
- example.</p>
-
- <p>These differences combine to make many things
- impossible. For all of its marvelous sophistication, TeX
- cannot help you typeset mathematics<a id="id2916172"
- class="indexterm" name="id2916172"></a> in plain ASCII. It
- just can't be done. Most tables can't be done in plain
- ASCII either (at least not if you want lines that are only
- 80 characters or so long).</p>
-
- <p>The following sections describe tools that may help you
- achieve the goal of online and typeset documentation from
- the same sources. Each tool has its own advantages and
- disadvantages. The ones that work best for you will depend
- on the type of documentation you are producing and the
- amount of work you are willing to do.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2916199"
- name="id2916199"></a>TeXinfo</h2>
- </div>
- </div>
-
- <p>TeXinfo<a id="id2916208" class="indexterm"
- name="id2916208"></a> is the document formatting system
- adopted by the Free Software Foundation (FSF)<a
- id="id2916220" class="indexterm" name="id2916220"></a> and
- the GNU Project<a id="id2916230" class="indexterm"
- name="id2916230"></a>. It is a special TeX format that is
- very different from standard TeX.<sup>[<a id="id2916239"
- name="id2916239" href="#ftn.id2916239">110</a>]</sup> The
- goal of TeXinfo is to devise an input format that can be
- processed by TeX to produce typeset output and then be
- processed by another program to produce <span
- class="emphasis"><em>hypertext</em></span> output. (The
- other program in this case is <b>MakeInfo</b><a
- id="id2916259" class="indexterm"
- name="id2916259"></a>.)</p>
-
- <p>TeXinfo supports ordinary text, sectioning commands,
- itemize and enumeration environments, footnotes,
- cross-references, tables of contents, lists of figures and
- tables, and multiple indexes.</p>
-
- <p>The TeXinfo example from Chapter&#160;<a
- href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>,
- is reproduced in Example&#160;<a
- href="ch10.html#ex.on.infinp"
- title="Example&#160;10.1.&#160;TeXinfo Commands">Example&#160;10.1</a>
- (the TeXinfo input), Figure&#160;<a
- href="ch10.html#fig.on.infex"
- title="Figure&#160;10.1.&#160;TeXinfo sample page">Figure&#160;10.1</a>
- (the typeset page), and Figure&#160;<a
- href="ch10.html#fig.on.infinf"
- title="Figure&#160;10.2.&#160;Online documentation produced by MakeInfo">
- Figure&#160;10.2</a> (the resulting online
- documentation).</p>
-
- <div class="example">
- <a id="ex.on.infinp" name="ex.on.infinp"></a>
-
- <p class="title"><b>Example&#160;10.1.&#160;TeXinfo
- Commands</b></p>
-<pre class="programlisting">
-<a type="simple" show="embed" actuate="onLoad" href="perf-inf"></a>
-</pre>
- </div>
-
- <div class="figure">
- <a id="fig.on.infex" name="fig.on.infex"></a>
-
- <p class="title"><b>Figure&#160;10.1.&#160;TeXinfo sample
- page</b></p>
-
- <div class="mediaobject">
- <img src="perf-inf.eps" />
- </div>
- </div>
-
- <div class="figure">
- <a id="fig.on.infinf" name="fig.on.infinf"></a>
-
- <p class="title"><b>Figure&#160;10.2.&#160;Online
- documentation produced by MakeInfo</b></p>
-
- <div class="literallayout">
- <p>&#160;&#160;<br />
- &#160;&#160;&#160;&#160;\FramedVerbInput{perf-inf.inf}<br />
-
- </p>
- </div>
- </div>
-
- <p>The output from <b>MakeInfo</b> is very nearly pure
- ASCII. The motivation for {hypertext} output is to make
- cross references dynamic<a id="id2916438" class="indexterm"
- name="id2916438"></a> when the &#8220;info&#8221; version
- of the document is used for online reference.<sup>[<a
- id="id2916455" name="id2916455"
- href="#ftn.id2916455">111</a>]</sup> The result is close
- enough to pure ASCII that converting it to pure ASCII is
- not (usually) too difficult. For example, the <span
- class="emphasis"><em>comp.fonts</em></span> newsgroup<a
- id="id2916474" class="indexterm" name="id2916474"></a>'s
- Frequently Asked Questions list is maintained as a TeXinfo
- document. It is posted as an info version that has been
- processed by a Perl script to &#8220;flatten&#8221; the
- hypertext.</p>
-
- <p>The TeXinfo format is well documented, so a brief
- description here will suffice. First, the backslash, which
- is ordinarily used to introduce control sequences in TeX,
- is not special. Instead the &#8220;@&#8221;-sign is used.
- Second, a TeXinfo document is divided into &#8220;nodes<a
- id="id2916507" class="indexterm"
- name="id2916507"></a>.&#8221; A node corresponds roughly to
- a chapter or a large section of a chapter. In the online
- documentation, it is easy to jump between related
- nodes.</p>
-
- <p>Because the info version of the document is ASCII text,
- many of the special typesetting features of TeX aren't
- applicable. To support them in the typeset document,
- TeXinfo allows you to specify that some portions of the
- input should be seen only by TeX and some should be seen
- only by <b>MakeInfo</b>. Example&#160;<a
- href="ch10.html#ex.on.infinp"
- title="Example&#160;10.1.&#160;TeXinfo Commands">Example&#160;10.1</a>
- uses this feature to typeset mathematics using the best
- features of both TeX and <b>MakeInfo</b>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2916555"
- name="id2916555"></a>\LaTeX2HTML</h2>
- </div>
- </div>
-
- <p>\LaTeX2HTML<a id="id2916564" class="indexterm"
- name="id2916564"></a> attempts to convert LaTeX documents
- into HTML<a id="id2916576" class="indexterm"
- name="id2916576"></a>, the document structuring language
- used by the World Wide Web (WWW)<a id="id2916586"
- class="indexterm" name="id2916586"></a> project. HTML
- stands for HyperText Markup Language<a id="id2916595"
- class="indexterm" name="id2916595"></a>; it is a way of
- describing documents in terms of their structure (headings,
- paragraphs, lists, etc.). SGML<a id="id2916606"
- class="indexterm" name="id2916606"></a>, the Standard
- Generalized Markup Language, provides a framework for
- developing structured documentation; HTML is one specific
- SGML document type. HTML documents are displayed by special
- programs called browsers<a id="id2916618" class="indexterm"
- name="id2916618"></a> that interpret the markup and present
- the information in a consistent manner. Because an HTML
- document is described in terms of its structure and not its
- appearance, HTML documents can be effectively displayed by
- browsers in non-graphical environments.</p>
-
- <p>One of the most important features of HTML documents is
- the ability to form hypertext links<a id="id2916638"
- class="indexterm" name="id2916638"></a><a id="id2916647"
- class="indexterm" name="id2916647"></a> between documents.
- Hypertext links allow you to build dynamic relationships
- between documents. For example, selecting a marked word or
- phrase in the current document displays more information
- about the topic, or a list of related topics.</p>
-
- <p>\LaTeX2HTML preserves many of the features of a LaTeX
- document in HTML. Elements that are too complex to
- represent in HTML, such as mathematical equations and logos
- like &#8220;TeX,&#8221; are converted into graphic images
- that can be displayed online by graphical browsers. All
- types of cross referencing elements (including footnotes)
- are preserved as hypertext links.</p>
-
- <p>When installed, \LaTeX2HTML understands many basic LaTeX
- commands, but it can be customized to handle other styles.
- \LaTeX2HTML is written in <b>Perl</b>.</p>
-
- <p>All in all, \LaTeX2HTML is one of the easiest and most
- effective tools for translating typeset documentation into
- a format suitable for online presentation. In a graphical
- environment like X11, Microsoft Windows, or the Macintosh,
- HTML documents offer very good support for online
- documentation.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2916701"
- name="id2916701"></a>LameTeX</h2>
- </div>
- </div>
-
- <p>LameTeX<a id="id2916710" class="indexterm"
- name="id2916710"></a> is a PostScript translator<a
- id="id2916722" class="indexterm" name="id2916722"></a> for
- a (very limited) subset of LaTeX. One of its original
- design goals, the inclusion of sophisticated PostScript
- commands directly in a LaTeX document, has been superseded
- by the PSTricks<a id="id2916733" class="indexterm"
- name="id2916733"></a> package. However, one of the side
- effects of a special-purpose translator for LaTeX is the
- ability of that translator to produce different kinds of
- output, including plain ASCII.</p>
-
- <p>The primary advantage of this method is that it does not
- require learning an entirely foreign macro package like
- TeXinfo. The disadvantage is that it understands only a
- very small subset of LaTeX. This subset includes <span
- class="emphasis"><em>only</em></span> the following
- commands:</p>
-
- <div class="informaltable">
- <table border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <tbody>
- <tr>
- <td align="left">\#</td>
-
- <td align="left">\footnotesize</td>
-
- <td align="left">\ref</td>
- </tr>
-
- <tr>
- <td align="left">\$</td>
-
- <td align="left">\hspace</td>
-
- <td align="left">\rm</td>
- </tr>
-
- <tr>
- <td align="left">\%</td>
-
- <td align="left">\hspace*</td>
-
- <td align="left">\sc</td>
- </tr>
-
- <tr>
- <td align="left">\&#160;</td>
-
- <td align="left">\huge</td>
-
- <td align="left">\scriptsize</td>
- </tr>
-
- <tr>
- <td align="left">\Huge</td>
-
- <td align="left">\include</td>
-
- <td align="left">\section</td>
- </tr>
-
- <tr>
- <td align="left">\LARGE</td>
-
- <td align="left">\input</td>
-
- <td align="left">\section*</td>
- </tr>
-
- <tr>
- <td align="left">\Large</td>
-
- <td align="left">\it</td>
-
- <td align="left">\setlength</td>
- </tr>
-
- <tr>
- <td align="left">\_</td>
-
- <td align="left">\item</td>
-
- <td align="left">\sf</td>
- </tr>
-
- <tr>
- <td align="left">\addtolength</td>
-
- <td align="left">\itemize</td>
-
- <td align="left">\sl</td>
- </tr>
-
- <tr>
- <td align="left">\backslash</td>
-
- <td align="left">\label</td>
-
- <td align="left">\small\smallskip</td>
- </tr>
-
- <tr>
- <td align="left">\begin</td>
-
- <td align="left">\large</td>
-
- <td align="left">\subparagraph</td>
- </tr>
-
- <tr>
- <td align="left">\bf</td>
-
- <td align="left">\ldots</td>
-
- <td align="left">\subparagraph*</td>
- </tr>
-
- <tr>
- <td align="left">\bigskip</td>
-
- <td align="left">\medskip</td>
-
- <td align="left">\subsection</td>
- </tr>
-
- <tr>
- <td align="left">\center</td>
-
- <td align="left">\newlength</td>
-
- <td align="left">\subsection*</td>
- </tr>
-
- <tr>
- <td align="left">\chapter</td>
-
- <td align="left">\newline</td>
-
- <td align="left">\subsubsection</td>
- </tr>
-
- <tr>
- <td align="left">\chapter*</td>
-
- <td align="left">\normalsize</td>
-
- <td align="left">\subsubsection*</td>
- </tr>
-
- <tr>
- <td align="left">\clearpage</td>
-
- <td align="left">\par</td>
-
- <td align="left">\tiny</td>
- </tr>
-
- <tr>
- <td align="left">\description</td>
-
- <td align="left">\paragraph</td>
-
- <td align="left">\today</td>
- </tr>
-
- <tr>
- <td align="left">\document</td>
-
- <td align="left">\paragraph*</td>
-
- <td align="left">\tt</td>
- </tr>
-
- <tr>
- <td align="left">\documentstyle</td>
-
- <td align="left">\part</td>
-
- <td align="left">\verbatim</td>
- </tr>
-
- <tr>
- <td align="left">\em</td>
-
- <td align="left">\part*</td>
-
- <td align="left">\verbatim*</td>
- </tr>
-
- <tr>
- <td align="left">\end</td>
-
- <td align="left">\quotation</td>
-
- <td align="left">\verse</td>
- </tr>
-
- <tr>
- <td align="left">\enumerate</td>
-
- <td align="left">\quote</td>
-
- <td align="left">\vspace</td>
- </tr>
-
- <tr>
- <td align="left">\flushleft</td>
-
- <td align="left">\raggedleft</td>
-
- <td align="left">\vspace*</td>
- </tr>
-
- <tr>
- <td align="left">\flushright</td>
-
- <td align="left">\raggedright</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>In addition, unlike LaTeX, LameTeX doesn't understand
- any Plain TeX commands (other than the ones listed).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2917217"
- name="id2917217"></a>latex2hy</h2>
- </div>
- </div>
-
- <p><b>latex2hy</b><a id="id2917230" class="indexterm"
- name="id2917230"></a> is a LaTeX-to-ASCII converter<a
- id="id2917238" class="indexterm" name="id2917238"></a>. It
- has several options for controlling the input and output
- character sets. In addition, <b>latex2hy</b> has a number
- of options for improving the quality of both ASCII and
- printed documentation. For example, input documents can
- contain both TeX and ASCII representations for complex
- objects (like mathematical formulae). The printed
- documentation uses the TeX version while <b>latex2hy</b>
- uses the ASCII version. Provision is also made for
- &#8220;fixups,&#8221; which allow character sequences from
- the input text to be translated into different sequences on
- output. For example, &#8220;$9.81\frac{m}{s^2}$&#8221; can
- be automatically translated into <tt>9.81m/s^2</tt>. By
- adding specific fixups to each document that you translate,
- you can obtain successively better approximations
- automatically.</p>
-
- <p><b>latex2hy</b> gives particular attention to cross
- references<a id="id2917305" class="indexterm"
- name="id2917305"></a>. Cross references are translated into
- &#8220;links<a id="id2917320" class="indexterm"
- name="id2917320"></a>&#8221; between topics in <span
- class="emphasis"><em>hypertext</em></span> output formats.
- Currently, only the <span
- class="emphasis"><em>TurboVision</em></span><a
- id="id2917336" class="indexterm" name="id2917336"></a>
- hypertext format is supported, although several other
- formats are being considered.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2917348"
- name="id2917348"></a>detex</h2>
- </div>
- </div>
-
- <p><b>detex</b><a id="id2917361" class="indexterm"
- name="id2917361"></a> is a simple program that does little
- more than strip control sequences and other TeXish
- character sequences from your document. Doing this makes
- the document more amenable to other kinds of processing
- (like spellchecking) but does a poor job of producing
- &#8220;online documentation.&#8221; Still, it's an
- option.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2917381"
- name="id2917381"></a>dvispell</h2>
- </div>
- </div>
-
- <p>The <b>dvispell</b><a id="id2917395" class="indexterm"
- name="id2917395"></a> program produces plain text output
- from a <tt>DVI</tt> file. It is not a spellchecker, but it
- was designed to extract the words from a TeX document which
- were then fed to a spellchecking program that was unable to
- ignore TeX control sequences.</p>
-
- <p>The <b>dvispell</b> program is part of the emTeX<a
- id="id2917428" class="indexterm" name="id2917428"></a>
- package, and it is remarkably sophisticated. There are many
- ways in which <b>dvispell</b> can be programmed to perform
- complex manipulations. One special strength of
- <b>dvispell</b> is its ability to handle conversion of
- accented characters and Greek symbols.</p>
-
- <p><b>dvispell</b> differs from the other programs
- described here because it works with TeX output, the
- <tt>DVI</tt> file. On the one hand, this provides
- <b>dvispell</b> with more information (character positions,
- line breaks, floating bodies, etc). On the other hand, all
- of the formatting commands are missing, so it isn't easy to
- determine what the user had in mind. (It's a bit like
- reverse-engineering a piece of software---without the
- source code, it's not always easy to tell why things look
- the way they do.) But <b>dvispell</b> gives you access to
- most of the information that is present in the <tt>DVI</tt>
- file.</p>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2910836" name="ftn.id2910836"
- href="#id2910836">109</a>]</sup> {Structured markup
- languages like SGML also address this problem, but they
- introduce their own set of difficulties. Regardless of
- whatever advantages they may hold, I'm not going to
- discuss them here.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2916239" name="ftn.id2916239"
- href="#id2916239">110</a>]</sup> {A LaTeX implementation,
- called LaTeXinfo, is also available.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2916455" name="ftn.id2916455"
- href="#id2916455">111</a>]</sup> {&#8220;Info&#8221; is
- the name of both the output format and a program for
- displaying the text in a hypertext fashion. Another
- common way to access info files is with the GNU emacs
- online help system.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;9.&#160;Previewing"
- href="ch09.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;11.&#160;Introducing MetaFont"
- href="ch11.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;9.&#160;Previewing&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;11.&#160;Introducing MetaFont</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch11.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch11.html
deleted file mode 100644
index b75eb560ed1..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch11.html
+++ /dev/null
@@ -1,1139 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;11.&#160;Introducing MetaFont</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation" />
- <link rel="next" href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;10.&#160;Online Documentation"
- href="ch10.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries"
- href="ch12.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.mf"
- name="chap.mf"></a>Chapter&#160;11.&#160;Introducing
- MetaFont</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>TeX builds pages out of boxes<a id="id2915957"
- class="indexterm" name="id2915957"></a> and glue<a
- id="id2915971" class="indexterm" name="id2915971"></a>. The
- smallest boxes are usually individual characters. MetaFont<a
- id="id2915983" class="indexterm" name="id2915983"></a> is a
- tool that creates the actual characters.</p>
-
- <p>In the last few years, a real explosion has taken place in
- the number of readily available fonts<a id="id2916000"
- class="indexterm" name="id2916000"></a><a id="id2915858"
- class="indexterm" name="id2915858"></a><a id="id2915866"
- class="indexterm" name="id2915866"></a>. Today, many people
- have access to a large number of high quality typefaces. Not
- too long ago (before Adobe Type Manager (ATM)<a
- id="id2915883" class="indexterm" name="id2915883"></a> was
- available for the Macintosh and Microsoft Windows), fonts
- were too expensive to be generally available. In those days,
- a font building tool like MetaFont was essential if TeX was
- going to have a number of typefaces and a large number of
- mathematical symbols. Today, the role of MetaFont is
- diminishing. Many people choose to use PostScript fonts<a
- id="id2915891" class="indexterm" name="id2915891"></a> almost
- entirely. In fact, with PostScript alternatives to the
- Computer Modern Math fonts<a id="id2915912" class="indexterm"
- name="id2915912"></a><a id="id2915918" class="indexterm"
- name="id2915918"></a> now available, it's possible to use TeX
- without using MetaFont fonts at all.</p>
-
- <p>On the other hand, lots of people do still use the
- Computer Modern fonts, and there are many other MetaFont
- fonts (for non-English languages like Arabic and Japanese,
- for example), so MetaFont is still a useful tool. Also, it
- can be used to make nice portable diagrams.</p>
-
- <p>This chapter cannot teach you how to harness all of
- MetaFont's power. The only practical way to learn how to
- design your own images with MetaFont is to read <span
- class="emphasis"><em>The \MF{}book</em></span>&#160;[<a
- href="bi01.html#kn:mfbook">kn:mfbook</a>] (even if your
- images are nowhere near as complex as an entire font).</p>
-
- <p>What you will learn from this chapter is how to run
- MetaFont to create TeX <tt>PK</tt> fonts<a id="id2917710"
- class="indexterm" name="id2917710"></a> and <tt>TFM</tt>
- files<a id="id2917745" class="indexterm"
- name="id2917745"></a> from existing MetaFont programs. The
- Computer Modern fonts, the \AmS fonts, and the DC Fonts are
- all created with MetaFont. It is not unreasonable to imagine
- that you might someday want to create one of these fonts at a
- non-standard size or unusual magnification.</p>
-
- <p>Knowing how to run MetaFont will also help you set up a
- system for performing automatic font generation. This can
- save a lot of disk space. See the section called &#8220;<a
- href="ch05.html#sec.autofont"
- title="Automatic Font Generation by DVI Drivers">the section
- called &#8220;Automatic Font Generation by DVI
- Drivers&#8221;</a>&#8221; in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>, <span
- class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>,
- for more information about setting up automatic font
- generation.</p>
-
- <p>From many perspectives, TeX and MetaFont behave in
- analogous ways. Where TeX reads a plain text <tt>TEX</tt>
- document, processes it, and produces a <tt>DVI</tt> file,
- MetaFont reads a plain text <tt>MF</tt> program, processes
- it, and produces a generic bitmap font file as output.</p>
-
- <p>Because you probably aren't going to be writing your own
- font programs for MetaFont, you have to get them from
- somewhere. Many distributions of TeX include MetaFont and the
- font files for the Computer Modern fonts. This chapter will
- concentrate on just the Computer Modern font programs because
- those are the most likely to be available.</p>
-
- <p>Many MetaFont fonts can be retrieved from the CTAN
- archives. Table&#160;<a href="ch11.html#tab.mf.mfdistrib"
- title="Table&#160;11.1.&#160;Some Popular MetaFont Fonts on the CTAN Archives">
- Table&#160;11.1</a> lists some common fonts and their
- location in the CTAN archives. A collection of font samples
- is shown in Appendix&#160;<a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a>,
- <span class="emphasis"><em><a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a></em></span>.</p>
-
- <div class="table">
- <a id="tab.mf.mfdistrib" name="tab.mf.mfdistrib"></a>
-
- <p class="title"><b>Table&#160;11.1.&#160;Some Popular
- MetaFont Fonts on the CTAN Archives</b></p>
-
- <table
- summary="Some Popular MetaFont Fonts on the CTAN Archives"
- border="1">
- <colgroup>
- <col />
- <col />
- </colgroup>
-
- <thead>
- <tr>
- <th>Fonts</th>
-
- <th>Location</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td>Standard Computer Modern</td>
-
- <td><tt>fonts/cm</tt></td>
- </tr>
-
- <tr>
- <td>Standard LaTeX</td>
-
- <td><tt>macros/latex/distribs/base/fonts</tt></td>
- </tr>
-
- <tr>
- <td>A<sub>m</sub>S Fonts</td>
-
- <td><tt>fonts/ams</tt></td>
- </tr>
-
- <tr>
- <td>DC Fonts</td>
-
- <td><tt>fonts/dc</tt></td>
- </tr>
-
- <tr>
- <td>Concrete</td>
-
- <td><tt>fonts/concrete</tt></td>
- </tr>
-
- <tr>
- <td>Pandora</td>
-
- <td><tt>fonts/pandora</tt></td>
- </tr>
-
- <tr>
- <td>Ralph Smith's Script Font</td>
-
- <td><tt>fonts/rsfs</tt></td>
- </tr>
-
- <tr>
- <td>St. Mary's Road</td>
-
- <td><tt>fonts/stmary</tt></td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.mf.gettingstarted"
- name="sec.mf.gettingstarted"></a>What to Run?</h2>
- </div>
- </div>
-
- <p>Like TeX itself, the actual MetaFont file you have to
- execute <a id="id2918084" class="indexterm"
- name="id2918084"></a> varies between platforms and
- implementations. If you have built and/or installed TeX,
- you probably already know what program to run. You'll have
- to ask your system administrator for help if you cannot
- figure out what the name of the MetaFont executable is on
- your computer. In the rest \linebreak</p>
-
- <p>of this chapter, I'll assume that the command <span
- class="emphasis"><em>mf</em></span> runs MetaFont. You
- should substitute the name of the executable program on
- your system for <span class="emphasis"><em>mf</em></span>
- in the examples that follow.</p>
-
- <p>MetaFont comes in big and small versions just like TeX.
- You will need the big MetaFont if you are building fonts
- for very high-resolution devices or at very large sizes.
- Most fonts can be built with a small MetaFont.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2918131"
- name="id2918131"></a>What Files Does MetaFont
- Need?</h2>
- </div>
- </div>
-
- <p>In addition to the MetaFont programs, MetaFont<a
- id="id2918140" class="indexterm" name="id2918140"></a> must
- be able to find several other files. The files that are
- needed are normally created during the installation
- process. The sections that follow describe each of the
- files that MetaFont needs.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2918156"
- name="id2918156"></a>Pool Files</h3>
- </div>
- </div>
-
- <p>The pool file<a id="id2918169" class="indexterm"
- name="id2918169"></a> for each version of MetaFont has
- the same purpose as the pool file created for TeX. It is
- created when MetaFont is compiled. If you don't have a
- pool file, there's nothing you can do about it. If you
- obtained precompiled programs (from the Internet, from a
- friend, or commercially) and you don't have the pool file
- needed by MetaFont, you received an incomplete
- distribution.</p>
-
- <p>If you did not install MetaFont, and the pool file is
- missing, contact the system administrator who performed
- the installation. Something was done incorrectly.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2918200"
- name="id2918200"></a>Base Files</h3>
- </div>
- </div>
-
- <p>Base files<a id="id2918209" class="indexterm"
- name="id2918209"></a> for MetaFont are analogous to
- format files for TeX. Unlike TeX, which has many
- different format files, there are relatively few base
- files for MetaFont.</p>
-
- <p>Base files are created by a special version of
- MetaFont, usually called \iniMF. However, some
- implementations combine MetaFont and \iniMF into one
- program, in which case you must select \iniMF with a
- special option when you run the program.</p>
-
- <p>Like iniTeX, \iniMF interprets all the control
- sequences in a set of base macros and builds the
- in-memory data structures that the MetaFont program
- needs. After loading all the files, \iniMF writes the
- memory image into a base file. When MetaFont loads the
- base file, it simply copies it into memory; no
- interpretation is necessary.</p>
-
- <p>Because MetaFont loads the base files without
- interpretation, they are not generally portable from one
- system to another, or even between different versions of
- MetaFont on the same system. Different versions of
- MetaFont load differently in memory, and this makes the
- base files incompatible. For example, you need a big
- \iniMF to make base files for big MetaFont and small
- \iniMF for a small MetaFont.</p>
-
- <p>The &#8220;<a href="ch11.html#sec.mf.gettingstarted"
- title="What to Run?">the section called &#8220;What to
- Run?&#8221;</a>&#8221; section later in this chapter
- describes how to build a base file, if you do not already
- have one.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2918279"
- name="id2918279"></a>MetaFont Programs</h3>
- </div>
- </div>
-
- <p>When you run MetaFont, you have to tell it what file
- (MetaFont program)<a id="id2918287" class="indexterm"
- name="id2918287"></a> to process. MetaFont programs are
- stored in files with the extension <tt>.mf</tt>. If you
- specify a complete pathname, MetaFont will load the
- specific file that you request. If you specify a simple
- filename without a path, MetaFont looks for the file in
- several user-defined and, possibly, system-defined
- locations. The most common way to specify user-defined
- locations is by setting the <tt>MFINPUTS</tt> environment
- variable to a list of subdirectories where MetaFont
- programs are kept. The format of the environment variable
- differs according to the platform you use. On unix
- systems, it is a list of directory names separated by
- colons. On MS-DOS and OS/2 systems, it is a list of
- directory names separated by semicolons. Consult the
- documentation for the particular implementation of
- MetaFont you use for more information about
- system-defined locations where MetaFont looks for input
- files.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2918336"
- name="id2918336"></a>Command-line Options</h2>
- </div>
- </div>
-
- <p>In addition to the name of the MetaFont program,
- MetaFont has very few command-line<a id="id2918345"
- class="indexterm" name="id2918345"></a><a id="id2918360"
- class="indexterm" name="id2918360"></a> options. The name
- of a base file is the only option regularly used. In this
- section, I'll explain what can go on the MetaFont command
- line.</p>
-
- <p>A formal specification of the MetaFont command line
- looks like this:</p>
-<pre class="screen">
-$ <span class="bold"><b>mf <span
-class="emphasis"><em>switches</em></span> <span
-class="bold"><b>&amp;</b></span><span
-class="emphasis"><em>base</em></span> mf-program mf-commands</b></span>
-</pre>
-
- <p>After the name of the MetaFont program, the first things
- that you can specify on the command line are
- implementation-dependent switches and options. For example,
- implementations of MetaFont that combine \iniMF and
- MetaFont into a single program may use the switch <span
- class="emphasis"><em>/I</em></span> to specify that \iniMF
- processing is desired. There are no system-independent
- switches for MetaFont. Consult the documentation that comes
- with your implementation for more information about
- system-dependent switches.</p>
-
- <p>After any system-dependent switches, you can specify the
- name of the base file to use. This option, if present, must
- come before any other options, and you must put an
- ampersand (&amp;) in front of the base file name. If you do
- not specify a base file, MetaFont will use a default
- base.</p>
-
- <p>After the base, MetaFont looks for the name of a
- MetaFont program file. If MetaFont finds a filename on the
- command line, it will process the program contained in that
- file before looking at any other options that may
- follow.</p>
-
- <p>Finally, you can insert arbitrary MetaFont commands on
- the command line by typing them just as you would in a
- program. In fact, this is frequently done to change the
- size or magnification of the font being created. Exactly
- how this is accomplished is described in the section called
- &#8220;<a href="ch11.html#sec.buildfont"
- title="Running MetaFont">the section called &#8220;Running
- MetaFont&#8221;</a>&#8221; later in this chapter.</p>
-
- <p>Please read the section called &#8220;<a
- href="ch03.html#sec.runtex.cmdcautions"
- title="Command-line Options">the section called
- &#8220;Command-line Options&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>,
- for a detailed description of some common problems with
- MetaFont commands on the command line. They are exactly the
- same problems that can occur on the TeX command line.</p>
-
- <p>Also, the behavior of MetaFont when run without any
- options at all is the same as the behavior of TeX as
- described in the section called &#8220;<a
- href="ch03.html#sec.runtex.texwoopts"
- title="Filenames and TeX">the section called
- &#8220;Filenames and TeX&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2918545"
- name="id2918545"></a>Building a Base File</h2>
- </div>
- </div>
-
- <p>Building a base file<a id="id2918553" class="indexterm"
- name="id2918553"></a> for MetaFont is exactly analogous to
- building a format file for TeX. Fortunately, there are far
- fewer base files. The two most common base files are the
- <span class="emphasis"><em>plain</em></span> <a
- id="id2918571" class="indexterm" name="id2918571"></a> base
- and the <span class="emphasis"><em>cmbase</em></span><a
- id="id2918583" class="indexterm" name="id2918583"></a> (the
- base used for the Computer Modern fonts). Use the \iniMF
- program<a id="id2918593" class="indexterm"
- name="id2918593"></a> to build a base file. For example, to
- build the plain base, use:</p>
-<pre class="screen">
-\$ <span class="bold"><b>inimf plain</b></span>
-</pre>
-
- <p>Move the resulting files, <tt>plain.base</tt><a
- id="id2918627" class="indexterm" name="id2918627"></a> and
- <tt>plain.log</tt><a id="id2918646" class="indexterm"
- name="id2918646"></a>, into the directory where MetaFont
- looks for base files (typically in a <tt>bases</tt> or
- <tt>formats</tt> subdirectory under the standard TeX
- directory).</p>
-
- <p>The <span class="emphasis"><em>cmbase</em></span> is
- actually an extension of the plain base. To build it, use
- the command:</p>
-<pre class="screen">
-\$ <span class="bold"><b>inimf &amp;plain cmbase</b></span>
-</pre>
-
- <p>Remember to use appropriate quotation or shell escape
- characters to prevent the ampersand from being
- misinterpreted.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.buildfont" name="sec.buildfont"></a>Running
- MetaFont</h2>
- </div>
- </div>
-
- <p><a id="id2918724" class="indexterm"
- name="id2918724"></a><a id="id2918736" class="indexterm"
- name="id2918736"></a>The sections that follow describe how
- to use MetaFont to make a font from an existing <tt>MF</tt>
- file. You should reread the sections &#8220;<a
- href="ch05.html#sec.issueofsize"
- title="What TeX Needs To Know">the section called
- &#8220;What TeX Needs To Know&#8221;</a>&#8221; from
- Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>,
- and &#8220;<a href="ch08.html#sec.bitfonts"
- title="Built-in Fonts">the section called &#8220;Built-in
- Fonts&#8221;</a>&#8221; from Chapter&#160;<a
- href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a>,
- <span class="emphasis"><em><a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a></em></span>,
- if you are unfamiliar with the notions of bitmap and device
- resolution and magnification and design size in TeX
- fonts.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2918826"
- name="id2918826"></a>Picking a Mode</h3>
- </div>
- </div>
-
- <p>The input to MetaFont<a id="id2918833"
- class="indexterm" name="id2918833"></a> is an
- &#8220;outline&#8221; description of a font. The output
- is a set of bitmaps that realize the outline on a
- particular device at a particular size.</p>
-
- <p>Output from MetaFont is naturally device-dependent
- because different printers have different resolutions.
- But even two printers with the same resolution sometimes
- produce different looking results from the same bit
- patterns. For example, some laser printers are
- &#8220;write white&#8221; printers, and some are
- &#8220;write black&#8221; printers---depending on whether
- the printer fills in the black (text) areas or the white
- (non-text) areas of the page. A small, intricate bitmap
- (like a character from a font) designed for a write-black
- printer may not look as good on a write-white printer and
- vice versa.</p>
-
- <p>There are several internal parameters that can be
- modified to produce optimal output on any given device.
- These parameters are grouped together in a <span
- class="emphasis"><em>mode</em></span>. Whenever you run
- MetaFont to create a new set of bitmaps, you must select
- a mode.</p>
-
- <p>There are no rules for determining what parameters
- produce the best mode for a particular printer; it's just
- done by trial and error (set some values, print a font,
- see if it looks good, adjust some values, print another
- font, etc.).</p>
-
- <p>Luckily, a large collection of predefined MetaFont
- modes is available in the CTAN archives. The file
- <tt>fonts/modes/modes.mf</tt> contains appropriate
- MetaFont modes for many printers.</p>
-
- <p>Each mode has a name<a id="id2918916"
- class="indexterm" name="id2918916"></a>. For example,
- <tt>laserwriter</tt> and <tt>LNOthree</tt> are two modes
- from <tt>modes.mf</tt>. See &#8220;<a
- href="ch11.html#sec.buildfont"
- title="Running MetaFont">the section called
- &#8220;Running MetaFont&#8221;</a>,&#8221; later in this
- chapter for how to select a mode when you run
- MetaFont.</p>
-
- <p>Internally, MetaFont has a variable called
- <tt>mode</tt> that it uses to keep track of the current
- mode. The examples in this chapter use the
- <tt>laserwriter</tt> mode because that is appropriate for
- my printer.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2918994"
- name="id2918994"></a>Proofing mode</h4>
- </div>
- </div>
-
- <p>Proofing mode<a id="id2919003" class="indexterm"
- name="id2919003"></a> is the mode that MetaFont uses if
- you do not select another mode. In proofing mode,
- MetaFont displays each character on the screen. This
- mode does not usually produce a useful font because it
- sets the device resolution to 2601.72 dots per inch
- (dpi). That resolution is chosen so that there are
- exactly 36 pixels per point (one point is 1/72.27
- inches in TeX).</p>
-
- <p>Because font designers are going to want to look at
- a font on the screen far more often than they will want
- to print it, MetaFont uses proofing mode as the
- default.</p>
-
- <p>If you find that MetaFont is producing fonts with
- huge resolutions (thousands of dots per inch) or fonts
- without <tt>TFM</tt> files, you're probably running in
- proofing mode. Remember to use the mode-setting
- commands on the command line when you run MetaFont.
- These commands are described in &#8220;<a
- href="ch11.html#sec.buildfont"
- title="Running MetaFont">the section called
- &#8220;Running MetaFont&#8221;</a>,&#8221; later in
- this chapter.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2919066"
- name="id2919066"></a>Selecting a Size</h3>
- </div>
- </div>
-
- <p>The design size<a id="id2919075" class="indexterm"
- name="id2919075"></a> of the font you are creating is
- determined by the <tt>MF</tt> file you use. For example,
- the design size of <tt>cmr10.mf</tt> is 10pt. The design
- size of <tt>cmr12.mf</tt> is 12pt, etc. To select how
- large you want the bitmaps to be, you must set the
- magnification. There is no other way to select the size
- when you are running MetaFont.</p>
-
- <p>If you know the design size of a font and the size of
- the bitmaps that you actually want to produce, it is easy
- to calculate the magnification required. The
- magnification is simply the ratio of the size you want to
- the design size.</p>
-
- <p>For example, suppose you need a 16pt version of
- Computer Modern Roman. First, pick the font that has a
- design size closest to the size you want---in this case,
- Computer Modern Roman 17pt (<tt>cmr17.mf</tt>). To
- calculate the magnification, simply divide 16 by 17; in
- other words, the desired magnification is 0.9412. To make
- a 13pt version of <tt>cmr12</tt>, use a magnification of
- 1.0833. Remember, in order to use these fonts in TeX, you
- will have to use the <tt>at</tt> or <tt>scaled</tt>
- operators (for example, <tt>\font\cmrxvi=cmr17 at
- 16pt</tt>).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2919175"
- name="id2919175"></a>Making a GF Font</h3>
- </div>
- </div>
-
- <p><a id="id2919183" class="indexterm"
- name="id2919183"></a><a id="id2919196" class="indexterm"
- name="id2919196"></a><a id="id2919208" class="indexterm"
- name="id2919208"></a>After you have selected a mode and a
- magnification, running MetaFont is easy. In general, you
- use a command line like the following:</p>
-<pre class="screen">
-\$ <span class="bold"><b>mf {\bs}mode=</b></span><span
-class="emphasis"><em>selected-mode</em></span><span
-class="bold"><b>; mag=</b></span><span
-class="emphasis"><em>desired-magnification</em></span><span
-class="bold"><b>; {\bs}input</b></span> <span
-class="emphasis"><em>mf-file</em></span>
-</pre>
-
- <p>For example, on a unix system, the following command
- line would make a GF file for the Computer Modern Roman
- 12pt font at a size of 13pt:</p>
-<pre class="screen">
-\$ <span
-class="bold"><b>mf '{\bs}mode=laserwriter; mag=1.0833; {\bs}input cmr12'</b></span>
-</pre>
-
- <p>Note the use of quotation marks to avoid
- shell-expansion of the backslash characters.</p>
-
- <p>On an MS-DOS or OS/2 system, where the backslash is
- not a special character, the 13pt version of
- <tt>cmr12</tt> is made with the following command:</p>
-<pre class="screen">
-\$ <span
-class="bold"><b>mf {\bs}mode=laserwriter; mag=1.0833; {\bs}input cmr12</b></span>
-</pre>
-
- <p>As you can see, the semicolons are <span
- class="emphasis"><em>required</em></span> in both
- cases.</p>
-
- <p>Magnification<a id="id2919326" class="indexterm"
- name="id2919326"></a> can be expressed with the
- <tt>magstep()</tt> function if the font is being built at
- a standard magstep size. For example, the following
- command builds a 14.44pt version of <tt>cmr12</tt>:</p>
-<pre class="screen">
- \$ <span
-class="bold"><b>mf {\bs}mode=hplaser; mag=magstep(1); {\bs}input cmr12</b></span>
-</pre>
-
- <p>This corresponds to \magstep1. This example also
- illustrates how a different mode can be selected. In this
- case, the font is being built for an HP LaserJet printer.
- The command is shown without quotations, but they are
- still necessary on unix systems.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2919378"
- name="id2919378"></a>Making a PK Font</h3>
- </div>
- </div>
-
- <p><a id="id2919390" class="indexterm"
- name="id2919390"></a><a id="id2919415" class="indexterm"
- name="id2919415"></a><a id="id2919427" class="indexterm"
- name="id2919427"></a>Running MetaFont, as shown above,
- produces a <tt>TFM</tt> file and a <tt>GF</tt> file. TeX
- only needs the <tt>TFM</tt> file, which can simply be
- copied to the appropriate directory. For the Computer
- Modern fonts, you probably already have copies of the
- <tt>TFM</tt> files, so the duplicates produced by
- MetaFont can be deleted. The <tt>TFM</tt> file does not
- change at different magnifications, so you do not need to
- save different <tt>TFM</tt> files for different
- sizes.</p>
-
- <p>The <tt>GF</tt> file contains a font in the
- &#8220;generic bitmap&#8221; format. Most DVI drivers use
- <tt>PK</tt> files. The <b>GFtoPK</b> program converts
- <tt>GF</tt> fonts into <tt>PK</tt> fonts. If MetaFont
- creates the file <tt>cmr12.gf</tt>, you can convert it
- into a <tt>PK</tt> file by issuing the command:</p>
-<pre class="screen">
- \$ <span class="bold"><b>gftopk cmr12.gf cmr12.pk</b></span>
-</pre>
-
- <p>After conversion, you should move the <tt>PK</tt> file
- to the appropriate directory for your DVI driver and
- delete the <tt>GF</tt> file. <tt>PK</tt> files are
- generally stored in one of two directory structures. On
- operating systems that support long filenames, it is most
- common to store all the <tt>PK</tt> files for a given
- font in the same directory, using the extension to
- identify the resolution. In this case, a 360dpi version
- of <tt>cmr10</tt> would be stored as
- <tt>cmr10.360pk</tt>. Under operating systems like
- MS-DOS, which do not support long filenames, different
- resolutions are stored in their own directories. In this
- case the 360dpi font just described would be stored as
- <tt>cmr10.pk</tt> in a directory called <tt>360dpi</tt>
- or <tt>dpi360</tt>.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2919679"
- name="id2919679"></a>What About Errors?</h2>
- </div>
- </div>
-
- <p>Because I'm operating under the assumption that you are
- not writing your own MetaFont programs, errors<a
- id="id2919688" class="indexterm" name="id2919688"></a> are
- far less likely. Nevertheless, there are a few things that
- can go wrong.</p>
-
- <p>Figure&#160;<a href="ch11.html#fig.eight"
- title="Figure&#160;11.1.&#160;A figure eight created with MetaFont">
- Figure&#160;11.1</a> shows a simple figure eight created
- with MetaFont. The code which creates this symbol is shown
- in Example&#160;<a href="ch11.html#ex.eightcode"
- title="Example&#160;11.1.&#160;The Code for the Figure Eight">
- Example&#160;11.1</a>.</p>
-
- <div class="figure">
- <a id="fig.eight" name="fig.eight"></a>
-
- <p class="title"><b>Figure&#160;11.1.&#160;A figure eight
- created with MetaFont</b></p>
-<pre class="screen">
-8
-</pre>
- </div>
-
- <div class="example">
- <a id="ex.eightcode" name="ex.eightcode"></a>
-
- <p class="title"><b>Example&#160;11.1.&#160;The Code for
- the Figure Eight</b></p>
-<pre class="screen">
-mode_setup;
-u# := 2mm#;
-define_pixels(u);
-
-beginchar("A", 8u#, 9u#, 5u#);
- z1 = ( 0u, 0u);
- z2 = ( 8u, 0u);
- z3 = ( 1u, 8u);
- z4 = ( 7u, 8u);
- pickup pencircle scaled 1u#;
- draw z4 .. z1 .. z2 .. z3 .. cycle;
- pickup pencircle scaled 3u#;
- drawdot z1;
- drawdot z2;
- drawdot z3;
- drawdot z4;
-endchar;
-
-\end
-</pre>
- </div>
-
- <p>Let's look at some of the things that can go wrong. In
- the following examples, a unix implementation of MetaFont
- is being used. Quotation marks are used to prevent
- misinterpretation of the backslashes.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><tt>! I can't find file
- `mode=laserwriter.mf'.</tt></span></dt>
-
- <dd>
- <p>If you forget to put a backslash in front of the
- <tt>mode</tt> parameter, MetaFont thinks that mode
- specification is the name of the <tt>MF</tt> file.
- For example, <tt>mode=laserwriter</tt> is
- misinterpreted as the filename:</p>
-<pre class="screen">
-$ mf 'mode=laserwriter; \input eight'
-This is METAFONT, Version 2.71 (C version 6.1)
-! I can't find file `mode=laserwriter.mf'.
-&lt;*&gt; mode=laserwriter
- ; \input eight
-Please type another input file name:
-</pre>
- </dd>
-
- <dt><span class="term"><tt>! Value is too large
- (xxxx).</tt></span></dt>
-
- <dd>
- <p>This error occurs if some element of the image
- goes outside of the bounds allowed by MetaFont.
- Frequently, this occurs in proofing mode when the
- image is so large that it can't be rendered.<sup>[<a
- id="id2919870" name="id2919870"
- href="#ftn.id2919870">112</a>]</sup> In this example,
- MetaFont is in proofing mode because I forgot the
- \mode=laserwriter parameter on the command line:</p>
-<pre class="screen">
-$ mf '\input eight'
-This is METAFONT, Version 2.71 (C version 6.1)
-(eight.mf
-! Value is too large (4097).
-&lt;recently read&gt; ;
-
-beginchar-&gt;...rdp:=(EXPR3);w:=hround(charwd*hppp);
- h:=vround(charht*hppp);
-l.5 beginchar("A", 8u#, 9u#, 5u#)
- ;
-?
-</pre>
-
- <p>This doesn't mean that MetaFont can't render very
- large images; it just means that my design isn't
- robust enough to handle an extremely high
- resolution.</p>
- </dd>
-
- <dt><span class="term"><tt>! Curve out of
- range.</tt></span></dt>
-
- <dd>
- <p>This error is also caused by an image that is too
- large to be rendered.<sup>[<a id="id2919932"
- name="id2919932" href="#ftn.id2919932">113</a>]</sup>
- Again, MetaFont is trying to create the image at an
- extremely high resolution; it is in proofing mode
- because I forgot the \mode=laserwriter parameter on
- the command line:</p>
-<pre class="screen">
-$ mf '\input eight'
-This is METAFONT, Version 2.71 (C version 6.1)
-(eight.mf
-! Curve out of range.
-&lt;to be read again&gt;
- ;
-l.11 draw z4 .. z1 .. z2 .. z3 .. cycle;
-
-?
-</pre>
- </dd>
-
- <dt><span class="term"><tt>unknown
- string</tt></span></dt>
-
- <dd>
- <p>This is what happens if you forget the semicolon
- after the \mode parameter. In this example, MetaFont
- thinks that &#8220;<tt>laserwriter \input
- eight</tt>&#8221; is the mode, which doesn't make
- sense:</p>
-<pre class="screen">
-$ mf '\mode=laserwriter \input eight'
-This is METAFONT, Version 2.71 (C version 6.1)
-(eight.mf
-&gt;&gt; unknown string mode_name0
-! Not a string.
-&lt;to be read again&gt;
- ;
-mode_setup-&gt;...nput "&amp;mode)else:mode_name[mode]fi;
- if.unknown.mag:...
-l.1 mode_setup
- ;
-?
-</pre>
- </dd>
-
- <dt><span class="term"><tt>! Extra tokens will be
- flushed.</tt></span></dt>
-
- <dd>
- <p>Oops, another missing semicolon:</p>
-<pre class="screen">
-$ mf '\mode=laserwriter; mag=magstep(1) \input eight'
-This is METAFONT, Version 2.71 (C version 6.1)
-(eight.mf
-! Extra tokens will be flushed.
-&lt;to be read again&gt;
- warningcheck
-mode_setup-&gt;warningcheck
- :=0;if.unknown.mode:mode=proof;fi...
-l.1 mode_setup
-?
-</pre>
- </dd>
-
- <dt><span class="term">Nothing
- happens&#8230;</span></dt>
-
- <dd>
- <p>MetaFont is sitting at the asterisk prompt waiting
- for you to do something. You forgot to \input the
- font:</p>
-<pre class="screen">
-$ mf '\mode=laserwriter; eight'
-This is METAFONT, Version 2.71 (C version 6.1)
-
-*
-</pre>
- </dd>
-
- <dt><span class="term"><tt>Output written on
- eight.nnngf&#8230;</tt></span></dt>
-
- <dd>
- <p>Success! A 300dpi version of <tt>eight.mf</tt> has
- been created and stored in the file
- <tt>eight.300gf</tt>:</p>
-<pre class="screen">
-$ mf '\mode=laserwriter; \input eight'
-This is METAFONT, Version 2.71 (C version 6.1)
-(eight.mf [65] )
-Font metrics written on eight.tfm.
-Output written on eight.300gf (1 character, 1964 bytes).
-Transcript written on eight.log.
-</pre>
-
- <p>On systems that place restrictions on the length
- of a filename extension, it is abbreviated to
- <tt>eight.300</tt>. The next step is to run <span
- class="emphasis"><em>gftopk eight.300gf</em></span>.
- This will produce <tt>eight.300pk</tt>, which our DVI
- driver can use.</p>
- </dd>
- </dl>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2920144"
- name="id2920144"></a>Other Errors</h3>
- </div>
- </div>
-
- <p>The list of errors in the preceding sections is hardly
- exhaustive. For example, the gothic fonts (see
- Appendix&#160;<a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a>,
- <span class="emphasis"><em><a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a></em></span>)
- produce two more errors when rendered at low resolutions:
- <span class="emphasis"><em>! inconsistent
- equation</em></span>, caused by apparently contradictory
- statements (probably due to rounding errors) and <span
- class="emphasis"><em>{! strange path}</em></span>, caused
- by a path that does not appear to run counter-clockwise
- (again probably caused by rounding errors, these are very
- complex fonts).<sup>[<a id="id2920188" name="id2920188"
- href="#ftn.id2920188">114</a>]</sup></p>
-
- <p>Most of the other errors that are encountered can be
- ignored (the preceding examples from the gothic fonts can
- certainly be ignored---at least at 300dpi). Entering
- <b>H</b> at MetaFont's question mark prompt will describe
- the cause of the error in more detail.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2920215"
- name="id2920215"></a>Output at Very High
- Resolutions</h2>
- </div>
- </div>
-
- <p>Producing MetaFont output for very high resolution <a
- id="id2920224" class="indexterm" name="id2920224"></a>
- devices like phototypesetters is sometimes difficult. This
- will frequently require a big MetaFont for the same reasons
- that processing a large document requires a big TeX.</p>
-
- <p>It is possible to construct examples that cannot be
- rendered at very high resolutions because they are simply
- too large and complex.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2920252"
- name="id2920252"></a>Output at Very Low
- Resolutions</h2>
- </div>
- </div>
-
- <p><a id="id2920260" class="indexterm"
- name="id2920260"></a>The intricate detail of many
- characters is difficult to render at very low resolutions.
- Yet, it is sometimes desirable to produce output at low
- resolutions for on-screen previewers and dot matrix
- printers.</p>
-
- <p>Usually, errors like &#8220;<tt>strange turning
- path</tt>&#8221; that result from attempting to produce
- output at low resolutions can be ignored, but sometimes the
- resulting characters will be distorted.</p>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2919870" name="ftn.id2919870"
- href="#id2919870">112</a>]</sup> {Obtaining this error
- from <tt>eight.mf</tt> required changing unit size from
- 2mm to 5mm.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2919932" name="ftn.id2919932"
- href="#id2919932">113</a>]</sup> {Obtaining this error
- from <tt>eight.mf</tt> required changing unit size from
- 2mm to 4mm.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2920188" name="ftn.id2920188"
- href="#id2920188">114</a>]</sup> {There are very specific
- rules about which way paths must be drawn so that
- MetaFont's algorithms for filling in the character's
- outline can succeed.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;10.&#160;Online Documentation"
- href="ch10.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries"
- href="ch12.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Chapter&#160;10.&#160;Online
- Documentation&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;12.&#160;Bibliographies, Indexes, and
- Glossaries</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch12.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch12.html
deleted file mode 100644
index 99e5fde712f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch12.html
+++ /dev/null
@@ -1,1542 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;12.&#160;Bibliographies, Indexes, and
- Glossaries</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document" />
- <link rel="previous" href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont" />
- <link rel="next" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;11.&#160;Introducing MetaFont"
- href="ch11.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.bibtex"
- name="chap.bibtex"></a>Chapter&#160;12.&#160;Bibliographies,
- Indexes, and Glossaries</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>Bibliographies<a id="id2917618" class="indexterm"
- name="id2917618"></a><a id="id2917626" class="indexterm"
- name="id2917626"></a> and indexes<a id="id2917640"
- class="indexterm" name="id2917640"></a><a id="id2917647"
- class="indexterm" name="id2917647"></a> are typically
- difficult to incorporate into a document. Bibliographies have
- stringent, but varying, presentation requirements (the MLA
- wants bibliographies to look one way, the Association of
- Computing Machinery wants them another, etc.). Indexes don't
- vary that much, but they are tedious to put together.</p>
-
- <p>BibTeX provides a powerful mechanism for handling
- bibliographies and citations. <b>Tib</b> is another
- bibliography package for TeX. The <b>MakeIndex</b> program
- helps manage the construction of one or more indexes for a
- document. Glossaries are also constructed with the
- <b>MakeIndex</b> program<a id="id2917542" class="indexterm"
- name="id2917542"></a><a id="id2917549" class="indexterm"
- name="id2917549"></a>.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.indexeslooklike"
- name="sec.indexeslooklike"></a>BibTeX</h2>
- </div>
- </div>
-
- <p><a id="id2917577" class="indexterm"
- name="id2917577"></a>What's wrong with doing bibliographies
- by hand? Two things. First, it is tedious to typeset each
- bibliography entry according to the strict requirements of
- the publisher. Chances are, you'll have to look up the
- requirements each time, and you're bound to make mistakes.
- Second, no matter what field you work in, it's likely that
- you'll cite some of the same articles and books in more
- than one publication. Computers are supposed to reduce
- effort, not replicate it.</p>
-
- <p>BibTeX provides a powerful mechanism for dealing with
- bibliographies in a mechanical way, considerably reducing
- effort on your part. Rather than formatting each
- bibliography entry, you build a database of bibliography
- information<a id="id2920467" class="indexterm"
- name="id2920467"></a>. Each time you want to make a
- citation, you simply use BibTeX to build the bibliography
- from your database into your document. That's easy to do,
- as you'll see in a few minutes.</p>
-
- <p>The idea of a bibliography database is introduced in
- Appendix&#160;B of <span class="emphasis"><em>LaTeX: A
- Document Preparation System</em></span>&#160;[<a
- href="bi01.html#ll:latexbook">ll:latexbook</a>] and is
- described in more detail in <span
- class="emphasis"><em>\BibTeX{}ing</em></span>&#160;[<a
- href="bi01.html#op:btxdoc">op:btxdoc</a>] and <span
- class="emphasis"><em>Designing BibTeX
- Styles</em></span>&#160;[<a
- href="bi01.html#op:btxhak">op:btxhak</a>]. The purpose of
- this chapter is to familiarize you with the concepts of a
- bibliography database and to describe many of the freely
- available tools for manipulating databases. It is not
- intended to replace any of the preceding documents.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2920526"
- name="id2920526"></a>How BibTeX Works</h3>
- </div>
- </div>
-
- <p>The LaTeX command \cite inserts citations<a
- id="id2920539" class="indexterm" name="id2920539"></a>
- into your document.<sup>[<a id="id2920553"
- name="id2920553" href="#ftn.id2920553">115</a>]</sup> You
- use a short <span class="emphasis"><em>key</em></span><a
- id="id2920570" class="indexterm" name="id2920570"></a> to
- identify the publication you cite. For example, in this
- book, when I want to cite <span class="emphasis"><em>The
- TeXbook</em></span>&#160;[<a
- href="bi01.html#kn:texbook">kn:texbook</a>], I use the
- command <tt>FIXME:</tt>. The string <tt>kn:texbook</tt>
- is the key. When you build your bibliography database,
- you assign a key to each document in the database.</p>
-
- <p>When LaTeX processes your document, it stores
- information about the documents that you cite (including
- the key for each document) in the <tt>AUX</tt> file<a
- id="id2920623" class="indexterm" name="id2920623"></a>.
- The following commands identify how the bibliography
- should be formatted and what bibliography databases
- contain the publications you cite. LaTeX also writes this
- information to the <tt>AUX</tt> file:</p>
-<pre class="screen">
-\bibliographystyle{abbrv}
-\bibliography{texpubs}
-</pre>
-
- <p>BibTeX examines the <tt>AUX</tt> file and extracts the
- appropriate entries from the bibliography database. It
- then formats those entries according to the <span
- class="emphasis"><em>bibliography style</em></span> that
- you specify. The bibliography style (stored in a plain
- text file with the extension <tt>BST</tt>)<a
- id="id2920687" class="indexterm" name="id2920687"></a>
- tells BibTeX exactly how each entry should be formatted.
- After formatting the entries, BibTeX writes a
- <tt>BBL</tt> file<a id="id2920710" class="indexterm"
- name="id2920710"></a> that LaTeX incorporates into your
- document (at the place where the \bibliography command
- occurs) the next time you process it.</p>
-
- <p>Sometimes it seems confusing to use LaTeX to create a
- bibliography. If LaTeX keeps warning you about
- &#8220;unknown citations&#8221; for documents that you
- <span class="emphasis"><em>know</em></span> are in the
- database, try the following: run LaTeX, then BibTeX, then
- LaTeX, and then LaTeX again.</p>
-
- <p>The first time you run LaTeX, it writes the citation
- keys to the <tt>AUX</tt> file (but it doesn't know what
- publications they refer to). BibTeX writes the
- <tt>BBL</tt> file, which includes the printable,
- formatted bibliography and information about what
- publication corresponds to each citation. The second time
- you run LaTeX, it still doesn't know what publication
- each citation refers to because it hasn't seen the
- <tt>BBL</tt> file yet (bibliographies are usually at the
- end of a document). During the second pass, LaTeX writes
- the citation referents to the <tt>AUX</tt> file. Finally,
- on the third LaTeX pass, it knows what each citation
- refers to, so it can typeset the citations as well as the
- bibliography!</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2920800"
- name="id2920800"></a>Building a Bibliography
- Database</h3>
- </div>
- </div>
-
- <p>A bibliography database<a id="id2920809"
- class="indexterm" name="id2920809"></a><a id="id2920817"
- class="indexterm" name="id2920817"></a> is a plain text
- file that contains information about a collection of
- publications. Bibliography databases generally have the
- extension <tt>.bib</tt>. Example&#160;<a
- href="ch12.html#ex.bib.bibexample"
- title="Example&#160;12.1.&#160;A Sample BibTeX entry">Example&#160;12.1</a>
- is an example of a single database entry. This entry is
- from a database of TeX-related publications that I put
- together while writing this book.</p>
-
- <div class="example">
- <a id="ex.bib.bibexample" name="ex.bib.bibexample"></a>
-
- <p class="title"><b>Example&#160;12.1.&#160;A Sample
- BibTeX entry</b></p>
-<pre class="screen">
-@book{kn:texbook,
- author = "Donald E. Knuth",
- title = "The {TeX}book",
- publisher = "Addison-Wesley",
- year = 1989,
- edition = "Fifteenth",
-}
-</pre>
- </div>
-
- <p>The entry in Example&#160;<a
- href="ch12.html#ex.bib.bibexample"
- title="Example&#160;12.1.&#160;A Sample BibTeX entry">Example&#160;12.1</a>
- describes <span class="emphasis"><em>The
- {TeX}book</em></span> by Donald Knuth<a id="id2920892"
- class="indexterm" name="id2920892"></a>. The key for this
- entry is <tt>kn:texbook</tt>.</p>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>All of the keys in a BibTeX database must be unique.
- If you use multiple databases for a single document,
- all of the keys in all of the databases must be
- unique.</p>
- </div>
-
- <p>In database jargon, the bibliography database contains
- a collection of records describing publications. There
- may be several types of records in the same database.
- Each record contains several fields, some of which are
- required and some optional. The required fields vary
- according to the type of record.</p>
-
- <p>In English, this means that each entry in the database
- describes a specific type of publication (book, article,
- technical report, etc.). Every publication is described
- by its characteristics. For example, books have a title,
- an author or editor, a publisher, and a year of
- publication. Some books also have a publisher's address,
- a volume or number, a series, edition, or month of
- publication (or some combination of these elements).
- These characteristics are called <span
- class="emphasis"><em>fields</em></span>, and they are
- identified by their name.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2920948"
- name="id2920948"></a>Database entries</h4>
- </div>
- </div>
-
- <p>This is the general structure<a id="id2920957"
- class="indexterm" name="id2920957"></a><a
- id="id2920968" class="indexterm" name="id2920968"></a>
- of an entry in a bibliography database:</p>
-<pre class="screen">
-<tt>@</tt><span
-class="emphasis"><em>type</em></span><tt>{</tt><span
-class="emphasis"><em>key</em></span>,
- <span class="emphasis"><em>field1</em></span> = "<span
-class="emphasis"><em>value1</em></span>",
- <span class="emphasis"><em>field2</em></span> = "<span
-class="emphasis"><em>value2</em></span>",
- . . .
- <span class="emphasis"><em>fieldn</em></span> = "<span
-class="emphasis"><em>valuen</em></span>"
-<tt>}</tt>
-</pre>
-
- <p>Always enter complete bibliography information in
- mixed case. Never abbreviate or set field values in all
- upper or all lowercase, even if the bibliography style
- that you most frequently use specifies, for example,
- that book titles appear in uppercase or that only the
- author's first initial should appear. BibTeX will take
- care of formatting the entry according to the style. If
- you store incomplete information in the database,
- BibTeX can't work correctly if you change styles.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2921042"
- name="id2921042"></a>Entry types</h4>
- </div>
- </div>
-
- <p>Table&#160;<a href="ch12.html#tab.bib.entries"
- title="Table&#160;12.1.&#160;Types of Entries with Required and Optional Fields">
- Table&#160;12.1</a> shows the required and optional
- fields for article and book entries. Similar lists
- exist for the other standard entry types: booklet,
- conference, inbook, incollection, inproceedings,
- manual, mastersthesis, phdthesis, proceedings,
- techreport, unpublished, and a catch-all miscellaneous
- type.</p>
-
- <div class="table">
- <a id="tab.bib.entries" name="tab.bib.entries"></a>
-
- <p class="title"><b>Table&#160;12.1.&#160;Types of
- Entries with Required and Optional Fields</b></p>
-
- <table
- summary="Types of Entries with Required and Optional Fields"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Type</th>
-
- <th align="left">\bf Required Fields</th>
-
- <th align="left">\bf Optional Fields</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">article</td>
-
- <td align="left">author</td>
-
- <td align="left">month</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">journal</td>
-
- <td align="left">number</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">title</td>
-
- <td align="left">pages</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">year</td>
-
- <td align="left">volume</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">&#160;</td>
-
- <td align="left">note</td>
- </tr>
-
- <tr>
- <td align="left">book</td>
-
- <td align="left">author or editor</td>
-
- <td align="left">address</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">publisher</td>
-
- <td align="left">edition</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">title</td>
-
- <td align="left">month</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">year</td>
-
- <td align="left">volume or number</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">&#160;</td>
-
- <td align="left">series</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">&#160;</td>
-
- <td align="left">note</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>Fields that are neither required nor optional are
- ignored. Therefore, you can and should associate
- arbitrary information about a publication in its entry.
- Abstracts and keywords, for example, are two additional
- pieces of information that you might keep for some
- publications. They can be stored in <tt>abstract</tt>
- and <tt>keyword</tt> fields in each entry, even though
- it is unlikely that they will ever occur in a
- bibliography.</p>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>The types of records that are valid, and the
- required and optional fields they contain are
- determined solely by the bibliography style. There is
- nothing in the BibTeX program that makes <span
- class="emphasis"><em>book</em></span> and <span
- class="emphasis"><em>article</em></span> entries more
- legitimate than <span
- class="emphasis"><em>reptile</em></span> or <span
- class="emphasis"><em>cartoon</em></span> entries.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2921363"
- name="id2921363"></a>Abbreviations</h4>
- </div>
- </div>
-
- <p><a id="id2921371" class="indexterm"
- name="id2921371"></a>The database entry structure that
- I've shown isn't entirely accurate. In my example,
- every field has a quoted string value. The truth is,
- every value is either a quoted string or an
- abbreviation or a number. An abbreviation is created
- with the <tt>@string</tt> command. Typically,
- <tt>@string</tt> commands are placed at the top of the
- bibliography database. For example, the following
- command defines <tt>ora</tt> to be an abbreviation for
- O'Reilly &amp; Associates.</p>
-<pre class="screen">
-<tt>@string{ora = "O'Reilly &amp; Associates, Inc."}</tt>
-</pre>
-
- <p>The months of the year should always be specified
- with abbreviations so that bibliography styles can
- redefine how they appear in the bibliography (for this
- reason, three-letter abbreviations for the months are
- defined in the standard styles---you don't have to
- define them yourself). The names of journals that you
- cite frequently are also obvious candidates for
- abbreviation.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2921436"
- name="id2921436"></a>Preamble</h4>
- </div>
- </div>
-
- <p><a id="id2921443" class="indexterm"
- name="id2921443"></a>Sometimes it is helpful to define
- TeX control sequences in a bibliography database.
- BibTeX provides a <tt>@preamble</tt> entry for this
- purpose.</p>
-
- <p>Consider the following example, paraphrased from
- <span
- class="emphasis"><em>\BibTeX{}ing</em></span>&#160;[<a
- href="bi01.html#op:btxdoc">op:btxdoc</a>]: You have a
- database which contains entries for each volume of a
- two-volume set by the same author. It happens that
- Volume One has been reprinted, so it has a more recent
- date than Volume Two. The standard styles sort by
- author and then date, so as it stands, the bibliography
- would list Volume Two before Volume One.</p>
-
- <p>To correct this problem, you could specify the dates
- for Volume One as:</p>
-<pre class="screen">
-year = "{\noopsort{1990a}}1992"
-</pre>
-
- <p>and for Volume Two:</p>
-<pre class="screen">
-year = "{\noopsort{1990b}}1990"
-</pre>
-
- <p>BibTeX will sort &#8220;1990a&#8221; before
- &#8220;1990b,&#8221; so they will appear in the correct
- order, and the following definition for \noopsort will
- simply discard its argument, so nothing extra will
- appear in the bibliography:<sup>[<a id="id2921530"
- name="id2921530"
- href="#ftn.id2921530">116</a>]</sup></p>
-<pre class="screen">
-\def\noopsort#1{}
-</pre>
-
- <p>The best place to put this definition is in the
- database that uses it (so that it will always be
- present when that database is used). The
- <tt>@preamble</tt> command simply copies its argument
- to the top of the <tt>BBL</tt> file, so this definition
- at the top of the database will do exactly what we
- want:</p>
-<pre class="screen">
-@preamble{"\def\noopsort#1{}"}
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2921587"
- name="id2921587"></a>Comments</h4>
- </div>
- </div>
-
- <p><a id="id2921594" class="indexterm"
- name="id2921594"></a>Anything that does not appear
- inside a <tt>@</tt><span
- class="emphasis"><em><tt>type</tt></em></span><tt>{}</tt>
- command is a comment. However, many programs that
- manipulate bibliography databases will misplace
- comments appearing before or after an entry if the
- entries are reordered.</p>
-
- <p>BibTeX includes a <tt>@comment</tt> entry for
- backwards compatibility with older systems. Unlike TeX,
- the percent sign (\%) is <span
- class="emphasis"><em>not</em></span> a comment
- character in BibTeX.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2921649"
- name="id2921649"></a>Special characters</h4>
- </div>
- </div>
-
- <p>Inserting TeX control sequences<a id="id2921657"
- class="indexterm" name="id2921657"></a><a
- id="id2921671" class="indexterm"
- name="id2921671"></a><a id="id2921681"
- class="indexterm" name="id2921681"></a> (to form
- accented characters, for example) into a bibliography
- entry requires special care. Some styles specify that
- entries should be shifted to upper or lowercase, and
- shifting the case control sequence names would make
- them different.</p>
-
- <p>BibTeX is aware of the case sensitivity of TeX
- control sequence names and will not change them. To
- specify accents or other special characters, always
- enclose them in <tt>{</tt> and <tt>}</tt> braces. The
- same treatment should be given to portions of an
- author's name that should remain in lowercase even if
- the rest of the name is shifted to uppercase.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2921724"
- name="id2921724"></a>Bibliography Styles</h3>
- </div>
- </div>
-
- <p>BibTeX styles<a id="id2921733" class="indexterm"
- name="id2921733"></a> are really programs written in a
- simple but powerful stack-based language and interpreted
- by BibTeX.<sup>[<a id="id2921744" name="id2921744"
- href="#ftn.id2921744">117</a>]</sup> Don't confuse
- bibliography styles (<tt>BST</tt> files)<a id="id2921775"
- class="indexterm" name="id2921775"></a> with LaTeX styles
- (<tt>STY</tt> files<a id="id2921796" class="indexterm"
- name="id2921796"></a>); they are unrelated. Although a
- complete description of the BibTeX language is not
- presented here, a short example will help give you a
- sense of the language.</p>
-
- <p>Each <tt>BST</tt> file defines a number of functions.
- The highest level functions determine how each entry is
- formatted: when BibTeX needs to format a
- &#8220;book&#8221; entry, it executes the <tt>book</tt>
- function, which must be defined by the <tt>BST</tt> file
- in use or an error will result.</p>
-
- <p>Let's consider part of the task of formatting a book
- entry. These code fragments are from the standard
- bibliography style <tt>plain.bst</tt>. When the
- <tt>book</tt> function is ready to output the book title,
- it calls the <tt>format.btitle</tt> function, shown
- here:</p>
-<pre class="screen">
-FUNCTION {format.btitle}
-{ title emphasize
-}
-</pre>
-
- <p>This function places the <span
- class="emphasis"><em>title</em></span> field on top of
- the stack and calls <tt>emphasize</tt>:</p>
-<pre class="screen">
-FUNCTION {emphasize}
-{ duplicate$ empty$
- { pop$ "" }
- { "<span class="emphasis"><em>" swap$ * "</em></span>" * }
- if$
-}
-</pre>
-
- <p>This is what <tt>emphasize</tt> will do when the <span
- class="emphasis"><em>title</em></span> is not an empty
- field:</p>
-
- <div class="orderedlist">
- <ol type="1">
- <li>
- <p>Duplicate what is on the top of the stack.</p>
- </li>
-
- <li>
- <p>Test the value on the top of the stack. The
- <tt>empty$</tt> function removes the top value from
- the stack and places a boolean &#8220;true&#8221;
- value there if what it removed was an empty field,
- and a &#8220;false&#8221; value otherwise.</p>
- </li>
-
- <li>
- <p>Push <tt>{ pop$ "" }</tt> onto the stack.</p>
- </li>
-
- <li>
- <p>Push <tt>{ "&lt;emphasis&gt;" swap$ *
- "&lt;/emphasis&gt;" * }</tt> onto the stack.</p>
- </li>
-
- <li>
- <p>Test the condition. The <tt>if$</tt> function
- takes three values from the stack: a boolean value,
- something to do if that value is true, and
- something to do if that value is false. In this
- case, the title is not an empty field, so the value
- is false. The <tt>{ pop$ "" }</tt> value is
- discarded, and <tt>{ "&lt;emphasis&gt;" swap$ *
- "&lt;/emphasis&gt;" * }</tt> is evaluated.</p>
- </li>
-
- <li>
- <p>Push <tt>{\em</tt>&#160; onto the top of the
- stack.</p>
- </li>
-
- <li>
- <p>Swap the top two items on the stack. Now
- \em&#160; is below the book title on the stack.</p>
- </li>
-
- <li>
- <p>Concatenate the top two items on the stack. Now
- the top of the stack holds the value <tt>\bs
- em&#160;<i><tt>book title</tt></i></tt>.</p>
- </li>
-
- <li>
- <p>Push <tt>}</tt> onto the top of the stack.</p>
- </li>
-
- <li>
- <p>Concatenate the top two items on the stack. Now
- the top of the stack holds the value
- <tt>{\ttopenbrace\bs em&#160;<i><tt>{book
- title}</tt></i><tt>}</tt>}</tt>.</p>
- </li>
- </ol>
- </div>
-
- <p>The resulting value left on top of the stack when
- <tt>emphasize</tt> is finished is the TeX code required
- to print the book title with emphasis.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922142"
- name="id2922142"></a>Special-purpose styles</h4>
- </div>
- </div>
-
- <p>A number of styles<a id="id2922152"
- class="indexterm" name="id2922152"></a> have been
- written to allow you to develop special-purpose
- bibliographies. A few of them are listed here:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p><tt>bibunits</tt> supports multiple
- bibliographies in different sections of a single
- document.</p>
- </li>
-
- <li>
- <p><tt>chapterbib</tt> supports separate
- bibliographies in each chapter of a single
- document.</p>
- </li>
-
- <li>
- <p><tt>makebst</tt> asks a number of questions
- about the bibliography style you need and
- constructs an appropriate BibTeX style.</p>
- </li>
- </ul>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2922224"
- name="id2922224"></a>Bibliography Database Tools</h3>
- </div>
- </div>
-
- <p><a id="id2922232" class="indexterm"
- name="id2922232"></a><a id="id2922242" class="indexterm"
- name="id2922242"></a>There are a lot of programs designed
- to help you extract information from bibliography
- databases, sort the entries, build subset-bibliographies
- that contain only some of the entries from a larger
- bibliography, and enter or edit information in an
- existing or new database. A lot of these programs are
- written in unix shell<a id="id2922253" class="indexterm"
- name="id2922253"></a> script languages and rely on
- existing text-processing tools like <b>awk</b>,
- <b>sed</b>, <b>sort</b>, and <b>grep</b>. Of course, many
- of these text-processing tools have been ported to other
- operating systems. Most of the utilities written in shell
- script languages can be modified to work in other
- environments by an ambitious individual.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922304"
- name="id2922304"></a>bibsort</h4>
- </div>
- </div>
-
- <p>The <b>bibsort</b><a id="id2922318"
- class="indexterm" name="id2922318"></a> shell script
- reorders the entries in a bibliography database into
- alphabetical order by entry key name. <tt>@string</tt>
- commands are reordered by macro name. This program
- cannot deal correctly with comments that appear outside
- of an entry. These comments are always associated with
- the preceding entry, which is frequently incorrect.</p>
-
- <p>Consider carefully before you reorder the entries in
- a database. BibTeX places some restrictions on the
- available orderings. Cross references, for example,
- must appear before the entry to which they refer.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922350"
- name="id2922350"></a>biblook</h4>
- </div>
- </div>
-
- <p><b>biblook</b><a id="id2922362" class="indexterm"
- name="id2922362"></a> is an interactive program that
- searches rapidly through a bibliography database for
- key words in specified fields. Compound conditions
- (using &#8220;and&#8221; and &#8220;or&#8221;) can be
- specified. The entries located by a search can be saved
- into a separate file.</p>
-
- <p>To use <b>biblook</b>, you must preprocess the
- database with <b>bibindex</b><a id="id2922400"
- class="indexterm" name="id2922400"></a>, which builds a
- binary index of the entries. Differences in case are
- removed, TeX control sequences are stripped out, and
- non-alphanumeric characters are removed. This increases
- the likelihood of correct matches.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922415"
- name="id2922415"></a>bibclean</h4>
- </div>
- </div>
-
- <p><b>bibclean</b><a id="id2922428" class="indexterm"
- name="id2922428"></a> is a syntax checker for
- bibliography databases. Running <b>bibclean</b> before
- using <b>bibsort</b>, <b>biblook</b>, or any other
- programs described here can eliminate a lot of the
- problems these programs may encounter. Although
- bibliography databases are plain text files with a very
- loose structure, some tools are more easily confused
- than others.</p>
-
- <p><b>bibclean</b> identifies possible problems in the
- database and pretty-prints it in a standard way. The
- following formatting changes are made by
- <b>bibclean</b>:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>The structure of each database entry is made
- consistent with respect to the following
- criteria: the &#8220;@&#8221; sign that begins
- the entry type is moved into column 1; each line
- in the entry is changed to contain exactly one
- &#8220;field = value&#8221; pair; and the closing
- right brace is placed in column 1 on a line of
- its own. Additionally, outer parentheses are
- converted into braces; tabs are expanded into
- blanks; hyphens in a sequence of pages are
- converted into en-dashes; and month names are
- converted into standard abbreviations.</p>
- </li>
-
- <li>
- <p>Long string values are split at a blank and
- continued on the following line. The continuation
- lines are indented.</p>
- </li>
-
- <li>
- <p>Individual names in the author and editor
- fields are normalized. A single space is placed
- after periods that separate initials, and all
- entries are converted into &#8220;first-name
- middle-name last-name&#8221; form (instead of
- &#8220;last-name, first-name&#8221; form, for
- example).</p>
- </li>
-
- <li>
- <p>The checksums of ISBN and ISSN numbers are
- verified.</p>
- </li>
-
- <li>
- <p>Uppercase letters that appear outside of
- braces are enclosed in braces to prevent them
- from being erroneously shifted to lowercase by
- some bibliography styles.</p>
- </li>
-
- <li>
- <p>Text outside of entries is not changed.
- Entries are separated by a single blank line.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922594"
- name="id2922594"></a>citetags</h4>
- </div>
- </div>
-
- <p><a id="id2922602" class="indexterm"
- name="id2922602"></a>When documents must be transmitted
- in &#8220;source&#8221; form (meaning that the actual
- TeX files will be shipped around), it's generally
- unnecessary to include entire bibliography databases.
- In these cases, it would be more convenient to send
- only the bibliography entries that are actually
- used.</p>
-
- <p>The <b>citetags</b> program extracts the citations
- from an <tt>AUX</tt> file. This list of citations can
- be passed to the <b>citefind</b> program to build a
- small bibliography database of just the required
- entries.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922652"
- name="id2922652"></a>citefind</h4>
- </div>
- </div>
-
- <p><b>citefind</b><a id="id2922665" class="indexterm"
- name="id2922665"></a> processes a list of citations and
- a list of bibliography databases and writes out a new
- database containing just the entries required to match
- the citations present. This provides a minimal database
- that can be shipped with the document if the TeX files
- must be processed on another computer.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922681"
- name="id2922681"></a>bibextract</h4>
- </div>
- </div>
- <a id="id2922687" class="indexterm"
- name="id2922687"></a>
-
- <p>Given a list of fields and values (specified as
- regular expressions), <b>bibextract</b> creates a new
- database containing only the entries that match one or
- more of the specified values in one or more of the
- specified fields. The necessary <tt>@string</tt> and
- <tt>@preamble</tt> commands are also included in the
- new database.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922726"
- name="id2922726"></a>lookbibtex</h4>
- </div>
- </div>
-
- <p><b>lookbibtex</b><a id="id2922738" class="indexterm"
- name="id2922738"></a> offers the same features as
- <b>bibextract</b>. However, <b>lookbibtex</b> is
- written in <b>Perl</b> rather than a shell script
- language.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922771"
- name="id2922771"></a>bibdestringify</h4>
- </div>
- </div>
-
- <p>As the name implies, <b>bibdestringify</b><a
- id="id2922786" class="indexterm" name="id2922786"></a>
- replaces all <tt>@string</tt> macros in a database by
- their textual expansions.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922804"
- name="id2922804"></a>edb</h4>
- </div>
- </div>
-
- <p><b>edb</b><a id="id2922817" class="indexterm"
- name="id2922817"></a>, or the &#8220;Emacs
- Database&#8221; is a powerful database programming
- system built on top of GNU Emacs Lisp<a id="id2922831"
- class="indexterm" name="id2922831"></a>. <b>edb</b> has
- been used to write a database-editing mode for BibTeX
- databases. It can be extended to handle new entry
- types.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922854"
- name="id2922854"></a>Emacs BibTeX mode</h4>
- </div>
- </div>
-
- <p>BibTeX mode<a id="id2922863" class="indexterm"
- name="id2922863"></a><a id="id2922876"
- class="indexterm" name="id2922876"></a> is a mode for
- editing BibTeX databases in emacs. It provides some
- template expansion and alignment features, but is
- essentially a text-editing mode (as opposed to
- <b>edb</b>, which is specifically a database-entry
- editor).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922902"
- name="id2922902"></a>bibview</h4>
- </div>
- </div>
-
- <p><b>bibview</b><a id="id2922915" class="indexterm"
- name="id2922915"></a> is an X Window-based program for
- editing bibliography databases. Figure&#160;<a
- href="ch12.html#fig.bib.bibview"
- title="Figure&#160;12.1.&#160;Editing an article entry with \program{bibview}">
- Figure&#160;12.1</a> shows an example of <b>bibview</b>
- editing a database entry.</p>
-
- <div class="figure">
- <a id="fig.bib.bibview" name="fig.bib.bibview"></a>
-
- <p class="title"><b>Figure&#160;12.1.&#160;Editing an
- article entry with \program{bibview}</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>Unlike the <b>xbibtex</b> program, <b>bibview</b>
- can handle optional and ignored fields in bibliography
- entries. It does not handle new entry types.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2922989"
- name="id2922989"></a>xbibtex</h4>
- </div>
- </div>
-
- <p><b>xbibtex</b><a id="id2923002" class="indexterm"
- name="id2923002"></a> is an X Window-based program for
- creating bibliography databases. Figure&#160;<a
- href="ch12.html#fig.bib.xbibtex"
- title="Figure&#160;12.2.&#160;Editing an article entry with \program{xbibtex}">
- Figure&#160;12.2</a> shows an example of <b>xbibtex</b>
- creating a bibliography entry.</p>
-
- <div class="figure">
- <a id="fig.bib.xbibtex" name="fig.bib.xbibtex"></a>
-
- <p class="title"><b>Figure&#160;12.2.&#160;Editing an
- article entry with \program{xbibtex}</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>It does not appear that <b>xbibtex</b> can edit
- existing entries. It also does not handle unexpected
- fields or new entry types.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2923067"
- name="id2923067"></a>bibdb</h4>
- </div>
- </div>
-
- <p>The <b>bibdb</b><a id="id2923082" class="indexterm"
- name="id2923082"></a> program is an MS-DOS-based
- bibliography database editor. The screen capture in
- Figure&#160;<a href="ch12.html#fig.bib.bibdb"
- title="Figure&#160;12.3.&#160;Editing an article entry with \program{bibdb}">
- Figure&#160;12.3</a> shows an example of <b>bibdb</b>
- editing a bibliography entry. <b>bibdb</b> displays
- only fields that have values.</p>
-
- <div class="figure">
- <a id="fig.bib.bibdb" name="fig.bib.bibdb"></a>
-
- <p class="title"><b>Figure&#160;12.3.&#160;Editing an
- article entry with \program{bibdb}</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>Although it does not handle arbitrary fields,
- <b>bibdb</b> has a large selection of optional fields.
- It does not handle new entry types.</p>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2923157"
- name="id2923157"></a>Tib</h2>
- </div>
- </div>
-
- <p><b>Tib</b><a id="id2923170" class="indexterm"
- name="id2923170"></a> is another tool for maintaining
- bibliography databases. The format of a <b>Tib</b> database
- is the same as the format for the <b>troff</b> <b>refer</b>
- processor.<sup>[<a id="id2923201" name="id2923201"
- href="#ftn.id2923201">118</a>]</sup> An example entry for
- <span class="emphasis"><em>The TeXbook</em></span> is shown
- in Example&#160;<a href="ch12.html#ex.tibdb"
- title="Example&#160;12.2.&#160;A Tib style database entry">Example&#160;12.2</a>.</p>
-
- <div class="example">
- <a id="ex.tibdb" name="ex.tibdb"></a>
-
- <p class="title"><b>Example&#160;12.2.&#160;A Tib style
- database entry</b></p>
-<pre class="screen">
-
-
-
-</pre>
- </div>
-
- <p>Unlike BibTeX, which relies on the citation macros to
- format citations correctly, <b>Tib</b> actually replaces
- the citations<a id="id2923270" class="indexterm"
- name="id2923270"></a> with the appropriate information. In
- other words, <b>Tib</b>-style citations are not control
- sequences; they are just text strings. The <b>Tib</b>
- processor creates an entirely new document file that should
- be passed to TeX.</p>
-
- <p>The general format of a <b>Tib</b> citation is
- <tt>[.</tt><tt><i><tt>citation
- key(s)</tt></i></tt><tt>.]</tt>. <b>Tib</b> databases do
- not contain a key field; instead, the citation keys can
- come from any fields in the database entry (you can exclude
- some fields if you wish). The punctuation around citations
- in square brackets is adjusted by <b>Tib</b>. An alternate
- form of citation using angle brackets inserts a citation
- without adjusting any of the surrounding punctuation.</p>
-
- <p>The bibliography is inserted into your document wherever
- the string &#8220;<tt>.[]</tt>&#8221; occurs at the
- beginning of a line. Analogous to BibTeX, the format of the
- reference list is controlled by a <b>Tib</b> style. Styles
- for roughly fifteen technical journals are provided.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2923378"
- name="id2923378"></a>Making Indexes</h2>
- </div>
- </div>
-
- <p>Constructing an index<a id="id2923387" class="indexterm"
- name="id2923387"></a><a id="id2923394" class="indexterm"
- name="id2923394"></a> for a TeX document is relatively
- straightforward. First, you must identify each occurrence
- of each word or concept that you want indexed. To do this,
- you must insert \index entries into your document.<sup>[<a
- id="id2923416" name="id2923416"
- href="#ftn.id2923416">119</a>]</sup> When you format your
- document containing the index entries, an <tt>IDX</tt>
- file<a id="id2923469" class="indexterm"
- name="id2923469"></a> is created that contains all of the
- entries along with the page number where each entry
- occurred.</p>
-
- <p>The <b>MakeIndex</b><a id="id2923488" class="indexterm"
- name="id2923488"></a> program<sup>[<a id="id2923499"
- name="id2923499" href="#ftn.id2923499">120</a>]</sup> reads
- the <tt>IDX</tt> file, sorts and collates the entries, and
- writes an <tt>IND</tt> file<a id="id2923532"
- class="indexterm" name="id2923532"></a>. The
- <b>MakeIndex</b> program can also load an index style file,
- discussed in the next section.</p>
-
- <p>When LaTeX processes your document, it inserts the
- contents of the <tt>IND</tt> file into your document at the
- point where you use the \printindex control sequence.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2923569"
- name="id2923569"></a>Index Entries</h3>
- </div>
- </div>
-
- <p>Index entries<a id="id2923578" class="indexterm"
- name="id2923578"></a><a id="id2923588" class="indexterm"
- name="id2923588"></a><a id="id2923598" class="indexterm"
- name="id2923598"></a> use special characters to identify
- different types of entries (simple entries,
- multiple-level entries, see-also's, etc.). The exact
- characters used are controlled by the index style file,
- and it may be convenient to select an alternate style.
- For example, <b>MakeIndex</b> uses the double-quote
- character by default to identify literal characters in
- the index entry, but the German<a id="id2923626"
- class="indexterm" name="id2923626"></a> Babel style makes
- the literal double quote character a shortcut for the
- umlaut accent; this use makes it unavailable as the
- quotation character in index entries.</p>
-
- <p>Another point to consider when coding index entries is
- that the arguments to the index macros are expanded by
- TeX. This makes it difficult to insert some control
- sequences<a id="id2923644" class="indexterm"
- name="id2923644"></a> in an index entry (for example
- <tt><a id="id2923661" class="indexterm"
- name="id2923661"></a></tt>). In LaTeX, you can combat
- this problem by using the control sequence: <tt><a
- id="id2923682" class="indexterm"
- name="id2923682"></a></tt>.</p>
-
- <p>A complete list of the different kinds of index
- entries that can be created is included in <span
- class="emphasis"><em>{MakeIndex: An Index Processor for
- LaTeX}</em></span>&#160;[<a
- href="bi01.html#ll:makeindex">ll:makeindex</a>].</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2923830"
- name="id2923830"></a>Index Format</h2>
- </div>
- </div>
-
- <p>The format of the index is controlled by both the index
- style (which specifies whether or not headings should be
- present, what the delimiters should be, etc.) and the
- definition of several control sequences:<sup>[<a
- id="id2923841" name="id2923841"
- href="#ftn.id2923841">121</a>]</sup></p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term">\bs\texttt{theindex}</span></dt>
-
- <dd>
- <p>Controls what happens just before the index is
- printed. This sequence should establish a new page,
- set up running headers and footers, select multiple
- columns, and do whatever other global setup is
- desired.</p>
- </dd>
-
- <dt><span class="term">\bs\texttt{item}</span></dt>
-
- <dd>
- <p>Executed just before a first-level entry.</p>
- </dd>
-
- <dt><span class="term">\bs\texttt{subitem}</span></dt>
-
- <dd>
- <p>Executed just before a second-level entry.</p>
- </dd>
-
- <dt><span
- class="term">\bs\texttt{subsubitem}</span></dt>
-
- <dd>
- <p>Executed just before a third-level entry.</p>
- </dd>
-
- <dt><span
- class="term">\bs\texttt{indexspace}</span></dt>
-
- <dd>
- <p>Executed between alphabetical sections.</p>
- </dd>
-
- <dt><span
- class="term">\bs\texttt{endtheindex}</span></dt>
-
- <dd>
- <p>Controls what happens just after the index is
- printed. This sequence should undo anything that was
- started by \theindex.</p>
- </dd>
- </dl>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2923963"
- name="id2923963"></a>Special-purpose styles</h2>
- </div>
- </div>
-
- <p>A number of styles have been written to allow you to
- develop special-purpose indexes. <b>multind</b> and
- <b>index</b> are described here.</p>
-
- <p><tt>multind</tt> supports multiple indexes in a single
- document.</p>
-
- <p><tt>index</tt> is a reimplementation of the LaTeX
- indexing commands. It stores index entries in the
- <tt>AUX</tt> files so that portions of a document can be
- reformatted without losing the entire index. It also
- provides support for multiple indexes and replaces the
- <span class="emphasis"><em>makeidx</em></span> style
- option.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2924031"
- name="id2924031"></a>Making Glossaries</h2>
- </div>
- </div>
-
- <p><a id="id2924039" class="indexterm"
- name="id2924039"></a><a id="id2924046" class="indexterm"
- name="id2924046"></a>The LaTeX command \glossary can be
- used to accumulate words and concepts for a document
- glossary. The output, stored in a <tt>GLO</tt> file<a
- id="id2924076" class="indexterm" name="id2924076"></a>, is
- very similar to an <tt>IDX</tt> file<a id="id2924094"
- class="indexterm" name="id2924094"></a>. Like an index, the
- glossary file can be processed by <b>MakeIndex</b><a
- id="id2924109" class="indexterm" name="id2924109"></a> to
- produce a sorted list of terms. To produce a glossary, you
- must create an index style for the glossary. Here is a
- minimal <tt>glossary.ist</tt>:</p>
-<pre class="screen">
-keyword "\\glossaryentry"
-preamble "\n\\begin{theglossary}\n"
-postamble "\n\\end{theglossary}\n"
-</pre>
-
- <p>The output file that <b>MakeIndex</b> creates will have
- to be edited by hand, naturally, in order to incorporate
- the definitions of the entries. You will also have to
- define an appropriate glossary environment by defining the
- control sequences<a id="id2924153" class="indexterm"
- name="id2924153"></a> used to make the glossary:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span
- class="term">\bs\texttt{theglossary}</span></dt>
-
- <dd>
- <p>Controls what happens just before the glossary is
- printed. This sequence should establish a new page,
- set up running headers and footers, and do whatever
- other global setup is desired.</p>
- </dd>
-
- <dt><span class="term">\bs\texttt{item}</span></dt>
-
- <dd>
- <p>Executed just before a glossary item.</p>
- </dd>
-
- <dt><span
- class="term">\bs\texttt{endtheglossary}</span></dt>
-
- <dd>
- <p>Controls what happens just after the glossary is
- printed. This sequence should undo anything that was
- started by \theglossary.</p>
- </dd>
- </dl>
- </div>
-
- <p>Finally, you will have to \input or \include the
- glossary in your document.</p>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2920553" name="ftn.id2920553"
- href="#id2920553">115</a>]</sup> {For Plain TeX and other
- formats derived from Plain, the <tt>btxmac.tex</tt>
- macros provide these commands.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2921530" name="ftn.id2921530"
- href="#id2921530">116</a>]</sup> {This example uses Plain
- TeX syntax rather than a LaTeX <tt>\bs newcommand</tt>,
- because BibTeX databases can be used from Plain TeX as
- well as LaTeX.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2921744" name="ftn.id2921744"
- href="#id2921744">117</a>]</sup> {A complete description
- of BibTeX's programming language can be found in <span
- class="emphasis"><em>Designing BibTeX
- Styles</em></span>&#160;[<a
- href="bi01.html#op:btxhak">op:btxhak</a>].}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2923201" name="ftn.id2923201"
- href="#id2923201">118</a>]</sup> {<span
- class="emphasis"><em>refer</em></span> databases can
- reportedly be converted to and from BibTeX format.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2923416" name="ftn.id2923416"
- href="#id2923416">119</a>]</sup> {The format you use must
- also provide support for indexing. In LaTeX<a
- id="id2923420" class="indexterm" name="id2923420"></a>,
- most of the support is built in, but you must use the
- makeidx style option<a id="id2923437" class="indexterm"
- name="id2923437"></a>. In Plain TeX and other
- Plain-derived formats, input the <tt>idxmac.tex</tt>
- macros at the top of your document. The rest of this
- section assumes that you use LaTeX, although the
- principles hold for any macro package that supports
- indexing.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2923499" name="ftn.id2923499"
- href="#id2923499">120</a>]</sup> {Frequently called
- <tt>makeidx</tt> on MS-DOS systems.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2923841" name="ftn.id2923841"
- href="#id2923841">121</a>]</sup> {In LaTeX, these control
- sequences have default definitions that you may not need
- to change.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;11.&#160;Introducing MetaFont"
- href="ch11.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;11.&#160;Introducing MetaFont&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;II.&#160;Elements of a Complex Document"
- href="pt02.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">&#160;Part&#160;III.&#160;A
- Tools Overview</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch13.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch13.html
deleted file mode 100644
index 821c3409e15..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch13.html
+++ /dev/null
@@ -1,2491 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;13.&#160;Non-commercial
- Environments</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="next" href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;14.&#160;Commercial Environments"
- href="ch14.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.freetex"
- name="chap.freetex"></a>Chapter&#160;13.&#160;Non-commercial
- Environments</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p><a id="id2920434" class="indexterm"
- name="id2920434"></a>This chapter offers an overview of
- several common free and shareware TeX systems. If you notice
- any conflicts between the information in this chapter and the
- documentation that comes with the software, please consider
- the documentation to be more accurate and up-to-date. I've
- attempted to provide hints and practical suggestions, but
- software installation is largely dependent on your system
- configuration and the way you want to use TeX.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="free.web"
- name="free.web"></a>Web2C</h2>
- </div>
- </div>
-
- <p><a id="id2920341" class="indexterm"
- name="id2920341"></a><a id="id2920347" class="indexterm"
- name="id2920347"></a> The official sources for all of the
- standard TeX programs are distributed in a format known as
- \web.<sup>[<a id="id2920364" name="id2920364"
- href="#ftn.id2920364">122</a>]</sup> \web is an
- implementation of a programming style known as
- &#8220;literate programming.&#8221; One central tenet of
- literate programming is that source code and documentation
- should be written in parallel. Literate programming
- enforces this tenet by combining the two in a single file.
- \web source files contain a mixture of source code and
- documentation.</p>
-
- <p>In \web files, the documentation is written in TeX, and
- the source code is written in Pascal. (Other literate
- programming environments use different documentation and
- programming languages.) To print the documentation, a
- special preprocessor called <b>weave</b><a id="id2920395"
- class="indexterm" name="id2920395"></a> transforms the \web
- source into a TeX document that can be formatted and
- printed. Another preprocessor, called <b>tangle</b><a
- id="id2924413" class="indexterm" name="id2924413"></a>,
- transforms the \web source into a Pascal program that can
- be compiled and executed.</p>
-
- <p>In practice, it is far more likely that you have access
- to a C compiler than to a Pascal compiler. This is where
- <b>Web2C</b> comes in. <b>Web2C</b> is a special-purpose
- Pascal-to-C translator that makes it possible to compile
- and build the TeX sources in most unix environments (and
- probably many other environments as well).</p>
-
- <p>Karl Berry<a id="id2924450" class="indexterm"
- name="id2924450"></a> maintains the <b>Web2C</b>
- distribution. You can retrieve it from the CTAN archives in
- the directory <tt>systems/unix/web2c</tt>.</p>
-
- <p>Preparing to build TeX with the <b>Web2C</b>
- distribution is very straightforward. Unpack the archive
- files, read the file named <tt>README</tt>, and follow the
- instructions in the file named <tt>INSTALL</tt>. Many
- people have built TeX using these sources. If you have
- difficulty, readers of the <tt>Info-TeX</tt> mailing list<a
- id="id2924515" class="indexterm" name="id2924515"></a> or
- the <tt>comp.text.tex</tt> newsgroup<a id="id2924539"
- class="indexterm" name="id2924539"></a> will almost
- certainly be able to help.</p>
-
- <p>In my experience, there are only two parts of the
- installation that are likely to cause any difficulty:
- compiling <tt>tangleboot.c</tt> and building the X Windows
- support in MetaFont.</p>
-
- <p>Because <b>tangle</b> is written in \web, there is an
- obvious bootstrapping problem (how do you <b>tangle</b>
- <tt>tangle.web</tt> in order to compile <b>tangle</b>?).
- The <b>Web2C</b> distribution includes a small C program
- called <tt>tangleboot.c</tt><a id="id2924617"
- class="indexterm" name="id2924617"></a>, which overcomes
- this hurdle. It's possible that getting
- <tt>tangleboot.c</tt> to compile on your machine may
- require some tinkering. I had this problem on one machine
- with one release of <b>Web2C</b>. Subsequent releases of
- <b>Web2C</b> seem to have corrected this problem (in my
- case, at least).</p>
-
- <p>Compiling X Window support for MetaFont has regularly
- been a thornier problem. If you are not comfortable
- programming in C, I cannot suggest a simple way to correct
- these difficulties in the general case. (However, asking
- for help in the appropriate newsgroups is very likely to
- produce a solution for any particular problem.)</p>
-
- <p>The most common errors that I've encountered in building
- the X Windows support for MetaFont are conflicting
- prototypes and type definitions. My solution to these
- problems, inelegant though it may be, has generally been to
- &#8220;correct&#8221; or remove the offending declarations
- from the MetaFont sources. (Note: the X Window support is
- written directly in C, not \web, so it is considerably
- easier to edit.) In my experience, this has always been
- successful, but your mileage may vary.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.emtex.testinstall"
- name="sec.emtex.testinstall"></a>emTeX</h2>
- </div>
- </div>
-
- <p><a id="id2924692" class="indexterm"
- name="id2924692"></a><a id="id2924702" class="indexterm"
- name="id2924702"></a> The emTeX distribution is a very
- complete, free distribution of TeX for MS-DOS and OS/2
- systems. emTeX will run on any 80x86 processor, although
- some of the larger, faster executables require at least a
- 386. There is no single right way to install TeX, so what
- follows is only one possible installation. This
- installation uses the default directories and assumes a
- single-user environment. Installing emTeX in a network
- environment is mentioned briefly in &#8220;<span
- class="emphasis"><em><a href="ch13.html#sec.netemtex"
- title="Installing emTeX on a Network">the section called
- &#8220;Installing emTeX on a
- Network&#8221;</a></em></span>,&#8221; later in this
- chapter. Incorporating the more recent, beta test versions
- of emTeX is described in the section called \linebreak</p>
-
- <p>&#8220;<a href="ch13.html#sec.betaemtex"
- title="Environment variables">the section called
- &#8220;Environment variables&#8221;</a>.&#8221; emTeX is
- available on CTAN in the directory
- <tt>systems/msdos/emtex</tt>.</p>
-
- <p>On the whole, the installation instructions for emTeX
- are provided in the distribution. Begin by reading the
- English or German versions of the documentation provided.
- Additionally, you should read the DVI driver documentation
- at least once. (It's quite long, and you may not remember
- all of it after a single reading, but at least you'll have
- a feel for what can be done.)</p>
-
- <p>Table&#160;<a href="ch13.html#tab.emtexfilesum"
- title="Table&#160;13.1.&#160;Summary of the \protect\emTeX Distribution">
- Table&#160;13.1</a> summarizes the files in the
- distribution. The standard emTeX distribution occupies six
- high-density floppy disks. A complete installation requires
- more than 12 megabytes of storage without fonts. You must
- also get a set of fonts (available in font library format
- for emTeX) or set up automatic font generation.</p>
-
- <div class="table">
- <a id="tab.emtexfilesum" name="tab.emtexfilesum"></a>
-
- <p class="title"><b>Table&#160;13.1.&#160;Summary of the
- \protect\emTeX Distribution</b></p>
-
- <table
- summary="Summary of the \protect\emTeX Distribution"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="right" />
- <col align="right" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">&#160;</th>
-
- <th align="left">&#160;</th>
-
- <th align="right">&#160;</th>
-
- <th align="right">\multicolumn{1}{l}{\bf
- Expanded}</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left"><span>\bf File</span></td>
-
- <td align="left">\bf Abbreviated Contents</td>
-
- <td align="right">\multicolumn{1}{l}{\bf Size}</td>
-
- <td align="right">\multicolumn{1}{|l}{\bf
- Size}</td>
- </tr>
-
- <tr>
- <td align="left">\it *.eng</td>
-
- <td align="left">English documentation</td>
-
- <td align="right">125Kb</td>
-
- <td align="right">125Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it{}*.ger</td>
-
- <td align="left">German documentation</td>
-
- <td align="right">140Kb</td>
-
- <td align="right">140Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it{}*.exe</td>
-
- <td align="left">Delete, remove, pkunzip</td>
-
- <td align="right">227Kb</td>
-
- <td align="right">227Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it tex1.zip</td>
-
- <td align="left">TeX executables, <tt>TFM</tt>s,
- inputs</td>
-
- <td align="right">368Kb</td>
-
- <td align="right">645Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it tex2.zip</td>
-
- <td align="left">Plain formats, more
- <tt>TFM</tt>s</td>
-
- <td align="right">262Kb</td>
-
- <td align="right">403Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it blatex.zip</td>
-
- <td align="left">Big TeX LaTeX format</td>
-
- <td align="right">227Kb</td>
-
- <td align="right">494Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it latex1.zip</td>
-
- <td align="left">Documentation and formats</td>
-
- <td align="right">243Kb</td>
-
- <td align="right">393Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it latex2.zip</td>
-
- <td align="left">LaTeX styles and
- <tt>TFM</tt>s</td>
-
- <td align="right">233Kb</td>
-
- <td align="right">705Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it latexdoc.zip</td>
-
- <td align="left">LaTeX style documentation</td>
-
- <td align="right">110Kb</td>
-
- <td align="right">315Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it makeindx.zip</td>
-
- <td align="left"><b>MakeIndex</b></td>
-
- <td align="right">52Kb</td>
-
- <td align="right">152Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it pictex.zip</td>
-
- <td align="left">PiCTeX macros</td>
-
- <td align="right">43Kb</td>
-
- <td align="right">144Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it texware.zip</td>
-
- <td align="left"><b>texchk</b>, <b>texconv</b>,
- <b>maketcp</b>,</td>
-
- <td align="right">265Kb</td>
-
- <td align="right">433Kb</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">TeXware</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it dvidrv1.zip</td>
-
- <td align="left">Driver configuration, batch,</td>
-
- <td align="right">119Kb</td>
-
- <td align="right">370Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it</td>
-
- <td align="left">and setup files</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it dvidrv2.zip</td>
-
- <td align="left">Driver executables</td>
-
- <td align="right">345Kb</td>
-
- <td align="right">551Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it dvidrv3.zip</td>
-
- <td align="left">Preview executables</td>
-
- <td align="right">293Kb</td>
-
- <td align="right">506Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it texcad.zip</td>
-
- <td align="left">TeXCad</td>
-
- <td align="right">118Kb</td>
-
- <td align="right">236Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it bmf1.zip</td>
-
- <td align="left">Big MetaFont</td>
-
- <td align="right">261Kb</td>
-
- <td align="right">472Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it mf1.zip</td>
-
- <td align="left">MetaFont executables</td>
-
- <td align="right">245Kb</td>
-
- <td align="right">398Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it mf2.zip</td>
-
- <td align="left">MetaFont sources,</td>
-
- <td align="right">337Kb</td>
-
- <td align="right">613Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it</td>
-
- <td align="left">OS/2 executable</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it mf3.zip</td>
-
- <td align="left">MetaFont sources</td>
-
- <td align="right">273Kb</td>
-
- <td align="right">768Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it mfware1.zip</td>
-
- <td align="left"><tt>GF</tt> tools, <tt>PK</tt>
- tools</td>
-
- <td align="right">320Kb</td>
-
- <td align="right">504Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it bibtex.zip</td>
-
- <td align="left">BibTeX</td>
-
- <td align="right">117Kb</td>
-
- <td align="right">319Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it bmf2.zip</td>
-
- <td align="left">OS/2 executable,</td>
-
- <td align="right">266Kb</td>
-
- <td align="right">564Kb</td>
- </tr>
-
- <tr>
- <td align="left">&#160;</td>
-
- <td align="left">Big MetaFont bases</td>
-
- <td class="auto-generated">&#160;</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it btex1.zip</td>
-
- <td align="left">Big TeX executables</td>
-
- <td align="right">259Kb</td>
-
- <td align="right">447Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it btex2.zip</td>
-
- <td align="left">Big TeX Plain format</td>
-
- <td align="right">269Kb</td>
-
- <td align="right">533Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it emsy.zip</td>
-
- <td align="left">Special fonts from emTeX</td>
-
- <td align="right">8Kb</td>
-
- <td align="right">11Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it mfware2.zip</td>
-
- <td align="left"><b>MFjob</b>, some more
- inputs</td>
-
- <td align="right">138Kb</td>
-
- <td align="right">230Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it misc_mf.zip</td>
-
- <td align="left">Miscellaneous inputs</td>
-
- <td align="right">36Kb</td>
-
- <td align="right">130Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it pkedit.zip</td>
-
- <td align="left"><b>PKEdit</b></td>
-
- <td align="right">51Kb</td>
-
- <td align="right">97Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it dvidrvma.zip</td>
-
- <td align="left">DVI driver manual</td>
-
- <td align="right">178Kb</td>
-
- <td align="right">494Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it web.zip</td>
-
- <td align="left">\web tools</td>
-
- <td align="right">128Kb</td>
-
- <td align="right">252Kb</td>
- </tr>
-
- <tr>
- <td align="left">\it g*.zip</td>
-
- <td align="left">German versions of TeX</td>
-
- <td align="right">800Kb</td>
-
- <td align="right">1614Kb</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>For simplicity, the discussion that follows assumes that
- you have enough disk space to install the entire 12Mb
- distribution. If you can't get that much space (even
- temporarily), you can perform the steps discussed in the
- section &#8220;<a href="ch13.html#sec.emtex.smaller"
- title="Installing Fonts">the section called
- &#8220;Installing Fonts&#8221;</a>&#8221; as you
- install.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2925718"
- name="id2925718"></a>Where to Start</h3>
- </div>
- </div>
-
- <p>Begin by reading the English (<tt>*.eng</tt>) or
- German (<tt>*.ger</tt>) documentation files on the first
- disk. Where there is disagreement between this book and
- those files, believe the files---especially if a new
- version of emTeX has been released.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2925747"
- name="id2925747"></a>Unpacking the Archives</h3>
- </div>
- </div>
-
- <p>The emTeX<a id="id2925756" class="indexterm"
- name="id2925756"></a> distribution is a collection of
- <tt>ZIP</tt> files spread over six disks. You must
- install these files into your hard drive. If you have
- more than one hard disk, you may install emTeX on any
- drive you choose. Select one with more than 12Mb of free
- space, at first. You can copy the files onto another
- drive after you've deleted things that you don't
- need.</p>
-
- <p>All of the emTeX files are installed in a subdirectory
- tree rooted at <tt>emtex</tt>. If you absolutely must use
- a different subdirectory tree, unpack each archive file
- into a temporary directory and then copy the files into
- the subtree you want to use. You will have to do much
- more extensive customization of the batch files and
- configuration files before emTeX will work. That sort of
- customization isn't described here in detail.</p>
-
- <p>Make the root directory of the hard disk that you wish
- to install onto the current directory, and then use the
- <b>pkunzip</b><a id="id2925817" class="indexterm"
- name="id2925817"></a> program distributed on the first
- disk, or any later version of <b>pkunzip</b>, to unpack
- each of the archive files. You can also use the
- <b>Info-Zip</b><a id="id2925862" class="indexterm"
- name="id2925862"></a> version of <b>unzip</b> (version
- 5.0 or later) to unpack the archives. If you do not want
- the German versions of the TeX macro files, do not bother
- to unpack the <tt>lkurz.zip</tt> or <tt>g*.zip</tt> files
- on disk six.</p>
-
- <p>After you have unpacked the files, you will have a
- directory tree rooted at <tt>\bs EMTEX</tt> containing
- about 12Mb of files and the following additional
- directories: <tt>bibinput</tt>, <tt>bmfbases</tt>,
- <tt>btexfmts</tt>, <tt>doc</tt>, <tt>mfbases</tt>,
- <tt>mfinput</tt>, <tt>MFjob</tt>, <tt>remove</tt>,
- <tt>texfmts</tt>, <tt>texinput</tt>, and
- <tt>tfm</tt>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2925984"
- name="id2925984"></a>Setting Up the Environment</h3>
- </div>
- </div>
- <a id="id2925990" class="indexterm" name="id2925990"></a>
-
- <p>A lot of information about where and how things are
- installed for emTeX is stored in the \glo{environment}.
- If you are unfamiliar with the DOS or OS/2 environment,
- consult your operating system reference for more details.
- In brief, the environment<a id="id2926007"
- class="indexterm" name="id2926007"></a> is a collection
- of named strings. For example, your <tt>PATH</tt> is in
- the environment.</p>
-
- <p>The emTeX distribution includes a batch file called
- <tt>set-tex</tt><a id="id2926042" class="indexterm"
- name="id2926042"></a>, which sets all of the environment
- variables that emTeX uses. Edit this file and change all
- references to C: to the drive where you installed emTeX.
- If you installed emTeX on drive C:, you needn't change
- anything. The section &#8220;<a
- href="ch13.html#sec.emtex.basiccust"
- title="Deleting extra documentation">the section called
- &#8220;Deleting extra documentation&#8221;</a>&#8221;
- later in this chapter describes the variables used by
- emTeX in greater detail.</p>
-
- <p>If you are using MS-DOS and haven't already made the
- environment larger than its default size, you may need to
- do so in order to use emTeX. Insert the following
- command, or something like it, in your
- <tt>CONFIG.SYS</tt> file:</p>
-<pre class="screen">
-SHELL=C:\COMMAND.COM /P /E:1024
-</pre>
-
- <p>This is very system-dependent. You will have to use
- different settings if you keep <tt>COMMAND.COM</tt> in a
- subdirectory or if you use a different command
- processor.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2926107"
- name="id2926107"></a>Testing the Installation</h3>
- </div>
- </div>
-
- <p><a id="id2926114" class="indexterm"
- name="id2926114"></a>After you have set up the
- environment, make the <tt>emtex</tt> directory the
- current directory and test TeX by typing:</p>
-
- <div class="informalexample">
-<pre class="screen">
-C:\ttbackslash{}EMTEX&gt;{\bf tex}
-This is emTeX, Version 3.0 [3a] (no format preloaded)
-**{\bf \ttbackslash{}relax}
-
-*{\bf This is a test}
-
-*{\bf \ttbackslash{}bye}
-[1]
-Output written on texput.dvi (1 page, 224 bytes).
-Transcript written on texput.log.
-</pre>
- </div>
-
- <p>This will produce a small <tt>DVI</tt> file called
- <tt>texput.dvi</tt><a id="id2926173" class="indexterm"
- name="id2926173"></a>. Keep this file; you can use it in
- a few minutes to test the previewer.</p>
-
- <p>To test LaTeX, enter the command:</p>
-<pre class="screen">
-\$ <span class="bold"><b>tex &amp;lplain testpage</b></span>
-</pre>
-
- <p>See the section &#8220;<a
- href="ch03.html#sec.runtex.cmdcautions"
- title="Command-line Options">the section called
- &#8220;Command-line Options&#8221;</a>&#8221; in
- Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>,
- for an explanation of some potential problems with using
- the ampersand (&amp;) character on the command line.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.emtex.smaller"
- name="sec.emtex.smaller"></a>Installing Fonts</h3>
- </div>
- </div>
-
- <p><a id="id2926254" class="indexterm"
- name="id2926254"></a><a id="id2926267" class="indexterm"
- name="id2926267"></a>There are several sets of fonts
- available for emTeX. You should select the set that is
- appropriate for your printer. They are summarized in
- Table&#160;<a href="ch13.html#tab.emtex.fontlibs"
- title="Table&#160;13.2.&#160;Fonts Libraries Available for \protect\emTeX on CTAN">
- Table&#160;13.2</a>. The CTAN directory
- <tt>systems/msdos/emtex</tt> contains the libraries or
- disks of libraries.</p>
-
- <div class="table">
- <a id="tab.emtex.fontlibs"
- name="tab.emtex.fontlibs"></a>
-
- <p class="title"><b>Table&#160;13.2.&#160;Fonts
- Libraries Available for \protect\emTeX on CTAN</b></p>
-
- <table
- summary="Fonts Libraries Available for \protect\emTeX on CTAN"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf CTAN Directory</th>
-
- <th align="left">\bf Resolution</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it fx_\,fonts</td>
-
- <td align="left">240x216</td>
-
- <td align="left">Epson FX series printers, Tandy
- DMP-130 printer</td>
- </tr>
-
- <tr>
- <td align="left">\it fx_med_\,fonts</td>
-
- <td align="left">240x144</td>
-
- <td align="left">Epson FX series (for Windows
- drivers)</td>
- </tr>
-
- <tr>
- <td align="left">\it ito_\,fonts</td>
-
- <td align="left">160x144</td>
-
- <td align="left">C. ITOH 8510A printers</td>
- </tr>
-
- <tr>
- <td align="left">\it lj_\,fonts</td>
-
- <td align="left">300x300</td>
-
- <td align="left">300dpi Laser printers</td>
- </tr>
-
- <tr>
- <td align="left">\it p6h_\,fonts</td>
-
- <td align="left">360x360</td>
-
- <td align="left">Epson LQ series, NEC P6 \</td>
-
- <td>P7, IBM Proprinter, and Panasonic KX-P1124
- printers</td>
- </tr>
-
- <tr>
- <td align="left">\it p6m_\,fonts</td>
-
- <td align="left">360x180</td>
-
- <td align="left">Epson LQ series, NEC P6 \</td>
-
- <td>P7, IBM Proprinter, and Panasonic KX-P1124
- printers</td>
- </tr>
-
- <tr>
- <td align="left">\it p6l_\,fonts</td>
-
- <td align="left">180x180</td>
-
- <td align="left">Epson LQ series, NEC P6 \</td>
-
- <td>P7, IBM Proprinter and Panasonic KX-P1124
- printers</td>
- </tr>
-
- <tr>
- <td align="left">\it psfonts</td>
-
- <td align="left">300x300</td>
-
- <td align="left">Standard 35 PostScript
- fonts</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>Not every font set is appropriate for every model of
- the series mentioned. If your printer isn't mentioned,
- use the <b>dvidot</b><a id="id2926534" class="indexterm"
- name="id2926534"></a> program included with emTeX to
- generate an appropriate configuration file. Select the
- font set with the same resolution as your printer.</p>
-
- <p>The PostScript fonts included in the
- <tt>psfonts</tt><a id="id2926555" class="indexterm"
- name="id2926555"></a> libraries are suited primarily for
- previewing. The quality of many of the fonts is
- substandard. (They were generated from unhinted outlines
- with <b>Ghostscript</b><a id="id2926572"
- class="indexterm" name="id2926572"></a>.) A font
- substitution file is provided for 300dpi, 180dpi, and
- 360dpi printers.</p>
-
- <p>Once you have retrieved the font libraries that you
- need, unpack them (if they are in <tt>ZIP</tt> archives)
- and place the <tt>FLI</tt> files in the <tt>\bs
- TEXFONTS</tt> directory of the drive where you installed
- emTeX. The amount of disk space required depends on the
- font set that you install. It can be more than 5.5
- megabytes. The section called &#8220;<a
- href="ch13.html#sec.emtex.autofont"
- title="Running emTeX 386 in Windows">the section called
- &#8220;Running emTeX 386 in Windows&#8221;</a>,&#8221;
- later in this chapter, provides an overview of automatic
- font generation under emTeX. This can save a considerable
- amount of disk space.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2926632"
- name="id2926632"></a>Testing font installation</h4>
- </div>
- </div>
-
- <p>After you have installed a font set, you should be
- able to preview and print TeX documents. If you
- followed the instructions in &#8220;<a
- href="ch13.html#sec.emtex.testinstall"
- title="emTeX">the section called
- &#8220;emTeX&#8221;</a>,&#8221; earlier in this
- chapter, you have two <tt>DVI</tt> files in your
- <tt>\bs EMTEX</tt> directory.</p>
-
- <p>First, figure out which configuration file is
- appropriate for your installation. The table near the
- top of <tt>dvidrv.doc</tt> in the emTeX documentation
- directory should help you determine which one is
- appropriate.</p>
-
- <p>The default configuration file for previewing is the
- LaserJet configuration. If you installed the LaserJet
- fonts (<tt>lj\ttunder*.fli</tt>), you do not have to
- change the previewer. Otherwise, edit the preview batch
- file (<tt>v.bat</tt> for MS-DOS systems and
- <tt>v.cmd</tt> for OS/2 systems) and change the
- configuration file. The preview batch file looks like
- this:</p>
-<pre class="screen">
-@echo off
-dviscr @lj.cnf /ocr=1 /fl=-1
-</pre>
-
- <p>The configuration file name is <tt>lj.cnf</tt>. If,
- for example, you are using the Epson FX series printer
- fonts, you would change this to <tt>fx.cnf</tt>:</p>
-<pre class="screen">
-@echo off
-dviscr @fx.cnf /ocr=1 /fl=-1
-</pre>
-
- <p>Now type <span class="bold"><b>v texput</b></span>
- to preview the test file. Under OS/2, you should do
- this from a full-screen session, not a windowed
- session. You can type <span class="bold"><b>v
- testpage</b></span> to preview the LaTeX test page, if
- you created it.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2926788"
- name="id2926788"></a>Making emTeX Smaller</h3>
- </div>
- </div>
-
- <p><a id="id2926796" class="indexterm"
- name="id2926796"></a>The complete distribution of emTeX
- is much larger than the practical requirements. This
- section discusses the pros and cons of deleting (or at
- least archiving) parts of the emTeX distribution.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.emtex.basiccust"
- name="sec.emtex.basiccust"></a>Deleting extra
- documentation</h4>
- </div>
- </div>
-
- <p>The <tt>\bs emtex\bs doc</tt> directory contains two
- complete sets of documentation, one in English and the
- other in German. Delete the set that you do not need.
- This will save about 500Kb.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2926842"
- name="id2926842"></a>Deleting extra
- executables</h4>
- </div>
- </div>
-
- <p>There are six versions of the TeX and MetaFont
- executables in the emTeX distribution. You can probably
- delete at least four from each. Follow these
- guidelines:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>If you have a 80286 or larger processor,
- delete the non-286 versions: <tt>btex.exe</tt>,
- <tt>tex.exe</tt>, <tt>bmf.exe</tt>, and
- <tt>mf.exe</tt>.</p>
- </li>
-
- <li>
- <p>If you do not have OS/2, delete the OS/2
- versions: <tt>btexp.exe</tt>, <tt>texp.exe</tt>,
- <tt>bmfp.exe</tt>, and <tt>mfp.exe</tt>.
- Conversely, if you have OS/2 and you are
- satisfied that you will never want to run TeX or
- MetaFont under DOS or Windows, delete the
- non-OS/2 versions: <tt>btex286.exe</tt>,
- <tt>tex286.exe</tt>, <tt>bmf286.exe</tt>,
- <tt>mf286.exe</tt>, and the non-286 versions
- listed above. If you need both, you'll have to
- keep both around, of course.</p>
- </li>
-
- <li>
- <p>Finally, if disk space is at a premium and/or
- you have a fast computer, you may choose to
- delete the small versions of TeX and MetaFont.
- The small versions are faster than the big
- versions, but large or complex documents and
- fonts may require the big versions, so don't
- delete them. If you want to delete the small
- versions, delete <tt>tex.exe</tt>,
- <tt>tex286.exe</tt>, <tt>mf.exe</tt>,
- <tt>mf286.exe</tt>, <tt>texp.exe</tt>, and
- <tt>mfp.exe</tt>. In this case you must keep at
- least one of <tt>btex.exe</tt>,
- <tt>btex286.exe</tt>, and <tt>btexp.exe</tt>
- depending on your environment. Similarly, you
- must keep at least one of the big \MF{}s. If
- you've decided to delete the small versions, you
- can also delete two directories:
- <tt>emtex{\bs}mfbases</tt> and
- <tt>emtex{\bs}texfmts</tt>. These contain the
- format files and base files for the small
- versions of TeX and MetaFont.</p>
- </li>
- </ul>
- </div>
-
- <p>Suppose that you have a 80386 computer running
- MS-DOS (not OS/2) and you are willing to sacrifice the
- speed of the small versions of TeX and MetaFont. You
- would keep the <tt>btex286.exe</tt> and
- <tt>bmf286.exe</tt> executables and delete the rest
- plus the formats and bases that you don't need, saving
- 2704Kb. You can save an equivalent amount of space by
- deleting the big 80286 versions and keeping the big
- non-286 versions, or by deleting all of the non-OS/2
- versions, depending on your environment.</p>
-
- <p>Table&#160;<a href="ch13.html#tab.emtexotherex"
- title="Table&#160;13.3.&#160;Other \protect\emTeX Executables">
- Table&#160;13.3</a> summarizes the other executables in
- the emTeX distribution. This will help you decide which
- programs you need to keep. Programs that you don't feel
- you need should probably be stored in archive files,
- possibly on diskettes, in case you change your
- mind.</p>
-
- <div class="table">
- <a id="tab.emtexotherex" name="tab.emtexotherex"></a>
-
- <p class="title"><b>Table&#160;13.3.&#160;Other
- \protect\emTeX Executables</b></p>
-
- <table summary="Other \protect\emTeX Executables"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="right" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Program</th>
-
- <th align="right">\multicolumn{1}{|l|}{\bf
- Size}</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it ask.exe</td>
-
- <td align="right">6Kb</td>
-
- <td align="left">Prompts user in batch file,
- only used by gh.bat</td>
- </tr>
-
- <tr>
- <td align="left">\it bibtex.exe</td>
-
- <td align="right">94Kb</td>
-
- <td align="left">BibTeX</td>
- </tr>
-
- <tr>
- <td align="left">\it chtopx.exe</td>
-
- <td align="right">39Kb</td>
-
- <td align="left">Obsolete: converts
- <tt>CHR</tt> files to <tt>PXL</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it pxtoch.exe</td>
-
- <td align="right">40Kb</td>
-
- <td align="left">Obsolete: converts
- <tt>PXL</tt> files to <tt>CHR</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it pxtopk.exe</td>
-
- <td align="right">49Kb</td>
-
- <td align="left">Obsolete: converts
- <tt>PXL</tt> files to <tt>PK</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it dvidot.exe</td>
-
- <td align="right">129Kb</td>
-
- <td align="left">Dot matrix printer driver</td>
- </tr>
-
- <tr>
- <td align="left">\it dvihplj.exe</td>
-
- <td align="right">134Kb</td>
-
- <td align="left">HP LaserJet printer
- driver</td>
- </tr>
-
- <tr>
- <td align="left">\it makedot.exe</td>
-
- <td align="right">54Kb</td>
-
- <td align="left">Updates dot matrix printer
- parameters</td>
- </tr>
-
- <tr>
- <td align="left">\it dvimsp.exe</td>
-
- <td align="right">128Kb</td>
-
- <td align="left">Converts <tt>DVI</tt> files
- into graphic images</td>
- </tr>
-
- <tr>
- <td align="left">\it fontlib.exe</td>
-
- <td align="right">67Kb</td>
-
- <td align="left">Font library management</td>
- </tr>
-
- <tr>
- <td align="left">\it maketcp.exe</td>
-
- <td align="right">28Kb</td>
-
- <td align="left">Change the TeX code page</td>
- </tr>
-
- <tr>
- <td align="left">\it MFjob.exe</td>
-
- <td align="right">51Kb</td>
-
- <td align="left">MetaFont driver</td>
- </tr>
-
- <tr>
- <td align="left">\it pcltomsp.exe</td>
-
- <td align="right">56Kb</td>
-
- <td align="left">Converts HP LaserJet graphics
- into <tt>MSP</tt> or <tt>PCX</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it pkedit.exe</td>
-
- <td align="right">94Kb</td>
-
- <td align="left">Edits <tt>PK</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it pktopx.exe</td>
-
- <td align="right">55Kb</td>
-
- <td align="left">Converts <tt>PK</tt> files to
- <tt>PXL</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it texcad.exe</td>
-
- <td align="right">79Kb</td>
-
- <td align="left">Interactive LaTeX drawing
- tool</td>
- </tr>
-
- <tr>
- <td align="left">\it texchk.exe</td>
-
- <td align="right">49Kb</td>
-
- <td align="left">Syntax checker for LaTeX</td>
- </tr>
-
- <tr>
- <td align="left">\it texconv.exe</td>
-
- <td align="right">27Kb</td>
-
- <td align="left">Converts input files (see
- &#8220;code pages&#8221;)</td>
- </tr>
-
- <tr>
- <td align="left">\it dviscr.exe</td>
-
- <td align="right">215Kb</td>
-
- <td align="left">Previewer</td>
- </tr>
-
- <tr>
- <td align="left">\it dviscrs.exe</td>
-
- <td align="right">164Kb</td>
-
- <td align="left">Previewer for small-memory
- configurations</td>
- </tr>
-
- <tr>
- <td align="left">\it dvivik.exe</td>
-
- <td align="right">142Kb</td>
-
- <td align="left">Previewer for Viking I
- displays</td>
- </tr>
-
- <tr>
- <td align="left">\it dvitype.exe</td>
-
- <td align="right">72Kb</td>
-
- <td align="left">Texware: shows <tt>DVI</tt>
- file</td>
- </tr>
-
- <tr>
- <td align="left">\it pltotf.exe</td>
-
- <td align="right">74Kb</td>
-
- <td align="left">Texware: converts <tt>PL</tt>
- files to <tt>TFM</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it tftopl.exe</td>
-
- <td align="right">48Kb</td>
-
- <td align="left">Texware: converts <tt>TFM</tt>
- files to <tt>PL</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it gftodvi.exe</td>
-
- <td align="right">69Kb</td>
-
- <td align="left">Mfware: makes proof sheets for
- a font</td>
- </tr>
-
- <tr>
- <td align="left">\it gftopk.exe</td>
-
- <td align="right">53Kb</td>
-
- <td align="left">Mfware: converts <tt>GF</tt>
- files to <tt>PK</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it gftopxl.exe</td>
-
- <td align="right">59Kb</td>
-
- <td align="left">Mfware: converts <tt>GF</tt>
- files to <tt>PXL</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it gftype.exe</td>
-
- <td align="right">61Kb</td>
-
- <td align="left">Mfware: shows <tt>GF</tt>
- file</td>
- </tr>
-
- <tr>
- <td align="left">\it mft.exe</td>
-
- <td align="right">55Kb</td>
-
- <td align="left">Mfware: pretty-prints
- <tt>MF</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it pktogf.exe</td>
-
- <td align="right">47Kb</td>
-
- <td align="left">Mfware: converts <tt>PK</tt>
- files to <tt>GF</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it pktype.exe</td>
-
- <td align="right">45Kb</td>
-
- <td align="left">Mfware: shows <tt>PK</tt>
- file</td>
- </tr>
-
- <tr>
- <td align="left">\it makeindx.exe</td>
-
- <td align="right">102Kb</td>
-
- <td align="left">Builds indices for
- documents</td>
- </tr>
-
- <tr>
- <td align="left">\it pooltype.exe</td>
-
- <td align="right">31Kb</td>
-
- <td align="left">Web: shows contents of pool
- files</td>
- </tr>
-
- <tr>
- <td align="left">\it tangle.exe</td>
-
- <td align="right">52Kb</td>
-
- <td align="left">Web: creates compilable
- file</td>
- </tr>
-
- <tr>
- <td align="left">\it weave.exe</td>
-
- <td align="right">72Kb</td>
-
- <td align="left">Web: creates documentation
- file</td>
- </tr>
-
- <tr>
- <td align="left">\it vftovp.exe</td>
-
- <td align="right">69Kb</td>
-
- <td align="left">Virtual fonts: converts
- <tt>VF</tt> files to <tt>VPL</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it vptovf.exe</td>
-
- <td align="right">73Kb</td>
-
- <td align="left">Virtual fonts: converts
- <tt>VPL</tt> files to <tt>VF</tt> format</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>Deciding which programs to remove from the emTeX
- directory depends, to a large extent, on how you use
- TeX. If you haven't been using TeX for very long, try
- to keep as many things as you can until you get a
- better feel for what you'll be using. Save copies of
- all the programs you delete on floppy disks so that
- they are easy to get back. Here are some
- suggestions:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Delete the previewer and printer drivers that
- you don't need.</p>
- </li>
-
- <li>
- <p>Delete obsolete programs unless you know you
- need them.</p>
- </li>
-
- <li>
- <p>Delete \web programs if you'll never be
- compiling TeX yourself or reading TeX program
- source code.</p>
- </li>
-
- <li>
- <p>Delete <b>Mfware</b> programs if you won't be
- doing a lot of work with fonts. Note: keep
- <b>gftopk.exe</b> if you want to use automatic
- font generation.</p>
- </li>
-
- <li>
- <p>Delete <b>Texware</b> and <b>Virtual</b> font
- programs if you won't be working with virtual
- fonts. (You can probably delete
- <b>dvitype.exe</b>, in any case).</p>
- </li>
-
- <li>
- <p>Delete <b>bibtex.exe</b> if you won't be
- working with bibliographic databases.</p>
- </li>
-
- <li>
- <p>Delete <b>makeindx.exe</b> if you won't be
- working with indexes.</p>
- </li>
-
- <li>
- <p>Delete <b>ask.exe</b> if you won't be using
- <b>gh.bat</b>.</p>
- </li>
- </ul>
- </div>
-
- <p>Next, figure out what batch files you'll be using
- and delete (or archive) all the others. If you aren't
- using OS/2, this includes all of the <tt>*.cmd</tt>
- files.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2928261"
- name="id2928261"></a>Deleting extra printer
- drivers</h4>
- </div>
- </div>
-
- <p>Read about the <b>dvidot</b><a id="id2928276"
- class="indexterm" name="id2928276"></a> program for
- printing to a dot matrix printer, if you have one. When
- you figure out which of the <tt>DOT</tt> parameter
- files you need, delete (or archive) the rest. Follow
- these guidelines:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>If you don't have a Viking I display, delete
- <b>dvivik.exe</b>.</p>
- </li>
-
- <li>
- <p>If you don't have a laser printer, delete
- <b>dvihplj.exe</b>.</p>
- </li>
-
- <li>
- <p>Delete <b>dviscrs.exe</b> if you have enough
- memory to use <b>dviscr</b> instead. If you are
- always going to use a Windows or OS/2 previewer,
- you can delete <b>dviscr.exe</b> as well.</p>
- </li>
- </ul>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2928367"
- name="id2928367"></a>Basic Customization</h3>
- </div>
- </div>
-
- <p><a id="id2928375" class="indexterm"
- name="id2928375"></a>There are two ways to customize
- emTeX. One way is to customize the environment variables
- that emTeX uses; the other is to customize the
- configuration files that emTeX uses for previewing and
- printing (configuration files have no effect on TeX
- itself).</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="sec.betaemtex"
- name="sec.betaemtex"></a>Environment variables</h4>
- </div>
- </div>
-
- <p>There are thirteen environment variables<a
- id="id2928409" class="indexterm"
- name="id2928409"></a><a id="id2928422"
- class="indexterm" name="id2928422"></a> that emTeX
- uses. For simplicity in the following discussion,
- assume that emTeX is installed on drive C:. If it is
- not, change <span
- class="emphasis"><em>every</em></span> reference to C:
- to the drive actually in use.</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><tt>EMTEXDRV</tt><a
- id="id2928458" class="indexterm"
- name="id2928458"></a> (Not set by
- default)</span></dt>
-
- <dd>
- <p>Special note: this variable will become
- obsolete with the next release of emTeX.</p>
-
- <p>This variable tells emTeX what drive to use
- when searching for default paths. Although I
- don't recommend it, if you use entirely standard
- paths for your files, you can rely on the
- compiled-in defaults in the emTeX
- executables.<sup>[<a id="id2928486"
- name="id2928486"
- href="#ftn.id2928486">123</a>]</sup> The
- <tt>EMTEXDRV</tt> environment variable should be
- set to the single letter of the drive on which
- these paths reside. For example, if you installed
- emTeX on drive C: (in completely standard
- directories), you could set
- <tt><tt>EMTEXDRV</tt>=C</tt>.</p>
- </dd>
-
- <dt><span class="term"><tt>EMTEXDIR</tt><a
- id="id2928532" class="indexterm"
- name="id2928532"></a> (Not set by
- default)</span></dt>
-
- <dd>
- <p>Special note: this is a new variable; it will
- become available with the next release of emTeX.
- <tt>EMTEXDIR</tt> replaces <tt>EMTEXDRV</tt>.</p>
-
- <p>This variable tells emTeX what path to use
- when searching for default paths. The
- <tt>EMTEXDIR</tt> environment variable should be
- set to the root path where emTeX is installed
- (for example, <tt>C:\EMTEX</tt>).</p>
- </dd>
-
- <dt><span class="term"><tt>TEXINPUT</tt><a
- id="id2928598" class="indexterm"
- name="id2928598"></a></span></dt>
-
- <dd>
- <p>Defines the directories that emTeX uses when
- searching for TeX input files. You would
- typically leave
- <tt>C:{\bs}EMTEX{\bs}TEXINPUT</tt> in this path
- and extend it with directories of your own in
- place of <tt>C:{\bs}MYTEX</tt>.</p>
- </dd>
-
- <dt><span class="term"><tt>TEXFMT</tt><a
- id="id2928651" class="indexterm"
- name="id2928651"></a></span></dt>
-
- <dd>
- <p>Specifies where small versions of TeX look for
- format files. Typically you would leave this set
- as it is and add new format files to that
- directory. You do not have to set this variable
- if you are not using the small versions of
- TeX.</p>
- </dd>
-
- <dt><span class="term"><tt>BTEXFMT</tt><a
- id="id2928691" class="indexterm"
- name="id2928691"></a></span></dt>
-
- <dd>
- <p>Specifies where large versions of TeX look for
- format files. You will typically leave this set
- as it is and add new format files to the
- directory specified. If you do not use large
- versions of TeX, you need not set this
- variable.</p>
- </dd>
-
- <dt><span class="term"><tt>TEXTFM</tt><a
- id="id2928731" class="indexterm"
- name="id2928731"></a></span></dt>
-
- <dd>
- <p>TeX uses the directories stored in this
- variable when searching for <tt>TFM</tt> files
- for fonts used in your documents. If you install
- new fonts, you should put the <tt>TFM</tt> files
- for these fonts in their own directory and add
- the name of that directory to the <tt>TEXTFM</tt>
- path.</p>
- </dd>
-
- <dt><span class="term"><tt>MFINPUT</tt><a
- id="id2928794" class="indexterm"
- name="id2928794"></a></span></dt>
-
- <dd>
- <p>The MetaFont program looks for input files in
- this path. It is analogous to the
- <tt>TEXINPUT</tt> variable. If you add new
- MetaFont fonts to your system, for example, the
- \AmS fonts, place them in a different directory
- and add that directory to this path. If you do
- not use MetaFont, you do not need this
- variable.</p>
- </dd>
-
- <dt><span class="term"><tt>MFBAS</tt><a
- id="id2928840" class="indexterm"
- name="id2928840"></a></span></dt>
-
- <dd>
- <p>Analogous to <tt>TEXFMT</tt>. Specifies where
- small versions of MetaFont look for base files.
- If you do not use MetaFont, you do not need this
- variable.</p>
- </dd>
-
- <dt><span class="term"><tt>BMFBAS</tt><a
- id="id2928882" class="indexterm"
- name="id2928882"></a></span></dt>
-
- <dd>
- <p>Analogous to <tt>BTEXFMT</tt>. Specifies where
- large versions of MetaFont look for base files.
- If you do not use MetaFont, you do not need this
- variable.</p>
- </dd>
-
- <dt><span class="term"><tt>MFJOB</tt><a
- id="id2928924" class="indexterm"
- name="id2928924"></a></span></dt>
-
- <dd>
- <p>Specifies where <b>MFjob</b> looks for input
- files. If you are not using MetaFont or
- <b>MFjob</b> for font generation, you do not need
- this variable.</p>
- </dd>
-
- <dt><span class="term"><tt>BIBINPUT</tt><a
- id="id2928976" class="indexterm"
- name="id2928976"></a></span></dt>
-
- <dd>
- <p>Specifies where <b>bibtex</b> searches for
- bibliography database files (<tt>BIB</tt> files).
- Clearly, if you're not using BibTeX, you don't
- need <tt>BIBINPUT</tt>.</p>
- </dd>
-
- <dt><span class="term"><tt>DVIDRVINPUT</tt><a
- id="id2929034" class="indexterm"
- name="id2929034"></a></span></dt>
-
- <dd>
- <p>This tells the emTeX DVI drivers where to
- search for <tt>DVI</tt> files. In practice, I
- simply set this to &#8220;<tt>.</tt>&#8221; so
- that only the current directory is used. If you
- find it convenient to search for <tt>DVI</tt>
- files, by all means set it to an appropriate
- path. The default path includes
- <tt>C:{\bs}EMTEX{\bs}DOC</tt> so that it is easy
- to preview or print the local guide.</p>
- </dd>
-
- <dt><span class="term"><tt>DVIDRVFONTS</tt><a
- id="id2929109" class="indexterm"
- name="id2929109"></a></span></dt>
-
- <dd>
- <p>This tells the emTeX DVI drivers where to
- search for fonts. The <tt>C:{\bs}TEXFONTS</tt>
- directory is the default location for font
- libraries. If other fonts are installed, it's
- natural to include them in this path. For
- example, preview versions of the PostScript fonts
- are now available from CTAN in font library
- format. If you install those libraries in
- <tt>C:{\bs}PSFONTS</tt>, you should change the
- <tt>DVIDRVFONTS</tt> environment variable to
- include both paths.</p>
- </dd>
-
- <dt><span class="term"><tt>DVIDRVGRAPH</tt><a
- id="id2929166" class="indexterm"
- name="id2929166"></a></span></dt>
-
- <dd>
- <p>The emTeX DVI drivers can incorporate
- <tt>PCX</tt> and <tt>MSP</tt> graphics with a
- \special command. The <tt>DVIDRVGRAPH</tt>
- environment variable tells the drivers where to
- look for the graphic files. The <tt>$r</tt>
- portion of the path is replaced by the resolution
- of the image required. For example, I set this to
- <tt>C:{\bs}TEXGRAPH{\bs}GR\$r</tt> and put 300dpi
- graphic images in
- <tt>C:{\bs}TEXGRAPH{\bs}GR300</tt>, 420dpi images
- in <tt>C:{\bs}TEXGRAPH{\bs}GR420</tt>, etc. The
- default value of this variable is set so that the
- local guide will print properly.</p>
- </dd>
- </dl>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2929255"
- name="id2929255"></a>Setting up configuration
- files</h4>
- </div>
- </div>
-
- <p><a id="id2929262" class="indexterm"
- name="id2929262"></a>Configuration file options are
- described completely in the DVI driver documentation
- that accompanies emTeX. Read the English or German
- versions of <tt>dvidrv.doc</tt> carefully. The
- &#8220;out of the box&#8221; configuration is
- sufficient for most uses, but specifying a new
- configuration file is a convenient way to alter the
- default size of the page in preview mode or set up
- emTeX to print pages in &#8220;two-up&#8221; or
- &#8220;four-up&#8221; variations (for printing
- booklets, for example).</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2929307"
- name="id2929307"></a>Installing the Beta Test
- Versions of emTeX</h3>
- </div>
- </div>
-
- <p>It has been several years since the standard
- distribution of emTeX was assembled. In that time,
- several other releases have been made. These are beta
- test releases, but they are as rock-solid as the standard
- distribution. Personally, I encourage you to install the
- beta test versions, especially because they offer
- features not found in the standard release.</p>
-
- <p>The beta test versions are stored in a series of
- <tt>ZIP</tt> files at CTAN in the directory
- <tt>systems/msdos/emtex/betatest</tt>. Table&#160;<a
- href="ch13.html#tab.emtex.betasummary"
- title="Table&#160;13.4.&#160;The Beta Test Files for \protect\emTeX">
- Table&#160;13.4</a> summarizes the files in the beta test
- distribution.\footnote{As this chapter is being written,
- Eberhard Mattes\index{Mattes, Eberhard} is working on a
- new version of \emTeX. This new version will, at some
- point, replace the existing beta test files, making this
- section somewhat out of date. Use the <span
- class="emphasis"><em>READ.ME</em></span> files in the
- actual distribution as the definitive source of
- information.</p>
-
- <div class="table">
- <a id="tab.emtex.betasummary"
- name="tab.emtex.betasummary"></a>
-
- <p class="title"><b>Table&#160;13.4.&#160;The Beta Test
- Files for \protect\emTeX</b></p>
-
- <table summary="The Beta Test Files for \protect\emTeX"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf File</th>
-
- <th align="left">\bf Contents</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it btexb8.zip</td>
-
- <td align="left">Big \TeX executables</td>
- </tr>
-
- <tr>
- <td align="left">\it dvidrv_1.zip</td>
-
- <td align="left">New drivers and support
- files</td>
- </tr>
-
- <tr>
- <td align="left">\it dvispell.zip</td>
-
- <td align="left">\program{dvispell}</td>
- </tr>
-
- <tr>
- <td align="left">\it maketcp.zip</td>
-
- <td align="left">\program{maketcp}</td>
- </tr>
-
- <tr>
- <td align="left">\it mfb1.zip</td>
-
- <td align="left">\MF executables</td>
- </tr>
-
- <tr>
- <td align="left">\it MFjob11l.zip</td>
-
- <td align="left">\program{MFjob}</td>
- </tr>
-
- <tr>
- <td align="left">\it mfpm.zip</td>
-
- <td align="left">OS/2 support for \MF
- preview</td>
- </tr>
-
- <tr>
- <td align="left">\it pkeditpm.zip</td>
-
- <td align="left">OS/2 PM version of
- \program{PKEdit}</td>
- </tr>
-
- <tr>
- <td align="left">\it tex386b8.zip</td>
-
- <td align="left">386 version of \TeX</td>
- </tr>
-
- <tr>
- <td align="left">\it texb5.zip</td>
-
- <td align="left">Small \TeX executables</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>To install the beta test versions, simply unpack the
- archives into your <tt>\bs emtex</tt> directory,
- replacing any existing files with the new versions. After
- you have installed the beta test versions, you can repeat
- the space-saving steps suggested earlier in this
- chapter.</p>
-
- <p>What are the advantages of the beta test versions?</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>Automatic font generation is supported. This
- means that you do not need large font library
- files.</p>
- </li>
-
- <li>
- <p>The beta test versions are TeX version 3.141;
- the standard distribution is the slightly older
- version 3.0.</p>
- </li>
-
- <li>
- <p>The beta test distribution includes a
- 386-specific version of TeX, which is much faster
- than other versions.</p>
- </li>
-
- <li>
- <p>For OS/2 users, a Presentation Manager
- <tt>DVI</tt> previewer is provided.</p>
- </li>
- </ul>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.emtex.autofont"
- name="sec.emtex.autofont"></a>Running emTeX 386 in
- Windows</h3>
- </div>
- </div>
-
- <p><a id="id2929644" class="indexterm"
- name="id2929644"></a><a id="id2929656" class="indexterm"
- name="id2929656"></a>The 386-specific version of TeX
- provided by the beta test distributions of emTeX has some
- compelling advantages over the other TeX executables:
- it's a big TeX and it's fast. Unfortunately, it does not
- run in Windows (or some other MS-DOS environments).</p>
-
- <p>The problem is memory management. In order to be large
- and fast, the <tt>tex386</tt><a id="id2929686"
- class="indexterm" name="id2929686"></a> executable relies
- on some advanced features of the 386 (and higher)
- processors. These features are provided under MS-DOS by a
- &#8220;DOS extender.&#8221; The DOS extender<a
- id="id2929701" class="indexterm" name="id2929701"></a>
- allows MS-DOS applications to use &#8220;protected
- mode,&#8221; where they can address more than 640Kb of
- memory. There are several competing standards for
- protected mode memory management. <tt>emx</tt><a
- id="id2929728" class="indexterm" name="id2929728"></a>,
- the extender implemented in emTeX, is not compatible with
- the DPMI standard used by Microsoft Windows and some
- other MS-DOS extenders (for example, MS-DOS sessions
- under OS/2).</p>
-
- <p>Luckily, there is a freely available MS-DOS extender,
- which is compatible with both DPMI and emTeX, the RSX
- extender. Starting with version beta-11 of emTeX, the<a
- id="id2929744" class="indexterm" name="id2929744"></a> is
- very easy to use.<sup>[<a id="id2929756" name="id2929756"
- href="#ftn.id2929756">124</a>]</sup></p>
-
- <p>There are two versions of the extender: <tt>rsx</tt><a
- id="id2929798" class="indexterm" name="id2929798"></a>,
- for use in MS-DOS with DPMI extenders<a id="id2929808"
- class="indexterm" name="id2929808"></a>, and
- <tt>rsxwin</tt><a id="id2929822" class="indexterm"
- name="id2929822"></a>, for use in Windows. Both versions
- are available on the CTAN archives in the directory
- <tt>support/msdos/dpmi/rsx</tt>.</p>
-
- <p>To use the RSX extender in MS-DOS with <tt>tex386</tt>
- version beta-11 or later, simply put <tt>rsx.exe</tt>
- somewhere on your <tt>PATH</tt>. When emTeX discovers a
- DPMI extender, it will use <tt>rsx</tt> instead of
- <tt>emx</tt>.</p>
-
- <p>To use the RSX extender in Windows, you must modify
- the command line that is executed to run <tt>tex386</tt>.
- Where you currently use:</p>
-<pre class="screen">
-<span class="emphasis"><em>d:{\bs}path1\bs</em></span>tex.exe <span
-class="emphasis"><em>options</em></span>
-</pre>
-
- <p>you must now use:</p>
-<pre class="screen">
-<span
-class="emphasis"><em>d:{\bs}path2\bs</em></span>rsxwin.exe -e <span
-class="emphasis"><em>d:\bs path1\bs</em></span>tex386.exe <span
-class="emphasis"><em>options</em></span>
-</pre>
-
- <p>The <tt>rsxwin</tt> extender will set up an extender
- for emTeX and then run TeX.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2929946"
- name="id2929946"></a>Automatic Font Generation with
- emTeX</h3>
- </div>
- </div>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>Automatic font generation<a id="id2929960"
- class="indexterm" name="id2929960"></a><a
- id="id2929972" class="indexterm" name="id2929972"></a>
- is not supported by the standard distribution of emTeX.
- You must install the beta test versions to use
- automatic font generation.</p>
- </div>
-
- <p>The new versions of the emTeX DVI drivers include a
- program called <b>dvidrv</b><a id="id2930004"
- class="indexterm" name="id2930004"></a>, which handles
- automatic font generation. The <b>dvidrv</b> program runs
- the driver and if the driver indicates that fonts are
- missing, gives you the opportunity to use font
- substitution or build new fonts. The <b>MFjob</b> program
- is used to build the fonts. <b>MFjob</b> runs the
- MetaFont and <b>GFtoPK</b> to produce and install the
- necessary fonts. <b>MFjob</b> installs the <tt>PK</tt>
- files into the first directory on the font path.</p>
-
- <p>The <b>dvidrv</b> program can be replaced by a batch
- file that can select an appropriate font-rendering
- program (something other than MetaFont, for example) to
- build the necessary fonts. This feature is only available
- in the OS/2 versions of emTeX releases 1.4t and later.
- The batch file in Example&#160;<a
- href="apd.html#ex.dvidxx"
- title="Example&#160;D.3.&#160;dvidxx.btm">Example&#160;D.3</a>
- in Appendix&#160;<a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a>,
- <span class="emphasis"><em><a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a></em></span>,
- is a replacement for <b>dvidrv</b>. It uses
- <b>ps2pk</b><a id="id2930120" class="indexterm"
- name="id2930120"></a> to make <tt>PK</tt> versions of
- PostScript Type&#160;1 fonts if an appropriate
- <tt>PFB</tt> file can be found. Otherwise, it calls
- <b>MFjob</b> in the same way that <b>dvidrv</b> does.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.netemtex"
- name="sec.netemtex"></a>Installing emTeX on a
- Network</h3>
- </div>
- </div>
-
- <p>Ordinarily, emTeX does not require write access to any
- of its data files, so installation on a network<a
- id="id2930180" class="indexterm" name="id2930180"></a> is
- not a problem. The location of temporary files that must
- be writable is controlled with environment variables. If
- automatic font generation is being used, there are two
- applicable cautions.</p>
-
- <p>First, if you use the batch file approach to automatic
- font generation in order to support different rendering
- software, be aware that your batch file must handle the
- fact that multiple files may be written to the same
- directory from different users. Don't let filenames
- collide.</p>
-
- <p>Second, it is ideal if you can provide a single
- world-writable location for automatically generated
- fonts. If multiple users are working with similar
- documents, each will not need private copies of the fonts
- they require. If your networking software tracks the time
- of last file access, you can determine which files to
- delete from this global font area on a regular basis.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2930222"
- name="id2930222"></a>texas</h2>
- </div>
- </div>
-
- <p><b>texas</b><a id="id2930235" class="indexterm"
- name="id2930235"></a> is a 32-bit MS-DOS version of TeX. It
- is a big TeX. Unlike <b>tex386</b>, which comes with emTeX,
- the <b>texas</b> executable uses a royalty-free, commercial
- DOS extender. The advantage of this extender is that it can
- run under Windows and other protected-mode environments
- such as DESQview.</p>
-
- <p>Before you install <b>texas</b>, you should get a
- complete TeX system from some other location (emTeX or
- gTeX, for example). The <b>texas</b> distribution does not
- include anything other than the TeX executable and the
- MS-DOS extender---no format files, no input files,
- nothing.</p>
-
- <p>The <span class="emphasis"><em>-i</em></span> switch
- runs <b>texas</b> in iniTeX<a id="id2930301"
- class="indexterm" name="id2930301"></a> mode. Using the
- instructions from Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>,
- you should be able to build new format files for use with
- <b>texas</b> if you have another TeX distribution to work
- from.</p>
-
- <p><b>texas</b> uses the following environment <a
- id="id2930352" class="indexterm" name="id2930352"></a><a
- id="id2930362" class="indexterm" name="id2930362"></a>
- variables:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><tt>TEXINPUTS</tt></span></dt>
-
- <dd>
- <p><a id="id2930395" class="indexterm"
- name="id2930395"></a>Defines the directories that
- <b>texas</b> uses when searching for TeX input files.
- You would typically leave the defaults in this path
- and extend it with directories of your own in place
- of <tt>C:{\bs}MYTEX</tt>.</p>
- </dd>
-
- <dt><span class="term"><tt>TEXFORMATS</tt><a
- id="id2930448" class="indexterm"
- name="id2930448"></a></span></dt>
-
- <dd>
- <p>Specifies where <b>texas</b> looks for format
- files. Typically you would leave this set as is and
- add new format files to that directory.</p>
- </dd>
-
- <dt><span class="term"><tt>TEXFONTS</tt><a
- id="id2930492" class="indexterm"
- name="id2930492"></a></span></dt>
-
- <dd>
- <p>TeX uses the directories stored in this variable
- when searching for <tt>TFM</tt> files for fonts used
- in your documents. If you install new fonts, you
- should put the <tt>TFM</tt> files in their own
- directory and add the name of that directory to the
- <tt>TEXFONTS</tt> path.</p>
- </dd>
-
- <dt><span class="term"><tt>TEXPOOL</tt><a
- id="id2930555" class="indexterm"
- name="id2930555"></a></span></dt>
-
- <dd>
- <p>Specifies where <b>texas</b> looks for its pool
- file. Unless you have installed <b>texas</b> in an
- unusual way, you will not have to change this
- setting.</p>
- </dd>
-
- <dt><span class="term"><tt>DOS4GVM</tt><a
- id="id2930602" class="indexterm"
- name="id2930602"></a></span></dt>
-
- <dd>
- <p><b>texas</b> uses a DOS extender<a id="id2930630"
- class="indexterm" name="id2930630"></a> to overcome
- memory limitations under MS-DOS. If the extender runs
- out of memory, it writes parts of the memory-image
- that it is maintaining out to disk. This environment
- variable specifies where that information should be
- written. You do not usually need to change this
- setting.</p>
- </dd>
- </dl>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2930652"
- name="id2930652"></a>sbTeX</h2>
- </div>
- </div>
-
- <p>sbTeX<a id="id2930661" class="indexterm"
- name="id2930661"></a> is another MS-DOS implementation of
- TeX. The <tt>sb38tex</tt><a id="id2930680"
- class="indexterm" name="id2930680"></a> distribution
- includes TeX and iniTeX executables, <tt>TFM</tt> files for
- the Computer Modern Roman fonts, and TeX sources for the
- Plain TeX format. This is TeX version 3.141. You will have
- to get DVI drivers and other TeX tools from a different
- package.</p>
-
- <p>The <tt>sb32xet</tt><a id="id2930712" class="indexterm"
- name="id2930712"></a> distribution is \XeT version
- 3.1.<sup>[<a id="id2930721" name="id2930721"
- href="#ftn.id2930721">125</a>]</sup> The source files for
- the \XeT <tt>nailp</tt> format are included, as well as the
- supporting files for Hebrew.</p>
-
- <p>The <tt>sbmf13</tt><a id="id2930746" class="indexterm"
- name="id2930746"></a> distribution is MetaFont version
- 2.71. Only the sources for the Plain MetaFont base file are
- provided. Like the sbTeX distribution, this is a very
- minimal set of files. Only the <b>GFtoPK</b><a
- id="id2930763" class="indexterm" name="id2930763"></a>
- utility is included; all of the other MetaFont programs you
- need will have to be obtained from another package.</p>
-
- <p>The default directories for sbTeX are <tt>\bs TEX\bs
- INPUTS</tt> for input files, <tt>\bs TEX\bs FORMATS</tt>
- for format files, and <tt>{\bs TEX\bs FONTTFMS}</tt> for
- <tt>TFM</tt> files. The default drive is C:, but that can
- be changed with the <b>sb38set</b> program.</p>
-
- <p>You can also modify these paths by setting the
- <tt>TEXINPUTS</tt> environment variable<a id="id2930826"
- class="indexterm" name="id2930826"></a><a id="id2930839"
- class="indexterm" name="id2930839"></a> for input files,
- the <tt>FMTSB</tt> environment variable for format files,
- and the <tt>FONTTFMS</tt> environment variable for
- <tt>TFM</tt> files. Additionally, sbTeX uses the
- <tt>SBFTMP</tt> environment variable to determine where
- temporary files should be located if font caching is
- performed. Here is a more complete description of sbTeX's
- environment variables:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><tt>TEXINPUTS</tt></span></dt>
-
- <dd>
- <p><a id="id2930903" class="indexterm"
- name="id2930903"></a>Defines the directories that
- sbTeX uses when searching for TeX input files. You
- would typically leave the defaults in this path and
- extend it with directories of your own in place of
- <tt>C:{\bs}MYTEX</tt>.</p>
- </dd>
-
- <dt><span class="term"><tt>FMTSB</tt><a id="id2930949"
- class="indexterm" name="id2930949"></a></span></dt>
-
- <dd>
- <p>Specifies where sbTeX looks for format files.
- Typically you would leave this set as it is and add
- new format files to that directory.</p>
- </dd>
-
- <dt><span class="term"><tt>FONTTFMS</tt><a
- id="id2930987" class="indexterm"
- name="id2930987"></a></span></dt>
-
- <dd>
- <p>TeX uses the directories stored in this variable
- when searching for <tt>TFM</tt> files for fonts used
- in your documents. If you install new fonts, you
- should put the <tt>TFM</tt> files for these fonts in
- their own directory and add the name of that
- directory to the <tt>FONTTFMS</tt> path.</p>
- </dd>
-
- <dt><span class="term"><tt>SBFTMP</tt><a id="id2931046"
- class="indexterm" name="id2931046"></a></span></dt>
-
- <dd>
- <p>When font-caching is enabled, sbTeX writes cached
- information to disk when it runs out of memory. This
- environment variable specifies where that information
- should be written. You do not usually need to change
- this setting.</p>
- </dd>
- </dl>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2931076"
- name="id2931076"></a>gTeX</h2>
- </div>
- </div>
-
- <p>The gTeX<a id="id2931085" class="indexterm"
- name="id2931085"></a> package is distributed in two ways.
- One way is intended to supplement (actually, replace part
- of) the emTeX distribution. The advantage of gTeX
- executables over emTeX is that they will run under Windows.
- The 386 versions of emTeX executables will not run under
- Windows. On the other hand, although gTeX will run in an
- MS-DOS session under OS/2, only the emTeX executables will
- actually run in a native OS/2 session. The other
- distribution is a complete set of <tt>TFM</tt> files,
- source, and input files for Plain TeX, LaTeX, and AMSTeX.
- In either distribution, you must get DVI drivers and some
- ancillary programs from another complete package (like
- emTeX).</p>
-
- <p>The following programs are included in the gTeX
- distribution:</p>
-<pre class="screen">
-\begin{tabular}{lll}
-&amp;BibTeX; &amp; &lt;command&gt;GFtoPK&lt;/command&gt; &amp; &lt;command&gt;VFtoVP&lt;/command&gt; \\
-&lt;command&gt;DVItype&lt;/command&gt; &amp; &lt;command&gt;MFT&lt;/command&gt; &amp; &lt;command&gt;VPtoVF&lt;/command&gt; \\
-&lt;command&gt;DVIcopy&lt;/command&gt; &amp; &lt;command&gt;PKtoGF&lt;/command&gt; \ &amp; &lt;command&gt;MakeIndx&lt;/command&gt; \\
-&lt;command&gt;GFtoDVI&lt;/command&gt; \ &amp; &lt;command&gt;PKtype&lt;/command&gt; &amp; &amp;MF; \\[2pt]
-\multicolumn{3}{l}{\program{amSpell} (a third party spell-checker, not traditionally part of \TeX)}\\[2pt]
-\multicolumn{3}{l}{\program{MEwin} (an Emacs-like editor for Windows, also not traditionally part of \TeX)}\\
-\end{tabular}
-</pre>
-
- <p>The gTeX executables use the same environment
- variables<a id="id2931134" class="indexterm"
- name="id2931134"></a><a id="id2931160" class="indexterm"
- name="id2931160"></a> as emTeX.</p>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2920364" name="ftn.id2920364"
- href="#id2920364">122</a>]</sup> {Hence the spider on the
- cover, by the way.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2928486" name="ftn.id2928486"
- href="#id2928486">123</a>]</sup> {One of the reasons I
- don't recommend it is that it isn't easy to determine
- precisely what the compiled-in defaults are, and they may
- change without notice.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2929756" name="ftn.id2929756"
- href="#id2929756">124</a>]</sup> {Earlier versions of
- <tt>tex386.exe</tt> had the <tt>emx</tt> extender
- &#8220;bound&#8221; into the executable, which made the
- process more complicated. The <tt>emx</tt> extender had
- to be unbound before the new one could be used.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2930721" name="ftn.id2930721"
- href="#id2930721">125</a>]</sup> {\XeT is a variant of
- TeX that can typeset in both left-to-right and
- right-to-left modes.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;14.&#160;Commercial Environments"
- href="ch14.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Part&#160;III.&#160;A Tools
- Overview&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;14.&#160;Commercial Environments</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch14.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch14.html
deleted file mode 100644
index fd0de2a07ff..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch14.html
+++ /dev/null
@@ -1,866 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;14.&#160;Commercial Environments</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments" />
- <link rel="next" href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;13.&#160;Non-commercial Environments"
- href="ch13.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;15.&#160;TeX on the Macintosh"
- href="ch15.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.commercialtex"
- name="chap.commercialtex"></a>Chapter&#160;14.&#160;Commercial
- Environments</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>There are several commercial versions<a id="id2924356"
- class="indexterm" name="id2924356"></a> of TeX on the market.
- The advantage of commercial programs over free ones is that
- they provide an automated installation procedure and some
- level of technical support. There's no reason to believe that
- a commercial implementation of TeX is necessarily better than
- a free one (or vice versa, for that matter) because the
- source code for TeX is in the public domain.</p>
-
- <p>The following sections highlight several commercial
- implementations of TeX.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.com.turbo" name="sec.com.turbo"></a>µTeX by
- ArborText</h2>
- </div>
- </div>
-
- <p>ArborText<a id="id2924394" class="indexterm"
- name="id2924394"></a> sells µTeX<a id="id2924249"
- class="indexterm" name="id2924249"></a> for MS-DOS<a
- id="id2924260" class="indexterm" name="id2924260"></a>
- systems as well as an implementation of TeX for unix
- workstations. The ArborText previewer and DVI driver
- software are also available for both unix and MS-DOS
- systems. The following discussion is based on experiences
- with µTeX version 3.14B, the MS-DOS implementation of
- ArborText's TeX package.</p>
-
- <p>The µTeX package is a complete TeX implementation for
- MS-DOS. The additional utilities, <b>PLtoTF</b><a
- id="id2924296" class="indexterm" name="id2924296"></a>,
- <b>TFtoPL</b><a id="id2924310" class="indexterm"
- name="id2924310"></a>, and BibTeX<a id="id2924318"
- class="indexterm" name="id2924318"></a>, are also included.
- Neither MetaFont nor <b>MakeIndex</b> is provided.</p>
-
- <p>The default installation of µTeX creates format files
- for Plain TeX and LaTeX. To be as fast as possible, µTeX
- creates executable versions of TeX for each of these
- formats; these versions have the appropriate macro packages
- preloaded into the executable. You can use the standard
- notation to load alternate macro packages if you wish to
- save disk space.</p>
-
- <p>ArborText includes a lot of support for using TeX for
- non-English documents<a id="id2931362" class="indexterm"
- name="id2931362"></a>. Several files of international
- hyphenation patterns (English, French<a id="id2931375"
- class="indexterm" name="id2931375"></a>, German<a
- id="id2931383" class="indexterm" name="id2931383"></a>,
- Dutch<a id="id2931392" class="indexterm"
- name="id2931392"></a>, and Portuguese<a id="id2931400"
- class="indexterm" name="id2931400"></a>) are provided, as
- well as reprints of the TUGboat articles describing new
- features of TeX version 3.0 and virtual fonts.</p>
-
- <p>Designed for an MS-DOS environment having only limited
- memory, µTeX uses a swap file (potentially located in EMS<a
- id="id2931415" class="indexterm" name="id2931415"></a> or
- XMS memory<a id="id2931426" class="indexterm"
- name="id2931426"></a>) to process large files. Several
- environment variables can be used to alter the size of
- internal TeX data structures when a new format is being
- produced. In terms of big and small versions, µTeX can be
- configured either way. These choices are made when you
- create the format file however, so you will need to use
- iniTeX<a id="id2931434" class="indexterm"
- name="id2931434"></a> (included with µTeX) to make a
- &#8220;bigger&#8221; TeX.</p>
-
- <p>One of the most interesting features of µTeX is a
- quick-and-dirty preview mode provided by the TeX
- executable. After at least one page of your document has
- been processed, you can switch to a preview mode and see
- what the page looks like while TeX continues processing
- your document. This previewer is not particularly
- attractive, but it's quick and easy to use. No other
- previewer is provided. ArborText sells a fully functional
- previewer as a separate package.</p>
-
- <p>To print your documents, you must purchase or obtain a
- DVI driver separately. ArborText sells two drivers, one for
- HP LaserJet printers and another for PostScript printers.
- The µTeX distribution includes a complete set of
- <tt>TFM</tt> files, but it does not include any <tt>PK</tt>
- files.</p>
-
- <p>The ArborText previewer is summarized in the section
- called &#8220;<a href="ch09.html#sec.arb.preview"
- title="TeX Preview">the section called &#8220;TeX
- Preview&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- <span class="emphasis"><em><a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a></em></span>.
- The ArborText printer drivers, <b>DVILASER/HP</b><a
- id="id2931542" class="indexterm" name="id2931542"></a> and
- <b>DVILASER/PS</b><a id="id2931556" class="indexterm"
- name="id2931556"></a>, are described in Chapter&#160;<a
- href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a>,
- <span class="emphasis"><em><a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a></em></span>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2931589"
- name="id2931589"></a>\yyTeX</h2>
- </div>
- </div>
-
- <p>\yyTeX<a id="id2931596" class="indexterm"
- name="id2931596"></a> is an MS-DOS<a id="id2931608"
- class="indexterm" name="id2931608"></a> implementation of
- TeX by Y&amp;Y Inc.<a id="id2931622" class="indexterm"
- name="id2931622"></a> (a 386 or higher processor is
- required). \yyTeX is sold as a bundled package with
- <b>DVIWindo</b><a id="id2931641" class="indexterm"
- name="id2931641"></a>, <b>dvipsone</b><a id="id2931655"
- class="indexterm" name="id2931655"></a>,<sup>[<a
- id="id2931663" name="id2931663"
- href="#ftn.id2931663">126</a>]</sup> and a set of
- PostScript fonts (either the Computer Modern fonts, the
- Lucida Bright and Lucida New Math fonts, or the MathTime
- fonts). The installation provides format files for Plain
- TeX and LaTeX.</p>
-
- <p>\yyTeX stands out among TeX systems because of its
- memory management. Unlike other TeX systems, which exist in
- big and small versions, all of \yyTeX's memory management
- is dynamic. All of the buffers that TeX uses (main memory,
- font memory, string memory, etc.) will expand to meet the
- needs of the most complex documents you create. The memory
- required for hyphenation patterns is dynamically allocated
- as well, which means that you can construct multilingual
- formats with as many sets of hyphenation patterns as you
- need (multilingual formats are discussed in more detail in
- Chapter&#160;<a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">Chapter&#160;7</a>,
- <span class="emphasis"><em><a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">Chapter&#160;7</a></em></span>).
- The advantage of dynamic memory management over a fast and
- big TeX is that \yyTeX starts out small (big TeXs reserve a
- large fixed amount of memory even when processing simple
- jobs that don't require very much). In a multitasking
- environment where several programs are competing for
- memory, one large program can slow the progress of the
- entire system. \yyTeX's memory manager supports XMS<a
- id="id2931742" class="indexterm" name="id2931742"></a>,
- VCPI<a id="id2931757" class="indexterm"
- name="id2931757"></a>, and DPMI<a id="id2931765"
- class="indexterm" name="id2931765"></a>. This means that it
- can run under MS-DOS with any of the common memory managers
- and under Windows, Windows NT, and DOS sessions in OS/2<a
- id="id2931776" class="indexterm" name="id2931776"></a><a
- id="id2931789" class="indexterm" name="id2931789"></a><a
- id="id2931802" class="indexterm" name="id2931802"></a>.</p>
-
- <p>\yyTeX has a couple of additional strengths for
- multilingual use: it supports customizable input character
- translation and more than 255 internal font numbers. Most
- versions of TeX only support a maximum of 255 fonts in any
- single document.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2931820"
- name="id2931820"></a>Textures</h2>
- </div>
- </div>
-
- <p><b>Textures</b><a id="id2931838" class="indexterm"
- name="id2931838"></a> is a commercial implementation of TeX
- for the Macintosh<a id="id2931846" class="indexterm"
- name="id2931846"></a> distributed by Blue Sky Research<a
- id="id2931862" class="indexterm" name="id2931862"></a>. It
- is described fully in Chapter&#160;<a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a>,
- <span class="emphasis"><em><a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a></em></span>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2931894"
- name="id2931894"></a>TurboTeX</h2>
- </div>
- </div>
-
- <p>TurboTeX<a id="id2931902" class="indexterm"
- name="id2931902"></a> is a complete TeX system for MS-DOS<a
- id="id2931914" class="indexterm" name="id2931914"></a><a
- id="id2931927" class="indexterm" name="id2931927"></a> with
- full support for Microsoft Windows. It is distributed by
- the Kinch Computer Company<a id="id2931943"
- class="indexterm" name="id2931943"></a>. The programs
- included in TurboTeX version 3.0 are shown in Table&#160;<a
- href="ch14.html#tab.turbotex"
- title="Table&#160;14.1.&#160;TurboTeX Programs">Table&#160;14.1</a>.
- The <b>dvideo</b> and <b>wdviwin</b> previewers are
- described in Chapter&#160;<a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>.</p>
-
- <div class="table">
- <a id="tab.turbotex" name="tab.turbotex"></a>
-
- <p class="title"><b>Table&#160;14.1.&#160;TurboTeX
- Programs</b></p>
-
- <table summary="TurboTeX Programs" border="1">
- <colgroup>
- <col />
- <col />
- </colgroup>
-
- <thead>
- <tr>
- <th>Program</th>
-
- <th>Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td><tt>dvialw</tt><sup>[<a id="tab.turbotex.ftn"
- name="tab.turbotex.ftn"
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>A PostScript DVI driver</td>
- </tr>
-
- <tr>
- <td><tt>dvideo</tt></td>
-
- <td>An EGA (non-Windows) previewer</td>
- </tr>
-
- <tr>
- <td><tt>wdviwin</tt></td>
-
- <td>A Windows previewer</td>
- </tr>
-
- <tr>
- <td><tt>dvielq</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>An Epson LQ driver</td>
- </tr>
-
- <tr>
- <td><tt>dvieps</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>An Epson/IBM graphics printer driver</td>
- </tr>
-
- <tr>
- <td><tt>dvijep</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>An HP LaserJet PLus/Series II driver</td>
- </tr>
-
- <tr>
- <td><tt>dvijet</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>An HP LaserJet/DeskJet driver</td>
- </tr>
-
- <tr>
- <td><tt>dvilj4</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>An HP LaserJet 4 driver</td>
- </tr>
-
- <tr>
- <td><tt>initex</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>iniTeX for building new format files</td>
- </tr>
-
- <tr>
- <td><tt>latex</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>TeX with the LaTeX format preloaded</td>
- </tr>
-
- <tr>
- <td><tt>tex</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>TeX with the Plain format preloaded</td>
- </tr>
-
- <tr>
- <td><tt>texidx</tt></td>
-
- <td>The GNU TeX indexing program</td>
- </tr>
-
- <tr>
- <td><tt>tif2hp</tt></td>
-
- <td>Converts TIFF bitmapped graphics to HP LaserJet
- bitmaps</td>
- </tr>
-
- <tr>
- <td><tt>virtex</tt><sup>[<a
- href="#ftn.tab.turbotex.ftn">a</a>]</sup></td>
-
- <td>TeX with no format preloaded</td>
- </tr>
- </tbody>
-
- <tbody class="footnotes">
- <tr>
- <td colspan="2">
- <div class="footnote">
- <p><sup>[<a id="ftn.tab.turbotex.ftn"
- name="ftn.tab.turbotex.ftn"
- href="#tab.turbotex.ftn">a</a>]</sup> Windows
- version included.</p>
- </div>
- </td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>The Microsoft Windows version of TurboTeX is a superset
- of the DOS version (you must install both, but you can
- delete the non-Windows executable programs that have
- Windows versions, if you wish).</p>
-
- <p>TurboTeX includes a complete MetaFont distribution. In
- addition to the programs shown in Table&#160;<a
- href="ch14.html#tab.turbomf"
- title="Table&#160;14.2.&#160;Turbo\protect\TeX \protect\MF Programs">
- Table&#160;14.2</a>, the complete sources for the Computer
- Modern, LaTeX, and \AmS-fonts are also provided.</p>
-
- <div class="table">
- <a id="tab.turbomf" name="tab.turbomf"></a>
-
- <p class="title">
- <b>Table&#160;14.2.&#160;Turbo\protect\TeX \protect\MF
- Programs</b></p>
-
- <table summary="Turbo\protect\TeX \protect\MF Programs"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Program</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it gftodvi\x</td>
-
- <td align="left">Creates proof sheets of MetaFont
- characters</td>
- </tr>
-
- <tr>
- <td align="left">\it inimf</td>
-
- <td align="left">MetaFont with no base file
- preloaded</td>
- </tr>
-
- <tr>
- <td align="left">\it mfscript</td>
-
- <td align="left">A script generator (for building
- multiple fonts)</td>
- </tr>
-
- <tr>
- <td align="left">\it mfcga</td>
-
- <td align="left">MetaFont for CGA displays</td>
- </tr>
-
- <tr>
- <td align="left">\it mfhga</td>
-
- <td align="left">MetaFont for Hercules
- displays</td>
- </tr>
-
- <tr>
- <td align="left">\it gftopk\x</td>
-
- <td align="left">Converts <tt>GF</tt> files to
- <tt>PK</tt> files</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>At the time of this writing, a new version of TurboTeX
- is actively being developed. Unfortunately, it was not
- available for review in time for this edition of <span
- class="emphasis"><em>Making TeX Work</em></span>. The Kinch
- Computer Company claims that the next release will include
- a big TeX running under Windows 3.1/Win32s and Windows NT
- as a native, protected-mode 32-bit application. A new
- Windows previewer will also be available, and it takes
- advantage of Windows &#8220;multiple document
- interface&#8221; to preview multiple documents in the same
- session. Kinch will also provide a set of the standard
- Computer Modern Fonts in TrueType and Type 1 formats.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="sec.pctex"
- name="sec.pctex"></a>PCTeX</h2>
- </div>
- </div>
-
- <p>PCTeX<a id="id2932539" class="indexterm"
- name="id2932539"></a> is a complete TeX system for MS-DOS<a
- id="id2932551" class="indexterm" name="id2932551"></a>
- distributed by Personal TeX, Inc.<a id="id2932565"
- class="indexterm" name="id2932565"></a> It is one of two
- offerings from PTI. The version for Windows is described
- later in this chapter.</p>
-
- <p>PCTeX is sold in two configurations. The PCTeX Starter
- System includes the latest releases of PCTeX and
- PCTeX/386<a id="id2932582" class="indexterm"
- name="id2932582"></a>, <b>PTI View</b><a id="id2932607"
- class="indexterm" name="id2932607"></a> (for previewing),
- one printer driver with the appropriate Computer Modern
- fonts in <tt>PK</tt> format, <span
- class="emphasis"><em>LaTeX For
- Everyone</em></span>&#160;[<a
- href="bi01.html#jh:latexforeveryone">jh:latexforeveryone</a>],
- and the sources for Plain TeX, LaTeX, and AMSTeX. The PCTeX
- Laser System includes Big PCTeX/386, LaserJet, LaserJet 4,
- PostScript and DeskJet printer drivers (along with a
- complete set of Computer Modern fonts in <tt>PK</tt> format
- at 300dpi and 600dpi), and the <span
- class="emphasis"><em>PC TeX Manual</em></span>, in addition
- to everything contained in the Starter System.</p>
-
- <p>The discussion that follows is based on experiences with
- the PCTeX Starter System with PCTeX version 3.14 and the
- <b>PTI Laser/HP</b> DVI driver.</p>
-
- <p>In addition to the TeX executables and macro packages
- mentioned above, PCTeX includes these standard TeX
- utilities: BibTeX<a id="id2932675" class="indexterm"
- name="id2932675"></a>, <b>PLtoTF</b><a id="id2932694"
- class="indexterm" name="id2932694"></a>, <b>TFtoPL</b><a
- id="id2932708" class="indexterm" name="id2932708"></a>,
- <b>PXtoPK</b><a id="id2932722" class="indexterm"
- name="id2932722"></a>, and <b>PKtoPX</b><a id="id2932735"
- class="indexterm" name="id2932735"></a>. It does not
- include any of the other standard utilities or the
- <b>MakeIndex</b> processor. MetaFont is available as a
- separate package (although it is being discontinued, so it
- may not be available for long).</p>
-
- <p>Several additional features make PCTeX an attractive
- commercial alternative:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>It uses a text-based &#8220;menu system&#8221; for
- processing documents. This program makes the
- edit/format/preview cycle a simple matter of
- selecting the appropriate menu item. Figure&#160;<a
- href="ch14.html#fig.pcmenu"
- title="Figure&#160;14.1.&#160;The PCTeX menu system">Figure&#160;14.1</a>
- shows this system in use.</p>
-
- <div class="figure">
- <a id="fig.pcmenu" name="fig.pcmenu"></a>
-
- <p class="title"><b>Figure&#160;14.1.&#160;The
- PCTeX menu system</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
- </li>
-
- <li>
- <p>Support is provided for Bitstream fonts<a
- id="id2932819" class="indexterm"
- name="id2932819"></a>. Bitstream<a id="id2932830"
- class="indexterm" name="id2932830"></a> is a vendor
- of high-quality scalable typefaces. The utilities
- included with PCTeX allow you to create <tt>TFM</tt>
- and <tt>PK</tt> files from Bitstream compressed
- outline fonts.</p>
- </li>
-
- <li>
- <p>If you prepare multilingual documents, you'll
- appreciate the attention they receive in the PCTeX
- documentation. Although the ability to compose
- multilingual documents is really a feature of TeX
- version 3, not PCTeX in particular, PTI provides
- step-by-step instructions for building a multilingual
- format file. Support files for English, French<a
- id="id2932869" class="indexterm"
- name="id2932869"></a>, and Spanish<a id="id2932885"
- class="indexterm" name="id2932885"></a> are
- included.</p>
- </li>
- </ul>
- </div>
-
- <p>PTI's previewer, <b>PTI View</b>, is described in
- Chapter&#160;<a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- <span class="emphasis"><em><a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a></em></span>.
- The <b>PTI Laser/HP</b> and <b>PTI Laser/PS</b> printer
- drivers are discussed in Chapter&#160;<a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a>,
- <span class="emphasis"><em><a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a></em></span>.
- Drivers for DeskJet and Epson printers are also
- available.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.pctexforwin" name="sec.pctexforwin"></a>PCTeX
- For Windows</h2>
- </div>
- </div>
-
- <p>PCTeX For Windows<a id="id2932979" class="indexterm"
- name="id2932979"></a><a id="id2932991" class="indexterm"
- name="id2932991"></a> is a new offering from Personal TeX,
- Inc.<a id="id2933006" class="indexterm"
- name="id2933006"></a> PCTeX For Windows is a superset of
- Personal TeX's MS-DOS version of PCTeX.</p>
-
- <p>This version of PCTeX is an integrated system with a
- built-in editor (with complete on-line help), previewer,
- and push-button access to PCTeX for composing your
- documents. Figure&#160;<a href="ch14.html#fig.wpctex"
- title="Figure&#160;14.2.&#160;PCTeX For Windows editing and previewing a LaTeX document">
- Figure&#160;14.2</a> shows PCTeX For Windows in action.</p>
-
- <div class="figure">
- <a id="fig.wpctex" name="fig.wpctex"></a>
-
- <p class="title"><b>Figure&#160;14.2.&#160;PCTeX For
- Windows editing and previewing a LaTeX document</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p><b>PCTeX For Windows</b> includes a complete set of
- Computer Modern and \AmS fonts in scalable TrueType format.
- This allows PCTeX to print directly to any printer (or
- other device) supported by Microsoft Windows. To provide
- better access to other TrueType fonts that you may have
- installed, PCTeX includes a <tt>TFM</tt> generator for
- TrueType fonts. This generator is shown in Figure&#160;<a
- href="ch14.html#fig.wpctextttotf"
- title="Figure&#160;14.3.&#160;PCTeX For Windows TrueType font metric builder">
- Figure&#160;14.3</a>.</p>
-
- <div class="figure">
- <a id="fig.wpctextttotf" name="fig.wpctextttotf"></a>
-
- <p class="title"><b>Figure&#160;14.3.&#160;PCTeX For
- Windows TrueType font metric builder</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>Except for the <b>PXtoPK</b> and <b>PKtoPX</b>
- utilities, <b>PCTeX For Windows</b> has all of the features
- of the MS-DOS version of PCTeX.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2933148"
- name="id2933148"></a>Scientific Word</h2>
- </div>
- </div>
-
- <p><b>Scientific Word</b><a id="id2933161"
- class="indexterm" name="id2933161"></a>, a commercial
- package from TCI Software Research<a id="id2933174"
- class="indexterm" name="id2933174"></a>, bridges the gap
- between TeX and word processing by providing a more or less
- WYSIWYG interface on top of TeX. <b>Scientific Word</b>
- requires Microsoft Windows<a id="id2933192"
- class="indexterm" name="id2933192"></a>. Figure&#160;<a
- href="ch14.html#fig.sciword"
- title="Figure&#160;14.4.&#160;Editing a document with Scientific Word ">
- Figure&#160;14.4</a> shows a sample document being edited
- by <b>Scientific Word</b>.</p>
-
- <div class="figure">
- <a id="fig.sciword" name="fig.sciword"></a>
-
- <p class="title"><b>Figure&#160;14.4.&#160;Editing a
- document with Scientific Word</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p><b>Scientific Word</b> is a powerful program that might
- prove to be invaluable in some circumstances. An ideal
- candidate for <b>Scientific Word</b> is someone with little
- or no desire to learn TeX, but who wants professional
- quality output for documents containing a lot of
- mathematics. <b>Scientific Word</b> is not simply a fast,
- interactive previewer; it really is a visual editor that
- produces TeX code behind the scenes. You enter document
- elements (even complex elements like mathematics) in an
- interactive push-button fashion, and <b>Scientific Word</b>
- translates it into the appropriate LaTeX input. This is
- very different from Blue Sky Research's <b>Textures</b>
- where the user types in TeX but has nearly instantaneous
- feedback.</p>
-
- <p>Unfortunately, the complexity of TeX vastly exceeds
- <b>Scientific Word's</b> ability to act as a visual editor,
- and this leads to a number of potentially confusing
- discrepancies. For example, in a TeX document, the
- \parindent and \parskip control sequences control the
- indentation of the first line of a paragraph and the
- distance between paragraphs. In <b>Scientific Word</b>, the
- on-screen appearance of the document is controlled
- separately. This difference is apparent in Figure&#160;<a
- href="ch14.html#fig.sciword"
- title="Figure&#160;14.4.&#160;Editing a document with Scientific Word ">
- Figure&#160;14.4</a>, where the paragraphs appear to be
- indented with no additional space between them, and
- Figure&#160;<a href="ch14.html#fig.commercial.swpreview"
- title="Figure&#160;14.5.&#160;Preview of the Scientific Word document shown in Figure ">
- Figure&#160;14.5</a> (the same document shown in the
- previewer) where the paragraphs are not indented but have
- additional space between them.</p>
-
- <p>These discrepancies arise because <b>Scientific Word</b>
- was designed with the same philosophy as LaTeX: separation
- of content and form. The purpose of the <b>Scientific
- Word</b> editor is to allow you to organize your thoughts
- and perfect the content of your document. It is the job of
- LaTeX, in conjunction with the document style options that
- you select, to perfect the appearance of your document. The
- display shown in Figure&#160;<a
- href="ch14.html#fig.sciword"
- title="Figure&#160;14.4.&#160;Editing a document with Scientific Word ">
- Figure&#160;14.4</a> is not incorrect in any way, it just
- isn't WYSIWYG. TCI Research claims that &#8220;by going
- beyond WYSIWYG, <b>Scientific Word</b> allows you to focus
- on the creative process&#160;$&#8230;$ and not the layout
- commands necessary to typeset [your document].&#8221;</p>
-
- <div class="figure">
- <a id="fig.commercial.swpreview"
- name="fig.commercial.swpreview"></a>
-
- <p class="title"><b>Figure&#160;14.5.&#160;Preview of the
- Scientific Word document shown in Figure <a
- href="ch14.html#fig.sciword"
- title="Figure&#160;14.4.&#160;Editing a document with Scientific Word ">
- Figure&#160;14.4</a></b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>When <b>Scientific Word</b> encounters TeX code that it
- does not understand, it leaves a labelled grey box in the
- display (you can see two such boxes above the chapter title
- &#8220;Unsolved Problems&#8221; in Figure&#160;<a
- href="ch14.html#fig.sciword"
- title="Figure&#160;14.4.&#160;Editing a document with Scientific Word ">
- Figure&#160;14.4</a>).<sup>[<a id="id2933466"
- name="id2933466" href="#ftn.id2933466">127</a>]</sup> This
- means that you can edit all of the TeX code in your
- document from within <b>Scientific Word</b>, and small
- amounts of customization do not require abandoning the
- program. The <b>Scientific Word</b> technical reference,
- included online with the program, describes how you can
- tailor <b>Scientific Word</b> to recognize many of your
- customizations.</p>
-
- <p>Behind the scenes, <b>Scientific Word</b> documents are
- processed by a full-fledged TeX processor (TurboTeX<a
- id="id2933511" class="indexterm" name="id2933511"></a> by
- the Kinch Computer Company<a id="id2933524"
- class="indexterm" name="id2933524"></a>). This includes
- integrated document formatting and previewing under
- Windows. Starting with version 1.1 of <b>Scientific
- Word</b>, instructions are included to switch to a
- different version of TeX, or different previewers and DVI
- drivers, if you prefer.</p>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2931663" name="ftn.id2931663"
- href="#id2931663">126</a>]</sup> {<b>DVIWindo</b> is
- described in Chapter&#160;<a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- and <b>dvipsone</b> is described in Chapter&#160;<a
- href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a>.}</p>
- </div>
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2933466" name="ftn.id2933466"
- href="#id2933466">127</a>]</sup> {I forced the issue of
- unrecognized control sequences by inserting \parskip and
- \parindent control sequences into the body of the
- document. They really belong in a document style
- option.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;13.&#160;Non-commercial Environments"
- href="ch13.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;15.&#160;TeX on the Macintosh"
- href="ch15.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;13.&#160;Non-commercial
- Environments&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;15.&#160;TeX on the Macintosh</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch15.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch15.html
deleted file mode 100644
index 339ed29bd3f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch15.html
+++ /dev/null
@@ -1,958 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;15.&#160;TeX on the Macintosh</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments" />
- <link rel="next" href="ch16.html"
- title="Chapter&#160;16.&#160;TeX Utilities" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;14.&#160;Commercial Environments"
- href="ch14.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Chapter&#160;16.&#160;TeX Utilities"
- href="ch16.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.mac"
- name="chap.mac"></a>Chapter&#160;15.&#160;TeX on the
- Macintosh</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p><a id="id2931284" class="indexterm"
- name="id2931284"></a>For the most part, using TeX on the
- Macintosh is like using TeX on any other system. Certainly,
- the TeX documents that you edit are the same, and the output
- (on paper) is the same as the output from any other version
- of TeX.</p>
-
- <p>However, because they are immersed in a consistent
- graphical environment, Macintosh tools have a substantially
- different appearance from their non-graphical
- counterparts.<sup>[<a id="id2931310" name="id2931310"
- href="#ftn.id2931310">128</a>]</sup></p>
-
- <p>There are four implementations of TeX available for the
- Macintosh. Of these four, one is commercial, two are
- shareware, and one is (mostly) free. The following sections
- present an overview of each implementation, in alphabetical
- order.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.Excalibur"
- name="sec.Excalibur"></a>CMacTeX</h2>
- </div>
- </div>
-
- <p>The CMacTeX<a id="id2931194" class="indexterm"
- name="id2931194"></a> package includes the most recent
- versions of TeX and MetaFont and all of the standard tools.
- A port of \dvips\index{dvips!for Macintosh} is also
- included, as well as a <tt>DVI</tt> previewer and a
- <b>PrintPS<a id="id2931222" class="indexterm"
- name="id2931222"></a></b> tool for printing PostScript
- files directly to a LaserWriter printer over AppleTalk.</p>
-
- <p>Each utility is a straightforward port of its unix
- counterpart. Command-line options have been replaced by
- standard Mac dialog boxes and menus where appropriate. TeX
- has been extended to include a built-in editor, although it
- is not necessary to use that editor if you have another
- favorite.</p>
-
- <p>By design, CMacTeX is a very modular package. This makes
- it easy to substitute different tools, or different ports
- of the same tools, where it is advantageous to do so. For
- example, you can use <b>MacGS<a id="id2931255"
- class="indexterm" name="id2931255"></a></b><a
- id="id2933708" class="indexterm" name="id2933708"></a> (a
- Macintosh version of <b>Ghostscript</b>) as a previewer if
- you like.</p>
-
- <p>Small versions of TeX, iniTeX, MetaFont, and
- <b>iniMF</b> are provided in the free distribution of
- CMacTeX. Big versions are available only in a commercial
- distribution purchased directly from the author. At the
- time of this writing, the commercial distribution is
- available on diskettes and via email. The commercial
- version also provides fully automated font generation (see
- &#8220;<a href="ch05.html#sec.autofont"
- title="Automatic Font Generation by DVI Drivers">the
- section called &#8220;Automatic Font Generation by DVI
- Drivers&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>)
- and faster versions of TeX and MetaFont.</p>
-
- <p>The configuration files<a id="id2933780"
- class="indexterm" name="id2933780"></a> used by CMacTeX
- resemble the environment variables used by implementations
- of TeX on other systems. You can set up multiple search
- folders for input files and fonts, for example, by
- providing a list of folder names separated by colons.</p>
-
- <p>Table&#160;<a href="ch15.html#tab.mac.cmacdist"
- title="Table&#160;15.1.&#160;Summary of the \protect\cmactex Distribution at CTAN">
- Table&#160;15.1</a> summarizes the CMacTeX version 2.1
- distribution available on the CTAN archives (in
- <tt>systems/mac/cmactex</tt>) as of July, 1993. The
- top-level folders and their contents are presented, not a
- list of the archive files that form the distribution.</p>
-
- <div class="table">
- <a id="tab.mac.cmacdist" name="tab.mac.cmacdist"></a>
-
- <p class="title"><b>Table&#160;15.1.&#160;Summary of the
- \protect\cmactex Distribution at CTAN</b></p>
-
- <table
- summary="Summary of the \protect\cmactex Distribution at CTAN"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Folder</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it TeX</td>
-
- <td align="left">Small versions of TeX</td>
- </tr>
-
- <tr>
- <td align="left">\it Metafont</td>
-
- <td align="left">Small versions of MetaFont</td>
- </tr>
-
- <tr>
- <td align="left">\it view\</td>
-
- <td align="left">print</td>
-
- <td><tt>DVI</tt> previewer and <b>PrintPS</b></td>
- </tr>
-
- <tr>
- <td align="left">\it dvips5516</td>
-
- <td align="left">Complete distribution of \dvips,
- version 5.516.</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it Utilities</td>
-
- <td align="left">All of the standard \texware and
- \mfware utilities</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it ams</td>
-
- <td align="left">Versions of AMSTeX and
- AMSLaTeX</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it ams-pk</td>
-
- <td align="left">\AmS-fonts in <tt>PK</tt>
- format</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it ams-tfm</td>
-
- <td align="left"><tt>TFM</tt> files for the
- \AmS-fonts</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it amsfonts</td>
-
- <td align="left">MetaFont sources for version 2.0
- of the \AmS-fonts</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it tfms</td>
-
- <td align="left"><tt>TFM</tt> files for the CMR and
- LaTeX fonts</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it cmpk300</td>
-
- <td align="left">The CMR fonts in <tt>PK</tt>
- format</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
-
- <tr>
- <td align="left">\it lpk300</td>
-
- <td align="left">The LaTeX extensions to CMR in
- <tt>PK</tt> format</td>
-
- <td class="auto-generated">&#160;</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>The installation instructions for CMacTeX are easy to
- understand, but you will have to configure CMacTeX before
- you try to use it. Unfortunately, the default configuration
- files do not reflect the layout of folders that results
- directly from unpacking the archive files.</p>
-
- <p>CMacTeX includes a prebuilt format file for Plain TeX,
- but if you want to use LaTeX, you will have to build the
- format file with iniTeX first.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2934116"
- name="id2934116"></a>DirectTeX</h2>
- </div>
- </div>
-
- <p>DirectTeX<a id="id2934125" class="indexterm"
- name="id2934125"></a> <a id="id2934136" class="indexterm"
- name="id2934136"></a> is a Macintosh Programmer's Workshop
- (MPW)<a id="id2934152" class="indexterm"
- name="id2934152"></a> based TeX package. It is distributed
- in archive files containing eight disk images. You will
- have to copy each disk image onto a diskette (using a tool
- provided) before you can install DirectTeX.</p>
-
- <p>Because I don't have access to a Mac with MPW installed,
- there is very little that I can say about DirectTeX at this
- point.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2934176"
- name="id2934176"></a>OzTeX</h2>
- </div>
- </div>
-
- <p>OzTeX<a id="id2934185" class="indexterm"
- name="id2934185"></a> is a complete TeX package that
- includes an integrated <tt>DVI</tt> previewer. OzTeX can
- print TeX <tt>DVI</tt> files directly to any printer
- selected by the <b>Chooser<a id="id2934223"
- class="indexterm" name="id2934223"></a></b>. Because OzTeX
- does not include MetaFont, you may need to get from some
- other source <tt>PK</tt> files at a resolution appropiate
- for your printer. The standard OzTeX distribution includes
- a complete set of <tt>PK</tt> files<a id="id2934253"
- class="indexterm" name="id2934253"></a> for 300dpi and
- 360dpi printers.</p>
-
- <p>A default configuration file and a selection of
- specialized configuration files for different printers and
- environments are provided with OzTeX. The distinction
- between big and small implementations of TeX has been
- replaced by configurable memory limits<a id="id2934277"
- class="indexterm" name="id2934277"></a>. With enough RAM
- and appropriate configuration, you should be able to get
- OzTeX to process any TeX file you give it.</p>
-
- <p>OzTeX includes a simple text editor called
- <b>$\Sigma$Edit<a id="id2934309" class="indexterm"
- name="id2934309"></a></b>, but you can replace it with any
- editor you choose. Table&#160;<a
- href="ch15.html#tab.mac.oztexdist"
- title="Table&#160;15.2.&#160;Summary of the \protect\oztex Distribution at CTAN">
- Table&#160;15.2</a> summarizes the OzTeX version 1.5
- distribution available on the CTAN archives (in
- <tt>systems/mac/oztex</tt>) as of July, 1993. The top-level
- folders and their contents are given, not a list of the
- archive files that form the distribution.</p>
-
- <div class="table">
- <a id="tab.mac.oztexdist" name="tab.mac.oztexdist"></a>
-
- <p class="title"><b>Table&#160;15.2.&#160;Summary of the
- \protect\oztex Distribution at CTAN</b></p>
-
- <table
- summary="Summary of the \protect\oztex Distribution at CTAN"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Folder</th>
-
- <th align="left">\bf Contents</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it Configs</td>
-
- <td align="left">Configuration files</td>
- </tr>
-
- <tr>
- <td align="left">\it TeX-formats</td>
-
- <td align="left">Format files for Plain TeX and
- LaTeX</td>
- </tr>
-
- <tr>
- <td align="left">\it TeX-fonts</td>
-
- <td align="left"><tt>TFM</tt> files for CMR, LaTeX,
- and PostScript fonts</td>
- </tr>
-
- <tr>
- <td align="left">\it Help-files</td>
-
- <td align="left">Online help files</td>
- </tr>
-
- <tr>
- <td align="left">\it PS-files</td>
-
- <td align="left">PostScript sources for OzTeX's
- PostScript built-in driver</td>
- </tr>
-
- <tr>
- <td align="left">\it TeX-docs</td>
-
- <td align="left">Example TeX files</td>
- </tr>
-
- <tr>
- <td align="left">\it LaTeX-docs</td>
-
- <td align="left">LaTeX sources for a 26 page User's
- Guide to OzTeX</td>
- </tr>
-
- <tr>
- <td align="left">\it $\Sigma$Edit</td>
-
- <td align="left">A simple text editor desk
- accessory</td>
- </tr>
-
- <tr>
- <td align="left">\it TeX-inputs</td>
-
- <td align="left">Input files for Plain TeX and
- LaTeX</td>
- </tr>
-
- <tr>
- <td align="left">\it PK-files</td>
-
- <td align="left">A set of <tt>PK</tt> files for
- 300dpi and 360dpi printers</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>The OzTeX <tt>DVI</tt> printer recognizes \special
- commands for inserting PICT<a id="id2934565"
- class="indexterm" name="id2934565"></a>, PNTG<a
- id="id2934574" class="indexterm" name="id2934574"></a>
- (<b>MacPaint</b>), and EPSF<a id="id2934589"
- class="indexterm" name="id2934589"></a> images into your
- documents. Provision is also made for including raw
- PostScript code if the selected printer is a PostScript<a
- id="id2934601" class="indexterm" name="id2934601"></a>
- printer.</p>
-
- <p>OzTeX is a shareware program. If you continue to use it
- after a reasonable trial period, you are expected to
- purchase it.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2934618"
- name="id2934618"></a>Textures</h2>
- </div>
- </div>
-
- <p><b>Textures<a id="id2934631" class="indexterm"
- name="id2934631"></a></b> is a commercial implementation of
- TeX from Blue Sky Research<a id="id2934639"
- class="indexterm" name="id2934639"></a>. It has a number of
- features that make it unique in the TeX market. It is
- supported by a complete user's guide and access to
- telephone and email product support.</p>
-
- <p>Textures supports an interactive preview mode called
- <span class="emphasis"><em>Lightning</em></span> Textures<a
- id="id2934662" class="indexterm" name="id2934662"></a><a
- id="id2934669" class="indexterm" name="id2934669"></a>. It
- is this feature that really sets Textures apart from other
- implementations. In this mode, changes to your document are
- reflected immediately in the preview window. In an
- environment with sufficient resources (memory and
- processing speed), the result is striking. Constructing
- complex items like tables and mathematical formulae is much
- easier, especially for the TeX novice, than using the
- conventional edit, TeX, preview, debug cycle. Because the
- log file is also visible, it's easy to see when you've
- written erroneous TeX code.</p>
-
- <p>Note that <span class="emphasis"><em>Lightning
- Textures</em></span> is not really a WYSIWYG environment
- (like <b>Scientific Word</b>, for example) because you
- still enter regular TeX commands in a purely textual
- fashion. You get immediate feedback in a different
- window.</p>
-
- <p>Textures is fast. Extensive instrumentation and
- hand-tuning of the program has produced an executable that
- is several (maybe many) times faster than other TeX
- executables on similar hardware.</p>
-
- <p>A complete set of Computer Modern Roman fonts is
- provided in Adobe Type&#160;1 format. This means that any
- font can be rendered at any size without loss of quality.
- PostScript versions of the \AmS-fonts are also available.
- The fonts can be purchased separately in either Macintosh
- or Adobe <tt>PFB</tt> formats.</p>
-
- <p>Textures is a very integrated environment. This can
- hardly be labelled a disadvantage considering how well it
- works, but it does mean that some extra effort is required
- if you want access to your document in a less integrated
- fashion. Using another editor to compose your document is
- possible, but it prevents you from using <span
- class="emphasis"><em>Lighting</em></span> Textures.
- Starting with version 1.6, the Textures editor includes a
- macro programming language, so you can customize it with
- features that you find useful. Blue Sky Research provides
- the tools you need to incorporate other fonts into TeX or
- extract TeX files (like <tt>DVI</tt> files) that are
- normally hidden from view by Textures.</p>
-
- <p>Figure&#160;<a href="ch15.html#fig.mac.textures"
- title="Figure&#160;15.1.&#160;Editing, previewing, and typesetting in Textures">
- Figure&#160;15.1</a> shows an example of a Textures
- session. The preview quality in this image is less than
- optimal because the Macintosh that Textures is running on
- does not have Adobe Type Manager.</p>
-
- <div class="figure">
- <a id="fig.mac.textures" name="fig.mac.textures"></a>
-
- <p class="title"><b>Figure&#160;15.1.&#160;Editing,
- previewing, and typesetting in Textures</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
-
- <p>Because the Computer Modern Roman fonts are included in
- Adobe Type&#160;1 format, MetaFont is not provided in the
- Textures package. Recently, BSR made their version of
- MetaFont freely available. BSR's MetaFont was designed to
- work with Textures, and creates output files that are
- suitable for Textures, but not necessarily the standard
- <tt>GF</tt> and <tt>TFM</tt> files you might expect. Those
- files can be obtained elsewhere, of course.</p>
-
- <p>The Textures package includes implementations of many
- auxiliary TeX programs including BibTeX<a id="id2934846"
- class="indexterm" name="id2934846"></a>, <b>MakeIndex<a
- id="id2934864" class="indexterm" name="id2934864"></a></b>,
- the <b>Excalibur<a id="id2934878" class="indexterm"
- name="id2934878"></a></b> spellchecker (see the &#8220;<a
- href="ch15.html#sec.Excalibur" title="CMacTeX">the section
- called &#8220;CMacTeX&#8221;</a>&#8221; section later in
- this chapter), a <b>DVITool<a id="id2934906"
- class="indexterm" name="id2934906"></a></b> for importing
- and exporting <tt>DVI</tt> files, and font tools for
- importing and exporting fonts. (Because Textures doesn't
- use <tt>PK</tt> files directly, the standard \mfware tools
- are not provided.) The Textures font tools are freely
- available from Blue Sky Research; see the &#8220;<a
- href="ch15.html#sec.bsrtools" title="BSR Font Tools">the
- section called &#8220;BSR Font Tools&#8221;</a>&#8221;
- section later in this chapter. Textures also supports
- virtual fonts.</p>
-
- <p>Textures includes the Eplain<a id="id2934956"
- class="indexterm" name="id2934956"></a> and Midnight<a
- id="id2934964" class="indexterm" name="id2934964"></a>
- macro packages in addition to Plain TeX and LaTeX. iniTeX
- is built into Textures, so you can make additional format
- files as described in Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.
- Making format files with Textures requires a Macintosh Plus
- or other system with at least 1Mb of memory.</p>
-
- <p>The Textures previewer and printing operations
- understand bitmap or scalable (EPSF) pictures inserted into
- your document with \special commands. Although not visible
- on the previewer, raw PostScript can also be inserted for
- documents printed on PostScript devices.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2935013"
- name="id2935013"></a>Other Tools</h2>
- </div>
- </div>
-
- <p>The following sections describe Macintosh versions of
- other common tools. Some of these programs are unique to
- the Mac, while others are ports of tools from other
- systems.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935026"
- name="id2935026"></a>Alpha</h3>
- </div>
- </div>
-
- <p><b>Alpha<a id="id2935040" class="indexterm"
- name="id2935040"></a></b> is a sophisticated shareware
- editor for text files. <b>Alpha</b> uses <b>Tcl<a
- id="id2935061" class="indexterm"
- name="id2935061"></a></b>, an interpreted C-like
- language, as a macro programming language for extending
- the editor. LaTeX support, which is written in
- <b>Tcl</b>, is very complete. An example of the
- <b>Alpha</b> editor is shown in Figure&#160;<a
- href="ch15.html#fig.mac.alpha"
- title="Figure&#160;15.2.&#160;Alpha editing the fonts chapter from this book">
- Figure&#160;15.2</a>.</p>
-
- <div class="figure">
- <a id="fig.mac.alpha" name="fig.mac.alpha"></a>
-
- <p class="title"><b>Figure&#160;15.2.&#160;Alpha
- editing the fonts chapter from this book</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935128"
- name="id2935128"></a>BBEdit</h3>
- </div>
- </div>
-
- <p><b>BBEdit<a id="id2935142" class="indexterm"
- name="id2935142"></a></b> is another shareware editor.
- Like <b>Alpha</b>, it has a wide range of features
- including a LaTeX-aware editing mode. An example of the
- <b>BBEdit</b> editor is shown in Figure&#160;<a
- href="ch15.html#fig.mac.bbedit"
- title="Figure&#160;15.3.&#160;\program{BBEdit} editing the fonts chapter from this book">
- Figure&#160;15.3</a>.</p>
-
- <div class="figure">
- <a id="fig.mac.bbedit" name="fig.mac.bbedit"></a>
-
- <p class="title">
- <b>Figure&#160;15.3.&#160;\program{BBEdit} editing the
- fonts chapter from this book</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.bsrtools"
- name="sec.bsrtools"></a>BSR Font Tools</h3>
- </div>
- </div>
-
- <p>The Macintosh Programmer's Workshop (MPW)<a
- id="id2935216" class="indexterm" name="id2935216"></a> is
- required to use the Blue Sky Research Font Tools. These
- tools were written for Textures users so that they could
- make other fonts, like those created with MetaFont, for
- example, usable in Textures. In practice however, they
- create standard Macintosh font resources, so the
- resulting fonts can be used by any Mac application.
- Table&#160;<a href="ch15.html#tab.mac.bsrtools"
- title="Table&#160;15.3.&#160;Font Tools in the BSR package">
- Table&#160;15.3</a> describes the tools included in the
- <b>BSR Font Tools<a id="id2935252" class="indexterm"
- name="id2935252"></a></b> package.</p>
-
- <div class="table">
- <a id="tab.mac.bsrtools" name="tab.mac.bsrtools"></a>
-
- <p class="title"><b>Table&#160;15.3.&#160;Font Tools in
- the BSR package</b></p>
-
- <table summary="Font Tools in the BSR package"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Tool</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it GFtoPK</td>
-
- <td align="left">Converts MetaFont <tt>GF</tt>
- files into standard <tt>PK</tt> format</td>
- </tr>
-
- <tr>
- <td align="left">\it PKtoFOND</td>
-
- <td align="left">Creates Mac FOND resource from
- <tt>PK</tt> and <tt>TFM</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it TFMtoSuit</td>
-
- <td align="left">Creates a font metrics
- suitcase</td>
- </tr>
-
- <tr>
- <td align="left">\it NFNTcon</td>
-
- <td align="left">Finds NFNT resource numbering
- conflicts</td>
- </tr>
-
- <tr>
- <td align="left">\it TFtoPL</td>
-
- <td align="left">Converts <tt>TFM</tt> files into
- <tt>PL</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it PLtoTF</td>
-
- <td align="left">Translates <tt>PL</tt> files
- (back) into <tt>TFM</tt> files</td>
- </tr>
- </tbody>
- </table>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935468"
- name="id2935468"></a>Excalibur</h3>
- </div>
- </div>
-
- <p><b>Excalibur<a id="id2935481" class="indexterm"
- name="id2935481"></a></b> is a spellchecker designed to
- work with LaTeX documents. An example of <b>Excalibur</b>
- is shown in Figure&#160;<a
- href="ch15.html#fig.mac.Excalibur"
- title="Figure&#160;15.4.&#160;\program{Excalibur} spellchecking the fonts chapter from this book">
- Figure&#160;15.4</a>.</p>
-
- <div class="figure">
- <a id="fig.mac.Excalibur" name="fig.mac.Excalibur"></a>
-
- <p class="title">
- <b>Figure&#160;15.4.&#160;\program{Excalibur}
- spellchecking the fonts chapter from this book</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935534"
- name="id2935534"></a>HyperBibTeX</h3>
- </div>
- </div>
-
- <p><a id="id2935542" class="indexterm"
- name="id2935542"></a>This is a hypercard stack for
- maintaining bibliographic databases <a id="id2935554"
- class="indexterm" name="id2935554"></a> <a id="id2935565"
- class="indexterm" name="id2935565"></a> suitable for use
- with BibTeX<a id="id2935577" class="indexterm"
- name="id2935577"></a>. BibTeX is described in
- Chapter&#160;<a href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a>, <span class="emphasis"><em><a
- href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a></em></span>. An example of
- HyperBibTeX is shown in Figure&#160;<a
- href="ch15.html#fig.mac.hyperbib"
- title="Figure&#160;15.5.&#160;The \program{Hyper\BibTeX} view of a bibliographic database">
- Figure&#160;15.5</a>.</p>
-
- <div class="figure">
- <a id="fig.mac.hyperbib" name="fig.mac.hyperbib"></a>
-
- <p class="title"><b>Figure&#160;15.5.&#160;The
- \program{Hyper\BibTeX} view of a bibliographic
- database</b></p>
-<pre class="screen">
-FIXME:
-</pre>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935646"
- name="id2935646"></a>MacGS</h3>
- </div>
- </div>
-
- <p><b>MacGS<a id="id2935659" class="indexterm"
- name="id2935659"></a></b> is a Macintosh port of GNU
- <b>Ghostscript</b><a id="id2935673" class="indexterm"
- name="id2935673"></a>, described in Chapter&#160;<a
- href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- <span class="emphasis"><em><a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a></em></span>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935708"
- name="id2935708"></a>dvidvi</h3>
- </div>
- </div>
-
- <p><b>dvidvi<a id="id2935720" class="indexterm"
- name="id2935720"></a></b> is a Macintosh port of the
- <b>dvidvi</b> utility for rearranging pages in a
- <tt>DVI</tt> file.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935748"
- name="id2935748"></a>MacDVIcopy</h3>
- </div>
- </div>
-
- <p><b>MacDVIcopy<a id="id2935761" class="indexterm"
- name="id2935761"></a></b> is a port of the <b>DVICOPY<a
- id="id2935775" class="indexterm"
- name="id2935775"></a></b> utility, which transforms
- virtual font references in a <tt>DVI</tt> file into the
- appropriate non-virtual fonts or commands. This allows
- DVI drivers and previewers that lack support for virtual
- fonts to preview documents that use them.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935800"
- name="id2935800"></a>MacBibTeX</h3>
- </div>
- </div>
-
- <p>MacBibTeX<a id="id2935808" class="indexterm"
- name="id2935808"></a> is a port of the standard BibTeX
- utility for accessing bibliographic databases in a
- document. BibTeX is described in Chapter&#160;<a
- href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2935830"
- name="id2935830"></a>MacMakeIndex</h3>
- </div>
- </div>
-
- <p><b>MacMakeIndex<a id="id2935843" class="indexterm"
- name="id2935843"></a></b> is a port of the standard
- <b>MakeIndex</b> for creating sorted, multilevel indexes
- in a document. <b>MakeIndex</b> is described in
- Chapter&#160;<a href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a>.</p>
- </div>
- </div>
-
- <div class="footnotes">
- <br />
- <hr width="100" align="left" />
-
- <div class="footnote">
- <p><sup>[<a id="ftn.id2931310" name="ftn.id2931310"
- href="#id2931310">128</a>]</sup> {I'm not going to argue
- about the relative merits of graphical and non-graphical
- environments or particular implementations of graphical
- environments. When all is said and done, the Mac <span
- class="emphasis"><em>is</em></span> different. At least
- today.}</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;14.&#160;Commercial Environments"
- href="ch14.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;16.&#160;TeX Utilities"
- href="ch16.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;14.&#160;Commercial Environments&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;16.&#160;TeX Utilities</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/ch16.html b/Master/texmf-doc/doc/english/make-tex-work/html/ch16.html
deleted file mode 100644
index 8ab8648ab09..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/ch16.html
+++ /dev/null
@@ -1,1805 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Chapter&#160;16.&#160;TeX Utilities</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview" />
- <link rel="previous" href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh" />
- <link rel="next" href="apa.html"
- title="Appendix&#160;A.&#160;Filename Extension Summary" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;15.&#160;TeX on the Macintosh"
- href="ch15.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a
- title="Appendix&#160;A.&#160;Filename Extension Summary"
- href="apa.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="chapter">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="chap.utils"
- name="chap.utils"></a>Chapter&#160;16.&#160;TeX
- Utilities</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- <hr class="component-separator" />
- </div>
-
- <p>This chapter offers a brief summary of a large number of
- TeX utilities (some more commonly used than others). Some of
- these programs are mentioned elsewhere in this book in
- connection with the particular tasks that they perform.</p>
-
- <p>Although many programs are described in this chapter,
- there is no way that it can be entirely complete. There are
- just too many programs on CTAN for me to be familiar with
- <span class="emphasis"><em>all</em></span> of them. This list
- is representative of the collection of programs present in
- the archives during the winter of 1993. Regrettably, programs
- not documented in English are not included at this time. Take
- the time to explore the CTAN archives yourself; you won't be
- disappointed.</p>
-
- <div class="sidebar">
- <p class="title"><b>Use the Web, Luke!</b></p>
-
- <p>One of the most convenient online tools for searching
- the archives is the World Wide Web (WWW) interface
- available at <tt>http://jasper.ora.com/ctan.html</tt>. The
- WWW interface is constructed automatically from the most
- recent list of files in the CTAN archives with annotations
- taken from this chapter from the <tt>TeX-index</tt>, and
- from the <tt>ctan.dat</tt> descriptions maintained by the
- CTAN archivists.</p>
- </div>
-
- <p>This chapter attempts to describe only part of the
- archives. Here are some of the things that are <span
- class="emphasis"><em>not</em></span> described in this
- chapter:</p>
-
- <div class="itemizedlist">
- <ul type="disc">
- <li>
- <p>The thirty or more packages in the
- <tt>archive-tools</tt> directory. This directory
- contains sources and executables for almost every
- archiving tool imaginable. If you retrieve a file from
- an FTP site and you don't have the tool necessary to
- unpack it, you'll probably find it in here. You'll also
- find other archive-related programs like an FTP server
- and the <b>Gopher</b> sources.</p>
- </li>
-
- <li>
- <p>Files from the <tt>digests</tt>,
- <tt>documentation</tt>, and <tt>help</tt> directories.
- These are collections of electronic digests, documents,
- and articles that discuss aspects of TeX. They are
- recommended reading.</p>
- </li>
-
- <li>
- <p>Files from the <tt>fonts</tt> directory. These are
- summarized in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.</p>
- </li>
-
- <li>
- <p>Files from the <tt>languages</tt> directory. These
- are summarized in Chapter&#160;<a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a>, <span class="emphasis"><em><a
- href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a></em></span>.</p>
- </li>
-
- <li>
- <p>The many special macro files in the <tt>macros</tt>
- subtree. Many macro formats are described in
- Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.</p>
- </li>
-
- <li>
- <p>Architecture-specific applications from the
- <tt>systems</tt> subtree. These include applications
- for Amiga, Atari, Macintosh, MS-DOS, OS/2, unix, VMS,
- and Xenix systems. The Common-TeX distribution is also
- available under this directory, as well as the standard
- TeX distributions by Knuth. archiving tool imaginable.
- If you retrieve a file from an FTP site and you don't
- have the tool necessary to unpack it, you'll probably
- find it in here. You'll also find other archive-related
- programs like an FTP server and the <b>Gopher</b>
- sources.</p>
- </li>
-
- <li>
- <p>Files from the <tt>digests</tt>,
- <tt>documentation</tt>, and <tt>help</tt> directories.
- These are collections of electronic digests, documents,
- and articles that discuss aspects of TeX. They are
- recommended reading.</p>
- </li>
-
- <li>
- <p>Files from the <tt>fonts</tt> directory. These are
- summarized in Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.</p>
- </li>
-
- <li>
- <p>Files from the <tt>languages</tt> directory. These
- are summarized in Chapter&#160;<a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a>, <span class="emphasis"><em><a
- href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">
- Chapter&#160;7</a></em></span>.</p>
- </li>
-
- <li>
- <p>The many special macro files in the <tt>macros</tt>
- subtree. Many macro formats are described in
- Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.</p>
- </li>
- </ul>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2936355"
- name="id2936355"></a>List of Tools</h2>
- </div>
- </div>
-
- <p>These tools are available in the CTAN archives in the
- directories specified. This list is sorted by CTAN path
- name so that related utilities appear near each other.</p>
-
- <p>
- \package{bib2dvi}{bib2dvi}{sh}{biblio/bibtex/utils/bib2dvi}</p>
-
- <p><b>bib2dvi</b> is a shell script that creates a
- printable listing of an entire BibTeX database.</p>
-
- <p>
- \package{bibcard}{bibcard}{C}{biblio/bibtex/utils/bibcard}</p>
-
- <p><b>bibcard</b> is an X11 based database editor for
- BibTeX databases. This is an OpenWindows application
- requiring the <tt>xview</tt> and <tt>olgx</tt>
- libraries.</p>
-
- <p>
- \package{bibclean}{bibclean}{}{biblio/bibtex/utils/bibclean}</p>
-
- <p><b>bibclean</b> syntax-checks and pretty-prints a BibTeX
- database.</p>
-
- <p>
- \package{bibextract}{bibextract}{}{biblio/bibtex/utils/bibextract}</p>
-
- <p><b>bibextract</b> extracts bibliographic entries from a
- list of BibTeX databases based upon a user-supplied regular
- expression.</p>
-
- <p>
- \package{citefind}{citefind}{}{biblio/bibtex/utils/bibextract}</p>
-
- <p><b>citefind</b> extracts bibliographic entries from a
- list of BibTeX databases based upon a user-supplied list of
- keys.</p>
-
- <p>
- \package{citetags}{citetags}{}{biblio/bibtex/utils/bibextract}</p>
-
- <p><b>citetags</b> extracts citation tags from a list of
- LaTeX source files. These tags can be fed to
- <b>citefind</b> to produce a bibliography database
- customized for a particular document.</p>
-
- <p>
- \package{bibindex}{bibindex}{}{biblio/bibtex/utils/bibindex}</p>
-
- <p><b>bibindex</b> creates a bibliographic index for the
- <b>biblook</b> program.</p>
-
- <p>
- \package{biblook}{biblook}{}{biblio/bibtex/utils/bibindex}</p>
-
- <p><b>biblook</b> uses a binary index constructed by
- <b>bibindex</b> to perform very fast lookups into BibTeX
- databases.</p>
-
- <p>
- \package{bibsort}{bibsort}{}{biblio/bibtex/utils/bibsort}</p>
-
- <p><b>bibsort</b> sorts a BibTeX database.</p>
-
- <p>
- \package{bibtool}{bibtool}{}{biblio/bibtex/utils/bibtool}</p>
-
- <p><b>bibtool</b> performs a number of operations on BibTeX
- databases. It can pretty-print and syntax-check a database,
- automatically build new keys, extract particular entries,
- sort a database, and perform a number of other operations.
- The operation of <b>bibtool</b> can be customized with one
- or more resource files.</p>
-
- <p>
- \package{aux2bib}{aux2bib}{}{biblio/bibtex/utils/bibtools}</p>
-
- <p><b>aux2bib</b> extracts citations from a LaTeX
- <tt>AUX</tt> file and constructs a bibliography that
- contains only the entries required by the document.</p>
-
- <p>
- \package{bibify}{bibify}{}{biblio/bibtex/utils/bibtools}</p>
-
- <p><b>bibify</b> attempts to generate an <tt>AUX</tt> file
- that contains appropriate references for citations. This
- eliminates one LaTeX pass over the document and may be much
- faster for large documents. <b>bibify</b> cannot handle
- documents that use multiple <tt>AUX</tt> files.</p>
-
- <p>
- \package{bibkey}{bibkey}{}{biblio/bibtex/utils/bibtools}</p>
-
- <p>Lists all entries in a BibTeX database that contain a
- particular keyword in the keyword field.</p>
-
- <p>
- \package{cleantex}{cleantex}{}{biblio/bibtex/utils/bibtools}</p>
-
- <p>Deletes temporary files (<tt>AUX</tt>, <tt>LOF</tt>,
- etc.) created by LaTeX.</p>
-
- <p>
- \package{looktex}{looktex}{}{biblio/bibtex/utils/bibtools}</p>
-
- <p>Lists all BibTeX database entries that match a specified
- regular expression.</p>
-
- <p>
- \package{makebib}{makebib}{}{biblio/bibtex/utils/bibtools}</p>
-
- <p><b>makebib</b> creates a &#8220;portable&#8221; BibTeX
- database by performing string substitutions, removing
- comments, and optionally discarding all entries that do not
- match a given list of keys.</p>
-
- <p>
- \package{printbib}{printbib}{}{biblio/bibtex/utils/bibtools}</p>
-
- <p><b>printbib</b> creates a printable listing of an entire
- BibTeX database. <b>printbib</b> is also available in the
- <tt>biblio/bibtex/utils/printbib</tt> directory.</p>
-
- <p>
- \package{bibview}{bibview}{Perl}{biblio/bibtex/utils/bibview}</p>
-
- <p><b>bibview</b> is an interactive Perl script that allows
- you to view and search through a BibTeX database.</p>
-
- <p>
- \package{HyperBibTeX}{HyperBibTeX}{}{biblio/bibtex/utils/hyperbibtex}</p>
-
- <p><b>HyperBibTeX</b> is a Macintosh tool for manipulating
- BibTeX databases.</p>
-
- <p>
- \package{bibdestringify}{bibdestringify}{}{biblio/bibtex/utils/lookbibtex}</p>
-
- <p><b>bibdestringify</b> performs BibTeX string
- substitution on a BibTeX database.</p>
-
- <p>
- \package{lookbibtex}{lookbibtex}{}{biblio/bibtex/utils/lookbibtex}</p>
-
- <p>Lists all BibTeX database entries that match a specified
- regular expression.</p>
-
- <p>\package{r2bib}{r2bib}{C}{biblio/bibtex/utils/r2bib}</p>
-
- <p><b>r2bib</b> converts <b>refer</b> databases into BibTeX
- databases.</p>
-
- <p>
- \package{ref2bib}{ref2bib}{Perl}{biblio/bibtex/utils/ref2bib}</p>
-
- <p><b>ref2bib</b> converts <b>refer</b> databases into
- BibTeX databases.</p>
-
- <p>
- \package{xbibtex}{xbibtex}{}{biblio/bibtex/utils/xbibtex}</p>
-
- <p><b>xbibtex</b> is an X11 program for manipulating BibTeX
- databases.</p>
-
- <p>\package{Public Doman DVI Driver
- Family}{*}{C}{dviware/beebe}</p>
-
- <p>A collection of <tt>DVI</tt> drivers. This code has been
- used as the basis for many other <tt>DVI</tt>-aware
- programs. Table&#160;<a href="ch16.html#tab.util.beebedr"
- title="Table&#160;16.1.&#160;The Public Doman DVI Driver Family">
- Table&#160;16.1</a> summarizes the drivers included in this
- package.</p>
-
- <div class="table">
- <a id="tab.util.beebedr" name="tab.util.beebedr"></a>
-
- <p class="title"><b>Table&#160;16.1.&#160;The Public
- Doman DVI Driver Family</b></p>
-
- <table summary="The Public Doman DVI Driver Family"
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Driver</th>
-
- <th align="left">\bf Description</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it dvialw</td>
-
- <td align="left">PostScript (Apple LaserWriter
- laser printer)</td>
- </tr>
-
- <tr>
- <td align="left">\it dvibit</td>
-
- <td align="left">Version 3.10 BBN BitGraph
- terminal</td>
- </tr>
-
- <tr>
- <td align="left">\it dvica2</td>
-
- <td align="left">Canon LBP-8 A2 laser printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvican</td>
-
- <td align="left">Canon LBP-8 A2 laser printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvidjp</td>
-
- <td align="left">Hewlett-Packard Desk Jet plus
- (from LaserJet)</td>
- </tr>
-
- <tr>
- <td align="left">\it dvie72</td>
-
- <td align="left">Epson 9-pin family 240/216-dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvie72</td>
-
- <td align="left">Epson 9-pin family 60/72-dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvieps</td>
-
- <td align="left">Epson 9-pin family 240/216-dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvieps</td>
-
- <td align="left">Epson 9-pin family 60/72-dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvigd</td>
-
- <td align="left">Golden Dawn Golden Laser 100 laser
- printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dviimp</td>
-
- <td align="left">imPRESS (Imagen laser printer
- family)</td>
- </tr>
-
- <tr>
- <td align="left">\it dvijep</td>
-
- <td align="left">Hewlett-Packard LaserJet Plus
- laser printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvijet</td>
-
- <td align="left">Hewlett-Packard 2686A Laser Jet
- laser printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvil3p</td>
-
- <td align="left">Digital LN03-PLUS 300 dpi laser
- printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvil3p</td>
-
- <td align="left">Digital LN03-PLUS 150 dpi laser
- printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvil75</td>
-
- <td align="left">DEC LA75 144h x 144v dot matrix
- printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvil75</td>
-
- <td align="left">DEC LA75 72h x 72v dot matrix
- printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvim72</td>
-
- <td align="left">Apple ImageWriter 144 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvim72</td>
-
- <td align="left">Apple ImageWriter 72 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvimac</td>
-
- <td align="left">Apple ImageWriter 144 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvimac</td>
-
- <td align="left">Apple ImageWriter 72 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvimpi</td>
-
- <td align="left">MPI Sprinter 144h x 144v dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvimpi</td>
-
- <td align="left">MPI Sprinter 72h x 72v dot matrix
- printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvio72</td>
-
- <td align="left">OKIDATA Pacemark 2410 144 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvio72</td>
-
- <td align="left">OKIDATA Pacemark 2410 72 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvioki</td>
-
- <td align="left">OKIDATA Pacemark 2410 144 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvioki</td>
-
- <td align="left">OKIDATA Pacemark 2410 72 dpi dot
- matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dviprx</td>
-
- <td align="left">Printronix 300/600 60h x 72v dpi
- dot matrix printer</td>
- </tr>
-
- <tr>
- <td align="left">\it dvitos</td>
-
- <td align="left">Toshiba P-1351 180h x 180v dpi dot
- matrix printer</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>\package{bitpxl}{bitpxl}{C}{dviware/bitpxl}</p>
-
- <p>Converts HP LaserJet bitmaps into PXL files.</p>
-
- <p>\package{cdvi}{cdvi}{}{dviware/cdvi}</p>
-
- <p>MS-DOS <tt>DVI</tt> file previewer. Does not support
- external fonts, but has 16 Computer Modern fonts built
- in.</p>
-
- <p>
- \package{Crudetype}{crudetype}{Web}{dviware/crudetype/version3}</p>
-
- <p>A <tt>DVI</tt>-to-text translator. <b>Crudetype</b>
- attempts to make a readable <tt>DVI</tt> file. An
- interactive mode is available on some platforms. A
- 132-column display is expected for most output.</p>
-
- <p>\package{DVItoVDU}{dvgt, dvitovdu,
- dvi2vdu}{C}{dviware/dvgt}</p>
-
- <p><b>DVItoVDU</b> is a terminal previewer for <tt>DVI</tt>
- files. The <b>dvgt</b> version supports graphics preview
- using various graphics terminals and limited typeset
- preview on other terminals such as the VT100 and VT220.
- Tektronix emulation allows remote previewing of
- <tt>DVI</tt> files through Telnet or using Kermit from a
- PC, for example.</p>
-
- <p>\package{DVI2PCL}{dvi2pcl}{C}{dviware/dvi2pcl}</p>
-
- <p>Translates <tt>DVI</tt> files into HP LaserJet
- format.</p>
-
- <p>\package{dvi2ps}{}{C}{dviware/dvi2ps}</p>
-
- <p>There are a number of translators called <b>dvi2ps</b>.
- Some appear to be older <tt>DVI</tt> to PostScript
- translators supporting the MIT <tt>printcap</tt> entries
- and Apple LaserWriter printers, while others offer support
- for Asian fonts compatible with the tools used by the
- Japanese TeX User's Group and the <b>chfont</b> program,
- better support for built-in printer features, and faster
- execution.</p>
-
- <p>\package{psdvi}{psdvi}{C}{dviware/dvi2ps/psdvi}</p>
-
- <p>This program translates <tt>DVI</tt> files into
- resolution-independent PostScript files. This allows the
- PostScript output to be printed on high-resolution
- phototypesetting equipment. Many other
- <tt>DVI</tt>-to-PostScript converters assume that the
- output resolution is 300dpi, which makes the PostScript
- more difficult, or impossible, to print on high-resolution
- devices.</p>
-
- <p>Because bitmapped fonts are inherently
- resolution-dependent, documents that use them cannot be
- translated with this driver. This means that none of the
- Computer Modern or \AmS fonts can be used unless you have
- them in PostScript Type&#160;1 format.</p>
-
- <p>\package{DVI2QMS}{dvi2qms}{C}{dviware/dvi2qms}</p>
-
- <p>Translates <tt>DVI</tt> files into output suitable for
- QMS 800/1200/2400 printers.</p>
-
- <p>\package{DVI2TTY}{dvi2tty}{C}{dviware/dvi2tty}</p>
-
- <p>Translates <tt>DVI</tt> files into plain ASCII text.</p>
-
- <p>\package{dvi2xx}{dvilj2, dvilj2p, dvilj, dviljp,
- dvi3812}{C}{dviware/dvi2xx}</p>
-
- <p>Translates <tt>DVI</tt> files into output suitable for
- the HP LaserJet family of printers and compatible printers.
- It also supports output to the IBM 3812 printer. MS-DOS and
- OS/2 executables are provided.</p>
-
- <p>\package{dviapollo}{dviapollo}{C}{dviware/dviapollo}</p>
-
- <p>A screen previewer for Apollo workstations.</p>
-
- <p>\package{dvibit}{dvibit}{C}{dviware/dvibit}</p>
-
- <p>A screen previewer for BBN BitGraph terminals.</p>
-
- <p>\package{dvibook}{dvibook}{C}{dviware/dvibook}</p>
-
- <p>Rearranges <tt>DVI</tt> file pages into a sequence
- suitable for printing and folding into a book. Actually, it
- produces signatures, which are small groups of pages that
- can be folded together. A signature is composed of several
- folded pages; a book is composed of many signatures bound
- together.</p>
-
- <p>\package{DVIChk}{dvichk}{C}{dviware/dvichk}</p>
-
- <p><b>DVIChk</b> examines a <tt>DVI</tt> file and prints
- out the page numbers that occur in the document in the
- order in which they occur. Pages in a <tt>DVI</tt> file do
- not have to occur in any particular order.</p>
-
- <p>\package{DVICOPY}{dvicopy}{Web}{dviware/dvicopy}</p>
-
- <p>This program copies a <tt>DVI</tt> file that contains
- references to virtual fonts and creates an equivalent
- <tt>DVI</tt> file with all references to virtual fonts
- translated into references to the appropriate non-virtual
- fonts.</p>
-
- <p>\package{DVIDIS}{dvidis}{C}{dviware/dvidis}</p>
-
- <p>A <tt>DVI</tt> file previewer for VaxStations running
- VMS.</p>
-
- <p>\package{dvidoc}{dvidoc}{C}{dviware/dvidoc}</p>
-
- <p>Translates <tt>DVI</tt> files into plain ASCII. Although
- it does not attempt to form the same page breaks, it does
- claim to get the interword spacing correct.</p>
-
- <p>\package{DVIDVI}{dvidvi}{C}{dviware/dvidvi}</p>
-
- <p>Rearranges pages in a <tt>DVI</tt> file. The resulting
- file is a new <tt>DVI</tt> file containing only the
- selected pages. A Macintosh executable is available in
- <tt>dviware/dvidvi/mac</tt>.</p>
-
- <p>\package{DVIEW}{dview}{}{dviware/dview}</p>
-
- <p>A very old previewer for MS-DOS. This program relies on
- <tt>PXL</tt> files and requires the antique Almost Modern
- fonts to print the user manual.</p>
-
- <p>\package{DVIIMP}{dviimp}{Web}{dviware/dviimp}</p>
-
- <p>Translates <tt>DVI</tt> files into a format suitable for
- printing on an Imagen printer. This program reads
- <tt>GF</tt> files rather than <tt>PK</tt> files.</p>
-
- <p>\package{dvimerge}{dvimerge}{<span
- class="emphasis"><em>sh</em></span>}{dviware/dvimerge}</p>
-
- <p><b>dvimerge</b> is a shell script (written in <b>sh</b>)
- that uses <b>dvidvi</b> and <b>dviconcat</b> to merge two
- <tt>DVI</tt> files together.</p>
-
- <p>\package{DVIMSWin}{dvimswin}{}{dviware/dvimswin}</p>
-
- <p>A <tt>DVI</tt> previewer for MS-DOS running Windows 3.1.
- This program uses <tt>PK</tt> fonts at screen resolution.
- These can be generated by MetaFont or obtained from the
- <b>dvivga</b> distribution.</p>
-
- <p>\package{dvipage}{dvipage}{C}{dviware/dvipage}</p>
-
- <p>A <tt>DVI</tt> previewer for workstations running
- SunView version 3.0 or later.</p>
-
- <p>\package{dvipj}{dvipj}{C}{dviware/dvipj}</p>
-
- <p>This program is a modification of the <b>dvijet</b>
- driver that supports color printing on the HP PaintJet
- printer. To build this program, you need source from the
- Public Doman DVI Driver Family.</p>
-
- <p>\package{dvips}{afm2tfm, dvips}{C}{dviware/dvips}</p>
-
- <p>The <b>dvips</b> program is the de facto standard
- <tt>DVI</tt> to PostScript translator. Several versions are
- available, although the most recent release seems to offer
- a superset of the features provided by all the other
- versions.</p>
-
- <p>\package{dvipsk}{afm2tfm, dvipsk}{C}{dviware/dvipsk}</p>
-
- <p><b>dvipsk</b> is a modification of <b>dvips</b> version
- 5.516 that supports an extended path searching algorithm
- for <tt>PK</tt> fonts.</p>
-
- <p>\package{DVISUN}{dvisun}{C}{dviware/dvisun}</p>
-
- <p>A <tt>DVI</tt> previewer for Sun II terminals.</p>
-
- <p>\package{dvitodvi}{dvitodvi}{C}{dviware/dvitodvi}</p>
-
- <p>Rearranges pages in a <tt>DVI</tt> file, producing a new
- <tt>DVI</tt> file.</p>
-
- <p>\package{dvitool}{dvitool}{C}{dviware/dvitool}</p>
-
- <p>A <tt>DVI</tt> previewer for workstations running
- SunView.</p>
-
- <p>\package{dvitops}{psfont, pfbtops, aftopl,
- dvitops}{C}{dviware/dvitops/dvitops}</p>
-
- <p><b>dvitops</b> is a <tt>DVI</tt>-to-PostScript
- translator. <b>psfont</b> can be used to download
- PostScript fonts. <b>pfbtops</b> decodes printer font
- binary files into printer font ASCII files. <b>aftopl</b>
- builds a <tt>PL</tt> file from a PostScript <tt>AFM</tt>
- file. <tt>PL</tt> files can be further translated into
- <tt>TFM</tt> files with the standard <b>PLtoTF</b>
- utility.</p>
-
- <p>\package{dvitovdu}{dvitovdu}{C}{dviware/dvitovdu}</p>
-
- <p>A <tt>DVI</tt> previewer for terminals. <b>dvitovdu</b>
- handles plain ASCII terminals as well as some graphics
- terminals. Includes VMS and unix ports.</p>
-
- <p>\package{dvitovdu}{dvitovdu}{C}{dviware/dvitovdu32}</p>
-
- <p>Another version of the <b>dvitovdu</b> <tt>DVI</tt>
- previewer for terminals. <b>dvitovdu</b> handles plain
- ASCII terminals as well as some graphics terminals. This
- version seems to read only <tt>PXL</tt> files.</p>
-
- <p>\package{dvitty}{dvitty}{Pascal}{dviware/dvitty}</p>
-
- <p>A simple previewer for ASCII display of <tt>DVI</tt>
- files.</p>
-
- <p>\package{DVIVGA}{dvivga}{}{dviware/dvivga}</p>
-
- <p>The <b>DVIVGA</b> distribution includes a program for
- previewing <tt>DVI</tt> files on PCs with EGA, VGA, or MCGA
- displays. <b>DVIVGA</b> is derived from the Public Doman
- DVI Driver Family. \pagebreak The <b>DVIVGA</b>
- distribution also includes a full set of <tt>PK</tt> fonts
- at many resolutions: 70, 76, 84, 92, 100, 110, 121, 132,
- 145, 174, 208, 250, and 300dpi. Other previewers that
- require <tt>PK</tt> fonts at screen resolution (typically
- near 100dpi) can also use these fonts.</p>
-
- <p>\package{DVIWIN}{dviwin}{}{dviware/dviwin}</p>
-
- <p>A screen previewer for MS-DOS running Windows 3.1. This
- program includes the ability to use emTeX <tt>FLI</tt> font
- libraries.</p>
-
- <p>\goodbreak
- \package{eps}{eps}{C}{dviware/epson/eps-0.2}</p>
-
- <p>Prints a <tt>DVI</tt> file on an Epson dot-matrix
- printer. Some <tt>PK</tt> fonts at the appropriate
- resolutions are included in
- <tt>dviware/epson/epson</tt>.</p>
-
- <p>\package{ivd2dvi}{ivd2dvi}{C}{dviware/ivd2dvi}</p>
-
- <p>The TeX-\XeT driver produces <tt>IVD</tt> files, which
- are like <tt>DVI</tt> files except that they use some
- special commands to perform reflection, which allows them
- to print <span
- class="emphasis"><em>right-to-left</em></span>.</p>
-
- <p>This program translates an <tt>IVD</tt> file into a
- standard <tt>DVI</tt> file by replacing all of the special
- commands with standard <tt>DVI</tt> file commands.</p>
-
- <p>\package{dvijep}{dvijep}{C}{dviware/kane}</p>
-
- <p>Another <tt>DVI</tt>-to-HP LaserJet+ driver.</p>
-
- <p>\package{dvijep\_p}{dvijep\_p}{C}{dviware/kane}</p>
-
- <p>A modified version of <b>dvijep</b> with Centronics PP8
- workarounds <span class="emphasis"><em>removed</em></span>
- where they might confuse a real LaserJet+ printer.</p>
-
- <p>\package{dvi2kyo}{dvi2kyo}{C}{dviware/kyocera}</p>
-
- <p>A <tt>DVI</tt> translator that produces Kyocera's native
- Prescribe command language rather than relying on Kyocera's
- somewhat limited HP LaserJet compatibility mode.</p>
-
- <p>\package{kyodev}{kyodev}{C}{dviware/kyocera}</p>
-
- <p>This DVI driver produces output in Kyocera's native
- Prescribe format.</p>
-
- <p>\package{dviplus}{dviplus}{Web}{dviware/laserjet}</p>
-
- <p>An old <tt>DVI</tt>-to-HP LaserJet Plus translator that
- uses <tt>PXL</tt> files.</p>
-
- <p>\package{LN03 Driver}{ln03dvi}{C}{dviware/ln03}</p>
-
- <p>Translates <tt>DVI</tt> files into a format suitable for
- printing on a Digital LN03 printer.</p>
-
- <p>\package{PSPrint}{psprint}{Pascal}{dviware/psprint}</p>
-
- <p>A PostScript printing program that can handle
- <tt>DVI</tt> files, raw PostScript files, or text files.
- This program is a combined <tt>DVI</tt>-to-PostScript
- translator and file-printing utility.</p>
-
- <p>unix and VMS sources are provided, but a Pascal compiler
- is required.</p>
-
- <p>\package{QMS}{dvilg8, dviqms12,
- ddviqms8}{}{dviware/qms}</p>
-
- <p>An old VMS <tt>DVI</tt> driver for QMS printers.</p>
-
- <p>\package{QuicSpool}{pktoch, tfm2difont, tfm2ofont,
- dumpdesc, cati}{C}{dviware/quicspool}</p>
-
- <p>This is a collection of programs for printing files to
- QMS and Talaris laser printers. Support for <tt>DVI</tt>
- files is included.</p>
-
- <p>\package{SCREENVIEW}{crude}{Web}{dviware/screenview}</p>
-
- <p>A VMS tool based on <b>Crudetype</b> for previewing
- <tt>DVI</tt> files at an ASCII terminal.</p>
-
- <p>\package{See\protect\TeX}{xtex, texsun, texx, iptex,
- mftops}{C}{dviware/seetex}</p>
-
- <p>The <b>SeeTeX</b> package contains a number of tools for
- working with <tt>DVI</tt> files. The most substantial of
- these tools are the <b>xtex</b> and <b>texsun</b>
- previewers for workstations running the X Window system and
- the SunView window system, respectively.</p>
-
- <p><b>xtex</b> is unique among X11 previewers because it
- uses X Window fonts. This makes <b>xtex</b> quite fast. It
- also means that <b>xtex</b> has to build a lot of new X
- Window fonts the first few times that you use it. The
- <b>mftops</b> program converts TeX <tt>PK</tt> fonts into X
- Window fonts. <b>xtex</b> uses the <b>MakeTeXPK</b> program
- to build new <tt>PK</tt> fonts at the necessary
- resolutions. <b>xtex</b> also uses <b>Ghostscript</b> to
- display the PostScript figures in your document. This is
- typically much faster than using <b>GhostView</b> to
- preview the entire document. The <b>texx</b> previewer is a
- much simpler X Window previewer. It cannot interpret
- PostScript, but it does recognize most of the <b>tpic</b>
- specials. <b>SeeTeX</b> also includes <b>iptex</b>, an
- Imagen printer driver.</p>
-
- <p>\obsolete{symbolics}{symbolics}{}{dviware/symbolics}</p>
-
- <p>\package{\TeX{}tool}{textool}{}{dviware/textool}</p>
-
- <p>This is a TeX previewer for the SunView window
- system.</p>
-
- <p>\package{umddvi}{dvidmd, dvipr, dviselect,
- iptex}{C}{dviware/umddvi}</p>
-
- <p><b>dvidmd</b> is a <tt>DVI</tt> previewer for DMD 5620
- displays. <b>dvipr</b> is a <tt>DVI</tt> driver for
- Versatec printers. <b>iptex</b> is a <tt>DVI</tt> driver
- for Imagen printers. Finally, <b>dviselect</b> extracts
- pages from a <tt>DVI</tt> file and produces a new
- <tt>DVI</tt> file containing the selected pages.</p>
-
- <p>\package{VU\protect\TeX}{vutex}{Web}{dviware/vutex}</p>
-
- <p>Another VMS <tt>DVI</tt> previewer for ASCII
- terminals.</p>
-
- <p>\package{xdvi}{xdvi}{C}{dviware/xdvi}</p>
-
- <p>A screen previewer for workstations running the X11
- Window System. MS-DOS executables, useful only if you have
- an X11 Window system running on your PC, are available in
- the <tt>dviware/xdvi-dos</tt> directory.</p>
-
- <p>\package{xdvik}{xdvik}{C}{dviware/xdvik}</p>
-
- <p><b>xdvik</b> is a modification of <b>xdvi</b> that
- supports an extended path searching algorithm for
- <tt>PK</tt> fonts.</p>
-
- <p>\package{bit2spr}{bit2spr}{C}{graphics/bit2spr}</p>
-
- <p><b>bit2spr</b> converts X11 <tt>XBM</tt> bitmaps into a
- &#8220;sprite&#8221; format that can be included directly
- in TeX documents. The resulting sprites are fully portable,
- although they require a lot of memory, which may make large
- bitmaps impractical.</p>
-
- <p>
- \package{bm2font}{bm2font}{C/Pascal}{graphics/bm2font}</p>
-
- <p>The <b>bm2font</b> program converts bitmapped images
- into TeX, <tt>TFM</tt>, and <tt>PK</tt> files.
- <b>bm2font</b> also generates the Plain TeX or LaTeX
- statements necessary to insert the figure into your
- document. Color images can be dithered in a number of
- different ways. This is one of the most portable ways to
- insert pictures into a document; almost every available DVI
- driver can print TeX <tt>PK</tt> fonts.</p>
-
- <p>\package{fig2MF}{fig2mf}{C}{graphics/fig2mf}</p>
-
- <p>Translates Fig code into MetaFont source. This allows
- you to use interactive drawing tools like <b>xfig</b> to
- construct diagrams that can be included into your document
- in a portable manner with <b>fig2MF</b>.</p>
-
- <p>\package{gnuplot}{gnuplot}{C}{graphics/gnuplot}</p>
-
- <p><b>gnuplot</b> is an interactive function plotting
- program. Several different types of output are supported
- and can be included directly into your document.</p>
-
- <p>\package{hpgl2ps}{hpgl2ps}{C}{graphics/hpgl2ps}</p>
-
- <p>This program translates HPGL Plotter language commands
- into encapsulated PostScript.</p>
-
- <p>\package{mactotex}{mactotex}{C}{graphics/mactotex}</p>
-
- <p>This program cleans up Macintosh PostScript so it can be
- included into your documents with <b>psfig</b>. (Some
- printers have difficulty printing PostScript output
- generated on a Macintosh because the PostScript is tailored
- towards the Apple LaserWriter series of printers.)</p>
-
- <p>\package{MFPic}{mfpic}{C}{graphics/mfpic}</p>
-
- <p><b>MFPic</b> is a flexible replacement for the LaTeX
- <tt>picture</tt> environment. Instead of relying on special
- fonts to generate pictures, <b>MFPic</b> writes MetaFont
- code, which generates a font containing the picture
- specified. This makes <b>MFPic</b> more flexible than the
- standard <tt>picture</tt> environment without losing
- portability.</p>
-
- <p>\package{pbmtopk}{pbmtopk}{C}{graphics/pbmtopk}</p>
-
- <p>Translates <tt>PBM</tt> files into TeX <tt>PK</tt>
- fonts.</p>
-
- <p>\package{PiCTeX}{pictex}{C}{graphics/pictex}</p>
-
- <p>A sophisticated macro package that works on top of Plain
- TeX and LaTeX. It provides a device-independent way of
- producing many kinds of figures. The PiCTeX implementation
- frequently generates documents that are too complex for
- &#8220;small&#8221; versions of TeX to render. The PiCTeX
- manual is not freely available and must be purchased before
- PiCTeX can be used.</p>
-
- <p>\package{Glo+Index}{idxtex,
- glotex}{C}{indexing/glo+index}</p>
-
- <p>These are tools for automatic construction of indexes
- and glossaries. The glossary building tool uses \glossary
- entries from your document in conjunction with a database
- of word definitions to automatically construct a glossary.
- The <b>idxtex</b> program provides many of the same
- features as the <b>MakeIndex</b> program.</p>
-
- <p>\package{MakeIndex}{makeindex,
- makeindx}{C}{indexing/makeindex}</p>
-
- <p>This is the standard tool for processing \index entries
- from LaTeX documents. <b>MakeIndex</b> reads the entries,
- sorts them, handles a number of useful features (multilevel
- indexes, special sorting criteria, etc.) and produces LaTeX
- source code, which produces a typeset index.</p>
-
- <p>\package{RTF Translator}{rtf2text, rtf2troff,
- *}{C++}{support/RTF-1_06a1}</p>
-
- <p>The <b>RTF Translator</b> package includes several
- programs for converting RTF (Rich Text Format) files. RTF
- files contain information about the structure as well as
- the content of a document. Microsoft Word and several NeXT
- tools can produce RTF files.</p>
-
- <p>Table&#160;<a href="ch16.html#tab.rtfxlate"
- title="Table&#160;16.2.&#160;RTF Translators">Table&#160;16.2</a>
- summarizes the translators provided. Note that there is no
- TeX or LaTeX translator in this package at present.</p>
-
- <div class="table">
- <a id="tab.rtfxlate" name="tab.rtfxlate"></a>
-
- <p class="title"><b>Table&#160;16.2.&#160;RTF
- Translators</b></p>
-
- <table summary="RTF Translators" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Program</th>
-
- <th align="left">\bf Translation</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it rtf2null</td>
-
- <td align="left">Removes RTF codes</td>
- </tr>
-
- <tr>
- <td align="left">\it rtf2text</td>
-
- <td align="left">Translates to ASCII text</td>
- </tr>
-
- <tr>
- <td align="left">\it rtf2troff</td>
-
- <td align="left">Translates to <b>ms</b> macros in
- <b>troff</b></td>
- </tr>
-
- <tr>
- <td align="left">\it rtfwc</td>
-
- <td align="left">Counts actual words in an RTF
- document</td>
- </tr>
-
- <tr>
- <td align="left">\it rtfdiag</td>
-
- <td align="left">Verifies the RTF parser (or the
- RTF document)</td>
- </tr>
-
- <tr>
- <td align="left">\it rtfskel</td>
-
- <td align="left">A skeleton for producing new
- translators</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>\package{accents}{accents}{Web}{support/accents}</p>
-
- <p><b>accents</b> generates a virtual font containing
- accented letters arranged according to the KOI8-CS
- character set. This program constructs the accented letters
- from characters and accent marks, if necessary. If the
- input font is in Adobe Standard Encoding, <b>accents</b>
- can rearrange it into TeX Text encoding.</p>
-
- <p>\package{addindex}{addindex}{C}{support/addindex}</p>
-
- <p><b>addindex</b> inserts LaTeX \index commands into your
- document. Presented with a list of words and index entries,
- <b>addindex</b> reads your LaTeX files and indexes every
- word from the list that occurs in your document.</p>
-
- <p>\package{amSpell}{amspell}{}{support/amspell}</p>
-
- <p>The <b>amSpell</b> program is an interactive MS-DOS
- spellchecker for plain ASCII and TeX documents.</p>
-
- <p>\package{atops}{atops}{}{support/atops}</p>
-
- <p>A simple program to convert ASCII text files into
- PostScript.</p>
-
- <p>\package{\auctex}{}{elisp}{support/auctex}</p>
-
- <p>A comprehensive TeX editing environment for GNU
- emacs.</p>
-
- <p>\package{basix}{basix}{tex}{support/basix}</p>
-
- <p><b>basix</b> is a BASIC interpreter written entirely in
- TeX. Honest. ;-)</p>
-
- <p>\package{BibDB}{bibdb}{}{support/bibdb}</p>
-
- <p>An MS-DOS program for editing BibTeX bibliographic
- databases.</p>
-
- <p>\package{brief_t}{}{}{support/brief_t}</p>
-
- <p>The <b>brief_t</b> package is a LaTeX editing
- environment for Borland International's <b>Brief</b>
- editor.</p>
-
- <p>\package{c++2latex}{c2latex,
- c++2latex}{C}{support/c++2LaTeX-1_1}</p>
-
- <p>This program parses your C or C++ programs and creates
- LaTeX source code for pretty-printing them. The syntactic
- elements of the source (keywords, identifiers, comments,
- etc.) can be set in different fonts. Compiling this program
- requires <b>flex</b>.</p>
-
- <p>\package{C2\LaTeX}{c2latex}{}{support/c2latex}</p>
-
- <p><b>C2LaTeX</b> is a filter designed to provide simple
- literate programming support for C programming. This filter
- massages LaTeX-coded C comments and source code into a
- LaTeX document.</p>
-
- <p>\package{chi2tex}{chi2tex}{}{support/chi2tex}</p>
-
- <p><b>chi2tex</b> is an MS-DOS program for converting
- <b>ChiWriter</b> documents into TeX.</p>
-
- <p>\package{detex}{detex, texspell}{C}{support/detex}</p>
-
- <p><b>detex</b> removes TeX control sequences from a
- document. The <b>texspell</b> script pipes the resulting
- output through a spell checker.</p>
-
- <p>\package{bibtex-mode, web-mode}{bibtex-mode.el,
- web-mode.el}{elisp}{support/emacs-modes}</p>
-
- <p>GNU emacs macros that provide an enhanced editing
- environment for BibTeX databases and <b>Web</b> source
- files. Another substantial set of modes for editing LaTeX
- documents is provided by aucTeX, listed separately.</p>
-
- <p>\package{flow}{flow}{C}{support/flow}</p>
-
- <p><b>flow</b> reads a plain text description of a flow
- chart and produces the appropriate LaTeX <tt>picture</tt>
- environment for printing the flow chart.</p>
-
- <p>
- \package{byte2tex}{byte2tex}{C}{support/foreign/byte2tex}</p>
-
- <p>A translator for multilingual documents that use the
- upper range of the ASCII character set as a second
- alphabet. The translation performed is controlled by a
- plain text description of the alphabet. See also <b>EDI</b>
- and <b>cyrlatex</b>.</p>
-
- <p>
- \package{cyrlatex}{cyrlatex}{tex}{support/foreign/cyrlatex}</p>
-
- <p>A LaTeX style for using the \AmS Cyrillic fonts as a
- second alphabet under LaTeX. See also <b>EDI</b> and
- <b>byte2tex</b>.</p>
-
- <p>\package{EDI}{edi}{}{support/foreign/edi}</p>
-
- <p>An MS-DOS editor for multilingual (particularly
- Cyrillic) documents. <b>EDI</b> uses the upper range of the
- ASCII character set as a programmable second alphabet. See
- also <b>byte2tex</b> and <b>cyrlatex</b>. MS-DOS and Atari
- executables are available.</p>
-
- <p>\package{genfam}{genfam,
- modern}{Perl}{support/genfam}</p>
-
- <p>The <b>genfam</b> script reads a configuration file that
- describes a set of fonts and then runs the appropriate
- MetaFont commands to produce them. A sample configuration
- file, <tt>modern</tt>, is provided for the Computer Modern
- Roman family.</p>
-
- <p>\package{Ghostview}{ghostview}{C}{support/ghostview}</p>
-
- <p><b>Ghostview</b> provides an interactive interface to
- <b>Ghostscript</b>, the GNU PostScript interpreter.
- <b>Ghostview</b> requires X11, but there are ports to
- Microsoft Windows and OS/2.</p>
-
- <p>\package{Stanford
- GraphBase}{}{CWeb}{support/graphbase}</p>
-
- <p>This is a collection of <b>CWeb</b> programs for
- studying combinatorial algorithms. It is related to TeX
- only because <b>CWeb</b> files are part TeX.</p>
-
- <p>\package{HPTFM2PL}{hptfm2pl,
- showsym}{}{support/hp2pl}</p>
-
- <p>This program reads Hewlett-Packard Tagged Font Metric
- files and creates TeX <tt>PL</tt> files. The <tt>PL</tt>
- files can be further translated into TeX <tt>TFM</tt> files
- with the standard utility <b>PLtoTF</b>.</p>
-
- <p>Hewlett-Packard distributes metric information about
- LaserJet built-in fonts and font cartridges in Tagged Font
- Metric format, so this program gives you a way of getting
- TeX metrics for those fonts. To actually use them, you must
- have both the metrics and a DVI driver that can use
- built-in fonts.</p>
-
- <p>\package{HP2\protect\TeX}{hp2tex,
- hpopt}{}{support/hp2tex}</p>
-
- <p><b>HP2TeX</b> translates HPGL files into TeX documents
- that use the \special commands found in emTeX for drawing
- lines at arbitrary angles. This makes diagrams in HPGL
- format that use only straight lines printable directly with
- TeX. See also <b>HP2XX</b>.</p>
-
- <p>\package{HP2XX}{hp2xx}{}{support/hp2xx}</p>
-
- <p><b>HP2XX</b> converts HPGL diagrams into PostScript or
- one of several bitmapped formats. It can also translate
- some diagrams directly into TeX if \special commands are
- available for drawing lines at any angle.</p>
-
- <p>MS-DOS, Sparc, Convex 210, and HP9000 executables are
- available. A Windows front-end is also available for
- MS-DOS.</p>
-
- <p>\package{HPtoMF}{hptomf}{}{support/hptomf}</p>
-
- <p><b>HPtoMF</b> converts HPGL (Hewlett-Packard's plotter
- language) into a variety of other vector and raster
- formats.</p>
-
- <p>\undescribed{HTML}{html}{}{support/html}</p>
-
- <p>
- \package{HTMLto\LaTeX}{html2latex}{}{support/html2latex}</p>
-
- <p>This program converts HTML documents into LaTeX source
- for printing.</p>
-
- <p>\package{Icons}{}{}{support/icons}</p>
-
- <p>This is a collection of icons for TeX and MetaFont. They
- were designed by Donald Knuth for OpenWindows and have
- subsequently been translated into Microsoft Windows, OS/2,
- and X11 XBM format.</p>
-
- <p>\package{Imake-\TeX}{imaketex}{}{support/imaketex}</p>
-
- <p><b>Imake-TeX</b> helps you create an Imakefile for TeX
- documents. Imakefiles are used to generate custom makefiles
- for an application, in this case a LaTeX document.</p>
-
- <p>\package{ispell}{ispell}{C}{support/ispell}</p>
-
- <p>An interactive spellchecker. <b>ispell</b> is
- intelligent about TeX documents and can handle languages
- other than English. \editorial{there are two!}</p>
-
- <p>\package{jspell}{jspell}{C}{support/jspell}</p>
-
- <p><b>jspell</b> is an MS-DOS spellchecker. It includes
- special support for TeX documents.</p>
-
- <p>\package{\TeX{}Tools}{textools}{}{support/kamal}</p>
-
- <p>The <b>TeXTools</b> package includes several tools for
- manipulating TeX documents. <b>detex</b> strips TeX
- commands from a file. <b>texeqn</b> extracts displayed
- equations from a document. <b>texexpand</b> merges
- documents loaded with \input or \include into a single
- file. <b>texmatch</b> checks for matching delimiters.
- <b>texspell</b> uses <b>detex</b> to spellcheck the
- filtered version of a document.</p>
-
- <p>\package{LaCheck}{lacheck}{C}{support/lacheck}</p>
-
- <p><b>LaCheck</b> reads a LaTeX document and reports any
- syntax errors it finds. This is faster than running the
- document through TeX if you are only interested in finding
- TeXnical mistakes.</p>
-
- <p>
- \package{\LaTeX2HTML}{latex2html}{}{support/latex2html}</p>
-
- <p>Converts LaTeX documents into HTML documents, suitable
- for browsing with a WWW browser. Many complex document
- elements are handled automatically.</p>
-
- <p>\package{\LaTeX{}Mk}{latexmk}{}{support/latexmk}</p>
-
- <p>LaTeXMk is a <b>Perl</b> script that attempts to
- determine what operations need to be performed on a
- document to produce a complete <tt>DVI</tt> file. LaTeXMk
- runs LaTeX, BibTeX, etc. until a complete document has been
- built.</p>
-
- <p>\package{lgrind}{lgrind}{}{support/lgrind}</p>
-
- <p><b>lgrind</b> formats program sources using LaTeX.
- Syntactic elements are identified by typographic changes in
- the printed sources.</p>
-
- <p>\package{LSEdit}{}{}{support/lsedit}</p>
-
- <p>This is an add-on package for the VAX/VMS Language
- Sensitive Editor (<b>LSEDI</b>). It provides an editing
- environment for LaTeX documents.</p>
-
- <p>\package{make\_\hskip.25pt
- latex}{make\_latex}{}{support/make\_latex}</p>
-
- <p>Provides a set of <b>make</b> rules for LaTeX
- documents.</p>
-
- <p>\package{MakeProg}{makeprog}{Web}{support/makeprog}</p>
-
- <p><b>MakeProg</b> is a system for doing Literate
- Programming in TeX. It provides a mechanism for combining
- documentation with TeX macros. Donald Knuth's original
- articles on Literate Programming are included with the
- documentation.</p>
-
- <p>\package{MathPad}{mathpad}{}{support/mathpad}</p>
-
- <p>MathPad is an X11 editor for TeX sources. It was not
- available (or known to me) in time for review in this
- edition of <span class="emphasis"><em>Making TeX
- Work</em></span>.</p>
-
- <p>\package{MC\TeX}{}{tex}{support/mctex}</p>
-
- <p>A TeX macro package for pretty-printing <b>Lisp</b>
- code.</p>
-
- <p>\package{MEW\LaTeX}{}{}{support/mewltx}</p>
-
- <p>An extension to <b>microEMACS</b> for Windows. It
- provides a LaTeX editing environment that allows you to
- write, spellcheck, process, and view your document from
- within <b>microEMACS</b>.</p>
-
- <p>\package{MNU}{}{DOS}{support/mnu}</p>
-
- <p><b>MNU</b> is an MS-DOS menu system written with batch
- files. It was designed for running TeX but can be extended
- to other applications.</p>
-
- <p>\package{pbm2\TeX}{pbm2tex}{}{support/pbm2tex}</p>
-
- <p><b>pbm2TeX</b> converts PBM files into LaTeX
- <tt>picture</tt> environments. This provides a portable way
- to include bitmap images in documents. The documents take a
- long time to typeset, however, and may require a big
- TeX.</p>
-
- <p>\package{PCWri\TeX}{}{}{support/pcwritex}</p>
-
- <p>Adds TeX to <b>PC-Write</b> as a special kind of
- printer. Documents &#8220;printed&#8221; to the TeX printer
- can be processed with TeX to get typeset output.</p>
-
- <p>\package{PM\TeX}{pmtex}{}{support/pmtex}</p>
-
- <p>An OS/2 Presentation Manager application that provides a
- shell around common TeX-related activities (editing,
- TeXing, previewing, printing, etc.).</p>
-
- <p>\package{PP}{pp}{}{support/pp}</p>
-
- <p>A Pascal or Modula-2 pretty-printer. It translates code
- into a Plain TeX or LaTeX document. An MS-DOS executable is
- provided.</p>
-
- <p>\package{PS2EPS}{ps2eps}{c}{support/ps2eps}</p>
-
- <p>Attempts to convert PostScript output from other
- programs into encapsulated PostScript output suitable for
- including in TeX documents with <b>dvips</b>, for example.
- Support is included for converting output from <b>GEM</b>
- 3.0, <b>DrawPerfect</b> 1.1, <b>PSpice</b> 4.05,
- <b>OrCAD</b> 3.11, <b>PrintGL</b> 1.18, <b>Mathcad</b> 3.0,
- and <b>GNUPlot</b> 3.0.</p>
-
- <p>\package{PS Utils}{psbook, psselect, pstops, psnup,
- epsffit}{C}{support/psutils}</p>
-
- <p>A collection of utilities for transforming PostScript
- output files in various ways. <b>psbook</b> rearranges
- pages into signatures. <b>psselect</b> selects ranges of
- pages. <b>pstops</b> performs arbitrary rearrangement and
- selection of pages. <b>psnup</b> prints multiple pages on a
- single sheet of paper. <b>epsffit</b> rescales an
- encapsulated PostScript figure to fit within a specified
- bounding box. These programs can be used to rearrange the
- output from PostScript DVI drivers like <b>dvips</b>.</p>
-
- <p><b>PS Utils</b> also includes scripts for displaying
- character information and &#8220;fixing&#8221; PostScript
- output from other sources. (Some PostScript output is
- nonstandard and must be fixed-up before it can be used with
- the <b>PS Utils</b>.) These scripts are summarized in
- Table&#160;<a href="ch16.html#tab.psutils.scripts"
- title="Table&#160;16.3.&#160;Additional Scripts in PS Utils ">
- Table&#160;16.3</a>.</p>
-
- <div class="table">
- <a id="tab.psutils.scripts"
- name="tab.psutils.scripts"></a>
-
- <p class="title"><b>Table&#160;16.3.&#160;Additional
- Scripts in PS Utils</b></p>
-
- <table summary="Additional Scripts in PS Utils "
- border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">\bf Script</th>
-
- <th align="left">\bf Purpose</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">\it getafm</td>
-
- <td align="left">Retrieves font metrics from the
- printer</td>
- </tr>
-
- <tr>
- <td align="left">\it showchar</td>
-
- <td align="left">Prints a character and its
- metrics</td>
- </tr>
-
- <tr>
- <td align="left">\it fixfmps</td>
-
- <td align="left">Fixes output from
- <b>FrameMaker</b></td>
- </tr>
-
- <tr>
- <td align="left">\it fixwpps</td>
-
- <td align="left">Fixes output from
- <b>WordPerfect</b></td>
- </tr>
-
- <tr>
- <td align="left">\it fixwfwps</td>
-
- <td align="left">Fixes output from <b>Word</b> for
- Windows</td>
- </tr>
-
- <tr>
- <td align="left">\it fixmacps</td>
-
- <td align="left">Fixes Macintosh PostScript</td>
- </tr>
-
- <tr>
- <td align="left">\it fixpsditps</td>
-
- <td align="left">Fixes
- <b>Transcript</b><tt>psdit</tt> files</td>
- </tr>
-
- <tr>
- <td align="left">\it fixpspps</td>
-
- <td align="left">Fixes output from
- <b>PSPrint</b></td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>
- \package{rtf2\LaTeX}{rtf2latex}{C}{support/rtf2LaTeX}</p>
-
- <p>A conversion program to translate RTF sources into
- LaTeX.</p>
-
- <p>\package{rtf2\TeX}{rtf2tex}{C}{support/rtf2TeX}</p>
-
- <p>A conversion program to translate RTF sources into
- TeX.</p>
-
- <p>
- \package{RTF-to-\LaTeX}{rtflatex}{Pascal}{support/rtflatex}</p>
-
- <p>Another conversion program to translate RTF sources into
- LaTeX.</p>
-
- <p>\package{S2\LaTeX}{s2l}{C}{support/s2latex}</p>
-
- <p>A <b>Scribe</b>-to-LaTeX converter. Requires <b>lex</b>
- and <b>yacc</b> to compile.</p>
-
- <p>
- \package{Scheme\TeX}{schemetex}{C}{support/schemetex}</p>
-
- <p><b>SchemeTeX</b> provides support for Literate
- Programming in <b>Scheme</b>. <b>Lex</b> is required to
- build <b>SchemeTeX</b>.</p>
-
- <p>\package{\TeX{}OrTho}{texortho}{C}{support/spelchek}</p>
-
- <p><b>TeXOrTho</b> is a spellchecking filter for text
- files. It was designed for spellchecking TeX and LaTeX
- documents, but it is parameter-file driven so it may be
- possible to extend it to other formats.</p>
-
- <p>\package{Tek2EEPIC}{tek2eepic}{C}{support/tek2eepic}</p>
-
- <p>A filter for Tektronix 4015 escape sequences that allows
- graphics output designed for a Tektronix 4015 display to be
- included in a TeX document. The resulting <tt>DVI</tt> file
- must be processed by a DVI driver that recognizes the <span
- class="emphasis"><em>tpic</em></span> \special
- commands.</p>
-
- <p>\package{\TeX{}calc}{}{}{support/texcalc}</p>
-
- <p><b>TeXcalc</b> is an <b>InstaCalc</b> spreadsheet for
- calculating TeX typeface design sizes based upon
- magnification and scaling factors.</p>
-
- <p>
- \package{\TeXinfo{}2HTML}{texi2html}{Perl}{support/texi2html}</p>
-
- <p>Translates GNU TeXinfo sources into HTML.</p>
-
- <p>
- \package{\TeX{}i2roff}{texi2roff}{C}{support/texi2roff}</p>
-
- <p>This is a TeXinfo-to-<b>nroff</b> converter (although it
- should be possible to process most documents with
- <b>troff</b> as well).</p>
-
- <p>\package{\TeX{}it}{texit}{Perl}{support/texit}</p>
-
- <p>A <b>Perl</b> script for processing TeX documents
- intelligently.</p>
-
- <p>\package{texproc}{texproc}{C}{support/texproc}</p>
-
- <p><b>texproc</b> is a filter that inserts the output from
- a command into your document. This can be used, for
- example, to automatically insert the output from
- <b>GNUPlot</b> directly into your TeX document (assuming
- that you use one of the TeX-compatible output terminals in
- <b>GNUPlot</b>).</p>
-
- <p>\package{tgrind}{tgrind}{C}{support/tgrind}</p>
-
- <p><b>tgrind</b> is a source code pretty-printer modelled
- after the standard BSD unix <b>vgrind</b> utility. It
- produces a TeX or LaTeX document that typesets an
- attractive program listing from your source code.</p>
-
- <p>\package{tr2\LaTeX}{tr2latex}{C}{support/tr2latex}</p>
-
- <p>Translates <b>troff</b> sources into LaTeX.</p>
-
- <p>\package{tr2\TeX}{tr2tex}{C}{support/tr2tex}</p>
-
- <p>Translates <b>troff</b> sources into Plain TeX.</p>
-
- <p>\package{TRANSLIT}{translit}{C}{support/translit}</p>
-
- <p><b>TRANSLIT</b> transliterates ASCII character codes.
- Single characters can be translated into multiple
- characters and vice versa, in addition to simple
- permutations. This program allows files written in one
- national character set to be translated into another
- character set without losing characters or meaning.</p>
-
- <p>\package{TSpell}{tspell, chk,
- putback}{C}{support/tspell}</p>
-
- <p>A spellchecking filter for TeX documents. It strips TeX
- and LaTeX macros out of a document, runs the document
- through a spellchecker, and restores the TeX and LaTeX
- macros. It looks like it was designed for VAX machines.</p>
-
- <p>
- \package{umlaute}{umlaute}{\protect\TeX}{support/umlaute}</p>
-
- <p>A collection of style files for processing TeX documents
- with accented characters using machine-native character
- encodings. Support for the ISO standard character set (ISO
- Latin1) and the MS-DOS code page 437 character set is
- provided.</p>
-
- <p>\package{undump}{undump}{C}{support/undump}</p>
-
- <p><b>undump</b> combines a core dump and an executable
- program to build a new executable using the core dump to
- provide initial values for all of the program's static
- variables. One use of this program is to construct TeX
- executables with macro packages preloaded. This is
- unnecessary on most modern computers (they're fast enough
- to simply load the format files). <b>undump</b> is no
- longer a supported program.</p>
-
- <p>\package{untex}{untex}{C}{support/untex}</p>
-
- <p>Removes all LaTeX control sequences from a document. Can
- optionally remove arguments to control sequences, as well
- as all math-mode text. Replaces many accented characters
- with their IBM OEM character set equivalents.</p>
-
- <p>\package{VMSSpell}{vmsspell}{}{support/vmsspell}</p>
-
- <p>A VMS spellchecking tool. Distributed in a VMS-style
- archive package.</p>
-
- <p>\package{Vor\TeX}{}{Emacs lisp}{support/vortex}</p>
-
- <p>A GNU emacs editing mode for TeX documents. Also
- provides support for BibTeX databases.</p>
-
- <p>\package{windex}{windex}{C}{support/windex}</p>
-
- <p><b>windex</b> is an aid for building indexes in LaTeX
- documents. It modifies the LaTeX indexing macros to produce
- a different output format. The <b>windex</b> program can
- then sort the terms and construct an index for you.</p>
-
- <p>
- \package{WP2\protect\LaTeX}{wp2latex}{C/Pascal}{support/wp2latex-5_1}</p>
-
- <p>This program attempts to translate WordPerfect v5.1
- documents into LaTeX.</p>
-
- <p>\package{xet}{xet}{C}{support/xet}</p>
-
- <p>The <b>xet</b> program removes all commands and
- mathematical formulae from Plain TeX and LaTeX documents.
- <b>xet</b> has a number of options for handling different
- aspects of a document (such as accents and LaTeX
- environments) and claims to be useful as a simple syntax
- checker for TeX files.</p>
-
- <p>\package{xetal}{xetal}{C}{support/xetal}</p>
-
- <p>This is a more recent version of <b>xet</b>, described
- above.</p>
-
- <p>\package{xlatex}{xlatex}{C}{support/xlatex}</p>
-
- <p>An X11 Windows application that ties together several
- aspects of TeXing a document. It provides a &#8220;push
- button&#8221; interface to editing, processing, previewing,
- and printing your document.</p>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;15.&#160;TeX on the Macintosh"
- href="ch15.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Appendix&#160;A.&#160;Filename Extension Summary"
- href="apa.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Chapter&#160;15.&#160;TeX on
- the Macintosh&#160;</td>
-
- <td width="20%" align="center"><a
- title="Part&#160;III.&#160;A Tools Overview"
- href="pt03.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Appendix&#160;A.&#160;Filename Extension
- Summary</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/co01.html b/Master/texmf-doc/doc/english/make-tex-work/html/co01.html
deleted file mode 100644
index 58229bc7ad0..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/co01.html
+++ /dev/null
@@ -1,187 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Colophon</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="index.html" title="Making TeX Work" />
- <link rel="previous" href="bi01.html" title="Bibliography" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a title="Bibliography"
- href="bi01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Making TeX Work" href="index.html"><img
- src="figures/nav-up.png" alt="Up" border="0" />
- </a>&#160;<img src="figures/nav-xnext.png" alt="Next"
- border="0" /></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="colophon">
- <h2 class="title"><a id="colophon"
- name="colophon"></a>Colophon</h2>
-
- <p><span class="bold"><b>About this Book</b></span></p>
-
- <p>This is an <span class="emphasis"><em>alpha</em></span>
- edition of this book. This version may contain glaring
- inconsistencies, missing sections, and other misfeatures
- indicative of a &#8220;work in progress&#8221;.</p>
-
- <p><span class="bold"><b>About the Author</b></span></p>
-
- <p>Norm Walsh is a Production Tools Specialist at O'Reilly
- and Associates' Cambridge office. Before Norm joined ORA, he
- was a research assistant at the University of Massachusetts,
- Amherst where he earned his master's degree in computer
- science.</p>
-
- <p>Besides maintaining a number of TeX and font-related
- resources on the Net, Norm enjoys bicycling, herpetology,
- prestidigitation, and browsing record and book stores. Norm
- lives in Boxborough, MA with his wife Deborah, two cats, a
- box turtle, two toads, and two frogs.</p>
-
- <p><span class="bold"><b>Colophon</b></span></p>
-
- <p>Our look is the result of reader comments, our own
- experimentation, and feedback from distribution channels.</p>
-
- <p>Distinctive covers complement our distinctive approach to
- technical topics, breathing personality and life into
- potentially dry subjects. <span class="sc">UNIX</span> and
- its attendant programs can be unruly beasts. Nutshell
- Handbooks® help you tame them.</p>
-
- <p>The animal featured on the cover of <i>Making TeX Work</i>
- is the European garden spider. Garden spiders are orb
- weavers, known for their intricate orb-shaped webs. Web
- building is a complex process: support lines are constructed
- first; then the radial lines; and finally the spiraling
- strands are spun from the center outward. Without training
- from adults, even the tiniest just-hatched spiderlings are
- able to spin silk and weave webs. Another orb weaver, <span
- class="emphasis"><em>nephila</em></span>, builds an extremely
- thick and strong web, up to eight feet in diameter. People in
- Southeast Asia have found an interesting use for this
- spider's web&#8212;they bend a pliable stick into a loop and
- pass it through the large web, resulting in a surprisingly
- strong and effective fishing net!</p>
-
- <p>Spiders produce silk from glands called spinnerets. Orb
- weavers can have three or four pairs of these glands, each
- producing different textures of silk: non-stick silk for the
- radial web lines, and sticky silk for the spiraling strands.
- Some spiders even produce an ultraviolet silk to attract
- insects. Spider silk, a super protein that hardens as it is
- stretched from the spinnerets, may look delicate but it is
- unbelievably tough. The relative tension necessary to break
- it is far greater than for steel.</p>
-
- <p>When finished with the construction of its web, the garden
- spider will often go to the center, hang upside down, and
- wait for a flying or jumping insect to become ensnared.
- Having poor eyesight, orb weavers rely on a highly-developed
- sense of touch. When an insect because caught in th web and
- struggles, the spider is alerted by the vibrations. It rushes
- tout to secure its prey, usually wrapping it in silk. A
- poison is injected into the victim, paralyzing it and
- converting the contents of its body to a liquid. The spider
- returns later to insert its tube-like fangs and suck up its
- meal.</p>
-
- <p>The garden spider's profound sense of touch has another
- purpose: it provides male spiders with a channel to
- communicate with females. Before climbing onto the female's
- web, the male taps out a special message. Then he cautiously
- crawls toward his mate&#8212;a perilous task, for he is
- always in danger of being mistaken for prey. It is commonly
- thought that the female spider kills and eats the male after
- mating, but this is an exaggeration. The male, who stops
- eating during his mate-hunting ordeal, generally dies of
- malnourishment and exhaustion.</p>
-
- <p>Spiders are similar to, but not the same as insects. They
- belong to the class <span
- class="emphasis"><em>Arachnida</em></span>, named after
- Arachne, a maiden in Greek mythology. She defeated the
- goddess Athena in a weaving contest. In a fury of anger,
- Athena destroyed Arachne's weaving and beat the girl about
- the head. In utter disgrace, Arachne hanged herself. A
- regretful Athena changed Arachne into a spider so that she
- could weave forever.</p>
-
- <p>While they are certainly not going to win any popularity
- contests, spiders' insect-eating habits are extremely helpful
- to humans. Every year, billions of spiders do away with a
- large number of disease-carrying and crop-destroying insects.
- If every spider ate just one a day for a year, those insects,
- piled in one spot, would weigh as much as 50 million people.
- Spiders are, by far, the most important predator of insects
- in our world.</p>
-
- <p>Edie Freedman designed this cover and the entire UNIX
- bestiary that appears on other Nutshell Handbooks. The beasts
- themselves are adapted from nineteenth century engravings
- from the Dover Pictorial Archive. The cover layout was
- produced with QuarkXPress 3.1 using the ITC Garamond
- font.</p>
-
- <p>The inside layout was designed by Edie Freedman and
- implemented by Norm Walsh in TeX using the ITC Garamond font
- family. The figures (except those in chapter 6) were created
- in Aldus Freehand 3.1 by Chris Reilley. The colophon was
- written by Elaine and Michael Kalantarian.</p>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a title="Bibliography"
- href="bi01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;</td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Bibliography&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">&#160;</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/amspell.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/amspell.png
deleted file mode 100644
index 93178755a7b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/amspell.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/arab.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/arab.png
deleted file mode 100644
index 9276ca647d8..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/arab.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/badfont.err b/Master/texmf-doc/doc/english/make-tex-work/html/figures/badfont.err
deleted file mode 100644
index 01242196a7b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/badfont.err
+++ /dev/null
@@ -1,24 +0,0 @@
-This is emTeX (tex386), Version 3.141 [3c-beta8]
-**&lplain badfont
-(badfont.tex
-LaTeX Version 2.09 <25 March 1992>
-(d:\tex\latex\sty\article.sty
-Standard Document Style `article' <14 Jan 92>.
-(d:\tex\latex\sty\art10.sty)) (badfont.aux)
-! Font cmr/m/n/18 not found.
-extract@fontinfo ...@name space not found}
- fi
-extract@font ...fontinfo font@info 3<@nil
- csna...
-define@newfont ... endcsname extract@font
- fi e...
-pickup@font ...@name relax define@newfont
- fi
-p@selectfont ...ze endcsname }pickup@font
- font...
-<argument> reset@font Large
- bf
-...
-l.21 \section{First Section}
-
-?
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/bbox.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/bbox.png
deleted file mode 100644
index 9239fa11a6c..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/bbox.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/bezier.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/bezier.png
deleted file mode 100644
index 69136abd47c..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/bezier.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/caffeine.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/caffeine.png
deleted file mode 100644
index 479e1a7070c..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/caffeine.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/cover.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/cover.png
deleted file mode 100644
index d4595f75cdb..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/cover.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/eepic.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/eepic.png
deleted file mode 100644
index 6dac200314b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/eepic.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/eight.mf b/Master/texmf-doc/doc/english/make-tex-work/html/figures/eight.mf
deleted file mode 100644
index ea2f5ba3663..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/eight.mf
+++ /dev/null
@@ -1,19 +0,0 @@
-mode_setup;
-u# := 2mm#;
-define_pixels(u);
-
-beginchar("A", 8u#, 9u#, 5u#);
- z1 = ( 0u, 0u);
- z2 = ( 8u, 0u);
- z3 = ( 1u, 8u);
- z4 = ( 7u, 8u);
- pickup pencircle scaled 1u#;
- draw z4 .. z1 .. z2 .. z3 .. cycle;
- pickup pencircle scaled 3u#;
- drawdot z1;
- drawdot z2;
- drawdot z3;
- drawdot z4;
-endchar;
-
-\end \ No newline at end of file
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/epic.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/epic.png
deleted file mode 100644
index a384bb56398..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/epic.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/fi-ligs.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/fi-ligs.png
deleted file mode 100644
index 93b1612cf4a..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/fi-ligs.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/frog.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/frog.png
deleted file mode 100644
index 76c296ffa82..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/frog.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/g-h.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/g-h.png
deleted file mode 100644
index caa71c4adc8..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/g-h.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.1 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.1
deleted file mode 100644
index 10e335b5724..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.1
+++ /dev/null
@@ -1,40 +0,0 @@
-#! perl
-#
-# Usage: gs-eps epsfile <outputfile> <resolution> <device>
-#
-# Where: epsfile is the encapsulated postscript file
-# outputfile is the output file (the default name
-# is <basename epsfile>.<device>)
-# resolution is the output resolution (default=300)
-# device is the GS driver to use (default=pbm)
-
-($epsfile,$outputfile,$res,$device) = @ARGV;
-
-if (! $epsfile) {
- printf "Usage: gs-eps epsfile <outputfile> <resolution>";
- printf " <gsdriver>\n";
- printf "Note: parameters are positional. To specify a";
- printf " driver, you\n";
- printf "must also specify an outputfile and resolution.\n";
- exit 1;
- }
-
-$epsfile =~ tr/\\/\//; # translate \foo\bar -> /foo/bar
-
-if (! -r $epsfile) {
- printf "Cannot read file: $epsfile\n";
- exit 1;
- }
-
-if (! $res) { $res = 300 }
-if (! $device) { $device = "pbm" }
-
-if (! $outputfile ) {
- @pathname = split(/\//,$epsfile);
- $outputfile = $pathname[$#pathname];
- $outputfile =~ s/.eps$//;
- $outputfile = join(".", $outputfile, $device);
- }
-
-printf "Converting $epsfile to $outputfile at ${res}dpi...\n";
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.2 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.2
deleted file mode 100644
index 7ba4b721355..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/gs-eps.2
+++ /dev/null
@@ -1,41 +0,0 @@
-open (EPSFILE,$epsfile);
-
-undef $bbox;
-undef $showpg;
-while (<EPSFILE>) {
- $bbox = $_ if /\%\%\s*BoundingBox:\s*\d+\s+\d+\s+\d+\s+\d+/;
- $showpage = $_ if /showpage/;
- last if ($bbox && $showpage);
- }
-
-if (! $bbox) {
- printf "Cannot find a bounding box in $epsfile";
- exit 1;
- }
-
-$bbox =~ s/\D*//; # remove everything preceding the digits
-
-($llx,$lly,$urx,$ury) = split(/\s/,$bbox);
-
-$xsize = sprintf("%d", (($urx - $llx) * $res / 72) + 0.5);
-$ysize = sprintf("%d", (($ury - $lly) * $res / 72) + 0.5);
-
-printf "$llx neg $lly neg translate .gt. gs-eps-a.$$\n";
-printf "quit .gt. gs-eps-b.$$\n";
-
-if (! $showpg) {
- printf "showpage .gt. gs-eps-b.$$\n";
- printf "quit .gtgt. gs-eps-b.$$\n";
- }
-
-# join sillyness to keep the length of lines in the
-# script small enough to print in the book.
-$gscmd = join(" ", "gs -sDEVICE=$device",
- "-q -sOutputFile=$outputfile",
- "-g${xsize}x${ysize} -r$res",
- "gs-eps-a.$$ $epsfile -",
- ".lt. gs-eps-b.$$");
-
-printf "$gscmd\n";
-
-printf "rm -f gs-eps-a.$$ gs-eps-b.$$\n";
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/hebrew-sample.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/hebrew-sample.png
deleted file mode 100644
index cdffc323e6b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/hebrew-sample.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/jgenji.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/jgenji.png
deleted file mode 100644
index aed7ef606da..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/jgenji.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/lint.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/lint.png
deleted file mode 100644
index 2554447f0cc..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/lint.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/lithium.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/lithium.png
deleted file mode 100644
index fcecb0dc347..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/lithium.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.1 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.1
deleted file mode 100644
index e521a3b8f50..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.1
+++ /dev/null
@@ -1,6 +0,0 @@
-$ mf 'mode=localfont; \input eight'
-This is METAFONT, Version 2.71 (C version d)
-! I can't find file `mode=localfont.mf'.
-<*> mode=localfont
- ; \input eight
-Please type another input file name:
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.2 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.2
deleted file mode 100644
index c675a9ae738..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.2
+++ /dev/null
@@ -1,11 +0,0 @@
-$ mf '\input eight'
-This is METAFONT, Version 2.71 (C version d)
-(eight.mf
-! Value is too large (4097).
-<recently read> ;
-
-beginchar->...rdp:=(EXPR3);w:=hround(charwd*hppp);
- h:=vround(charht*hppp);d:=...
-l.5 beginchar("A", 8u#, 9u#, 5u#)
- ;
-?
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.3 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.3
deleted file mode 100644
index 65d8b4f38f0..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.3
+++ /dev/null
@@ -1,12 +0,0 @@
-$ mf '\mode=localfont \input eight'
-This is METAFONT, Version 2.71 (C version d)
-(eight.mf
->> unknown string mode_name0
-! Not a string.
-<to be read again>
- ;
-mode_setup->...nput "&mode)else:mode_name[mode]fi;
- if.unknown.mag:mag=1;fi.if...
-l.1 mode_setup
- ;
-?
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.4 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.4
deleted file mode 100644
index beb55d333fe..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.4
+++ /dev/null
@@ -1,12 +0,0 @@
-$ mf '\mode=localfont; mag=magstep(1) \input eight'
-Running MetaFont from /exp/rcf/share...
-This is METAFONT, Version 2.71 (C version d)
-(eight.mf
-! Extra tokens will be flushed.
-<to be read again>
- warningcheck
-mode_setup->warningcheck
- :=0;if.unknown.mode:mode=proof;fi.numeric.aspect_rat...
-l.1 mode_setup
- ;
-?
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.5 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.5
deleted file mode 100644
index 43aea3c7ffc..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.5
+++ /dev/null
@@ -1,6 +0,0 @@
-$ mf '\mode=localfont; \input eight'
-This is METAFONT, Version 2.71 (C version d)
-(eight.mf [65] )
-Font metrics written on eight.tfm.
-Output written on eight.300gf (1 character, 5444 bytes).
-Transcript written on eight.log.
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.6 b/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.6
deleted file mode 100644
index 2bc42d544f0..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mferr.6
+++ /dev/null
@@ -1,4 +0,0 @@
-$ mf '\mode=localfont; eight'
-This is METAFONT, Version 2.71 (C version d)
-
-*
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mozart.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/mozart.png
deleted file mode 100644
index 14b576a38aa..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/mozart.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-amt.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-amt.png
deleted file mode 100644
index bfca2fe30d8..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-amt.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-inf.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-inf.png
deleted file mode 100644
index e0aff2def97..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-inf.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-lol.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-lol.png
deleted file mode 100644
index a13d385c523..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-lol.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ltx.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ltx.png
deleted file mode 100644
index 23b583c291d..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ltx.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ptx.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ptx.png
deleted file mode 100644
index 5f480fffb90..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/perf-ptx.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pgenji.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/pgenji.png
deleted file mode 100644
index 031857f4efd..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pgenji.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pictex-example.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/pictex-example.png
deleted file mode 100644
index 9bc5ae06783..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pictex-example.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pictexex.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/pictexex.png
deleted file mode 100644
index 9bc5ae06783..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pictexex.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmc-sample.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmc-sample.png
deleted file mode 100644
index c89f1903daf..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmc-sample.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmcs-sample.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmcs-sample.png
deleted file mode 100644
index 687e2cbe691..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmcs-sample.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmj-sample.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmj-sample.png
deleted file mode 100644
index 41dcf6f31f1..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/pmj-sample.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/sample.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/sample.png
deleted file mode 100644
index 768583dc343..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/sample.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.03.png
deleted file mode 100644
index 7334208f9b3..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.04.png
deleted file mode 100644
index 396f34575cb..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.05.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.05.png
deleted file mode 100644
index 6a260c65b74..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.01.05.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.01.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.01.png
deleted file mode 100644
index bce3a64bead..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.01.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.02.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.02.png
deleted file mode 100644
index 601ac0fbb60..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.02.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.03.png
deleted file mode 100644
index 54ada26d77a..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.04.png
deleted file mode 100644
index e30cd30dae1..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.05.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.05.png
deleted file mode 100644
index d70f96f68ad..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.05.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.06.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.06.png
deleted file mode 100644
index 694a808c937..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.06.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.07.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.07.png
deleted file mode 100644
index 74531d7749c..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.07.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.08.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.08.png
deleted file mode 100644
index cecf1f94c5c..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.08.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.09.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.09.png
deleted file mode 100644
index 17bb3af1235..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.09.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.10.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.10.png
deleted file mode 100644
index 5daef5c96f9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.10.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.11.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.11.png
deleted file mode 100644
index 42f36aa3564..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.02.11.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.04.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.04.04.png
deleted file mode 100644
index 6a0bbdb8d73..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.04.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.04.png
deleted file mode 100644
index e69297e94e1..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.06.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.06.png
deleted file mode 100644
index b5b026e9ec9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.05.06.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.01.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.01.png
deleted file mode 100644
index 530759e7a3a..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.01.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.02.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.02.png
deleted file mode 100644
index 600ffb5bc61..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.02.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.03.png
deleted file mode 100644
index 3fb6821a15c..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.04.png
deleted file mode 100644
index a9e907586e0..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.05.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.05.png
deleted file mode 100644
index 06fc71848d6..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.05.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.06.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.06.png
deleted file mode 100644
index 507c9a42dc1..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.06.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.07.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.07.png
deleted file mode 100644
index 4387abe3f79..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.07.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.08.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.08.png
deleted file mode 100644
index e977c221c44..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.08.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.09.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.09.png
deleted file mode 100644
index 76c296ffa82..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.09.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.11.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.11.png
deleted file mode 100644
index 62f6aba41d1..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.11.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.12.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.12.png
deleted file mode 100644
index 35b1c89f30b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.12.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.13.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.13.png
deleted file mode 100644
index 45d2c1085ea..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.13.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.14.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.14.png
deleted file mode 100644
index 263bc7a1411..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.14.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.20.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.20.png
deleted file mode 100644
index 6afef50ec5f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.06.20.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.07.01.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.07.01.png
deleted file mode 100644
index f303e4156d0..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.07.01.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.08.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.08.03.png
deleted file mode 100644
index fa0c367eb24..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.08.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.01.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.01.png
deleted file mode 100644
index 6ff1c1ec782..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.01.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.02.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.02.png
deleted file mode 100644
index 58df0224e1f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.02.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.03.png
deleted file mode 100644
index 1102411266f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.04.png
deleted file mode 100644
index 6614ea3912b..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.05.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.05.png
deleted file mode 100644
index fa28961c414..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.05.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.06.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.06.png
deleted file mode 100644
index 9dfda0cefd3..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.06.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.07.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.07.png
deleted file mode 100644
index 55dc9b9c7bb..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.07.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.08.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.08.png
deleted file mode 100644
index 04c80e315dd..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.08.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.09.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.09.png
deleted file mode 100644
index 1beecc6f10a..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.09.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.10.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.10.png
deleted file mode 100644
index aecd009a70f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.10.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.11.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.11.png
deleted file mode 100644
index 399f09ca68c..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.11.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.12.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.12.png
deleted file mode 100644
index 4877acf713f..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.12.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.13.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.13.png
deleted file mode 100644
index 079a7b54faf..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.13.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.14.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.14.png
deleted file mode 100644
index b40c43f2a57..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.14.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.15.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.15.png
deleted file mode 100644
index e4362a8f3b9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.15.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.16.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.16.png
deleted file mode 100644
index cf1ff30acf0..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.16.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.17.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.17.png
deleted file mode 100644
index 05128392c97..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.09.17.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.01.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.01.png
deleted file mode 100644
index 3509192d3d7..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.01.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.02.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.02.png
deleted file mode 100644
index 89bff5c43b8..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.02.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.03.png
deleted file mode 100644
index 1ef84c323ff..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.12.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.01.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.01.png
deleted file mode 100644
index 80c64908d70..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.01.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.02.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.02.png
deleted file mode 100644
index 62d7aac9e69..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.02.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.03.png
deleted file mode 100644
index 92ff4140eae..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.04.png
deleted file mode 100644
index 25dbc639696..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.05.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.05.png
deleted file mode 100644
index 57c464c0aa2..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.14.05.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.01.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.01.png
deleted file mode 100644
index ad0bbedae03..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.01.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.02.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.02.png
deleted file mode 100644
index 1bd690e1398..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.02.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.03.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.03.png
deleted file mode 100644
index e70beb79290..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.03.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.04.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.04.png
deleted file mode 100644
index 5bf872d08b0..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.04.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.05.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.05.png
deleted file mode 100644
index d53a8a24af4..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/tex.15.05.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/troffvstex.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/troffvstex.png
deleted file mode 100644
index fa64d9cf8e4..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/troffvstex.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/two-rs.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/two-rs.png
deleted file mode 100644
index c814e1dda6e..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/two-rs.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/we-we.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/we-we.png
deleted file mode 100644
index 0bd677e26e1..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/we-we.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/figures/xypic-example.png b/Master/texmf-doc/doc/english/make-tex-work/html/figures/xypic-example.png
deleted file mode 100644
index 899f655e3e9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/figures/xypic-example.png
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/index.html b/Master/texmf-doc/doc/english/make-tex-work/html/index.html
deleted file mode 100644
index f452a53a723..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/index.html
+++ /dev/null
@@ -1,1956 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Making TeX Work</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="next" href="pr01.html"
- title="Forward to the SourceForge Edition" />
- </head>
-
- <body>
- <div class="book">
- <div class="titlepage">
- <div>
- <div class="mediaobject">
- <img src="figures/cover.png" align="left" />
- </div>
- </div>
-
- <div>
- <h1 class="title"><a id="id2788873"
- name="id2788873"></a>Making TeX Work</h1>
- </div>
-
- <div>
- <p class="titlepage-block"><span
- class="authorgroup">by&#160;NormanWalsh</span><br />
- <span class="isbn">ISBN: 156592-051-1
- (out-of-print)</span><br />
- <span class="version">Version 1.0.1</span><br />
- <span class="date">Updated: Fri, 23 Aug 2002</span></p>
-
- <p class="copyright"><a
- href="mtwcpyright.html">Copyright</a> © 1994 O'Reilly
- &amp; Associates, Inc. All rights reserved.</p>
- <br clear="all" />
- </div>
- <hr />
- </div>
-
- <div class="toc">
- <p><b>Table of Contents</b></p>
-
- <dl>
- <dt><a href="pr01.html">Forward to the SourceForge
- Edition</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="pr01.html#id2841267">Acknowledgments</a></dt>
- </dl>
- </dd>
-
- <dt><a href="pr02.html">Preface</a></dt>
-
- <dd>
- <dl>
- <dt><a href="pr02.html#sec.implementation">Why Read
- This Book?</a></dt>
-
- <dt><a href="pr02.html#id2788121">Scope of This
- Book</a></dt>
-
- <dt><a href="pr02.html#id2855196">Conventions Used in
- This Book</a></dt>
-
- <dt><a href="pr02.html#id2855490">How to Get
- TeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="pr02.html#id2855700">Where Are the
- Files?</a></dt>
-
- <dt><a href="pr02.html#id2855768">Getting
- Software Without FTP</a></dt>
-
- <dt><a
- href="pr02.html#sec.gettingexamples">Getting
- Examples From This Book</a></dt>
- </dl>
- </dd>
-
- <dt><a href="pr02.html#id2856562">Versions of
- TeX</a></dt>
-
- <dt><a href="pr02.html#id2856618">Implementations and
- Platforms</a></dt>
-
- <dd>
- <dl>
- <dt><a href="pr02.html#id2856757">UNIX</a></dt>
-
- <dt><a href="pr02.html#id2856866">MS-DOS</a></dt>
-
- <dt><a href="pr02.html#id2856997">OS/2</a></dt>
-
- <dt><a
- href="pr02.html#id2857046">Macintosh</a></dt>
- </dl>
- </dd>
-
- <dt><a href="pr02.html#id2857161">We'd Like to Hear
- From You</a></dt>
-
- <dt><a
- href="pr02.html#id2857251">Acknowledgments</a></dt>
- </dl>
- </dd>
-
- <dt>I. <a href="pt01.html">An Introduction to
- TeX</a></dt>
-
- <dd>
- <dl>
- <dt>1. <a href="ch01.html">The Big Picture</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch01.html#sec.texforbeginners">What
- Is TeX?</a></dt>
-
- <dt><a href="ch01.html#id2857628">TeX for
- Beginners</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch01.html#sec.tex.controlsequences">Boxes
- and Glue</a></dt>
-
- <dt><a href="ch01.html#id2858068">Control
- Sequences</a></dt>
-
- <dt><a
- href="ch01.html#sec.textformVSwordproc">Special
- Characters</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch01.html#id2859644">Text Formatting
- Versus Word Processing</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch01.html#sec.howtexworks">What
- About Desktop Publishing?</a></dt>
-
- <dt><a href="ch01.html#id2860232">What About
- troff?</a></dt>
-
- <dt><a href="ch01.html#id2860619">What About
- SGML?</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch01.html#id2860690">How TeX
- Works</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch01.html#subsubsec.runningtex">TeXing
- a Simple Document</a></dt>
-
- <dt><a href="ch01.html#id2861683">TeXing More
- Complex Documents</a></dt>
-
- <dt><a href="ch01.html#id2861875">Building a
- Table of Contents</a></dt>
-
- <dt><a href="ch01.html#id2861991">Figure
- References</a></dt>
-
- <dt><a href="ch01.html#id2862061">Indexes and
- Glossaries</a></dt>
-
- <dt><a
- href="ch01.html#id2862096">Bibliographies</a></dt>
-
- <dt><a href="ch01.html#id2862381">Special
- Things</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>2. <a href="ch02.html">Editing</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#sec.whatcando">What Can an
- Editor Do?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#sec.auctex">Quoting
- Automatically</a></dt>
-
- <dt><a href="ch02.html#id2862787">Matching
- Braces</a></dt>
-
- <dt><a href="ch02.html#id2862919">Inserting
- Common Control Sequences</a></dt>
-
- <dt><a href="ch02.html#id2862968">Running TeX
- Automatically</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2863045">GNU
- Emacs</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#id2863154">Starting
- TeX Mode</a></dt>
-
- <dt><a href="ch02.html#id2863366">Typing in
- Emacs</a></dt>
-
- <dt><a href="ch02.html#id2863418">Running TeX
- Automatically</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2863525">aucTeX</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch02.html#sec.multifile">Starting
- aucTeX</a></dt>
-
- <dt><a href="ch02.html#id2863748">Typing in
- aucTeX</a></dt>
-
- <dt><a href="ch02.html#id2865794">aucTeX
- Outline Mode</a></dt>
-
- <dt><a href="ch02.html#id2865831">Intelligent
- Paragraph Reformatting</a></dt>
-
- <dt><a href="ch02.html#id2865862">Multi-file
- Documents</a></dt>
-
- <dt><a href="ch02.html#sec.texcomp">Running
- TeX</a></dt>
-
- <dt><a href="ch02.html#id2866224">Finding
- Errors</a></dt>
- </dl>
- </dd>
-
- <dt><a
- href="ch02.html#id2866254">Multi-Edit</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#id2866322">Setting Up
- TeX Support</a></dt>
-
- <dt><a href="ch02.html#id2866543">Typing in
- Multi-Edit</a></dt>
-
- <dt><a href="ch02.html#id2866670">Running
- TeX</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2866742">Brief</a></dt>
-
- <dt><a
- href="ch02.html#id2866836">MicroEMACS</a></dt>
-
- <dt><a href="ch02.html#id2867057">epm: OS/2's
- Enhanced Editor</a></dt>
-
- <dt><a href="ch02.html#id2867165">Other
- Tools</a></dt>
-
- <dt><a href="ch02.html#id2867406">TeX as a
- Compiler</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#id2867481">Processing
- a Document</a></dt>
- </dl>
- </dd>
-
- <dt><a
- href="ch02.html#id2868148">Spellchecking</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch02.html#id2868250">ispell</a></dt>
-
- <dt><a
- href="ch02.html#id2868280">amSpell</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2868394">Revision
- Control</a></dt>
-
- <dt><a href="ch02.html#id2868511">TeX
- Shells</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch02.html#id2868544">TeXShell</a></dt>
-
- <dt><a
- href="ch02.html#id2868647">TeXPert</a></dt>
-
- <dt><a
- href="ch02.html#id2868748">4TeX</a></dt>
-
- <dt><a
- href="ch02.html#id2868860">PMTeX</a></dt>
-
- <dt><a
- href="ch02.html#id2868984">TeXit</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>3. <a href="ch03.html">Running TeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch03.html#run.sec.formatfiles">What
- Do You Run?</a></dt>
-
- <dt><a href="ch03.html#id2869278">What Files Does
- TeX Need?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch03.html#id2869610">Pool
- Files</a></dt>
-
- <dt><a href="ch03.html#id2869651">Format
- Files</a></dt>
-
- <dt><a href="ch03.html#sec.userfiles">User
- Files</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch03.html#sec.clineopts">The Command
- Line</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch03.html#sec.runtex.cmdcautions">Command-line
- Options</a></dt>
-
- <dt><a
- href="ch03.html#id2870602">Command-line
- Cautions</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch03.html#id2871334">TeX Without
- Options</a></dt>
-
- <dt><a href="ch03.html#sec.errors">What About
- Errors?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch03.html#sec.logfiles">Log
- Files</a></dt>
-
- <dt><a
- href="ch03.html#sec.qprompt">Interpreting TeX
- Error Messages</a></dt>
-
- <dt><a href="ch03.html#id2872461">Naming a
- File TeX Cannot Find</a></dt>
-
- <dt><a href="ch03.html#id2872549">Misspelling
- a Control Sequence Name</a></dt>
-
- <dt><a href="ch03.html#id2872653">Failure to
- Close an Environment</a></dt>
-
- <dt><a href="ch03.html#id2872844">Math
- Outside of Math Mode</a></dt>
-
- <dt><a href="ch03.html#id2873082">Missing
- Fonts</a></dt>
-
- <dt><a href="ch03.html#id2873273">Everything
- Else</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch03.html#id2873346">The Question
- Mark Prompt</a></dt>
- </dl>
- </dd>
-
- <dt>4. <a href="ch04.html">Macro Packages</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch04.html#macpack.sec.latexvslatexe">Installation:
- Making Format Files</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch04.html#id2874541">Hyphenation
- Patterns</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch04.html#id2874634">General-purpose
- Formats</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch04.html#id2874772">Plain
- TeX</a></dt>
-
- <dt><a href="ch04.html#id2875093">Extended
- Plain TeX</a></dt>
-
- <dt><a href="ch04.html#id2875359">LaTeX2e
- Versus LaTeX</a></dt>
-
- <dt><a
- href="ch04.html#sec.latexe">LaTeX2e</a></dt>
-
- <dt><a
- href="ch04.html#sec.latex">LaTeX</a></dt>
-
- <dt><a
- href="ch04.html#sec.texincolor">AMSTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2877047">AMSLaTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2877164">Lollipop</a></dt>
-
- <dt><a
- href="ch04.html#id2873910">TeXinfo</a></dt>
-
- <dt><a href="ch04.html#id2877747">Other
- Formats</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch04.html#id2878394">Special-purpose
- Formats</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch04.html#id2878827">SliTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2878922">FoilTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2878993">Seminar</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch04.html#id2879086">TeX in
- Color</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch04.html#id2879169">Setting Up
- Color</a></dt>
-
- <dt><a href="ch04.html#id2879595">Using
- Color</a></dt>
-
- <dt><a href="ch04.html#id2879708">Now I've
- Got Color, but I Need Black and
- White!</a></dt>
-
- <dt><a href="ch04.html#id2879774">Color Under
- LaTeX2e</a></dt>
-
- <dt><a href="ch04.html#id2879830">Color Is
- Subtle</a></dt>
-
- <dt><a href="ch04.html#id2879898">Further
- Reading</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>II. <a href="pt02.html">Elements of a Complex
- Document</a></dt>
-
- <dd>
- <dl>
- <dt>5. <a href="ch05.html">Fonts</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#sec.issueofsize">What TeX
- Needs To Know</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2880659">Selecting a
- Font in TeX</a></dt>
-
- <dt><a href="ch05.html#id2880773">Which
- Character Is Which?</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2880909">The Issue of
- Size</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch05.html#sec.gettingtfms">Expressing
- Design Size in TeX</a></dt>
-
- <dt><a href="ch05.html#id2881284">Expressing
- Magnification in TeX</a></dt>
-
- <dt><a href="ch05.html#id2881380">Standard
- Magnifications</a></dt>
-
- <dt><a href="ch05.html#id2881671">Where Do
- TFM Files Come From?</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#sec.nfss2">The New Font
- Selection Scheme</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch05.html#sec.fonts.defnfss2">Selecting
- Fonts with the New Font Selection
- Scheme</a></dt>
-
- <dt><a href="ch05.html#id2855857">Defining
- Fonts with NFSS2</a></dt>
-
- <dt><a href="ch05.html#id2884733">Storing
- Font Definitions</a></dt>
-
- <dt><a href="ch05.html#id2884863">Changing
- the Defaults</a></dt>
-
- <dt><a href="ch05.html#id2885098">NFSS
- Pitfalls</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2885459">PostScript
- Fonts Under NFSS</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2885510">Adjustments
- to Scale</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2885640">When Things Go
- Wrong</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2885669">When TeX
- Complains</a></dt>
-
- <dt><a href="ch05.html#id2885907">When the
- DVI Driver Complains</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2886211">Encoding
- Vectors</a></dt>
-
- <dt><a
- href="ch05.html#sec.fonts.virtualfonts">Virtual
- Fonts</a></dt>
-
- <dt><a href="ch05.html#sec.autofont">Automatic
- Font Generation by DVI Drivers</a></dt>
-
- <dt><a href="ch05.html#sec.t1fonts">Math Fonts in
- TeX</a></dt>
-
- <dt><a href="ch05.html#id2887790">Concrete
- Examples</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2887816">MetaFont
- Fonts</a></dt>
-
- <dt><a href="ch05.html#id2887929">PostScript
- Type 1 Fonts</a></dt>
-
- <dt><a href="ch05.html#id2890165">HP LaserJet
- Softfonts</a></dt>
-
- <dt><a href="ch05.html#id2890329">TrueType
- Fonts</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>6. <a href="ch06.html">Pictures and
- Figures</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#sec.devindrev">Different
- Kinds of Images</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#id2890411">Bitmapped
- Images</a></dt>
-
- <dt><a href="ch06.html#id2884033">Scalable
- Images</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2884144">Device
- Independence Revisited</a></dt>
-
- <dt><a href="ch06.html#sec.ptexpic">Using Only
- TeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#id2890867">Plain
- TeX</a></dt>
-
- <dt><a
- href="ch06.html#sec.pictures.latex">LaTeX</a></dt>
-
- <dt><a
- href="ch06.html#id2891692">PiCTeX</a></dt>
-
- <dt><a
- href="ch06.html#id2891884">XYPic</a></dt>
-
- <dt><a
- href="ch06.html#id2892057">DraTeX</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2892246">Using a Little
- Help</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch06.html#id2892297">MFPic</a></dt>
-
- <dt><a
- href="ch06.html#id2892403">Fig2MF</a></dt>
-
- <dt><a
- href="ch06.html#sec.tpic">MetaFont</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2892560">Using a Little
- More Help</a></dt>
-
- <dt><a
- href="ch06.html#sec.pictures.pstricks">PSTricks</a></dt>
-
- <dt><a
- href="ch06.html#id2892664">TeXdraw</a></dt>
-
- <dt><a href="ch06.html#id2892716">tpic</a></dt>
-
- <dt><a href="ch06.html#sec.scaleformat">Using a
- Lot of Help</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#id2892815">Electronic
- Cut-and-paste</a></dt>
-
- <dt><a href="ch06.html#id2893032">Scalable
- Image Formats</a></dt>
-
- <dt><a href="ch06.html#sec.incps">Bitmapped
- Image Formats</a></dt>
-
- <dt><a href="ch06.html#id2893872">Inserting
- PostScript Images into TeX</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#sec.picconv">Manipulating
- Images</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#sec.gs">Image
- Magick</a></dt>
-
- <dt><a
- href="ch06.html#id2895306">PBMplus</a></dt>
-
- <dt><a href="ch06.html#id2895807">xv</a></dt>
-
- <dt><a
- href="ch06.html#id2895932">xloadimage</a></dt>
-
- <dt><a href="ch06.html#id2896003">Image
- Alchemy</a></dt>
-
- <dt><a
- href="ch06.html#id2896234">ColorView</a></dt>
-
- <dt><a
- href="ch06.html#id2896325">Jpeg4</a></dt>
-
- <dt><a
- href="ch06.html#id2896400">pmjpeg</a></dt>
-
- <dt><a
- href="ch06.html#id2896523">txt2pcx</a></dt>
-
- <dt><a
- href="ch06.html#id2896564">Ghostscript</a></dt>
-
- <dt><a
- href="ch06.html#sec.screendump">GoScript</a></dt>
-
- <dt><a
- href="ch06.html#id2897312">hp2xx</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2897483">Image
- Editors</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch06.html#id2897734">xfig</a></dt>
-
- <dt><a
- href="ch06.html#id2897932">idraw</a></dt>
-
- <dt><a
- href="ch06.html#id2898057">tgif</a></dt>
-
- <dt><a
- href="ch06.html#id2898297">bitmap/pixmap</a></dt>
-
- <dt><a href="ch06.html#id2898403">Other
- Bitmap Editors</a></dt>
-
- <dt><a
- href="ch06.html#id2898442">texcad/xtexcad</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2898527">Screen
- Dumps</a></dt>
- </dl>
- </dd>
-
- <dt>7. <a href="ch07.html">International
- Considerations</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch07.html#sec.for.printing">Typesetting in
- Any Language</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch07.html#id2899289">Reading
- Input Files</a></dt>
-
- <dt><a href="ch07.html#id2900395">Changing
- the Rules</a></dt>
-
- <dt><a href="ch07.html#id2902005">Printing
- the Result</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch07.html#sec.babel">The Babel
- Styles</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch07.html#sec.babelfmt">Building
- Multilingual Babel Formats</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch07.html#sec.asciijtex">TeX
- Pitfalls</a></dt>
-
- <dt><a href="ch07.html#id2903161">Very Complex
- Languages</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch07.html#id2903174">Japanese</a></dt>
-
- <dt><a
- href="ch07.html#id2903882">Chinese</a></dt>
-
- <dt><a
- href="ch07.html#id2903985">Arabic</a></dt>
-
- <dt><a
- href="ch07.html#id2904076">Hebrew</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>8. <a href="ch08.html">Printing</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#sec.printing">Printing
- Fonts</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#sec.bitfonts">Built-in
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2904946">External
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2905223">Bitmapped
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2905872">Scalable
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2905916">Font
- Printing Pitfalls</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch08.html#id2906078">Printing
- Pictures and Figures</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#id2906166">Unsolvable
- Problems</a></dt>
-
- <dt><a href="ch08.html#id2906292">Solvable
- Problems</a></dt>
-
- <dt><a href="ch08.html#id2906405">Pictures
- Using Only TeX</a></dt>
-
- <dt><a href="ch08.html#id2906432">MetaFont
- Figures</a></dt>
-
- <dt><a href="ch08.html#id2906500">Scalable
- Images</a></dt>
-
- <dt><a href="ch08.html#id2906554">Bitmap
- Images</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch08.html#id2906581">Selected
- Drivers</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#id2906990">emTeX
- Drivers</a></dt>
-
- <dt><a
- href="ch08.html#id2907474">dvilj2</a></dt>
-
- <dt><a
- href="ch08.html#id2907508">dvips</a></dt>
-
- <dt><a
- href="ch08.html#sec.pr.dvilaserhp">DVILASER/HP</a></dt>
-
- <dt><a
- href="ch08.html#sec.pr.dvilaserps">DVILASER/PS</a></dt>
-
- <dt><a href="ch08.html#id2909658">PTI
- Laser/HP and PTI Jet</a></dt>
-
- <dt><a href="ch08.html#id2909924">PTI
- Laser/PS</a></dt>
-
- <dt><a
- href="ch08.html#id2910137">dvipsone</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>9. <a href="ch09.html">Previewing</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch09.html#sec.ghostscript">Previewing Under
- X11</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch09.html#id2911502">Previewing
- with xdvi</a></dt>
-
- <dt><a href="ch09.html#id2911812">Previewing
- with \xtex</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch09.html#id2912002">Previewing with
- Ghostscript</a></dt>
-
- <dt><a href="ch09.html#id2912205">Previewing with
- emTeX</a></dt>
-
- <dt><a href="ch09.html#id2912806">Previewing with
- dvivga</a></dt>
-
- <dt><a href="ch09.html#sec.arb.preview">TeX
- Preview</a></dt>
-
- <dt><a href="ch09.html#id2913678">dvideo</a></dt>
-
- <dt><a href="ch09.html#id2913841">PTI
- View</a></dt>
-
- <dt><a href="ch09.html#id2914028">Previewing
- Under Windows</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch09.html#id2914065">dvimswin</a></dt>
-
- <dt><a
- href="ch09.html#id2914192">dviwin</a></dt>
-
- <dt><a
- href="ch09.html#id2914502">wdviwin</a></dt>
-
- <dt><a
- href="ch09.html#id2914603">DVIWindo</a></dt>
- </dl>
- </dd>
-
- <dt><a
- href="ch09.html#sec.preview.tty">Previewing on a
- TTY</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch09.html#id2915377">dvi2tty</a></dt>
-
- <dt><a
- href="ch09.html#id2915519">dvgt/dvitovdu</a></dt>
-
- <dt><a
- href="ch09.html#id2915747">crudetype</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>10. <a href="ch10.html">Online
- Documentation</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch10.html#id2916146">Something Is
- Lost</a></dt>
-
- <dt><a
- href="ch10.html#id2916199">TeXinfo</a></dt>
-
- <dt><a
- href="ch10.html#id2916555">\LaTeX2HTML</a></dt>
-
- <dt><a
- href="ch10.html#id2916701">LameTeX</a></dt>
-
- <dt><a
- href="ch10.html#id2917217">latex2hy</a></dt>
-
- <dt><a href="ch10.html#id2917348">detex</a></dt>
-
- <dt><a
- href="ch10.html#id2917381">dvispell</a></dt>
- </dl>
- </dd>
-
- <dt>11. <a href="ch11.html">Introducing
- MetaFont</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch11.html#sec.mf.gettingstarted">What to
- Run?</a></dt>
-
- <dt><a href="ch11.html#id2918131">What Files Does
- MetaFont Need?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch11.html#id2918156">Pool
- Files</a></dt>
-
- <dt><a href="ch11.html#id2918200">Base
- Files</a></dt>
-
- <dt><a href="ch11.html#id2918279">MetaFont
- Programs</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch11.html#id2918336">Command-line
- Options</a></dt>
-
- <dt><a href="ch11.html#id2918545">Building a Base
- File</a></dt>
-
- <dt><a href="ch11.html#sec.buildfont">Running
- MetaFont</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch11.html#id2918826">Picking a
- Mode</a></dt>
-
- <dt><a href="ch11.html#id2919066">Selecting a
- Size</a></dt>
-
- <dt><a href="ch11.html#id2919175">Making a GF
- Font</a></dt>
-
- <dt><a href="ch11.html#id2919378">Making a PK
- Font</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch11.html#id2919679">What About
- Errors?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch11.html#id2920144">Other
- Errors</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch11.html#id2920215">Output at Very
- High Resolutions</a></dt>
-
- <dt><a href="ch11.html#id2920252">Output at Very
- Low Resolutions</a></dt>
- </dl>
- </dd>
-
- <dt>12. <a href="ch12.html">Bibliographies, Indexes,
- and Glossaries</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch12.html#sec.indexeslooklike">BibTeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch12.html#id2920526">How BibTeX
- Works</a></dt>
-
- <dt><a href="ch12.html#id2920800">Building a
- Bibliography Database</a></dt>
-
- <dt><a
- href="ch12.html#id2921724">Bibliography
- Styles</a></dt>
-
- <dt><a
- href="ch12.html#id2922224">Bibliography
- Database Tools</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch12.html#id2923157">Tib</a></dt>
-
- <dt><a href="ch12.html#id2923378">Making
- Indexes</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch12.html#id2923569">Index
- Entries</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch12.html#id2923830">Index
- Format</a></dt>
-
- <dt><a href="ch12.html#id2923963">Special-purpose
- styles</a></dt>
-
- <dt><a href="ch12.html#id2924031">Making
- Glossaries</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>III. <a href="pt03.html">A Tools Overview</a></dt>
-
- <dd>
- <dl>
- <dt>13. <a href="ch13.html">Non-commercial
- Environments</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch13.html#free.web">Web2C</a></dt>
-
- <dt><a
- href="ch13.html#sec.emtex.testinstall">emTeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch13.html#id2925718">Where to
- Start</a></dt>
-
- <dt><a href="ch13.html#id2925747">Unpacking
- the Archives</a></dt>
-
- <dt><a href="ch13.html#id2925984">Setting Up
- the Environment</a></dt>
-
- <dt><a href="ch13.html#id2926107">Testing the
- Installation</a></dt>
-
- <dt><a
- href="ch13.html#sec.emtex.smaller">Installing
- Fonts</a></dt>
-
- <dt><a href="ch13.html#id2926788">Making
- emTeX Smaller</a></dt>
-
- <dt><a href="ch13.html#id2928367">Basic
- Customization</a></dt>
-
- <dt><a href="ch13.html#id2929307">Installing
- the Beta Test Versions of emTeX</a></dt>
-
- <dt><a
- href="ch13.html#sec.emtex.autofont">Running
- emTeX 386 in Windows</a></dt>
-
- <dt><a href="ch13.html#id2929946">Automatic
- Font Generation with emTeX</a></dt>
-
- <dt><a
- href="ch13.html#sec.netemtex">Installing
- emTeX on a Network</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch13.html#id2930222">texas</a></dt>
-
- <dt><a href="ch13.html#id2930652">sbTeX</a></dt>
-
- <dt><a href="ch13.html#id2931076">gTeX</a></dt>
- </dl>
- </dd>
-
- <dt>14. <a href="ch14.html">Commercial
- Environments</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch14.html#sec.com.turbo">µTeX by
- ArborText</a></dt>
-
- <dt><a href="ch14.html#id2931589">\yyTeX</a></dt>
-
- <dt><a
- href="ch14.html#id2931820">Textures</a></dt>
-
- <dt><a
- href="ch14.html#id2931894">TurboTeX</a></dt>
-
- <dt><a href="ch14.html#sec.pctex">PCTeX</a></dt>
-
- <dt><a href="ch14.html#sec.pctexforwin">PCTeX For
- Windows</a></dt>
-
- <dt><a href="ch14.html#id2933148">Scientific
- Word</a></dt>
- </dl>
- </dd>
-
- <dt>15. <a href="ch15.html">TeX on the
- Macintosh</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch15.html#sec.Excalibur">CMacTeX</a></dt>
-
- <dt><a
- href="ch15.html#id2934116">DirectTeX</a></dt>
-
- <dt><a href="ch15.html#id2934176">OzTeX</a></dt>
-
- <dt><a
- href="ch15.html#id2934618">Textures</a></dt>
-
- <dt><a href="ch15.html#id2935013">Other
- Tools</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch15.html#id2935026">Alpha</a></dt>
-
- <dt><a
- href="ch15.html#id2935128">BBEdit</a></dt>
-
- <dt><a href="ch15.html#sec.bsrtools">BSR Font
- Tools</a></dt>
-
- <dt><a
- href="ch15.html#id2935468">Excalibur</a></dt>
-
- <dt><a
- href="ch15.html#id2935534">HyperBibTeX</a></dt>
-
- <dt><a
- href="ch15.html#id2935646">MacGS</a></dt>
-
- <dt><a
- href="ch15.html#id2935708">dvidvi</a></dt>
-
- <dt><a
- href="ch15.html#id2935748">MacDVIcopy</a></dt>
-
- <dt><a
- href="ch15.html#id2935800">MacBibTeX</a></dt>
-
- <dt><a
- href="ch15.html#id2935830">MacMakeIndex</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>16. <a href="ch16.html">TeX Utilities</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch16.html#id2936355">List of
- Tools</a></dt>
- </dl>
- </dd>
-
- <dt>A. <a href="apa.html">Filename Extension
- Summary</a></dt>
-
- <dt>B. <a href="apb.html">Font Samples</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apb.html#id2941555">Font
- Encodings</a></dt>
-
- <dt><a href="apb.html#id2945478">Font
- Samples</a></dt>
- </dl>
- </dd>
-
- <dt>C. <a href="apc.html">Resources</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apc.html#id2943524">TUG: The TeX
- Users Group</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apc.html#id2946099">Other User
- Groups</a></dt>
- </dl>
- </dd>
-
- <dt><a href="apc.html#id2946152">TeX
- Software</a></dt>
-
- <dt><a href="apc.html#id2946301">TeX
- Shells</a></dt>
-
- <dt><a href="apc.html#id2946342">Editors</a></dt>
-
- <dt><a href="apc.html#id2946460">Macro Packages
- (Formats)</a></dt>
-
- <dt><a href="apc.html#id2946539">Styles and
- Macros</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apc.html#id2946714">Styles That
- Produced This Book</a></dt>
- </dl>
- </dd>
-
- <dt><a
- href="apc.html#id2946829">Utilities</a></dt>
-
- <dt><a
- href="apc.html#id2948003">Miscellaneous</a></dt>
- </dl>
- </dd>
-
- <dt>D. <a href="apd.html">Long Examples</a></dt>
-
- <dt>E. <a href="ape.html">GNU Free Documentation
- License</a></dt>
-
- <dd>
- <dl>
- <dt>0. <a
- href="ape.html#id2948209">PREAMBLE</a></dt>
-
- <dt>1. <a href="ape.html#id2948100">APPLICABILITY
- AND DEFINITIONS</a></dt>
-
- <dt>2. <a href="ape.html#id2948673">VERBATIM
- COPYING</a></dt>
-
- <dt>3. <a href="ape.html#id2948707">COPYING IN
- QUANTITY</a></dt>
-
- <dt>4. <a
- href="ape.html#id2948791">MODIFICATIONS</a></dt>
-
- <dt>5. <a href="ape.html#id2949025">COMBINING
- DOCUMENTS</a></dt>
-
- <dt>6. <a href="ape.html#id2949073">COLLECTIONS
- OF DOCUMENTS</a></dt>
-
- <dt>7. <a href="ape.html#id2949112">AGGREGATION
- WITH INDEPENDENT WORKS</a></dt>
-
- <dt>8. <a
- href="ape.html#id2949149">TRANSLATION</a></dt>
-
- <dt>9. <a
- href="ape.html#id2949177">TERMINATION</a></dt>
-
- <dt>10. <a href="ape.html#id2949201">FUTURE
- REVISIONS OF THIS LICENSE</a></dt>
-
- <dt><a href="ape.html#id2948479">How to use this
- License for your documents</a></dt>
- </dl>
- </dd>
-
- <dt><a href="bi01.html">Bibliography</a></dt>
- </dl>
- </dd>
- </dl>
- </div>
-
- <div class="list-of-figures">
- <p><b>List of Figures</b></p>
-
- <dl>
- <dt>1.1. <a href="ch01.html#fig.charbox">The Letters g
- and h inside their boxes.</a></dt>
-
- <dt>1.2. <a href="ch01.html#id2860574">Example figure
- produced by both TeX and troff</a></dt>
-
- <dt>1.3. <a href="ch01.html#fig.wholesimple">A high-level
- view of TeX</a></dt>
-
- <dt>1.4. <a href="ch01.html#fig.wholething">High-level
- view of TeX including more detail</a></dt>
-
- <dt>1.5. <a href="ch01.html#fig.texcmplx">TeXing a More
- Complex Document</a></dt>
-
- <dt>2.1. <a href="ch02.html#fig.meextsetup">Extension
- setup in Multi-Edit</a></dt>
-
- <dt>2.2. <a href="ch02.html#fig.melatexcmp">LaTeX as a
- compiler in Multi-Edit</a></dt>
-
- <dt>2.3. <a href="ch02.html#fig.editing.mew">Editing a
- file with MicroEMACS</a></dt>
-
- <dt>2.4. <a href="ch02.html#fig.winhelp">Microsoft
- Windows online help for LaTeX</a></dt>
-
- <dt>2.5. <a href="ch02.html#fig.editing.epm">Editing a
- TeX document with epm under OS/2</a></dt>
-
- <dt>2.6. <a href="ch02.html#fig.mespell">Edit settings
- control word delimiters</a></dt>
-
- <dt>2.7. <a href="ch02.html#fig.amspell">Spellchecking a
- document with amSpell</a></dt>
-
- <dt>2.8. <a
- href="ch02.html#fig.texshell">TeXShell</a></dt>
-
- <dt>2.9. <a href="ch02.html#fig.texpert">TeXPert</a></dt>
-
- <dt>2.10. <a href="ch02.html#fig.fourtex">4TeX</a></dt>
-
- <dt>2.11. <a href="ch02.html#fig.pmtex">PMTeX</a></dt>
-
- <dt>2.12. <a href="ch02.html#fig.texit">TeXit</a></dt>
-
- <dt>4.1. <a href="ch04.html#fig.sampresults">Sample
- page</a></dt>
-
- <dt>4.2. <a href="ch04.html#ex.sampplaintex">Plain TeX
- Input</a></dt>
-
- <dt>4.3. <a href="ch04.html#fig.samplatex2e">LaTeX2e
- Input</a></dt>
-
- <dt>4.4. <a href="ch04.html#fig.samplatex">LaTeX Input
- File</a></dt>
-
- <dt>4.5. <a href="ch04.html#ex.sampamstex">AMSTeX Input
- File</a></dt>
-
- <dt>4.6. <a href="ch04.html#fig.amsresults">AMS sample
- page</a></dt>
-
- <dt>4.7. <a href="ch04.html#ex.samplollipop">Lollipop
- Input File</a></dt>
-
- <dt>4.8. <a href="ch04.html#ex.infinp">TeXinfo
- Input</a></dt>
-
- <dt>4.9. <a href="ch04.html#fig.infex">TeXinfo sample
- page</a></dt>
-
- <dt>4.10. <a href="ch04.html#fig.infinf">Online
- documentation produced by MakeInfo</a></dt>
-
- <dt>4.11. <a href="ch04.html#fig.caffeine">Caffeine by
- ChemTeX</a></dt>
-
- <dt>4.12. <a href="ch04.html#fig.caffeine-source">The
- ChemTeX Source for Caffeine</a></dt>
-
- <dt>4.13. <a href="ch04.html#fig.lithium">A lithium
- cation rendered by ChemStruct</a></dt>
-
- <dt>4.14. <a href="ch04.html#fig.lithium-source">The
- ChemStruct Source for the Lithium Cation</a></dt>
-
- <dt>4.15. <a href="ch04.html#fig.mozart">A little
- Mozart&#8230;</a></dt>
-
- <dt>4.16. <a href="ch04.html#fig.mozart-source">The
- MusicTeX Source for Figure</a></dt>
-
- <dt>5.1. <a href="ch05.html#fig.filig">fi as two
- characters and as a ligature</a></dt>
-
- <dt>5.2. <a href="ch05.html#fig.kerning">We unkerned and
- kerned</a></dt>
-
- <dt>5.3. <a href="ch05.html#fig.Rs">The Computer Modern
- Roman letter R at 150pt: (a) from a 5pt design; (b) from
- a 17pt design</a></dt>
-
- <dt>5.4. <a href="ch05.html#fig.vfdiagram">How TeX uses a
- virtual font</a></dt>
-
- <dt>6.1. <a href="ch06.html#fig.plaintex">An example
- diagram in Plain TeX</a></dt>
-
- <dt>6.2. <a href="ch06.html#fig.latexpic">A parallelogram
- in LaTeX</a></dt>
-
- <dt>6.3. <a href="ch06.html#fig.epic">A figure created
- with (a) epic, and (b) eepic</a></dt>
-
- <dt>6.4. <a href="ch06.html#fig.bezier">Several bezier
- curves created with the LaTeX bezier style</a></dt>
-
- <dt>6.5. <a href="ch06.html#fig.pictex">Sample diagrams
- using PiCTeX</a></dt>
-
- <dt>6.6. <a href="ch06.html#fig.xypic">An XYPic
- diagram</a></dt>
-
- <dt>6.7. <a href="ch06.html#fig.dratex">An DraTeX
- diagram</a></dt>
-
- <dt>6.8. <a href="ch06.html#fig.epsbox">A PostScript
- bounding box example</a></dt>
-
- <dt>6.9. <a href="ch06.html#fig.psfigure">An example of
- an encapsulated figure</a></dt>
-
- <dt>6.10. <a href="ch06.html#fig.psfigurerot">Another
- example of an encapsulated figure (resized and
- rotated)</a></dt>
-
- <dt>6.11. <a href="ch06.html#fig.sd-xfig">Editing an
- image with xfig</a></dt>
-
- <dt>6.12. <a href="ch06.html#fig.sd-idraw">Editing an
- image with idraw</a></dt>
-
- <dt>6.13. <a href="ch06.html#fig.sd-tgif">Editing an
- image with tgif</a></dt>
-
- <dt>6.14. <a href="ch06.html#fig.xbitmap">An example of
- bitmap editing an icon</a></dt>
-
- <dt>6.15. <a href="ch06.html#fig.textshot">A text mode
- screen dump.</a></dt>
-
- <dt>7.1. <a href="ch07.html#fig.charmap">Character
- mapping example</a></dt>
-
- <dt>7.2. <a href="ch07.html#fig.pmj">Poor Man's
- Japanese</a></dt>
-
- <dt>7.3. <a href="ch07.html#fig.jemtex">\jemtex
- sample</a></dt>
-
- <dt>7.4. <a href="ch07.html#fig.flang.arab">Arabic text
- typeset with ArabTeX</a></dt>
-
- <dt>7.5. <a href="ch07.html#fig.hebrew">Hebrew</a></dt>
-
- <dt>8.1. <a href="ch08.html#fig.reschange">Resolution of
- the bitmap and the device changed simultaneously</a></dt>
-
- <dt>8.2. <a href="ch08.html#fig.sizechange">Resolution of
- the bitmap changed while device held constant</a></dt>
-
- <dt>8.3. <a href="ch08.html#fig.emdvi">Previewing and
- printing with emTeX</a></dt>
-
- <dt>9.1. <a href="ch09.html#fig.xdvi">How Previewing with
- xdvi Works</a></dt>
-
- <dt>9.2. <a href="ch09.html#fig.preview.xdvi">Previewing
- with xdvi</a></dt>
-
- <dt>9.3. <a href="ch09.html#fig.xtex">How Previewing with
- xtex Works</a></dt>
-
- <dt>9.4. <a href="ch09.html#fig.preview.xtex">Previewing
- with xtex</a></dt>
-
- <dt>9.5. <a
- href="ch09.html#fig.preview.ghostview">Previewing with
- Ghostview</a></dt>
-
- <dt>9.6. <a
- href="ch09.html#fig.preview.dviscr">Previewing with
- emTeX's dviscr</a></dt>
-
- <dt>9.7. <a href="ch09.html#fig.preview.dvipm">Previewing
- with emTeX's dvipm</a></dt>
-
- <dt>9.8. <a href="ch09.html#fig.dvivga.vga">Previewing
- with dvivga</a></dt>
-
- <dt>9.9. <a href="ch09.html#fig.tpre.vga">Previewing with
- ArborText's Previewer</a></dt>
-
- <dt>9.10. <a href="ch09.html#fig.ttexd.ega">Previewing
- with TurboTeX dvideo (using limited selection of
- fonts)</a></dt>
-
- <dt>9.11. <a href="ch09.html#fig.ptipreview">Previewing
- with Personal TeX's Previewer</a></dt>
-
- <dt>9.12. <a
- href="ch09.html#fig.preview.dvimswin">Previewing with
- dvimswin</a></dt>
-
- <dt>9.13. <a
- href="ch09.html#fig.preview.dviwin">Previewing with
- dviwin</a></dt>
-
- <dt>9.14. <a
- href="ch09.html#fig.preview.wttpreview">Previewing with
- TurboTeX's wdviwin</a></dt>
-
- <dt>9.15. <a
- href="ch09.html#fig.preview.dviwindo">Previewing with
- Y&amp;Y's DVIWindo</a></dt>
-
- <dt>9.16. <a
- href="ch09.html#fig.preview.dviwindo2">DVIWindo preview
- much enlarged</a></dt>
-
- <dt>9.17. <a href="ch09.html#fig.dvgttek">Previewing with
- dvgt under Tektronix 4010 emulation</a></dt>
-
- <dt>10.1. <a href="ch10.html#fig.on.infex">TeXinfo sample
- page</a></dt>
-
- <dt>10.2. <a href="ch10.html#fig.on.infinf">Online
- documentation produced by MakeInfo</a></dt>
-
- <dt>11.1. <a href="ch11.html#fig.eight">A figure eight
- created with MetaFont</a></dt>
-
- <dt>12.1. <a href="ch12.html#fig.bib.bibview">Editing an
- article entry with \program{bibview}</a></dt>
-
- <dt>12.2. <a href="ch12.html#fig.bib.xbibtex">Editing an
- article entry with \program{xbibtex}</a></dt>
-
- <dt>12.3. <a href="ch12.html#fig.bib.bibdb">Editing an
- article entry with \program{bibdb}</a></dt>
-
- <dt>14.1. <a href="ch14.html#fig.pcmenu">The PCTeX menu
- system</a></dt>
-
- <dt>14.2. <a href="ch14.html#fig.wpctex">PCTeX For
- Windows editing and previewing a LaTeX document</a></dt>
-
- <dt>14.3. <a href="ch14.html#fig.wpctextttotf">PCTeX For
- Windows TrueType font metric builder</a></dt>
-
- <dt>14.4. <a href="ch14.html#fig.sciword">Editing a
- document with Scientific Word</a></dt>
-
- <dt>14.5. <a
- href="ch14.html#fig.commercial.swpreview">Preview of the
- Scientific Word document shown in Figure</a></dt>
-
- <dt>15.1. <a href="ch15.html#fig.mac.textures">Editing,
- previewing, and typesetting in Textures</a></dt>
-
- <dt>15.2. <a href="ch15.html#fig.mac.alpha">Alpha editing
- the fonts chapter from this book</a></dt>
-
- <dt>15.3. <a
- href="ch15.html#fig.mac.bbedit">\program{BBEdit} editing
- the fonts chapter from this book</a></dt>
-
- <dt>15.4. <a
- href="ch15.html#fig.mac.Excalibur">\program{Excalibur}
- spellchecking the fonts chapter from this book</a></dt>
-
- <dt>15.5. <a href="ch15.html#fig.mac.hyperbib">The
- \program{Hyper\BibTeX} view of a bibliographic
- database</a></dt>
- </dl>
- </div>
-
- <div class="list-of-tables">
- <p><b>List of Tables</b></p>
-
- <dl>
- <dt>1. <a href="pr02.html#id2855538"></a></dt>
-
- <dt>1.1. <a href="ch01.html#tab.activechars">Special
- Characters in Plain TeX</a></dt>
-
- <dt>1.2. <a href="ch01.html#tab.acttype">How to Typeset
- Special Characters</a></dt>
-
- <dt>2.1. <a href="ch02.html#tbl.mathops">aucTeX Math
- Operators in Mathematics Minor-mode</a></dt>
-
- <dt>2.2. <a href="ch02.html#tab.modes">TeX Modes of
- Interaction</a></dt>
-
- <dt>3.1. <a href="ch03.html#id2871639"></a></dt>
-
- <dt>5.1. <a href="ch05.html#tab.fontshapeww">Standard
- Weight and Width Designations</a></dt>
-
- <dt>5.2. <a href="ch05.html#tab.fontshapeex">Weight and
- Width Are Combined to Form Series</a></dt>
-
- <dt>5.3. <a href="ch05.html#tab.fontshapeshape">Standard
- Abbreviations of Font Shape</a></dt>
-
- <dt>5.4. <a
- href="ch05.html#tab.nfss2.userlevel">User-level Font
- Selection Control Sequences in NFSS2</a></dt>
-
- <dt>5.5. <a href="ch05.html#tab.nfss2.encoding">Encoding
- Schemes Supported by NFSS2</a></dt>
-
- <dt>5.6. <a href="ch05.html#tab.nfssdefaults">Default
- Fonts</a></dt>
-
- <dt>5.7. <a href="ch05.html#id2888084"></a></dt>
-
- <dt>6.1. <a href="ch06.html#tab.manipover">Graphics
- Manipulation Packages</a></dt>
-
- <dt>6.2. <a href="ch06.html#tab.drawingtools">Graphics
- Editing Packages</a></dt>
-
- <dt>7.1. <a href="ch07.html#tab.accentedchar">Standard
- Control Sequences for Symbols from Other Character
- Sets</a></dt>
-
- <dt>7.2. <a href="ch07.html#tab.newaccentedchar">New
- Control Sequences Proposed by TWGMLC</a></dt>
-
- <dt>7.3. <a href="ch07.html#tab.langswitch">Language
- Switch Macros Proposed by TUG</a></dt>
-
- <dt>8.1. <a href="ch08.html#tab.drivers">Common DVI
- Drivers</a></dt>
-
- <dt>8.2. <a href="ch08.html#tab.dvilaserhp.util">Other
- \protect\dvilaserhp Utilities</a></dt>
-
- <dt>8.3. <a href="ch08.html#tab.dvilaserps.util">Other
- \protect\dvilaserps Utilities</a></dt>
-
- <dt>8.4. <a href="ch08.html#tab.dvipsone.util">Other
- dvipsone Utilities</a></dt>
-
- <dt>9.1. <a href="ch09.html#tab.previewers">Common
- Previewers</a></dt>
-
- <dt>9.2. <a href="ch09.html#tab.tpre.utils">TeX Preview
- Utilities</a></dt>
-
- <dt>9.3. <a href="ch09.html#tab.dviwindo">DVIWindo
- Utilities</a></dt>
-
- <dt>11.1. <a href="ch11.html#tab.mf.mfdistrib">Some
- Popular MetaFont Fonts on the CTAN Archives</a></dt>
-
- <dt>12.1. <a href="ch12.html#tab.bib.entries">Types of
- Entries with Required and Optional Fields</a></dt>
-
- <dt>13.1. <a href="ch13.html#tab.emtexfilesum">Summary of
- the \protect\emTeX Distribution</a></dt>
-
- <dt>13.2. <a href="ch13.html#tab.emtex.fontlibs">Fonts
- Libraries Available for \protect\emTeX on CTAN</a></dt>
-
- <dt>13.3. <a href="ch13.html#tab.emtexotherex">Other
- \protect\emTeX Executables</a></dt>
-
- <dt>13.4. <a href="ch13.html#tab.emtex.betasummary">The
- Beta Test Files for \protect\emTeX</a></dt>
-
- <dt>14.1. <a href="ch14.html#tab.turbotex">TurboTeX
- Programs</a></dt>
-
- <dt>14.2. <a
- href="ch14.html#tab.turbomf">Turbo\protect\TeX
- \protect\MF Programs</a></dt>
-
- <dt>15.1. <a href="ch15.html#tab.mac.cmacdist">Summary of
- the \protect\cmactex Distribution at CTAN</a></dt>
-
- <dt>15.2. <a href="ch15.html#tab.mac.oztexdist">Summary
- of the \protect\oztex Distribution at CTAN</a></dt>
-
- <dt>15.3. <a href="ch15.html#tab.mac.bsrtools">Font Tools
- in the BSR package</a></dt>
-
- <dt>16.1. <a href="ch16.html#tab.util.beebedr">The Public
- Doman DVI Driver Family</a></dt>
-
- <dt>16.2. <a href="ch16.html#tab.rtfxlate">RTF
- Translators</a></dt>
-
- <dt>16.3. <a
- href="ch16.html#tab.psutils.scripts">Additional Scripts
- in PS Utils</a></dt>
-
- <dt>B.1. <a href="apb.html#tab.cmrencode">The Computer
- Modern Roman Font Encoding</a></dt>
-
- <dt>B.2. <a href="apb.html#tab.cmmiencode">The Computer
- Modern Math Italic Font Encoding</a></dt>
-
- <dt>B.3. <a href="apb.html#tab.font.corkencoding">The
- Cork Font Encoding</a></dt>
-
- <dt>B.4. <a href="apb.html#tab.adbstdencode">The Adobe
- Standard Font Encoding</a></dt>
- </dl>
- </div>
-
- <div class="list-of-examples">
- <p><b>List of Examples</b></p>
-
- <dl>
- <dt>1.1. <a href="ch01.html#ex.csexample">An Example of a
- TeX Document</a></dt>
-
- <dt>1.2. <a href="ch01.html#ex.knuthbbl">A typical
- bibliography database entry</a></dt>
-
- <dt>2.1. <a href="ch02.html#ex.driver">A Simple Driver
- File</a></dt>
-
- <dt>2.2. <a href="ch02.html#ex.localvars">Local Variables
- in an Emacs Buffer</a></dt>
-
- <dt>2.3. <a href="ch02.html#ex.madeuperr">A Contrived
- Error</a></dt>
-
- <dt>2.4. <a href="ch02.html#ex.rcsmac">Revision Control
- Macros for TeX Documents Using RCS}</a></dt>
-
- <dt>3.1. <a href="ch03.html#ex.badfonttex">The Document
- BADFONT.TEX</a></dt>
-
- <dt>5.1. <a href="ch05.html#ex.logoshape">Font-shape
- Declaration with NFSS2</a></dt>
-
- <dt>5.2. <a href="ch05.html#ex.logoshape2">Font-shape
- declaration with NFSS2 (simplified)</a></dt>
-
- <dt>5.3. <a href="ch05.html#ex.pstotexfont">The
- PStoTeXfont script</a></dt>
-
- <dt>6.1. <a href="ch06.html#ex.plaintexm">The Input for
- the Plain TeX Diagram</a></dt>
-
- <dt>6.2. <a href="ch06.html#ex.latexpicsrc">The LaTeX
- Input for</a></dt>
-
- <dt>6.3. <a href="ch06.html#ex.epicsrc">The epic Input
- for</a></dt>
-
- <dt>6.4. <a href="ch06.html#ex.beziersrc">The Input
- for</a></dt>
-
- <dt>6.5. <a href="ch06.html#ex.pictexsrc">PiCTeX Input
- for</a></dt>
-
- <dt>6.6. <a href="ch06.html#ex.xypicsrc">The XYPic Input
- for</a></dt>
-
- <dt>6.7. <a href="ch06.html#ex.dratexsrc">The DraTeX
- Input for</a></dt>
-
- <dt>6.8. <a href="ch06.html#ex.gseps">Converting
- Encapsulated PostScript to a Bitmap with
- Ghostscript</a></dt>
-
- <dt>6.9. <a href="ch06.html#ex.texscreencapt">Script for
- Inserting a Captured Text Screen</a></dt>
-
- <dt>7.1. <a href="ch07.html#ex.usinglangs">{A Sample
- Multilingual Document Using English and French}</a></dt>
-
- <dt>10.1. <a href="ch10.html#ex.on.infinp">TeXinfo
- Commands</a></dt>
-
- <dt>11.1. <a href="ch11.html#ex.eightcode">The Code for
- the Figure Eight</a></dt>
-
- <dt>12.1. <a href="ch12.html#ex.bib.bibexample">A Sample
- BibTeX entry</a></dt>
-
- <dt>12.2. <a href="ch12.html#ex.tibdb">A Tib style
- database entry</a></dt>
-
- <dt>D.1. <a
- href="apd.html#ex.maketexpk">MakeTeXPK.pl</a></dt>
-
- <dt>D.2. <a
- href="apd.html#ex.maketextfm">MakeTeXTFM.pl</a></dt>
-
- <dt>D.3. <a href="apd.html#ex.dvidxx">dvidxx.btm</a></dt>
-
- <dt>D.4. <a href="apd.html#ex.makepk">makepk.btm</a></dt>
-
- <dt>D.5. <a
- href="apd.html#ex.encafmpl">enc-afm.pl</a></dt>
-
- <dt>D.6. <a
- href="apd.html#ex.textoxfont">TeXtoXfont</a></dt>
-
- <dt>D.7. <a
- href="apd.html#ex.pstoxfont">PStoXfont</a></dt>
-
- <dt>D.8. <a
- href="apd.html#ex.txt2verb">txt2verb.pl</a></dt>
- </dl>
- </div>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/mtw.css b/Master/texmf-doc/doc/english/make-tex-work/html/mtw.css
deleted file mode 100644
index 6fc8bbe2b08..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/mtw.css
+++ /dev/null
@@ -1,150 +0,0 @@
-/* CSS2 Stylesheet for _Making TeX Work_
- *
- * $Id: mtw.css,v 1.1 2002/08/23 14:31:13 nwalsh Exp $
- */
-
-.box { border: thin solid #7F7F7F;
- }
-
-DIV.example-output {
- padding-left: 15px;
- border-style: solid;
- border-width: 0px;
- border-left-width: 2px;
- border-color: black;
-}
-
-pre.screen {
- background: #E8E8E8;
-}
-
-pre.programlisting {
- background: #E8E8E8;
-}
-
-div.example-source {
- background: #E8E8E8;
-}
-
-p.publisher {
- text-align: center;
-}
-
-div.component-title {
- text-align: right;
-}
-
-h1,h2,h3,h4,h5,h6 {
- font-style: italic;
-}
-
-h1.label {
- font-size: 150pt;
- font-weight: normal;
- font-family: sans-serif;
- margin-bottom: 0px;
- padding-bottom: 0px;
- margin-top: 0px;
- padding-top: 0px;
-}
-
-div.component-title h1.title {
- font-family: sans-serif;
- margin-top: 0px;
- padding-top: 0px;
- margin-right: 20px;
- font-size: 36pt;
-}
-
-p.alpha-version {
- margin-top: 0px;
- padding-top: 0px;
-}
-
-hr.component-separator {
- height: 1px;
-}
-
-div.refentry div.titlepage {
- margin-left: 20px;
-}
-
-div.refentry div.titlepage h1.title {
- margin-left: -20px;
- margin-bottom: 0px;
- font-size: 36pt;
-}
-
-body {
- margin-top: 0px;
- padding-top: 0px;
- margin-left: 0px;
- margin-right: 0px;
- padding-left: 0px;
- padding-right: 0px;
-}
-
-div.navheader {
- padding-top: 2px;
- background-color: #c6bec6;
- padding-right: 2px;
- border-bottom-style: solid;
- border-bottom-width: 1px;
-}
-
-div.navfooter {
- background-color: #c6bec6;
- margin-bottom: 0px;
- padding-bottom: 0px;
- padding-left: 10px;
- padding-right: 10px;
- border-top-style: solid;
- border-top-width: 1px;
- padding-top: 2px;
-}
-
-div.copyrightfooter {
- background-color: #c6bec6;
- margin-top: 0px;
- padding-top: 0px;
- padding-left: 10px;
- padding-right: 10px;
- padding-bottom: 2px;
-}
-
-div.copyrightfooter p {
- margin-top: 0px;
- padding-top: 10px;
-}
-
-div.refentry,
-div.preface,
-div.chapter,
-div.appendix,
-div.reference,
-div.part,
-div.bibliography,
-div.glossary,
-div.index,
-div.colophon,
-div.legalnotice {
- margin-left: 10px;
- margin-right: 10px;
-}
-
-div.book {
- margin-left: 10px;
- margin-right: 10px;
- margin-top: 5px;
-}
-
-thead {
- background-color: black;
- color: white;
-}
-
-table,
-tbody,thead,tfoot,
-tr,td {
- border-color: #8F8F8F;
-}
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/mtwcpyright.html b/Master/texmf-doc/doc/english/make-tex-work/html/mtwcpyright.html
deleted file mode 100644
index 64fd10d21c2..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/mtwcpyright.html
+++ /dev/null
@@ -1,63 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Making TeX Work</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- </head>
-
- <body>
- <div class="legalnotice">
- <p><i>Making TeX Work</i>. Copyright © 1994 O'Reilly &amp;
- Associates, Inc. All rights reserved.</p>
-
- <p>Permission is granted to copy, distribute and/or modify
- this document under the terms of the GNU Free Documentation
- License, Version 1.1 or any later version published by the
- Free Software Foundation; with the Back-Cover Texts being <a
- href="#backcover" target="_top">Back Cover Text</a>. A copy
- of the license is included in <a href="ape.html"
- title="Appendix&#160;E.&#160;GNU Free Documentation License">Appendix&#160;E</a>.</p>
-
- <p>Nutshell Handbook, the Nutshell Handbook logo, and the
- O'Reilly logo are registered trademarks of O'Reilly &amp;
- Associates, Inc. The association between the image of a
- spider and the topic of TeX is a trademark of O'Reilly &amp;
- Associates, Inc. Java and all Java-based trademarks and logos
- are trademarks or registered trademarks of Sun Microsystems,
- Inc., in the United States and other countries. O'Reilly
- &amp; Associates, Inc. is independent of Sun
- Microsystems.</p>
-
- <p>Many of the designations used by manufacturers and sellers
- to distinguish their products are claimed as trademarks.
- Where those designations appear in this book, and O'Reilly
- &amp; Associates, Inc. was aware of a trademark claim, the
- designations have been printed in caps or initial caps. While
- every precaution has been taken in the preparation of this
- book, the publisher assumes no responsibility for errors or
- omissions, or for damages resulting from the use of the
- information contained herein.</p>
-
- <p><a id="backcover" name="backcover"></a><b>Back Cover
- Text:&#160;</b></p>
-
- <p>Visit O'Reilly on the Web at <a
- href="http://www.oreilly.com/"
- target="_top">www.oreilly.com</a>.</p>
- <br />
- <br />
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/pr01.html b/Master/texmf-doc/doc/english/make-tex-work/html/pr01.html
deleted file mode 100644
index 5f97e9f53b3..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/pr01.html
+++ /dev/null
@@ -1,130 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Forward to the SourceForge Edition</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="index.html" title="Making TeX Work" />
- <link rel="previous" href="index.html"
- title="Making TeX Work" />
- <link rel="next" href="pr02.html" title="Preface" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Making TeX Work" href="index.html"><img
- src="figures/nav-prev.png" alt="Prev" border="0" />
- </a>&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a>&#160;<a title="Preface"
- href="pr02.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="preface">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="id2788712"
- name="id2788712"></a>Forward to the SourceForge
- Edition</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- </div>
-
- <p>I wrote <i>Making TeX Work</i> in 1994. It has not been
- updated and is unquestionably out-of-date. In fact, the TeX
- sources are still in LaTeX 2.09.</p>
-
- <p>It is provided here for the benefit of those readers who
- would like to read it (it has been out of print for several
- years) or its TeX sources.</p>
-
- <p>I have no plans to update it.</p>
-
- <div class="important"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Important</h3>
-
- <p>The conversion from TeX to XML <span
- class="emphasis"><em>is not</em></span> complete. There are
- lots of TeXisms left in the XML version. And tables that
- haven't been converted. And figures that haven't been
- converted. And probably lots of other stuff. I do plan,
- over time, to fix those errors so that the XML sources are
- a reasonable reflection of the published book.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2841267"
- name="id2841267"></a>Acknowledgments</h2>
- </div>
- </div>
-
- <p>My thanks to Tim O'Reilly for agreeing to republish this
- book under the <a href="ape.html"
- title="Appendix&#160;E.&#160;GNU Free Documentation License">
- GNU Free Documentation License</a>.</p>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a title="Preface"
- href="pr02.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Making TeX Work&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">&#160;Preface</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/pr02.html b/Master/texmf-doc/doc/english/make-tex-work/html/pr02.html
deleted file mode 100644
index 9442b1401d9..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/pr02.html
+++ /dev/null
@@ -1,1296 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Preface</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="index.html" title="Making TeX Work" />
- <link rel="previous" href="pr01.html"
- title="Forward to the SourceForge Edition" />
- <link rel="next" href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Forward to the SourceForge Edition"
- href="pr01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Making TeX Work" href="index.html"><img
- src="figures/nav-up.png" alt="Up" border="0" />
- </a>&#160;<a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="preface">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="id2841290"
- name="id2841290"></a>Preface</h2>
- </div>
-
- <div>
- <p class="releaseinfo">$Revision: 1.1 $</p>
- </div>
-
- <div>
- <p class="pubdate">$Date: 2002/08/23 14:31:13 $</p>
- </div>
- </div>
-
- <p>TeX is a tool for creating professional quality, typeset
- pages of any kind. It is particularly good, perhaps
- unsurpassed, at typesetting mathematics<a id="id2841277"
- class="indexterm" name="id2841277"></a> <a id="id2841322"
- class="indexterm" name="id2841322"></a>; as a result, it is
- widely used in scientific writing. Some of its other
- features, like its ability to handle multiple languages<a
- id="id2787586" class="indexterm" name="id2787586"></a> <a
- id="id2787597" class="indexterm" name="id2787597"></a> in the
- same document and the fact that the content of a document
- (chapters, sections, equations, tables, figures, etc.) can be
- separated from its form (typeface, size, spacing,
- indentation, etc.) are making TeX more common outside of
- scientific and academic circles.</p>
-
- <p>Designed by Donald Knuth<a id="id2787617"
- class="indexterm" name="id2787617"></a> in the late 1970s,
- more than a decade of refinement has gone into the program
- called &#8220;TeX&#8221; today. The resulting system produces
- publication-quality output while maintaining portability
- across an extremely wide range of platforms.</p>
-
- <p>Remarkably, TeX is free. This fact, probably as much as
- any other, has contributed to the development of a complete
- &#8220;TeX system&#8221; by literally thousands of
- volunteers. TeX, the program, forms the core of this
- environment and is now supported by hundreds of tools.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a
- id="sec.implementation"
- name="sec.implementation"></a>Why Read This Book?</h2>
- </div>
- </div>
-
- <p>This book is for anyone who uses TeX. Novices will need
- at least one other reference, because this book does not
- describe the nuts and bolts of writing documents with TeX
- in any great detail.</p>
-
- <p>If you are new to TeX, there is much to learn. There are
- many books that describe how to use TeX. However, the focus
- of this book is mostly at a higher level. After digesting
- Chapter&#160;<a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a>,
- <span class="emphasis"><em><a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a></em></span>,
- you should be able to proceed through the rest of the book
- without much difficulty even if you have never seen TeX
- before. So, if you are a system administrator interested in
- learning enough about these programs to install and test
- them for your users, you should be all set. If you are
- interested in learning how to write documents with TeX,
- this book will be helpful, but it will not be wholly
- sufficient.</p>
-
- <p>Why do you need this book at all? Although many
- individual components of the TeX system are well
- documented, there has never before been a complete
- reference to the whole system. This book surveys the entire
- world of TeX software and helps you see how the various
- pieces are related.</p>
-
- <p>A functioning TeX system is really a large collection of
- programs that interact in subtle ways to produce a document
- that, when formatted by TeX, prints the output you want.
- All the different interactions that take place ultimately
- result in less work for you, the writer, even though it may
- seem like more work at first. Heck, it may <span
- class="emphasis"><em>be</em></span> more work at first, but
- in the long run, the savings are tremendous.</p>
-
- <p>Many books about TeX refer the reader to a &#8220;local
- guide&#8221; for more information about previewing and
- printing documents and what facilities exist for
- incorporating special material into documents (like special
- fonts and pictures and figures). In reality, very few local
- guides exist.</p>
-
- <p>The TeX environment is now mature and stable enough to
- support a more &#8220;global guide.&#8221; That is what
- this book attempts to be. It goes into detail about
- previewing and printing, about incorporating other fonts,
- about adding pictures and figures to your documents, and
- about many other things overlooked by other books.</p>
-
- <p>Because fonts play a ubiquitous role in typesetting,
- this book is also about MetaFont, the tool that Donald
- Knuth<a id="id2788111" class="indexterm"
- name="id2788111"></a> designed for creating fonts.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2788121"
- name="id2788121"></a>Scope of This Book</h2>
- </div>
- </div>
-
- <p>Here's how the book is laid out.</p>
-
- <p><span class="bold"><b>Part&#160;<a href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX">Part&#160;I</a>:
- <span class="emphasis"><em><a href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX">Part&#160;I</a></em></span></b></span>.</p>
-
- <p>Chapter&#160;<a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a>,
- <span class="emphasis"><em><a href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture">Chapter&#160;1</a></em></span>.
- If you don't know anything about TeX at all, this chapter
- will help you get started. If you're a system adminstrator
- charged with the task of installing and maintaining TeX
- tools, you'll get enough information to do the job.</p>
-
- <p>Chapter&#160;<a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a>,
- <span class="emphasis"><em><a href="ch02.html"
- title="Chapter&#160;2.&#160;Editing">Chapter&#160;2</a></em></span>.
- An overview of some environments that can make working with
- TeX documents easier. It describes some editors that
- &#8220;understand&#8221; TeX, how to integrate TeX into a
- &#8220;programmer's editor,&#8221; spellchecking, revision
- control, and other aspects of TeXnical editing.</p>
-
- <p>Chapter&#160;<a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a>,
- <span class="emphasis"><em><a href="ch03.html"
- title="Chapter&#160;3.&#160;Running TeX">Chapter&#160;3</a></em></span>.
- The mechanics of running TeX, the program. It discusses
- what things TeX needs to be able to run, how to start TeX,
- command-line options, leaving TeX, and recovery from
- errors.</p>
-
- <p>Chapter&#160;<a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a>,
- <span class="emphasis"><em><a href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages">Chapter&#160;4</a></em></span>.
- Overview of TeX macro packages. This chapter describes how
- to make a format file, the major general-purpose writing
- packages, some special-purpose writing packages, how to
- make slides for presentations, and how to handle color in
- TeX.</p>
-
- <p><span class="bold"><b>Part&#160;<a href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document">Part&#160;II</a>:
- <span class="emphasis"><em><a href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document">Part&#160;II</a></em></span></b></span>.</p>
-
- <p>Chapter&#160;<a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a>,
- <span class="emphasis"><em><a href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts">Chapter&#160;5</a></em></span>.
- This chapter explores the issues that need to be addressed
- when using fonts. Many of these issues are not particularly
- TeX-related, but TeX is very flexible, and it's important
- to understand the tradeoffs that must be made. This chapter
- also examines some TeX-specific issues: font selection,
- files that TeX needs, automatic font generation, and
- virtual fonts.</p>
-
- <p>Chapter&#160;<a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a>,
- <span class="emphasis"><em><a href="ch06.html"
- title="Chapter&#160;6.&#160;Pictures and Figures">Chapter&#160;6</a></em></span>.
- How many ways are there to include pictures and figures in
- a TeX document? Lots and lots of ways. This chapter
- examines them all.</p>
-
- <p>Chapter&#160;<a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">Chapter&#160;7</a>,
- <span class="emphasis"><em><a href="ch07.html"
- title="Chapter&#160;7.&#160;International Considerations">Chapter&#160;7</a></em></span>.
- TeX is well qualified to do international typesetting. This
- chapter looks at the issues that are involved: representing
- international symbols in your input file, what TeX
- produces, getting the right fonts, multiple languages in
- the same document, and macro packages and style files that
- solve some of these problems. Some strategies for dealing
- with very difficult languages (like Japanese and Arabic)
- are also explored.</p>
-
- <p>Chapter&#160;<a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a>,
- <span class="emphasis"><em><a href="ch08.html"
- title="Chapter&#160;8.&#160;Printing">Chapter&#160;8</a></em></span>.
- What goes in has to come out. This chapter tells the what,
- where, why, and how of printing your documents.</p>
-
- <p>Chapter&#160;<a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a>,
- <span class="emphasis"><em><a href="ch09.html"
- title="Chapter&#160;9.&#160;Previewing">Chapter&#160;9</a></em></span>.
- Save paper; preview your documents before you print
- them.</p>
-
- <p>Chapter&#160;<a href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation">Chapter&#160;10</a>,
- <span class="emphasis"><em><a href="ch10.html"
- title="Chapter&#160;10.&#160;Online Documentation">Chapter&#160;10</a></em></span>.
- Online documentation is becoming increasingly popular. This
- chapter explores different ways that both typeset and
- online documentation can be produced from the same set of
- input files.</p>
-
- <p>Chapter&#160;<a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a>,
- <span class="emphasis"><em><a href="ch11.html"
- title="Chapter&#160;11.&#160;Introducing MetaFont">Chapter&#160;11</a></em></span>.
- Sometimes it is necessary or desirable to create a special
- version of a standard TeX font. Maybe you really need the
- standard 10pt font at 11.3pt. This chapter will tell you
- how to work with existing MetaFont fonts. It <span
- class="emphasis"><em>won't</em></span> tell you how to
- create your own fonts; that's a whole different story.</p>
-
- <p>Chapter&#160;<a href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a>, <span class="emphasis"><em><a
- href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries">
- Chapter&#160;12</a></em></span>. Maintaining a
- bibliographic database can be a great timesaver. This
- chapter looks at the BibTeX program and other tools for
- building and using bibliographic databases. It also
- discusses the creation of indexes and glossaries.</p>
-
- <p><span class="bold"><b>Part&#160;<a href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview">Part&#160;III</a>:
- <span class="emphasis"><em><a href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview">Part&#160;III</a></em></span></b></span>.</p>
-
- <p>Chapter&#160;<a href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">Chapter&#160;13</a>,
- <span class="emphasis"><em><a href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">Chapter&#160;13</a></em></span>.
- Many TeX environments are freely available. This chapter
- describes public domain, free, and shareware versions of
- TeX.</p>
-
- <p>Chapter&#160;<a href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a>,
- <span class="emphasis"><em><a href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a></em></span>.
- A large, complex system like TeX can be overwhelming
- (although I hope less so after you read this book ;-). One
- of the advantages of selecting a commercial implementation
- of TeX is that some form of customer support is usually
- provided. Still other commercial implementations offer
- features not found in any free releases. This chapter
- describes several commercial TeX releases.</p>
-
- <p>Chapter&#160;<a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a>,
- <span class="emphasis"><em><a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a></em></span>.
- Many issues discussed in this book apply equally to all
- platforms, including the Macintosh platform, but the Mac
- has its own special set of features. This chapter looks at
- some versions of TeX and other tools designed specifically
- for use on the Mac.</p>
-
- <p>Chapter&#160;<a href="ch16.html"
- title="Chapter&#160;16.&#160;TeX Utilities">Chapter&#160;16</a>,
- <span class="emphasis"><em><a href="ch16.html"
- title="Chapter&#160;16.&#160;TeX Utilities">Chapter&#160;16</a></em></span>.
- This chapter lists many of the the utilities available in
- the CTAN archives and provides a brief description of what
- they do.</p>
-
- <p>Appendix&#160;<a href="apa.html"
- title="Appendix&#160;A.&#160;Filename Extension Summary">Appendix&#160;A</a>,
- <span class="emphasis"><em><a href="apa.html"
- title="Appendix&#160;A.&#160;Filename Extension Summary">Appendix&#160;A</a></em></span>.
- Lots of files can be identified by their extensions. This
- appendix lists the extensions that are most often seen in
- conjunction with TeX and describes what the associated
- files contain.</p>
-
- <p>Appendix&#160;<a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a>,
- <span class="emphasis"><em><a href="apb.html"
- title="Appendix&#160;B.&#160;Font Samples">Appendix&#160;B</a></em></span>.
- Examples of many MetaFont fonts available from the CTAN
- archives.</p>
-
- <p>Appendix&#160;<a href="apc.html"
- title="Appendix&#160;C.&#160;Resources">Appendix&#160;C</a>,
- <span class="emphasis"><em><a href="apc.html"
- title="Appendix&#160;C.&#160;Resources">Appendix&#160;C</a></em></span>.
- A complete list of the resources described in this
- book.</p>
-
- <p>Appendix&#160;<a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a>,
- <span class="emphasis"><em><a href="apd.html"
- title="Appendix&#160;D.&#160;Long Examples">Appendix&#160;D</a></em></span>.
- This appendix contains examples (scripts, batch files,
- programs) that seemed too long to place in the running
- text.</p>
-
- <p><span class="emphasis"><em>Bibliography</em></span>.
- Where I learned what I know. Also, where you can look for
- more information about specific topics.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2855196"
- name="id2855196"></a>Conventions Used in This Book</h2>
- </div>
- </div>
-
- <p>The following typographic conventions are used in this
- book:</p>
-
- <div class="variablelist">
- <dl>
- <dt><span class="term"><span
- class="emphasis"><em>Italic</em></span></span></dt>
-
- <dd>
- <p>is used for filenames, directories, user commands,
- program names, and macro packages (except where the
- distinctive logo type is used). Sometimes italics are
- used in the traditional way for emphasis of new ideas
- and important concepts.</p>
- </dd>
-
- <dt><span class="term"><tt>Typewriter</tt></span></dt>
-
- <dd>
- <p>is used for program examples, FTP sites, TeX
- control sequences, and little bits of TeX syntax that
- appear in running text (for example, typewriter text
- in a reference to the LaTeX <tt>picture</tt>
- environment is a clue that LaTeX literally uses the
- word &#8220;picture&#8221; to identify this
- environment).</p>
- </dd>
-
- <dt><span class="term"><tt>\bf Typewriter
- Bold</tt></span></dt>
-
- <dd>
- <p>is used in examples to show the user's actual
- input at the terminal.</p>
- </dd>
-
- <dt><span class="term"><tt>\it Typewriter
- Italic</tt></span></dt>
-
- <dd>
- <p>identifies text that requires a context-specific
- substitution. For example, <span
- class="emphasis"><em><tt>filename</tt></em></span> in
- an example would be replaced by some particular
- filename.</p>
- </dd>
-
- <dt><span class="term">Footnotes</span></dt>
-
- <dd>
- <p>are used for parenthetical remarks. Sometimes,
- lies are spoken to simplify the discussion, and the
- footnotes restore the lie to the truth. (And
- sometimes they don't ;-)</p>
- </dd>
- </dl>
- </div>
-
- <p>Filename extensions, like &#8220;<span
- class="emphasis"><em>.tex</em></span>&#8221; in
- <tt>book.tex</tt>, are shown in uppercase letters when
- referring to a particular type of file. For example, a TeX
- Font Metric or <tt>TFM</tt> file would be
- <tt>somefile.tfm</tt>. The actual extension of the file may
- be different (upper or lowercase, longer or shorter)
- depending on your operating environment.</p>
-
- <p>When the shell prompt is shown in an example, it is
- shown as a dollar sign, \$. You should imagine that this is
- your system's prompt, which might otherwise be
- <tt>&lt;!--</tt> , <tt>C&gt;</tt>, --&gt; <tt>[C:\]</tt>,
- or a dialog box.</p>
-
- <p>When spaces are important in an example, the
- &#8220;{&#160;}&#8221; character is used to emphasize the
- spaces. Effective,&#160; isn't&#160; it?</p>
-
- <p>In some places, I refer to specific keys that you should
- press. When it's important that I mean pressing particular
- keys and not typing something, I emphasize the keys. For
- instance, an example that includes <b>Enter</b> means that
- you should literally press the Enter or Return key. The
- sequence <b>Ctrl-D</b> means that you should press and hold
- the &#8220;Control&#8221; and &#8220;d&#8221; keys
- simultaneously. Control-key combinations aren't case
- sensitive, so you needn't press the shift key.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2855490"
- name="id2855490"></a>How to Get TeX</h2>
- </div>
- </div>
-
- <p>TeX and the other programs mentioned in this book are
- available from a number of places. It's impossible to list
- all of the places where you might find any given tool, but
- there is one place where you will almost certainly find
- <span class="emphasis"><em>every</em></span> tool: the
- Comprehensive TeX Archive Network (CTAN)<a id="id2855505"
- class="indexterm" name="id2855505"></a>.</p>
-
- <p>This network is a fully-mirrored anonymous FTP hierarchy
- in three countries. Always use the FTP site<a
- id="id2855524" class="indexterm" name="id2855524"></a> that
- is geographically closest to you. The following table lists
- the current members of CTAN as of July, 1993:</p>
-
- <div class="table">
- <a id="id2855538" name="id2855538"></a>
-
- <p class="title"><b>Table&#160;1.&#160;</b></p>
-
- <table summary="" border="1">
- <colgroup>
- <col align="left" />
- <col align="left" />
- <col align="left" />
- <col align="left" />
- </colgroup>
-
- <thead>
- <tr>
- <th align="left">Geographic Location</th>
-
- <th align="left">Site</th>
-
- <th align="left">IP Address</th>
-
- <th align="left">Top Level Directory</th>
- </tr>
- </thead>
-
- <tbody>
- <tr>
- <td align="left">United States</td>
-
- <td align="left">\tt ftp.shsu.edu</td>
-
- <td align="left">192.92.115.10</td>
-
- <td align="left">\it /tex-archive</td>
- </tr>
-
- <tr>
- <td align="left">England</td>
-
- <td align="left">\tt ftp.tex.ac.uk</td>
-
- <td align="left">131.151.79.32</td>
-
- <td align="left">\it /tex-archive</td>
- </tr>
-
- <tr>
- <td align="left">Germany</td>
-
- <td align="left">\tt ftp.uni-stuttgart.de</td>
-
- <td align="left">129.69.8.13</td>
-
- <td align="left">\it /tex-archive</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>You may also access the CTAN archives by electronic
- mail<a id="id2855672" class="indexterm"
- name="id2855672"></a> if you do not have FTP access. For
- up-to-date instructions about the mail server, send the
- single-line message <tt>help</tt> to
- <tt>fileserv@shsu.edu</tt>.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2855700"
- name="id2855700"></a>Where Are the Files?</h3>
- </div>
- </div>
-
- <p>Every CTAN mirror site has the same well-organized
- directory structure<a id="id2855710" class="indexterm"
- name="id2855710"></a>. The top-level directory also
- contains a complete catalog of current files organized by
- name, date, and size. The catalogs are named
- <tt>FILES.byname</tt>, <tt>FILES.bydate</tt>, and
- <tt>FILES.bysize</tt>, respectively, in the top level
- directory. The top-level directory contains the following
- subdirectories:</p>
-<pre class="screen">
-&lt;table&gt;
-&lt;title&gt;&lt;/title&gt;
-&lt;tgroup cols="1"&gt;
-&lt;colspec align="left"&gt;
-&lt;colspec align="left"&gt;
-&lt;thead&gt;
-&lt;row&gt;
- &lt;entry&gt;Directory&lt;/entry&gt;
- &lt;entry&gt;Description of Contents &lt;/entry&gt;
-&lt;/row&gt;
-&lt;/thead&gt;
-&lt;tbody&gt;
-&lt;row&gt;
- &lt;entry&gt;tools&lt;/entry&gt;
- &lt;entry&gt;Archiving tools (&lt;command&gt;unzip&lt;/command&gt;, &lt;command&gt;tar&lt;/command&gt;, &lt;command&gt;compress&lt;/command&gt;, etc.) &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;biblio&lt;/entry&gt;
- &lt;entry&gt;Tools for maintaining bibliographic databases &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;digests&lt;/entry&gt;
- &lt;entry&gt;Electronic digests (&amp;TeX;hax, UK&amp;TeX;, etc.)&lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;info&lt;/entry&gt;
- &lt;entry&gt;Free documentation, many good guides &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;dviware&lt;/entry&gt;
- &lt;entry&gt;Printing and previewing software &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;fonts&lt;/entry&gt;
- &lt;entry&gt;Fonts for &amp;TeX; &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;graphics&lt;/entry&gt;
- &lt;entry&gt;Software for working with pictures and figures &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;help&lt;/entry&gt;
- &lt;entry&gt;Online help files, etc. &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;indexing&lt;/entry&gt;
- &lt;entry&gt;Indexing and glossary building tools &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;language&lt;/entry&gt;
- &lt;entry&gt;Multi-national language support &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;macros&lt;/entry&gt;
- &lt;entry&gt;Macro packages and style files &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;misc&lt;/entry&gt;
- &lt;entry&gt;Stuff that doesn't fit in any other category &lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;support&lt;/entry&gt;
- &lt;entry&gt;Tools for running and supporting &amp;TeX;&lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;systems&lt;/entry&gt;
- &lt;entry&gt;OS-specific programs and files&lt;/entry&gt;
-&lt;/row&gt;
-&lt;row&gt;
- &lt;entry&gt;web&lt;/entry&gt;
- &lt;entry&gt;Sources for &amp;TeX; programs (in &amp;Web;) &lt;/entry&gt;
-&lt;/row&gt;
-&lt;/tbody&gt;
-&lt;/tgroup&gt;
-&lt;/table&gt;
-</pre>
-
- <p>The archives at <tt>ftp.shsu.edu</tt> and
- <tt>ftp.tex.ac.uk</tt> also support <b>gopher</b><a
- id="id2788674" class="indexterm" name="id2788674"></a>
- access to the archives. The UK <b>gopher</b> supports
- indexed access to the archives. A World Wide Web
- (hypertext) interface<a id="id2788694" class="indexterm"
- name="id2788694"></a> to the archives is available
- from:</p>
-<pre class="screen">
-
-http://jasper.ora.com/ctan.html
-</pre>
-
- <p>This interface includes brief descriptions of many
- packages and the ability to perform keyword and date
- searches.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2855768"
- name="id2855768"></a>Getting Software Without
- FTP</h3>
- </div>
- </div>
-
- <p>The electronic alternatives<a id="id2788563"
- class="indexterm" name="id2788563"></a> to FTP, described
- in the section &#8220;<a
- href="pr02.html#sec.gettingexamples"
- title="Getting Examples From This Book">the section
- called &#8220;Getting Examples From This
- Book&#8221;</a>&#8221; of this chapter are also viable
- alternatives for getting software from the CTAN
- archives.</p>
-
- <p>In addition, there are a number of ways to get
- distributions through nonelectronic<a id="id2788597"
- class="indexterm" name="id2788597"></a> channels. The
- names and addresses of these sources are listed in
- Appendix&#160;<a href="apc.html"
- title="Appendix&#160;C.&#160;Resources">Appendix&#160;C</a>,
- <span class="emphasis"><em><a href="apc.html"
- title="Appendix&#160;C.&#160;Resources">Appendix&#160;C</a></em></span>.</p>
-
- <p>You can get many of the popular TeX distributions on
- diskette from the TeX Users Group (TUG)<a id="id2856094"
- class="indexterm" name="id2856094"></a>. Emacs,
- <b>Ghostscript</b>, and other packages by the Free
- Software Foundation (FSF)<a id="id2856119"
- class="indexterm" name="id2856119"></a> are available on
- tape directly from the FSF. You may also find large
- bulletin board systems that support TeX (for example,
- Channel1 in Cambridge, MA)</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="sec.gettingexamples"
- name="sec.gettingexamples"></a>Getting Examples From
- This Book</h3>
- </div>
- </div>
-
- <p>All of the substantial code fragments and programs
- printed in this book are available online. The examples<a
- id="id2856154" class="indexterm" name="id2856154"></a> in
- this book are all in <b>Perl</b><a id="id2856168"
- class="indexterm" name="id2856168"></a>, a language for
- easily manipulating text, files, and processes. I decided
- to use <b>Perl</b> simply because it is available for
- every platform discussed in this book. It is the only
- &#8220;universal&#8221; scripting language that will work
- under MS-DOS, OS/2, unix, and the Macintosh. All of the
- scripts in this book can be converted to a different
- scripting language (the various unix shells or something
- like <b>4DOS</b>'s extended batch language for MS-DOS and
- OS/2) if you prefer. I've tried to write the <b>Perl</b>
- scripts in a straightforward way so that any given task
- won't be too difficult.</p>
-
- <p>The examples are available electronically in a number
- of ways: by FTP, FTPMAIL, BITFTP, and UUCP. The cheapest,
- fastest, and easiest ways are listed first. If you read
- from the top down, the first one that works is probably
- the best. Use FTP if you are directly on the Internet.
- Use FTPMAIL if you are not on the Internet but can send
- and receive electronic mail to Internet sites (this
- includes CompuServe users). Use BITFTP if you send
- electronic mail via BITNET. Use UUCP if none of the above
- work.</p>
-
- <div class="note"
- style="margin-left: 0.5in; margin-right: 0.5in;">
- <h3 class="title">Note</h3>
-
- <p>The examples were prepared using a unix system. If
- you are running unix, you can use them without
- modification. If you are running on another platform,
- you may need to modify these examples to correct the
- end-of-line markers. For example, whereas under unix
- every line ends with a line feed character (the
- carriage return is implicit), under DOS every line must
- end with explicit carriage return and line feed
- characters.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2856246"
- name="id2856246"></a>FTP</h4>
- </div>
- </div>
-
- <p>To use FTP<a id="id2856255" class="indexterm"
- name="id2856255"></a>, you need a machine with direct
- access to the Internet. A sample session is shown
- below.</p>
-<pre class="screen">
-\${\bf ftp ftp.uu.net} Connected to ftp.uu.net.
-220 ftp.UU.NET FTP server (Version 6.34 Oct 22 14:32:01 1992) ready.
-Name (ftp.uu.net:prefect): {\bf anonymous}
-331 Guest login ok, send e-mail address as password.
-Password:{\bf prefect@guide.com} \ \ \ {\rm\it\small (use your user name and host here)}
-230 Guest login ok, access restrictions apply.
-ftp&gt;{\bf cd /published/oreilly/nutshell/maketexwork}
-250 CWD command successful.
-ftp&gt;{\bf get README}
-200 PORT command successful.
-150 Opening ASCII mode data connection for README (xxxx bytes).
-226 Transfer complete.
-local: README remote: README
-xxxx bytes received in xxx seconds (xxx Kbytes/s)
-ftp&gt;{\bf binary} \ \ {\rm\it\small (select binary mode for compressed files)}
-200 Type set to I.
-{\rm\it\small \ (Repeat get commands for the other files.}
-{\rm\it\small \ They are listed in the README file.)}
-ftp&gt;{\bf quit} 221 Goodbye.
-\$
-</pre>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2856292"
- name="id2856292"></a>FTPMAIL</h4>
- </div>
- </div>
-
- <p>FTPMAIL<a id="id2856301" class="indexterm"
- name="id2856301"></a> is a mail server available to
- anyone who can send electronic mail to, and receive it
- from, Internet sites. This includes most workstations
- that have an email connection to the outside world and
- CompuServe<a id="id2856314" class="indexterm"
- name="id2856314"></a> users. You do not need to be
- directly on the Internet.</p>
-
- <p>Send mail to <span
- class="emphasis"><em>ftpmail@decwrl.dec.com</em></span>.
- In the message body, give the name of the anonymous FTP
- host and the FTP commands you want to run. The server
- will run anonymous FTP for you and mail the files back
- to you. To get a complete help file, send a message
- with no subject and the single word <tt>help</tt> in
- the body. The following is an example mail session that
- should get you the examples. This command sends you a
- listing of the files in the selected directory and the
- requested example files. The listing is useful if
- there's a later version of the examples you're
- interested in.</p>
-<pre class="screen">
-\${\bf mail ftpmail@decwrl.dec.com}
-Subject: {\bf{}reply prefect@guide.com} \ \ {\rm\it\small (where you want files mailed)}
-{\bf{}connect ftp.uu.net}
-{\bf{}chdir /published/oreilly/nutshell/maketexwork}
-{\bf{}dir}
-{\bf{}get README}
-{\bf{}quit}
-</pre>
-
- <p>A signature at the end of the message is acceptable
- as long as it appears after <tt>quit</tt>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2856375"
- name="id2856375"></a>BITFTP</h4>
- </div>
- </div>
-
- <p>BITFTP<a id="id2856384" class="indexterm"
- name="id2856384"></a> is a mail server for BITNET
- users. You send it electronic mail messages requesting
- files, and it sends you back the files by electronic
- mail. BITFTP currently serves only users who send it
- mail from nodes that are directly on BITNET, EARN, or
- NetNorth. BITFTP is a public service of Princeton
- University.</p>
-
- <p>To use BITFTP, send mail containing your FTP
- commands to <span
- class="emphasis"><em>BITFTP@PUCC</em></span>. For a
- complete help file, send <tt>HELP</tt> as the message
- body.</p>
-
- <p>The following is the message body you should send to
- BITFTP:</p>
-<pre class="screen">
-
-FTP ftp.uu.net
-NETDATA USER anonymous
-PASS<span
-class="emphasis"><em>your Internet e-mail address</em></span> {\rm\it\small (not your BITNET address)}
-CD /published/oreilly/nutshell/maketexwork
-DIR
-GET README
-QUIT
-</pre>
-
- <p>Questions about BITFTP can be directed to <span
- class="emphasis"><em>MAINT@PUCC</em></span> on
- BITNET.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2856447"
- name="id2856447"></a>UUCP</h4>
- </div>
- </div>
-
- <p>UUCP<a id="id2856456" class="indexterm"
- name="id2856456"></a> is standard on virtually all unix
- systems and is available for IBM-compatible PCs and
- Apple Macintoshes. The examples are available by UUCP
- via modem from UUNET; UUNET's connect-time charges
- apply. You can get the examples from UUNET whether you
- have an account or not. If you or your company has an
- account with UUNET, you will have a system with a
- direct UUCP connection to UUNET. Find that system, and
- type (as one line):</p>
-<pre class="screen">
-\$ <span
-class="bold"><b>uucp uunet\!&#160;/published/oreilly/nutshell/maketexwork/README \</b></span>
-<span class="emphasis"><em>\ \ yourhost</em></span>\!&#160;/<span
-class="emphasis"><em>yourname</em></span>/
-</pre>
-
- <p>The README file should appear some time later (up to
- a day or more) in the directory <span
- class="emphasis"><em>/usr/spool/uucppublic/yourname</em></span>.
- If you don't have an account, but would like one so
- that you can get electronic mail, contact UUNET at
- 703-204-8000.</p>
-
- <p>If you don't have a UUNET account, you can set up a
- UUCP connection to UUNET in the United States using the
- phone number 1-900-468-7727. As of this writing, the
- cost is 50 cents per minute. The charges will appear on
- your next telephone bill. The login name is <span
- class="emphasis"><em>uucp</em></span> with no password.
- Your entry may vary depending on your UUCP
- configuration.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h4 class="title"><a id="id2856527"
- name="id2856527"></a>Gopher</h4>
- </div>
- </div>
-
- <p>If you are on the Internet, you can use the
- <b>gopher</b><a id="id2856542" class="indexterm"
- name="id2856542"></a> facility to learn about online
- access to examples through the O'Reilly Online
- Information Resource. Access <span
- class="emphasis"><em>gopher.ora.com</em></span> as
- appropriate from your site.</p>
- </div>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2856562"
- name="id2856562"></a>Versions of TeX</h2>
- </div>
- </div>
-
- <p>The most recent versions of TeX<a id="id2856571"
- class="indexterm" name="id2856571"></a> and MetaFont<a
- id="id2856585" class="indexterm" name="id2856585"></a> are
- version 3.1415 and version 2.71, respectively. Version 3 of
- TeX introduced several new features designed to improve
- support for non-English languages (including the use of
- 8-bit input and some refinements to hyphenation control).
- If you use an older version of TeX, you should upgrade.</p>
-
- <p>Donald Knuth<a id="id2856609" class="indexterm"
- name="id2856609"></a> has specified that TeX's version
- number converges to $&#960;$, therefore version 3.1415 is
- only the fourth minor revision after version 3. The next
- minor revision will be version 3.14159. Similarly,
- MetaFont's version number converges to $e$
- (2.7182818284$&#8230;$).</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2856618"
- name="id2856618"></a>Implementations and Platforms</h2>
- </div>
- </div>
-
- <p>The interface that TeX presents to the writer is very
- consistent. Most of the examples described in this book are
- applicable to every single implementation<a id="id2856636"
- class="indexterm" name="id2856636"></a><a id="id2856653"
- class="indexterm" name="id2856653"></a> of TeX. However,
- TeX is not a closed system. It is possible to step outside
- of TeX to incorporate special elements into your document
- or take advantage of the special features of a particular
- environment. These extensions can dramatically restrict the
- portability of your documents.</p>
-
- <p>Many of the topics covered in this book offer
- alternatives in those areas that are less portable.
- Therefore, it is natural to ask what implementations are
- really covered.</p>
-
- <p>Before outlining which implementations are covered, let
- me suggest that this book will be useful even if you are
- using an implementation not &#8220;officially&#8221;
- covered here. The reality of the situation is this: many,
- many tools have been ported with TeX. Many of the tools
- mentioned in this book are available on platforms that are
- not specifically discussed. Time and equipment constraints
- prevented Amiga<a id="id2856696" class="indexterm"
- name="id2856696"></a>, Atari<a id="id2856708"
- class="indexterm" name="id2856708"></a>, NeXT<a
- id="id2856719" class="indexterm" name="id2856719"></a>,
- VMS<a id="id2856731" class="indexterm"
- name="id2856731"></a>, and Windows NT<a id="id2856743"
- class="indexterm" name="id2856743"></a> implementations of
- TeX from being specifically addressed in this edition of
- the book.</p>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2856757"
- name="id2856757"></a>UNIX</h3>
- </div>
- </div>
-
- <p>unix<a id="id2856765" class="indexterm"
- name="id2856765"></a> is probably the most common TeX
- platform. The emphasis in this book is on unix
- workstations running X11, producing output for PostScript
- and HP LaserJet printers.</p>
-
- <p><b>Linux</b><a id="id2856788" class="indexterm"
- name="id2856788"></a> and other personal computer
- implementations of unix are not addressed specifically;
- however, with the successful port of X11 to <b>Linux</b>,
- I'm confident that every unix tool here can be, or has
- been, ported to <b>Linux</b> (and probably other PC unix
- environments).</p>
-
- <p>The only implementation of the TeX program for unix
- considered in any detail is the free implementation
- distributed in <span
- class="emphasis"><em>web2c</em></span>. This distribution
- is described in the section called &#8220;<a
- href="ch13.html#free.web" title="Web2C">the section
- called &#8220;Web2C&#8221;</a>&#8221; in Chapter&#160;<a
- href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">
- Chapter&#160;13</a>, <span class="emphasis"><em><a
- href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">
- Chapter&#160;13</a></em></span>. Most of the other unix
- tools discussed here are also free.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2856866"
- name="id2856866"></a>MS-DOS</h3>
- </div>
- </div>
-
- <p>With very few exceptions, the tools in this book are
- available under MS-DOS<a id="id2856875" class="indexterm"
- name="id2856875"></a>. Because PCs are very popular, a
- lot of effort has gone into porting unix tools to MS-DOS.
- Some packages, however, require a 386SX (or more
- powerful) processor. For the most part, I focus on PCs
- running MS-DOS only; however, Microsoft Windows<a
- id="id2856888" class="indexterm" name="id2856888"></a>
- and DesqView<a id="id2856906" class="indexterm"
- name="id2856906"></a> are not entirely ignored.</p>
-
- <p>There are quite a few options when it comes to
- selecting an implementation of the TeX program under
- MS-DOS. Several free implementations are discussed as
- well as some commercial implementations. For more
- information about these implementations, consult
- Chapter&#160;<a href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">
- Chapter&#160;13</a>, <span class="emphasis"><em><a
- href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments">
- Chapter&#160;13</a></em></span>, and Chapter&#160;<a
- href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a>,
- <span class="emphasis"><em><a href="ch14.html"
- title="Chapter&#160;14.&#160;Commercial Environments">Chapter&#160;14</a></em></span>.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2856997"
- name="id2856997"></a>OS/2</h3>
- </div>
- </div>
-
- <p>In this book, OS/2 is treated primarily as a superset
- of MS-DOS. When possible, I look at OS/2-specific
- versions of each utility, but rely on MS-DOS as a
- fall-back.</p>
-
- <p>Extensions to emTeX for OS/2<a id="id2857012"
- class="indexterm" name="id2857012"></a> are explored, as
- are editing environments such as <b>epm<a id="id2857032"
- class="indexterm" name="id2857032"></a></b>. The
- multi-threaded nature of OS/2 allows more complete
- porting of unix tools. When better ports are available
- for OS/2, they are discussed.</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h3 class="title"><a id="id2857046"
- name="id2857046"></a>Macintosh</h3>
- </div>
- </div>
-
- <p>The Macintosh<a id="id2857054" class="indexterm"
- name="id2857054"></a> is very different from the systems
- described above. Chapter&#160;<a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a>,
- <span class="emphasis"><em><a href="ch15.html"
- title="Chapter&#160;15.&#160;TeX on the Macintosh">Chapter&#160;15</a></em></span>,
- discusses the Macintosh environment in detail.</p>
-
- <p>There are four implementations of TeX for the
- Macintosh. Three are freely available, and one is
- commercial: CMacTeX<a id="id2857095" class="indexterm"
- name="id2857095"></a> is free, OzTeX<a id="id2857112"
- class="indexterm" name="id2857112"></a> and DirectTeX<a
- id="id2857123" class="indexterm" name="id2857123"></a>
- are shareware, and <b>Textures</b><a id="id2857140"
- class="indexterm" name="id2857140"></a> is a commercial
- package from Blue Sky Research<a id="id2857150"
- class="indexterm" name="id2857150"></a>.</p>
- </div>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2857161"
- name="id2857161"></a>We'd Like to Hear From You</h2>
- </div>
- </div>
-
- <p>We have tested and verified all of the information in
- this book to the best of our ability, but you may find that
- features have changed (or even that we have made
- mistakes!). Please let us know about any errors you find,
- as well as your suggestions for future editions, by
- writing:</p>
-
- <div class="address">
- <p><br />
- O'Reilly&#160;&amp;&#160;Associates,&#160;Inc.<br />
- 103&#160;Morris&#160;Street,&#160;Suite&#160;A<br />
- Sebastopol,&#160;CA&#160;95472<br />
- 1-800-998-9938&#160;(in&#160;the&#160;US&#160;or&#160;Canada)<br />
-
- 1-707-829-0515&#160;(international/local)<br />
- 1-707-829-0104&#160;(FAX)<br />
- </p>
- </div>
-
- <p>You can also send us messages electronically. To be put
- on the mailing list or request a catalog, send email
- to:</p>
-
- <div class="informaltable">
- <table border="1">
- <colgroup>
- <col />
- <col />
- </colgroup>
-
- <tbody>
- <tr>
- <td><span
- class="emphasis"><em>nuts@ora.com</em></span></td>
-
- <td>(via the Internet)</td>
- </tr>
-
- <tr>
- <td><span
- class="emphasis"><em>uunet!ora!nuts</em></span></td>
-
- <td>(via UUCP)</td>
- </tr>
- </tbody>
- </table>
- </div>
-
- <p>To ask technical questions or comment on the book, send
- email to:</p>
-
- <p><span
- class="emphasis"><em>bookquestions@ora.com</em></span> (via
- the Internet)</p>
- </div>
-
- <div class="section">
- <div class="titlepage">
- <div>
- <h2 class="title" style="clear: both"><a id="id2857251"
- name="id2857251"></a>Acknowledgments</h2>
- </div>
- </div>
-
- <p>This book would not exist if I had not received support
- and encouragement from my friends and colleagues, near and
- far. I owe the deepest debt of gratitude to my wife,
- Deborah, for patience, understanding, and support as I
- progressed through what is easily the most all-consuming
- task I have ever undertaken.</p>
-
- <p>The earliest draft of this book came about because my
- advisor at the University of Massachusetts, Eliot Moss,
- allowed me to tinker with the TeX installation in the
- Object Systems Lab and was always able to suggest ways to
- make it better. My friends and colleages at UMass, Amer
- Diwan, Darko Stefanovi\'c, Dave Yates, Eric Brown, Erich
- Nahum, Jody Daniels, Joe McCarthy, Ken Magnani, Rick
- Hudson, and Tony Hosking, asked all the hard questions and
- didn't seem to mind when I used them as guinea pigs for my
- latest idea.</p>
-
- <p>I'm indebted also to Eberhard Mattes, Geoffrey Tobin,
- George D. Greenwade, Peter Schmitt, Sebastian Rahtz, and
- Tomas Rokicki, who provided technical review comments on
- the materials presented here. Jim Breen and Ken Lunde
- offered invaluable feedback on Chapter 7.</p>
-
- <p>And I'd like to thank a lot of people at O'Reilly for
- their help and enthusiasm; in particular, my editor, Debby
- Russell, offered advice, helpful criticism, and support
- beyond the call of duty (Debby keyed most of the index for
- this book as production deadlines drew near and other
- arrangements fell through); Chris Tong organized the raw
- entries into a usable index; Lenny Muellner, Donna
- Woonteiler, and Sheryl Avruch allowed me to work on the
- book when it wasn't technically my job; Stephen Spainhour
- copyedited it into English with the help of Leslie Chalmers
- and Kismet McDonough (Stephen offered helpful suggestions
- along the way, too); Jennifer Niederst helped me get the
- design right; and Chris Reilly created the figures and
- screen dumps. I enjoyed working with everyone at O'Reilly
- so much that I left UMass and joined the production
- department myself ;-).</p>
-
- <p>Several companies provided review copies of their
- software while I was writing this book. I would like to
- thank ArborText, Blue Sky Research, Borland International,
- The Kinch Computer Company, LaserGo, Personal TeX, TCI
- Software Research, and Y&amp;Y, for their generosity.</p>
-
- <p>Finally, I'd like to thank the entire Internet TeX
- community. Countless thousands of questions and answers on
- the Net refined my understanding of how TeX works and what
- it can do.</p>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Forward to the SourceForge Edition"
- href="pr01.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Part&#160;I.&#160;An Introduction to TeX"
- href="pt01.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Forward to the SourceForge
- Edition&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">&#160;Part&#160;I.&#160;An
- Introduction to TeX</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/pt01.html b/Master/texmf-doc/doc/english/make-tex-work/html/pt01.html
deleted file mode 100644
index e86a45b1926..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/pt01.html
+++ /dev/null
@@ -1,489 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Part&#160;I.&#160;An Introduction to TeX</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="index.html" title="Making TeX Work" />
- <link rel="previous" href="pr02.html" title="Preface" />
- <link rel="next" href="ch01.html"
- title="Chapter&#160;1.&#160;The Big Picture" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a title="Preface"
- href="pr02.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Making TeX Work" href="index.html"><img
- src="figures/nav-up.png" alt="Up" border="0" />
- </a>&#160;<a title="Chapter&#160;1.&#160;The Big Picture"
- href="ch01.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="part">
- <div class="titlepage">
- <div>
- <h1 class="title"><a id="part.intro"
- name="part.intro"></a>An Introduction to TeX</h1>
- </div>
- </div>
-
- <div class="partintro">
- <p><a href="pt01.html"
- title="Part&#160;I.&#160;An Introduction to TeX">Part&#160;I</a>,
- introduces TeX and the tools that make up the TeX system.
- It describes various editing environments that simplify the
- job of editing TeX documents. It also discusses the
- mechanics of running TeX and recovery from errors, and it
- provides an overview of TeX macro packages and format
- files.</p>
-
- <div class="toc">
- <p><b>Table of Contents</b></p>
-
- <dl>
- <dt>1. <a href="ch01.html">The Big Picture</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch01.html#sec.texforbeginners">What Is
- TeX?</a></dt>
-
- <dt><a href="ch01.html#id2857628">TeX for
- Beginners</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch01.html#sec.tex.controlsequences">Boxes
- and Glue</a></dt>
-
- <dt><a href="ch01.html#id2858068">Control
- Sequences</a></dt>
-
- <dt><a
- href="ch01.html#sec.textformVSwordproc">Special
- Characters</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch01.html#id2859644">Text Formatting
- Versus Word Processing</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch01.html#sec.howtexworks">What
- About Desktop Publishing?</a></dt>
-
- <dt><a href="ch01.html#id2860232">What About
- troff?</a></dt>
-
- <dt><a href="ch01.html#id2860619">What About
- SGML?</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch01.html#id2860690">How TeX
- Works</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch01.html#subsubsec.runningtex">TeXing a
- Simple Document</a></dt>
-
- <dt><a href="ch01.html#id2861683">TeXing More
- Complex Documents</a></dt>
-
- <dt><a href="ch01.html#id2861875">Building a
- Table of Contents</a></dt>
-
- <dt><a href="ch01.html#id2861991">Figure
- References</a></dt>
-
- <dt><a href="ch01.html#id2862061">Indexes and
- Glossaries</a></dt>
-
- <dt><a
- href="ch01.html#id2862096">Bibliographies</a></dt>
-
- <dt><a href="ch01.html#id2862381">Special
- Things</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>2. <a href="ch02.html">Editing</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#sec.whatcando">What Can an
- Editor Do?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#sec.auctex">Quoting
- Automatically</a></dt>
-
- <dt><a href="ch02.html#id2862787">Matching
- Braces</a></dt>
-
- <dt><a href="ch02.html#id2862919">Inserting
- Common Control Sequences</a></dt>
-
- <dt><a href="ch02.html#id2862968">Running TeX
- Automatically</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2863045">GNU
- Emacs</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#id2863154">Starting TeX
- Mode</a></dt>
-
- <dt><a href="ch02.html#id2863366">Typing in
- Emacs</a></dt>
-
- <dt><a href="ch02.html#id2863418">Running TeX
- Automatically</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2863525">aucTeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#sec.multifile">Starting
- aucTeX</a></dt>
-
- <dt><a href="ch02.html#id2863748">Typing in
- aucTeX</a></dt>
-
- <dt><a href="ch02.html#id2865794">aucTeX
- Outline Mode</a></dt>
-
- <dt><a href="ch02.html#id2865831">Intelligent
- Paragraph Reformatting</a></dt>
-
- <dt><a href="ch02.html#id2865862">Multi-file
- Documents</a></dt>
-
- <dt><a href="ch02.html#sec.texcomp">Running
- TeX</a></dt>
-
- <dt><a href="ch02.html#id2866224">Finding
- Errors</a></dt>
- </dl>
- </dd>
-
- <dt><a
- href="ch02.html#id2866254">Multi-Edit</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#id2866322">Setting Up
- TeX Support</a></dt>
-
- <dt><a href="ch02.html#id2866543">Typing in
- Multi-Edit</a></dt>
-
- <dt><a href="ch02.html#id2866670">Running
- TeX</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2866742">Brief</a></dt>
-
- <dt><a
- href="ch02.html#id2866836">MicroEMACS</a></dt>
-
- <dt><a href="ch02.html#id2867057">epm: OS/2's
- Enhanced Editor</a></dt>
-
- <dt><a href="ch02.html#id2867165">Other
- Tools</a></dt>
-
- <dt><a href="ch02.html#id2867406">TeX as a
- Compiler</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch02.html#id2867481">Processing a
- Document</a></dt>
- </dl>
- </dd>
-
- <dt><a
- href="ch02.html#id2868148">Spellchecking</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch02.html#id2868250">ispell</a></dt>
-
- <dt><a
- href="ch02.html#id2868280">amSpell</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch02.html#id2868394">Revision
- Control</a></dt>
-
- <dt><a href="ch02.html#id2868511">TeX
- Shells</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch02.html#id2868544">TeXShell</a></dt>
-
- <dt><a
- href="ch02.html#id2868647">TeXPert</a></dt>
-
- <dt><a href="ch02.html#id2868748">4TeX</a></dt>
-
- <dt><a
- href="ch02.html#id2868860">PMTeX</a></dt>
-
- <dt><a
- href="ch02.html#id2868984">TeXit</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>3. <a href="ch03.html">Running TeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch03.html#run.sec.formatfiles">What Do
- You Run?</a></dt>
-
- <dt><a href="ch03.html#id2869278">What Files Does
- TeX Need?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch03.html#id2869610">Pool
- Files</a></dt>
-
- <dt><a href="ch03.html#id2869651">Format
- Files</a></dt>
-
- <dt><a href="ch03.html#sec.userfiles">User
- Files</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch03.html#sec.clineopts">The Command
- Line</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch03.html#sec.runtex.cmdcautions">Command-line
- Options</a></dt>
-
- <dt><a href="ch03.html#id2870602">Command-line
- Cautions</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch03.html#id2871334">TeX Without
- Options</a></dt>
-
- <dt><a href="ch03.html#sec.errors">What About
- Errors?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch03.html#sec.logfiles">Log
- Files</a></dt>
-
- <dt><a
- href="ch03.html#sec.qprompt">Interpreting TeX
- Error Messages</a></dt>
-
- <dt><a href="ch03.html#id2872461">Naming a File
- TeX Cannot Find</a></dt>
-
- <dt><a href="ch03.html#id2872549">Misspelling a
- Control Sequence Name</a></dt>
-
- <dt><a href="ch03.html#id2872653">Failure to
- Close an Environment</a></dt>
-
- <dt><a href="ch03.html#id2872844">Math Outside
- of Math Mode</a></dt>
-
- <dt><a href="ch03.html#id2873082">Missing
- Fonts</a></dt>
-
- <dt><a href="ch03.html#id2873273">Everything
- Else</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch03.html#id2873346">The Question Mark
- Prompt</a></dt>
- </dl>
- </dd>
-
- <dt>4. <a href="ch04.html">Macro Packages</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch04.html#macpack.sec.latexvslatexe">Installation:
- Making Format Files</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch04.html#id2874541">Hyphenation
- Patterns</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch04.html#id2874634">General-purpose
- Formats</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch04.html#id2874772">Plain
- TeX</a></dt>
-
- <dt><a href="ch04.html#id2875093">Extended
- Plain TeX</a></dt>
-
- <dt><a href="ch04.html#id2875359">LaTeX2e
- Versus LaTeX</a></dt>
-
- <dt><a
- href="ch04.html#sec.latexe">LaTeX2e</a></dt>
-
- <dt><a
- href="ch04.html#sec.latex">LaTeX</a></dt>
-
- <dt><a
- href="ch04.html#sec.texincolor">AMSTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2877047">AMSLaTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2877164">Lollipop</a></dt>
-
- <dt><a
- href="ch04.html#id2873910">TeXinfo</a></dt>
-
- <dt><a href="ch04.html#id2877747">Other
- Formats</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch04.html#id2878394">Special-purpose
- Formats</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch04.html#id2878827">SliTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2878922">FoilTeX</a></dt>
-
- <dt><a
- href="ch04.html#id2878993">Seminar</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch04.html#id2879086">TeX in
- Color</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch04.html#id2879169">Setting Up
- Color</a></dt>
-
- <dt><a href="ch04.html#id2879595">Using
- Color</a></dt>
-
- <dt><a href="ch04.html#id2879708">Now I've Got
- Color, but I Need Black and White!</a></dt>
-
- <dt><a href="ch04.html#id2879774">Color Under
- LaTeX2e</a></dt>
-
- <dt><a href="ch04.html#id2879830">Color Is
- Subtle</a></dt>
-
- <dt><a href="ch04.html#id2879898">Further
- Reading</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
- </dl>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a title="Preface"
- href="pr02.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;1.&#160;The Big Picture"
- href="ch01.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Preface&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;1.&#160;The Big Picture</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/pt02.html b/Master/texmf-doc/doc/english/make-tex-work/html/pt02.html
deleted file mode 100644
index 840f2ee62bc..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/pt02.html
+++ /dev/null
@@ -1,733 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Part&#160;II.&#160;Elements of a Complex
- Document</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="index.html" title="Making TeX Work" />
- <link rel="previous" href="ch04.html"
- title="Chapter&#160;4.&#160;Macro Packages" />
- <link rel="next" href="ch05.html"
- title="Chapter&#160;5.&#160;Fonts" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;4.&#160;Macro Packages"
- href="ch04.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Making TeX Work" href="index.html"><img
- src="figures/nav-up.png" alt="Up" border="0" />
- </a>&#160;<a title="Chapter&#160;5.&#160;Fonts"
- href="ch05.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="part">
- <div class="titlepage">
- <div>
- <h1 class="title"><a id="part.elements"
- name="part.elements"></a>Elements of a Complex
- Document</h1>
- </div>
- </div>
-
- <div class="partintro">
- <p><a href="pt02.html"
- title="Part&#160;II.&#160;Elements of a Complex Document">Part&#160;II</a>,
- describes the major components of TeX involved in producing
- a non-trivial document. It discusses how to use different
- font technologies, how to incorporate pictures and figures
- into the document, how to typeset non-English languages,
- and how to maintain complex structures like indexes and
- bibliographies. This section also explains the preview and
- printing processes in detail.</p>
-
- <div class="toc">
- <p><b>Table of Contents</b></p>
-
- <dl>
- <dt>5. <a href="ch05.html">Fonts</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#sec.issueofsize">What TeX
- Needs To Know</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2880659">Selecting a
- Font in TeX</a></dt>
-
- <dt><a href="ch05.html#id2880773">Which
- Character Is Which?</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2880909">The Issue of
- Size</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch05.html#sec.gettingtfms">Expressing
- Design Size in TeX</a></dt>
-
- <dt><a href="ch05.html#id2881284">Expressing
- Magnification in TeX</a></dt>
-
- <dt><a href="ch05.html#id2881380">Standard
- Magnifications</a></dt>
-
- <dt><a href="ch05.html#id2881671">Where Do TFM
- Files Come From?</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#sec.nfss2">The New Font
- Selection Scheme</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch05.html#sec.fonts.defnfss2">Selecting
- Fonts with the New Font Selection
- Scheme</a></dt>
-
- <dt><a href="ch05.html#id2855857">Defining
- Fonts with NFSS2</a></dt>
-
- <dt><a href="ch05.html#id2884733">Storing Font
- Definitions</a></dt>
-
- <dt><a href="ch05.html#id2884863">Changing the
- Defaults</a></dt>
-
- <dt><a href="ch05.html#id2885098">NFSS
- Pitfalls</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2885459">PostScript Fonts
- Under NFSS</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2885510">Adjustments
- to Scale</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2885640">When Things Go
- Wrong</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2885669">When TeX
- Complains</a></dt>
-
- <dt><a href="ch05.html#id2885907">When the DVI
- Driver Complains</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch05.html#id2886211">Encoding
- Vectors</a></dt>
-
- <dt><a
- href="ch05.html#sec.fonts.virtualfonts">Virtual
- Fonts</a></dt>
-
- <dt><a href="ch05.html#sec.autofont">Automatic Font
- Generation by DVI Drivers</a></dt>
-
- <dt><a href="ch05.html#sec.t1fonts">Math Fonts in
- TeX</a></dt>
-
- <dt><a href="ch05.html#id2887790">Concrete
- Examples</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch05.html#id2887816">MetaFont
- Fonts</a></dt>
-
- <dt><a href="ch05.html#id2887929">PostScript
- Type 1 Fonts</a></dt>
-
- <dt><a href="ch05.html#id2890165">HP LaserJet
- Softfonts</a></dt>
-
- <dt><a href="ch05.html#id2890329">TrueType
- Fonts</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>6. <a href="ch06.html">Pictures and
- Figures</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#sec.devindrev">Different
- Kinds of Images</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#id2890411">Bitmapped
- Images</a></dt>
-
- <dt><a href="ch06.html#id2884033">Scalable
- Images</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2884144">Device
- Independence Revisited</a></dt>
-
- <dt><a href="ch06.html#sec.ptexpic">Using Only
- TeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#id2890867">Plain
- TeX</a></dt>
-
- <dt><a
- href="ch06.html#sec.pictures.latex">LaTeX</a></dt>
-
- <dt><a
- href="ch06.html#id2891692">PiCTeX</a></dt>
-
- <dt><a
- href="ch06.html#id2891884">XYPic</a></dt>
-
- <dt><a
- href="ch06.html#id2892057">DraTeX</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2892246">Using a Little
- Help</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch06.html#id2892297">MFPic</a></dt>
-
- <dt><a
- href="ch06.html#id2892403">Fig2MF</a></dt>
-
- <dt><a
- href="ch06.html#sec.tpic">MetaFont</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2892560">Using a Little
- More Help</a></dt>
-
- <dt><a
- href="ch06.html#sec.pictures.pstricks">PSTricks</a></dt>
-
- <dt><a href="ch06.html#id2892664">TeXdraw</a></dt>
-
- <dt><a href="ch06.html#id2892716">tpic</a></dt>
-
- <dt><a href="ch06.html#sec.scaleformat">Using a Lot
- of Help</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#id2892815">Electronic
- Cut-and-paste</a></dt>
-
- <dt><a href="ch06.html#id2893032">Scalable
- Image Formats</a></dt>
-
- <dt><a href="ch06.html#sec.incps">Bitmapped
- Image Formats</a></dt>
-
- <dt><a href="ch06.html#id2893872">Inserting
- PostScript Images into TeX</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#sec.picconv">Manipulating
- Images</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#sec.gs">Image
- Magick</a></dt>
-
- <dt><a
- href="ch06.html#id2895306">PBMplus</a></dt>
-
- <dt><a href="ch06.html#id2895807">xv</a></dt>
-
- <dt><a
- href="ch06.html#id2895932">xloadimage</a></dt>
-
- <dt><a href="ch06.html#id2896003">Image
- Alchemy</a></dt>
-
- <dt><a
- href="ch06.html#id2896234">ColorView</a></dt>
-
- <dt><a
- href="ch06.html#id2896325">Jpeg4</a></dt>
-
- <dt><a
- href="ch06.html#id2896400">pmjpeg</a></dt>
-
- <dt><a
- href="ch06.html#id2896523">txt2pcx</a></dt>
-
- <dt><a
- href="ch06.html#id2896564">Ghostscript</a></dt>
-
- <dt><a
- href="ch06.html#sec.screendump">GoScript</a></dt>
-
- <dt><a
- href="ch06.html#id2897312">hp2xx</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2897483">Image
- Editors</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch06.html#id2897734">xfig</a></dt>
-
- <dt><a
- href="ch06.html#id2897932">idraw</a></dt>
-
- <dt><a href="ch06.html#id2898057">tgif</a></dt>
-
- <dt><a
- href="ch06.html#id2898297">bitmap/pixmap</a></dt>
-
- <dt><a href="ch06.html#id2898403">Other Bitmap
- Editors</a></dt>
-
- <dt><a
- href="ch06.html#id2898442">texcad/xtexcad</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch06.html#id2898527">Screen
- Dumps</a></dt>
- </dl>
- </dd>
-
- <dt>7. <a href="ch07.html">International
- Considerations</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch07.html#sec.for.printing">Typesetting in
- Any Language</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch07.html#id2899289">Reading Input
- Files</a></dt>
-
- <dt><a href="ch07.html#id2900395">Changing the
- Rules</a></dt>
-
- <dt><a href="ch07.html#id2902005">Printing the
- Result</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch07.html#sec.babel">The Babel
- Styles</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch07.html#sec.babelfmt">Building
- Multilingual Babel Formats</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch07.html#sec.asciijtex">TeX
- Pitfalls</a></dt>
-
- <dt><a href="ch07.html#id2903161">Very Complex
- Languages</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch07.html#id2903174">Japanese</a></dt>
-
- <dt><a
- href="ch07.html#id2903882">Chinese</a></dt>
-
- <dt><a
- href="ch07.html#id2903985">Arabic</a></dt>
-
- <dt><a
- href="ch07.html#id2904076">Hebrew</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>8. <a href="ch08.html">Printing</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#sec.printing">Printing
- Fonts</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#sec.bitfonts">Built-in
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2904946">External
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2905223">Bitmapped
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2905872">Scalable
- Fonts</a></dt>
-
- <dt><a href="ch08.html#id2905916">Font Printing
- Pitfalls</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch08.html#id2906078">Printing Pictures
- and Figures</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#id2906166">Unsolvable
- Problems</a></dt>
-
- <dt><a href="ch08.html#id2906292">Solvable
- Problems</a></dt>
-
- <dt><a href="ch08.html#id2906405">Pictures
- Using Only TeX</a></dt>
-
- <dt><a href="ch08.html#id2906432">MetaFont
- Figures</a></dt>
-
- <dt><a href="ch08.html#id2906500">Scalable
- Images</a></dt>
-
- <dt><a href="ch08.html#id2906554">Bitmap
- Images</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch08.html#id2906581">Selected
- Drivers</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch08.html#id2906990">emTeX
- Drivers</a></dt>
-
- <dt><a
- href="ch08.html#id2907474">dvilj2</a></dt>
-
- <dt><a
- href="ch08.html#id2907508">dvips</a></dt>
-
- <dt><a
- href="ch08.html#sec.pr.dvilaserhp">DVILASER/HP</a></dt>
-
- <dt><a
- href="ch08.html#sec.pr.dvilaserps">DVILASER/PS</a></dt>
-
- <dt><a href="ch08.html#id2909658">PTI Laser/HP
- and PTI Jet</a></dt>
-
- <dt><a href="ch08.html#id2909924">PTI
- Laser/PS</a></dt>
-
- <dt><a
- href="ch08.html#id2910137">dvipsone</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>9. <a href="ch09.html">Previewing</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch09.html#sec.ghostscript">Previewing
- Under X11</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch09.html#id2911502">Previewing
- with xdvi</a></dt>
-
- <dt><a href="ch09.html#id2911812">Previewing
- with \xtex</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch09.html#id2912002">Previewing with
- Ghostscript</a></dt>
-
- <dt><a href="ch09.html#id2912205">Previewing with
- emTeX</a></dt>
-
- <dt><a href="ch09.html#id2912806">Previewing with
- dvivga</a></dt>
-
- <dt><a href="ch09.html#sec.arb.preview">TeX
- Preview</a></dt>
-
- <dt><a href="ch09.html#id2913678">dvideo</a></dt>
-
- <dt><a href="ch09.html#id2913841">PTI View</a></dt>
-
- <dt><a href="ch09.html#id2914028">Previewing Under
- Windows</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch09.html#id2914065">dvimswin</a></dt>
-
- <dt><a
- href="ch09.html#id2914192">dviwin</a></dt>
-
- <dt><a
- href="ch09.html#id2914502">wdviwin</a></dt>
-
- <dt><a
- href="ch09.html#id2914603">DVIWindo</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch09.html#sec.preview.tty">Previewing
- on a TTY</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch09.html#id2915377">dvi2tty</a></dt>
-
- <dt><a
- href="ch09.html#id2915519">dvgt/dvitovdu</a></dt>
-
- <dt><a
- href="ch09.html#id2915747">crudetype</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>10. <a href="ch10.html">Online
- Documentation</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch10.html#id2916146">Something Is
- Lost</a></dt>
-
- <dt><a href="ch10.html#id2916199">TeXinfo</a></dt>
-
- <dt><a
- href="ch10.html#id2916555">\LaTeX2HTML</a></dt>
-
- <dt><a href="ch10.html#id2916701">LameTeX</a></dt>
-
- <dt><a href="ch10.html#id2917217">latex2hy</a></dt>
-
- <dt><a href="ch10.html#id2917348">detex</a></dt>
-
- <dt><a href="ch10.html#id2917381">dvispell</a></dt>
- </dl>
- </dd>
-
- <dt>11. <a href="ch11.html">Introducing
- MetaFont</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch11.html#sec.mf.gettingstarted">What
- to Run?</a></dt>
-
- <dt><a href="ch11.html#id2918131">What Files Does
- MetaFont Need?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch11.html#id2918156">Pool
- Files</a></dt>
-
- <dt><a href="ch11.html#id2918200">Base
- Files</a></dt>
-
- <dt><a href="ch11.html#id2918279">MetaFont
- Programs</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch11.html#id2918336">Command-line
- Options</a></dt>
-
- <dt><a href="ch11.html#id2918545">Building a Base
- File</a></dt>
-
- <dt><a href="ch11.html#sec.buildfont">Running
- MetaFont</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch11.html#id2918826">Picking a
- Mode</a></dt>
-
- <dt><a href="ch11.html#id2919066">Selecting a
- Size</a></dt>
-
- <dt><a href="ch11.html#id2919175">Making a GF
- Font</a></dt>
-
- <dt><a href="ch11.html#id2919378">Making a PK
- Font</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch11.html#id2919679">What About
- Errors?</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch11.html#id2920144">Other
- Errors</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch11.html#id2920215">Output at Very
- High Resolutions</a></dt>
-
- <dt><a href="ch11.html#id2920252">Output at Very
- Low Resolutions</a></dt>
- </dl>
- </dd>
-
- <dt>12. <a href="ch12.html">Bibliographies, Indexes,
- and Glossaries</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch12.html#sec.indexeslooklike">BibTeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch12.html#id2920526">How BibTeX
- Works</a></dt>
-
- <dt><a href="ch12.html#id2920800">Building a
- Bibliography Database</a></dt>
-
- <dt><a href="ch12.html#id2921724">Bibliography
- Styles</a></dt>
-
- <dt><a href="ch12.html#id2922224">Bibliography
- Database Tools</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch12.html#id2923157">Tib</a></dt>
-
- <dt><a href="ch12.html#id2923378">Making
- Indexes</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch12.html#id2923569">Index
- Entries</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch12.html#id2923830">Index
- Format</a></dt>
-
- <dt><a href="ch12.html#id2923963">Special-purpose
- styles</a></dt>
-
- <dt><a href="ch12.html#id2924031">Making
- Glossaries</a></dt>
- </dl>
- </dd>
- </dl>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;4.&#160;Macro Packages"
- href="ch04.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;5.&#160;Fonts" href="ch05.html"><img
- src="figures/nav-next.png" alt="Next" border="0" />
- </a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">Chapter&#160;4.&#160;Macro
- Packages&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;5.&#160;Fonts</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-
diff --git a/Master/texmf-doc/doc/english/make-tex-work/html/pt03.html b/Master/texmf-doc/doc/english/make-tex-work/html/pt03.html
deleted file mode 100644
index 18fd309698e..00000000000
--- a/Master/texmf-doc/doc/english/make-tex-work/html/pt03.html
+++ /dev/null
@@ -1,948 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator"
- content="HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org" />
- <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1" />
-
- <title>Part&#160;III.&#160;A Tools Overview</title>
- <link rel="stylesheet" href="mtw.css" type="text/css" />
- <meta name="generator"
- content="DocBook XSL Stylesheets V1.53.0" />
- <link rel="home" href="index.html" title="Making TeX Work" />
- <link rel="up" href="index.html" title="Making TeX Work" />
- <link rel="previous" href="ch12.html"
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries" />
- <link rel="next" href="ch13.html"
- title="Chapter&#160;13.&#160;Non-commercial Environments" />
- </head>
-
- <body>
- <div class="navheader">
- <table border="0" cellpadding="0" cellspacing="0"
- width="100%" summary="Navigation table">
- <tr>
- <td align="left">&#160;<a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a>&#160;<a
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries"
- href="ch12.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;<a
- title="Making TeX Work" href="index.html"><img
- src="figures/nav-up.png" alt="Up" border="0" /></a>&#160;<a
- title="Chapter&#160;13.&#160;Non-commercial Environments"
- href="ch13.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
-
- <td align="right"><i>Making TeX Work</i> Version 1.0.1
- <span class="alpha-version">(<a
- href="co01.html"><em>Alpha</em></a>)</span></td>
- </tr>
- </table>
- </div>
-
- <div class="part">
- <div class="titlepage">
- <div>
- <h1 class="title"><a id="part.tools"
- name="part.tools"></a>A Tools Overview</h1>
- </div>
- </div>
-
- <div class="partintro">
- <p><a href="pt03.html"
- title="Part&#160;III.&#160;A Tools Overview">Part&#160;III</a>,
- summarizes the tools you can use in processing TeX
- documents. It describes the major free and commercial
- implementations of TeX, and then briefly summarizes the
- many TeXnical tools available.</p>
-
- <div class="toc">
- <p><b>Table of Contents</b></p>
-
- <dl>
- <dt>13. <a href="ch13.html">Non-commercial
- Environments</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch13.html#free.web">Web2C</a></dt>
-
- <dt><a
- href="ch13.html#sec.emtex.testinstall">emTeX</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch13.html#id2925718">Where to
- Start</a></dt>
-
- <dt><a href="ch13.html#id2925747">Unpacking the
- Archives</a></dt>
-
- <dt><a href="ch13.html#id2925984">Setting Up
- the Environment</a></dt>
-
- <dt><a href="ch13.html#id2926107">Testing the
- Installation</a></dt>
-
- <dt><a
- href="ch13.html#sec.emtex.smaller">Installing
- Fonts</a></dt>
-
- <dt><a href="ch13.html#id2926788">Making emTeX
- Smaller</a></dt>
-
- <dt><a href="ch13.html#id2928367">Basic
- Customization</a></dt>
-
- <dt><a href="ch13.html#id2929307">Installing
- the Beta Test Versions of emTeX</a></dt>
-
- <dt><a
- href="ch13.html#sec.emtex.autofont">Running
- emTeX 386 in Windows</a></dt>
-
- <dt><a href="ch13.html#id2929946">Automatic
- Font Generation with emTeX</a></dt>
-
- <dt><a href="ch13.html#sec.netemtex">Installing
- emTeX on a Network</a></dt>
- </dl>
- </dd>
-
- <dt><a href="ch13.html#id2930222">texas</a></dt>
-
- <dt><a href="ch13.html#id2930652">sbTeX</a></dt>
-
- <dt><a href="ch13.html#id2931076">gTeX</a></dt>
- </dl>
- </dd>
-
- <dt>14. <a href="ch14.html">Commercial
- Environments</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch14.html#sec.com.turbo">µTeX by
- ArborText</a></dt>
-
- <dt><a href="ch14.html#id2931589">\yyTeX</a></dt>
-
- <dt><a href="ch14.html#id2931820">Textures</a></dt>
-
- <dt><a href="ch14.html#id2931894">TurboTeX</a></dt>
-
- <dt><a href="ch14.html#sec.pctex">PCTeX</a></dt>
-
- <dt><a href="ch14.html#sec.pctexforwin">PCTeX For
- Windows</a></dt>
-
- <dt><a href="ch14.html#id2933148">Scientific
- Word</a></dt>
- </dl>
- </dd>
-
- <dt>15. <a href="ch15.html">TeX on the
- Macintosh</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch15.html#sec.Excalibur">CMacTeX</a></dt>
-
- <dt><a
- href="ch15.html#id2934116">DirectTeX</a></dt>
-
- <dt><a href="ch15.html#id2934176">OzTeX</a></dt>
-
- <dt><a href="ch15.html#id2934618">Textures</a></dt>
-
- <dt><a href="ch15.html#id2935013">Other
- Tools</a></dt>
-
- <dd>
- <dl>
- <dt><a
- href="ch15.html#id2935026">Alpha</a></dt>
-
- <dt><a
- href="ch15.html#id2935128">BBEdit</a></dt>
-
- <dt><a href="ch15.html#sec.bsrtools">BSR Font
- Tools</a></dt>
-
- <dt><a
- href="ch15.html#id2935468">Excalibur</a></dt>
-
- <dt><a
- href="ch15.html#id2935534">HyperBibTeX</a></dt>
-
- <dt><a
- href="ch15.html#id2935646">MacGS</a></dt>
-
- <dt><a
- href="ch15.html#id2935708">dvidvi</a></dt>
-
- <dt><a
- href="ch15.html#id2935748">MacDVIcopy</a></dt>
-
- <dt><a
- href="ch15.html#id2935800">MacBibTeX</a></dt>
-
- <dt><a
- href="ch15.html#id2935830">MacMakeIndex</a></dt>
- </dl>
- </dd>
- </dl>
- </dd>
-
- <dt>16. <a href="ch16.html">TeX Utilities</a></dt>
-
- <dd>
- <dl>
- <dt><a href="ch16.html#id2936355">List of
- Tools</a></dt>
- </dl>
- </dd>
-
- <dt>A. <a href="apa.html">Filename Extension
- Summary</a></dt>
-
- <dt>B. <a href="apb.html">Font Samples</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apb.html#id2941555">Font
- Encodings</a></dt>
-
- <dt><a href="apb.html#id2945478">Font
- Samples</a></dt>
- </dl>
- </dd>
-
- <dt>C. <a href="apc.html">Resources</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apc.html#id2943524">TUG: The TeX Users
- Group</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apc.html#id2946099">Other User
- Groups</a></dt>
- </dl>
- </dd>
-
- <dt><a href="apc.html#id2946152">TeX
- Software</a></dt>
-
- <dt><a href="apc.html#id2946301">TeX
- Shells</a></dt>
-
- <dt><a href="apc.html#id2946342">Editors</a></dt>
-
- <dt><a href="apc.html#id2946460">Macro Packages
- (Formats)</a></dt>
-
- <dt><a href="apc.html#id2946539">Styles and
- Macros</a></dt>
-
- <dd>
- <dl>
- <dt><a href="apc.html#id2946714">Styles That
- Produced This Book</a></dt>
- </dl>
- </dd>
-
- <dt><a href="apc.html#id2946829">Utilities</a></dt>
-
- <dt><a
- href="apc.html#id2948003">Miscellaneous</a></dt>
- </dl>
- </dd>
-
- <dt>D. <a href="apd.html">Long Examples</a></dt>
-
- <dt>E. <a href="ape.html">GNU Free Documentation
- License</a></dt>
-
- <dd>
- <dl>
- <dt>0. <a
- href="ape.html#id2948209">PREAMBLE</a></dt>
-
- <dt>1. <a href="ape.html#id2948100">APPLICABILITY
- AND DEFINITIONS</a></dt>
-
- <dt>2. <a href="ape.html#id2948673">VERBATIM
- COPYING</a></dt>
-
- <dt>3. <a href="ape.html#id2948707">COPYING IN
- QUANTITY</a></dt>
-
- <dt>4. <a
- href="ape.html#id2948791">MODIFICATIONS</a></dt>
-
- <dt>5. <a href="ape.html#id2949025">COMBINING
- DOCUMENTS</a></dt>
-
- <dt>6. <a href="ape.html#id2949073">COLLECTIONS OF
- DOCUMENTS</a></dt>
-
- <dt>7. <a href="ape.html#id2949112">AGGREGATION
- WITH INDEPENDENT WORKS</a></dt>
-
- <dt>8. <a
- href="ape.html#id2949149">TRANSLATION</a></dt>
-
- <dt>9. <a
- href="ape.html#id2949177">TERMINATION</a></dt>
-
- <dt>10. <a href="ape.html#id2949201">FUTURE
- REVISIONS OF THIS LICENSE</a></dt>
-
- <dt><a href="ape.html#id2948479">How to use this
- License for your documents</a></dt>
- </dl>
- </dd>
-
- <dt><a href="bi01.html">Bibliography</a></dt>
- </dl>
- </div>
- </div>
-
- <div class="bibliography">
- <div class="titlepage">
- <div>
- <h2 class="title"><a id="id2935958"
- name="id2935958"></a>Bibliography</h2>
- </div>
- </div>
-
- <div class="bibliomixed">
- <a id="pk:texdraw" name="pk:texdraw"></a>
-
- <p class="bibliomixed">[pk:texdraw] manual author =
- "Peter Kabal", title = "{\TeX draw}: PostScript drawings
- from {\TeX}", edition = "1.4a", month = jul, year = 1992,
- etext = "CTAN:graphics/texdraw/manual/*"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="chicman" name="chicman"></a>
-
- <p class="bibliomixed">[chicman] manual editor = "John
- Grossman", Title = "The Chicago Manual of Style",
- publisher = "University of Chicago Press", year = "1993",
- edition = "fourteenth", organization = "University of
- Chicago"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="lw:progperl" name="lw:progperl"></a>
-
- <p class="bibliomixed">[lw:progperl] book Author = "Larry
- Wall and Randal L. Schwartz", Title = "Programming Perl",
- Publisher = O'Reilly &amp; Associates, Year = 1992, isbn
- = "0-937175-64-1"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="eu:international" name="eu:international"></a>
-
- <p class="bibliomixed">[eu:international] book Author =
- "Emmanual Uren and Robert Howard and Tiziana Perinotti",
- title = "Software Internationalization and Localization:
- An Introduction", publisher = "Van Nostrand Reinhold",
- year = 1993, isbn = "0-442-01498-8"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="latexcompanion" name="latexcompanion"></a>
-
- <p class="bibliomixed">[latexcompanion] book author =
- "Michel Goossens and Frank Mittelbach and Alexander
- Samarin", title = "The {\LaTeX} Companion", publisher =
- Addison Wesley, year = 1994, isbn = "0-201-54199-8"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="eg:dratex" name="eg:dratex"></a>
-
- <p class="bibliomixed">[eg:dratex] Book author = "Eitan
- M. Gurari", title = "{\TeX} {\&amp;} {\LaTeX}: Drawing
- and Literate Programming", publisher = "McGraw Hill",
- year = 1993, isbn = "0-07-911616-7"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="kl:japinfoproc" name="kl:japinfoproc"></a>
-
- <p class="bibliomixed">[kl:japinfoproc] Book author =
- "Ken Lunde", title = "Understanding Japanese Information
- Processing", address = "Sebastopol, CA", publisher =
- O'Reilly &amp; Associates, year = 1993, edition =
- "first", isbn = "1-56592-043-0"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="kn:texbook" name="kn:texbook"></a>
-
- <p class="bibliomixed">[kn:texbook] Book author = "Donald
- E. Knuth", title = "The {\TeX}book", publisher = Addison
- Wesley, year = 1989, edition = "Fifteenth", isbn =
- "0-201-13447-0", paperisbn = "0-201-13448-9"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="jh:latexforeveryone"
- name="jh:latexforeveryone"></a>
-
- <p class="bibliomixed">[jh:latexforeveryone] Book author
- = "Jane Hahn", title = "{\LaTeX} For Everyone", publisher
- = "Personal {\TeX}, Inc.", year = 1991, edition =
- "Second", paperisbn = "0-9631044-0-3"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="dn:psyeveryday" name="dn:psyeveryday"></a>
-
- <p class="bibliomixed">[dn:psyeveryday] Book author =
- "Donald A. Norman", title = "The Psychology of Everyday
- Things", publisher = "Basic Books, Inc.", year = 1988,
- paperisbn = "0-465-06709-3"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="ll:latexbook" name="ll:latexbook"></a>
-
- <p class="bibliomixed">[ll:latexbook] Book author =
- "Leslie Lamport", title = "{\rm \LaTeX:} A Document
- Preparation System", publisher = Addison Wesley, year =
- 1986, paperisbn = "0-201-15790-X"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="ll:makeindex" name="ll:makeindex"></a>
-
- <p class="bibliomixed">[ll:makeindex] unpublished author
- = "Leslie Lamport", title = "MakeIndex: An Index
- Processor for {\rm\LaTeX}", year = 1987, month = feb,
- etext = "CTAN:indexing/makeindex/doc/*"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="dc:colorlatex" name="dc:colorlatex"></a>
-
- <p class="bibliomixed">[dc:colorlatex] unpublished author
- = "David Carlisle", title = "The implementation of the
- {\LaTeX} Colour interface", year = 1994, month = feb</p>
- </div>
-
- <div class="bibliomixed">
- <a id="kn:mfbook" name="kn:mfbook"></a>
-
- <p class="bibliomixed">[kn:mfbook] Book author = "Donald
- E. Knuth", title = "{\TheMFbook}", publisher = Addison
- Wesley, year = 1986, isbn = "0-201-13445-4"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="ms:joyoftex" name="ms:joyoftex"></a>
-
- <p class="bibliomixed">[ms:joyoftex] Book author =
- "Michel Spivak", title = "The Joy of {\TeX}---A Gourmet
- Guide to Typesetting with the {\AMSTeX} Macro Package",
- publisher = Addison Wesley, year = "1986"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="or:emacs" name="or:emacs"></a>
-
- <p class="bibliomixed">[or:emacs] Book author = "Debra
- Cameron and Bill Rosenblatt", title = "Learning GNU
- Emacs", address = "Sebastopol, CA", publisher = O'Reilly
- &amp; Associates, year = "1991", isbn =
- "0-937175-84-6"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="gu:numbertheory" name="gu:numbertheory"></a>
-
- <p class="bibliomixed">[gu:numbertheory] Book author =
- "Richard K. Guy", title = "Unsolved Problems in Number
- Theory", publisher = "Springer-Verlag", year = 1981, isbn
- = "0-387-90593-6", series = "Unsolved Problems in
- Intuitive Mathematics", volume = 1</p>
- </div>
-
- <div class="bibliomixed">
- <a id="js:comp" name="js:comp"></a>
-
- <p class="bibliomixed">[js:comp] unpublished author =
- "Joachim Schrod", title = "The Components of {\TeX{}}",
- year = 1991, month = mar, etext =
- "CTAN:info/components-of-TeX/*"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="em:dvidrv" name="em:dvidrv"></a>
-
- <p class="bibliomixed">[em:dvidrv] manual author =
- "Eberhard Mattes", title = "The {\emTeX} DVI Driver
- Manual", year = 1993, month = Jun,</p>
- </div>
-
- <div class="bibliomixed">
- <a id="mw:pictex" name="mw:pictex"></a>
-
- <p class="bibliomixed">[mw:pictex] manual author =
- "Michael J. Wichura", title = "The {\PiCTeX} Manual",
- year = 1992, month = mar, publisher = "The \TeX\ User's
- Group"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="l3:project" name="l3:project"></a>
-
- <p class="bibliomixed">[l3:project] unpublished author =
- "Frank Mittelbach and Chris Rowley", title = "The
- {\LaTeX}3 Project", year = 1993, month = apr, etext =
- "CTAN:info/ltx3pub/l3d001.tex"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="FAQ:comp.text" name="FAQ:comp.text"></a>
-
- <p class="bibliomixed">[FAQ:comp.text] unpublished author
- = "Chris Lewis and Nils-Peter Nelson", title =
- "Frequently Asked Questions for {\texttt{comp.text}}",
- year = 1993, month = jun, etext =
- "rtfm.mit.edu:/pub/usenet/comp.text.tex"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="texware:tftopl" name="texware:tftopl"></a>
-
- <p class="bibliomixed">[texware:tftopl] unpublished
- author = "Donald E. Knuth", title = "The TF to PL
- Processor", howpublished = "Part of the {\web}
- distribution",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="texware:vptovf" name="texware:vptovf"></a>
-
- <p class="bibliomixed">[texware:vptovf] unpublished
- author = "Donald E. Knuth", title = "The VP to VF
- Processor", howpublished = "Part of the {\web}
- distribution",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="mfware:gftopk" name="mfware:gftopk"></a>
-
- <p class="bibliomixed">[mfware:gftopk] unpublished author
- = "Donald E. Knuth", title = "The GF to PK Processor",
- howpublished = "Part of the {\web} distribution",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="texware:pltotf" name="texware:pltotf"></a>
-
- <p class="bibliomixed">[texware:pltotf] unpublished
- author = "Donald E. Knuth", title = "The PL to TF
- Processor", howpublished = "Part of the {\web}
- distribution",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="texware:vftovp" name="texware:vftovp"></a>
-
- <p class="bibliomixed">[texware:vftovp] unpublished
- author = "Donald E. Knuth", title = "The VF to VP
- Processor", howpublished = "Part of the {\web}
- distribution",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="gt:mfbeginners" name="gt:mfbeginners"></a>
-
- <p class="bibliomixed">[gt:mfbeginners] unpublished
- author = "Geoffrey Tobin", title = "METAFONT for
- Beginners", year = 1992, month = dec, etext =
- "CTAN:info/metafont-for-beginners.tex"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="zw:simple" name="zw:simple"></a>
-
- <p class="bibliomixed">[zw:simple] unpublished author =
- "Zden\v{e}k Wagner", title = "Simple Drawings in {\MF}",
- year = "1993", etext = "CTAN:info/wagner-drawing.tex"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="lreq:metafonts" name="lreq:metafonts"></a>
-
- <p class="bibliomixed">[lreq:metafonts] unpublished
- author = "Liam R. E. Quin", title = "Definitive List of
- All Fonts Available for {\MF}", year = 1991, month = sep,
- etext = "CTAN:info/metafonts.lst"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="mf:inrstexref" name="mf:inrstexref"></a>
-
- <p class="bibliomixed">[mf:inrstexref] Manual author =
- "Michael J. Ferguson", title = "{\INRSTeX} Manual",
- organization = "INRS Communications", year = "1991",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="pcl5:techref" name="pcl5:techref"></a>
-
- <p class="bibliomixed">[pcl5:techref] Manual title = "PCL
- 5 Printer Language Technical Reference Manual",
- organization = "Hewlett Packard", year = 1990, month =
- sep, edition = "First"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="type1:format" name="type1:format"></a>
-
- <p class="bibliomixed">[type1:format] Manual title =
- "Adobe Type 1 Font Format, version 1.1", organization =
- Adobe Systems Incorporated, year = 1990, month = aug,
- Edition = "First"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="intellifont" name="intellifont"></a>
-
- <p class="bibliomixed">[intellifont] Manual title =
- "IntelliFont Scalable Typeface Format", organization =
- "Agfa Compugraphic Division", year = 1991, Month = apr,
- Edition = "First"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="nfss" name="nfss"></a>
-
- <p class="bibliomixed">[nfss] unpublished AUTHOR = "Frank
- Mittelbach and Rainer {Sch\"opf}", TITLE = "The New Font
- Selection Scheme---User Interface Standard to {\LaTeX}",
- YEAR = 1990, howpublished = "Part of the NFSS
- distribution"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="nfss2interface" name="nfss2interface"></a>
-
- <p class="bibliomixed">[nfss2interface] unpublished
- AUTHOR = "Frank Mittelbach", TITLE = "Interface
- description of NFSS2", YEAR = 1993, howpublished = "Part
- of the NFSS2 distribution"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="psfonts" name="psfonts"></a>
-
- <p class="bibliomixed">[psfonts] Techreport key = Adobe
- Systems Incorporated, TITLE = "Supporting Downloadable
- PostScript Fonts", address = "Mountain View, CA",
- INSTITUTION = Adobe Systems Incorporated, NUMBER =
- "5040", YEAR = 1988, MONTH = jan, etext =
- "CTAN:fonts/postscript/adobe/Documents/5040.Download_Fonts.ps"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="abffiles" name="abffiles"></a>
-
- <p class="bibliomixed">[abffiles] techreport key = adobe,
- TITLE = "Adobe Binary Screen Font Files", INSTITUTION =
- Adobe Systems Incorporated, YEAR = 1989, MONTH = jan,
- NUMBER = 5006, etext =
- "CTAN:fonts/postscript/adobe/Documents/5006.ABF_Spec.ps"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="afmfiles" name="afmfiles"></a>
-
- <p class="bibliomixed">[afmfiles] techreport key = adobe,
- TITLE = "Adobe Font Metric Files", INSTITUTION = Adobe
- Systems Incorporated, YEAR = 1990, MONTH = mar, NUMBER =
- 5004, etext =
- "CTAN:fonts/postscript/adobe/Documents/5004.AFM_Spec.ps"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="macfond" name="macfond"></a>
-
- <p class="bibliomixed">[macfond] Techreport key = adobe,
- TITLE = "Macintosh {FOND} Resources", INSTITUTION = Adobe
- Systems Incorporated, NUMBER = "0091", YEAR = 1990, MONTH
- = jul, etext =
- "jasper.ora.com:/pub/AdobeDocs/Specifications/0091-FondResources.ps"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="bdffiles" name="bdffiles"></a>
-
- <p class="bibliomixed">[bdffiles] techreport key = adobe,
- TITLE = "Character Bitmap Distribution Format",
- INSTITUTION = Adobe Systems Incorporated, YEAR = 1989,
- MONTH = jan, NUMBER = 5005, etext =
- "CTAN:fonts/postscript/adobe/Documents/5005.BDF_Spec.ps"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="dvi:standard" name="dvi:standard"></a>
-
- <p class="bibliomixed">[dvi:standard] unpublished key =
- "tug dvi driver standards committee", author = "{The TUG
- DVI Driver Standards Committee}", TITLE = "The DVI Driver
- Standard, Level 0 Version 0.05", INSTITUTION = "The
- {\TeX} User's Group", YEAR = 1991, MONTH = aug, etext =
- "jasper.ora.com:/pub/docs/DVI-Standard-level0/*"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="faq:comp.text.tex" name="faq:comp.text.tex"></a>
-
- <p class="bibliomixed">[faq:comp.text.tex] unpublished
- AUTHOR = "Bobby Bodenheimer", title = "{\TeX}, {\LaTeX},
- etc.: Frequently Asked Questions with Answers", year =
- 1992, month = dec, etext =
- "rtfm.mit.edu:/pub/usenet/comp.text.tex/*"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="faq:comp.fonts" name="faq:comp.fonts"></a>
-
- <p class="bibliomixed">[faq:comp.fonts] unpublished
- AUTHOR = "Norman Walsh", title = "The
- {\texttt{comp.fonts}} Frequently Asked Questions List",
- year = 1992, month = dec, etext =
- "rtfm.mit.edu:/pub/usenet/comp.fonts/FAQ.*"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="nw:fontbook" name="nw:fontbook"></a>
-
- <p class="bibliomixed">[nw:fontbook] unpublished AUTHOR =
- "Norman Walsh", title = "Font Samples of
- Internet-Available PostScript Type1 Fonts", year = 1992,
- month = dec, etext = "jasper.ora.com:/pub/fontbook/*"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="metapost" name="metapost"></a>
-
- <p class="bibliomixed">[metapost] unpublished AUTHOR =
- "John D. Hobby", title = "A User's Manual for MetaPost",
- institution = "AT{\&amp;}T Bell Laboratories", etext =
- "research.att.com:/pub/research/cstr/162.Z"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:10-2" name="tug:10-2"></a>
-
- <p class="bibliomixed">[tug:10-2] ARTICLE AUTHOR = "Frank
- Mittelbach and Rainer {Sch\"opf}", TITLE = "A new font
- selection scheme for {\TeX} macro packages---the basic
- macros", JOURNAL = "TUGboat", YEAR = 1989, MONTH = jul,
- NUMBER = 2, VOLUME = 10, PAGES = "222--238"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:vfonts:dek" name="tug:vfonts:dek"></a>
-
- <p class="bibliomixed">[tug:vfonts:dek] ARTICLE AUTHOR =
- "Donald E. Knuth", TITLE = "Virtual Fonts: More fun for
- Grand Wizards", JOURNAL = "TUGboat", YEAR = 1990, MONTH =
- apr, NUMBER = 1, VOLUME = 11, PAGES = "13--23"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:gr-tex-pc:1" name="tug:gr-tex-pc:1"></a>
-
- <p class="bibliomixed">[tug:gr-tex-pc:1] ARTICLE AUTHOR =
- "Lee S. Pickrell", TITLE = "Combining graphics with
- {\TeX} on IBM PC-compatible systems with LaserJet
- printers", JOURNAL = "TUGboat", YEAR = 1990, MONTH = apr,
- NUMBER = 1, VOLUME = 11, PAGES = "26--31"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:gr-tex-pc:2" name="tug:gr-tex-pc:2"></a>
-
- <p class="bibliomixed">[tug:gr-tex-pc:2] ARTICLE AUTHOR =
- "Lee S. Pickrell", TITLE = "Combining graphics with
- {\TeX} on PC systems with laser printers, part II",
- JOURNAL = "TUGboat", YEAR = 1990, MONTH = jun, NUMBER =
- 2, VOLUME = 11, PAGES = "200--206"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:gr-tex-implementation"
- name="tug:gr-tex-implementation"></a>
-
- <p class="bibliomixed">[tug:gr-tex-implementation]
- ARTICLE AUTHOR = "Gerhard Berendt", TITLE = "On the
- implementation of graphics into {\TeX}", JOURNAL =
- "TUGboat", YEAR = 1990, MONTH = jun, NUMBER = 2, VOLUME =
- 11, PAGES = "190--194"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:mac-graphics-latex"
- name="tug:mac-graphics-latex"></a>
-
- <p class="bibliomixed">[tug:mac-graphics-latex] ARTICLE
- AUTHOR = "Len Schwer", TITLE = "Including Macintosh
- graphics in {\LaTeX} documents", JOURNAL = "TUGboat",
- YEAR = 1990, MONTH = jun, NUMBER = 2, VOLUME = 11, PAGES
- = "194--200"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:nfss-userinterface"
- name="tug:nfss-userinterface"></a>
-
- <p class="bibliomixed">[tug:nfss-userinterface] ARTICLE
- AUTHOR = "Frank Mittelbach and Rainer {Sch\"opf}", TITLE
- = "The new font family selection---User Interface to
- Standard {\LaTeX}", JOURNAL = "TUGboat", YEAR = 1990,
- MONTH = jun, NUMBER = 1, VOLUME = 11, PAGES = "297--305",
- Note = "Reprinted with corrections in TUGboat 11:2."</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:transfig" name="tug:transfig"></a>
-
- <p class="bibliomixed">[tug:transfig] ARTICLE AUTHOR =
- "Micah Beck and A. Siegal", TITLE = "Transfig: Portable
- Graphics for {\TeX}", JOURNAL = "TUGboat", YEAR = 1990,
- MONTH = sep, NUMBER = 3, VOLUME = 11, PAGES =
- "373--380"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:vtex" name="tug:vtex"></a>
-
- <p class="bibliomixed">[tug:vtex] ARTICLE AUTHOR =
- "Michael Vulis", TITLE = "V{\TeX} enhancements to the
- {\TeX} language", JOURNAL = "TUGboat", YEAR = 1990, MONTH
- = sep, NUMBER = 3, VOLUME = 11, PAGES = "429--435"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:filenames-fonts"
- name="tug:filenames-fonts"></a>
-
- <p class="bibliomixed">[tug:filenames-fonts] ARTICLE
- AUTHOR = "Karl Berry", TITLE = "Filenames for Fonts",
- JOURNAL = "TUGboat", YEAR = 1990, MONTH = nov, NUMBER =
- 4, VOLUME = 11, PAGES = "517--520"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:gr-tex-bm2font" name="tug:gr-tex-bm2font"></a>
-
- <p class="bibliomixed">[tug:gr-tex-bm2font] ARTICLE
- AUTHOR = "Friedhelm Sowa", TITLE = "Integration of
- graphics into {\TeX}", JOURNAL = "TUGboat", YEAR = 1991,
- MONTH = mar, NUMBER = 1, VOLUME = 12, PAGES =
- "58--63",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:halftoning" name="tug:halftoning"></a>
-
- <p class="bibliomixed">[tug:halftoning] ARTICLE AUTHOR =
- "Adrian F. Clark", TITLE = "Practical halftoning in
- {\TeX}", JOURNAL = "TUGboat", YEAR = 1991, MONTH = mar,
- NUMBER = 1, VOLUME = 12, PAGES = "157--165",</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:xbitmaps" name="tug:xbitmaps"></a>
-
- <p class="bibliomixed">[tug:xbitmaps] ARTICLE AUTHOR =
- "Reinhard {F\"o\ss{}meier}", TITLE = "X bitmaps in
- {\TeX}", JOURNAL = "TUGboat", YEAR = 1991, MONTH = jun,
- NUMBER = 2, VOLUME = 12, PAGES = "229--232"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="tug:bm2font2" name="tug:bm2font2"></a>
-
- <p class="bibliomixed">[tug:bm2font2] ARTICLE AUTHOR =
- "Friedhelm Sowa", TITLE = "Bitmaps and halftones with
- BM2FONT", JOURNAL = "TUGboat", YEAR = 1991, MONTH = dec,
- NUMBER = 3, VOLUME = 12, PART = "II", PAGES =
- "534--539"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="op:btxdoc" name="op:btxdoc"></a>
-
- <p class="bibliomixed">[op:btxdoc] unpublished author =
- "Oren Patashnik", title = "{\BibTeX}ing", year = 1988,
- month = feb, etext =
- "CTAN:biblio/bibtex/distribs/doc/btxdoc.tex"</p>
- </div>
-
- <div class="bibliomixed">
- <a id="op:btxhak" name="op:btxhak"></a>
-
- <p class="bibliomixed">[op:btxhak] unpublished author =
- "Oren Patashnik", title = "Designing {\BibTeX} Styles",
- year = 1988, month = feb, etext =
- "CTAN:biblio/bibtex/distribs/doc/btxhak.tex"</p>
- </div>
- </div>
- </div>
-
- <div class="navfooter">
- <table width="100%" summary="Navigation table">
- <tr>
- <td width="40%" align="left"><a
- title="Chapter&#160;12.&#160;Bibliographies, Indexes, and Glossaries"
- href="ch12.html"><img src="figures/nav-prev.png"
- alt="Prev" border="0" /></a>&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-home.png"
- alt="Home" border="0" /></a></td>
-
- <td width="40%" align="right">&#160;<a
- title="Chapter&#160;13.&#160;Non-commercial Environments"
- href="ch13.html"><img src="figures/nav-next.png"
- alt="Next" border="0" /></a></td>
- </tr>
-
- <tr>
- <td width="40%" align="left">
- Chapter&#160;12.&#160;Bibliographies, Indexes, and
- Glossaries&#160;</td>
-
- <td width="20%" align="center"><a title="Making TeX Work"
- href="index.html"><img src="figures/nav-up.png" alt="Up"
- border="0" /></a></td>
-
- <td width="40%" align="right">
- &#160;Chapter&#160;13.&#160;Non-commercial
- Environments</td>
- </tr>
- </table>
- </div>
- </body>
-</html>
-