1 .TH TEX 1 "16 June 2015" "Web2C @VERSION@"
2 .\"=====================================================================
5 .if t .ds TX \fRT\\h'-0.1667m'\\v'0.20v'E\\v'-0.20v'\\h'-0.125m'X\fP
7 .ie t .ds OX \fIT\v'+0.25m'E\v'-0.25m'X\fP
9 .\" BX definition must follow TX so BX can use TX
10 .if t .ds BX \fRB\s-2IB\s0\fP\*(TX
12 .\" LX definition must follow TX so LX can use TX
13 .if t .ds LX \fRL\\h'-0.36m'\\v'-0.15v'\s-2A\s0\\h'-0.15m'\\v'0.15v'\fP\*(TX
16 .if t .ds WB W\s-2EB\s0
17 .\" EX and EE are used for displays that are pure code
26 .\"=====================================================================
28 tex, initex \- text formatting and typesetting
33 .RI [ file | \fB\e\fPcommands ]
34 .\"=====================================================================
36 Run the \*(TX typesetter on
40 If the file argument has no extension, ".tex" will be appended to it.
41 Instead of a filename, a set of \*(TX commands can be given, the first
42 of which must start with a backslash.
45 argument \*(TX uses a different set of precompiled commands,
47 .IR format\fB.fmt\fP ;
48 it is usually better to use the
54 formats the interspersed text and commands contained in the named
56 and outputs a typesetter independent file (called
59 .IR "DeVice Independent" ).
60 \*(TX's capabilities and language are described in
63 is normally used with a large body of precompiled macros,
64 and there are several specific formatting systems, such as
66 which require the support of several macro files.
68 This version of \*(TX looks at its command line to see what name it
69 was called under. If they exist, then both
73 are symbolic links to the
75 executable. When called as
79 option is given) it can be used to precompile macros into a
85 format. When called under any other name, \*(TX will use that name as
86 the name of the format to use. For example, when called as
90 format is used, which is identical to the
92 format. The commands defined by the
94 format are documented in
96 Other formats that are often available include
101 The non-option command line arguments to the
103 program are passed to it as the first input line. (But it is often
104 easier to type extended arguments as the first input line, since UNIX
105 shells tend to gobble up or misinterpret \*(TX's favorite symbols,
106 like backslashes, unless you quote them.)
108 .IR "The \*(OXbook" ,
109 that first line should begin with a filename, a
110 .IR \econtrolsequence ,
114 The normal usage is to say
122 will be the ``jobname'', and is used in forming
124 If \*(TX doesn't get a filename in the first line, the jobname is
126 When looking for a file, \*(TX looks for the name with and without the
129 appended, unless the name already contains that extension. If
132 a log of error messages, with rather more detail than normally appears
133 on the screen, will appear in
135 and the output file will be in
138 This version of \*(TX can look in the first line of the file
140 to see if it begins with the magic sequence
142 If the first line begins with
144 .BI -translate-file \ tcxname
145 then \*(TX will use the named format and translation table
147 to process the source file. Either the format name or the
149 specification may be omitted, but not both. This overrides the
150 format selection based on the name by which the program is invoked.
155 configuration variable controls whether this behaviour is enabled.
159 response to \*(TX's error prompt causes the system default editor to
160 start up at the current line of the current file. The environment
161 variable TEXEDIT can be used to change the editor used. It may
162 contain a string with "%s" indicating where the filename goes and "%d"
163 indicating where the decimal line number (if any) goes. For example,
170 \fITEXEDIT="emacs +%d %s"; export TEXEDIT\fP
173 A convenient file in the library is
176 When \*(TX can't find a file it thinks you want to input, it keeps
177 asking you for another filename; responding `null' gets you out
178 of the loop if you don't want to input anything. You can also type your
179 EOF character (usually control-D).
181 .\"=====================================================================
183 This version of \*(TX understands the following command line options.
186 Enable the enc\*(TX extensions. This option is only effective in
189 For documentation of the enc\*(TX extensions see
190 .BR http://www.olsak.net/enctex.html .
193 Print error messages in the form
195 which is similar to the way many compilers format them.
197 .B -no-file-line-error
198 Disable printing error messages in the
202 .B -file-line-error-style
203 This is the old name of the
210 as the name of the format to be used, instead of the name by which
211 \*(TX was called or a
216 Exit with an error code when an error is encountered during processing.
219 Print help message and exit.
224 mode, which is used to dump formats. The
226 mode can be used for typesetting, but no format is preloaded, and
227 basic initializations like setting catcodes may be required.
229 .BI -interaction \ mode
230 Sets the interaction mode. The mode can be either
236 The meaning of these modes is the same as that of the corresponding
240 Send DVI output to a socket as well as the usual output file. Whether
241 this option is available is the choice of the installer.
246 and starts the server at the other end as well. Whether this option
247 is available is the choice of the installer.
252 for the job name, instead of deriving it from the name of the input file.
254 .BI -kpathsea-debug \ bitmask
255 Sets path searching debugging flags according to the bitmask. See the
270 Enable ML\*(TX extensions. Only effective in combination with
283 .BI -output-comment \ string
288 file comment instead of the date.
290 .BI -output-directory \ directory
291 Write output files in
293 instead of the current directory. Look up input files in
295 first, then along the normal search path. See also description of the
296 TEXMFOUTPUT environment variable.
299 If the first line of the main input file begins with
301 parse it to look for a dump name or a
305 .B -no-parse-first-line
306 Disable parsing of the first line of the main input file.
309 Pretend to be program
311 This affects both the format used and the search paths.
314 Enable the filename recorder. This leaves a trace of the files opened
315 for input and output in a file with extension
320 .BI \ewrite18{ command }
323 can be any shell command. This construct is normally
324 disallowed for security reasons.
328 .BI \ewrite18{ command }
329 construct, even if it is enabled in the
334 Insert source specials into the
338 .BI -src-specials \ where
339 Insert source specials in certain places of the
343 is a comma-separated value list:
353 .BI -translate-file \ tcxname
356 translation table to set the mapping of input characters and
357 re-mapping of output characters.
359 .BI -default-translate-file \ tcxname
364 line can overrule this setting.
367 Print version information and exit.
368 .\"=====================================================================
370 See the Kpathsearch library documentation (the `Path specifications'
371 node) for precise details of how the environment variables are used.
374 utility can be used to query the values of the variables.
376 One caveat: In most \*(TX formats, you cannot use ~ in a filename you
377 give directly to \*(TX, because ~ is an active character, and hence is
378 expanded, not taken as part of the filename. Other programs, such as
379 \*(MF, do not have this problem.
383 Normally, \*(TX puts its output files in the current directory. If
384 any output file cannot be opened there, it tries to open it in the
385 directory specified in the environment variable TEXMFOUTPUT.
386 There is no default value for that variable. For example, if you say
388 and the current directory is not writable, if TEXMFOUTPUT has
391 \*(TX attempts to create
395 if any output is produced.) TEXMFOUTPUT is also checked for input
396 files, as \*(TX often generates files that need to be subsequently
397 read; for input, no suffixes (such as ``.tex'') are added by default,
398 the input name is simply checked as given.
406 This probably start with ``.'', so
407 that user files are found before system files. An empty path
408 component will be replaced with the paths defined in the
410 file. For example, set TEXINPUTS to ".:/home/user/tex:" to prepend the
411 current directory and ``/home/user/tex'' to the standard search path.
414 Search path for format files.
422 Command template for switching to editor. The default, usually
424 is set when \*(TX is compiled.
427 Search path for font metric
430 .\"=====================================================================
432 The location of the files mentioned below varies from system to
435 utility to find their locations.
438 Configuration file. This contains definitions of search paths as well
439 as other configuration parameters like
440 .BR parse_first_line .
443 Text file containing \*(TX's internal strings.
446 Filename mapping definitions.
449 Metric files for \*(TX's fonts.
452 Predigested \*(TX format (.\|fmt) files.
454 .I $TEXMFMAIN/tex/plain/base/plain.tex
455 The basic macro package described in the \*(OXbook.
457 .\"=====================================================================
459 This manual page is not meant to be exhaustive. The complete
460 documentation for this version of \*(TX can be found in the info manual
461 .IR "Web2C: A TeX implementation" .
462 .\"=====================================================================
464 This version of \*(TX implements a number of optional extensions.
465 In fact, many of these extensions conflict to a greater or lesser
466 extent with the definition of \*(TX. When such extensions are
467 enabled, the banner printed when \*(TX starts is changed to print
472 This version of \*(TX fails to trap arithmetic overflow when
473 dimensions are added or subtracted. Cases where this occurs are rare,
474 but when it does the generated
476 file will be invalid.
477 .\"=====================================================================
482 .IR "The \*(OXbook" ,
483 Addison-Wesley, 1986, ISBN 0-201-13447-0.
486 .IR "\*(LX \- A Document Preparation System" ,
487 Addison-Wesley, 1985, ISBN 0-201-15790-X.
490 .IR "Eplain: Expanded plain \*(TX" ,
491 ftp://ftp.cs.umb.edu/pub/tex/eplain/doc.
494 .IR "The Joy of \*(OX" ,
495 2nd edition, Addison-Wesley, 1990, ISBN 0-8218-2997-1.
498 (the journal of the \*(TX Users Group).
499 .\"=====================================================================
501 \*(TX, pronounced properly, rhymes with ``blecchhh.'' The proper
502 spelling in typewriter-like fonts is ``TeX'' and not ``TEX'' or ``tex.''
503 .\"=====================================================================
505 \*(TX was created by Donald E. Knuth,
506 who implemented it using his \*(WB system for Pascal programs.
507 It was ported to Unix at Stanford by Howard Trickey, and
508 at Cornell by Pavel Curtis.
509 The version now offered with the Unix \*(TX distribution is that
510 generated by the \*(WB to C system
512 originally written by Tomas Rokicki and Tim Morgan.
514 The enc\*(TX extensions were written by Petr Olsak.