1 .TH ALEPH 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
15 .if t .ds AX \fRA\\h'-0.1667m'\\v'0.20v'M\\v'-0.20v'\\h'-0.125m'S\fP\*(TX
17 .if t .ds AY \fRA\\h'-0.1667m'\\v'0.20v'M\\v'-0.20v'\\h'-0.125m'S\fP\*(LX
19 .\"=====================================================================
21 aleph \- extended Unicode TeX
26 .RI [ file | \fB\e\fPcommands ]
27 .\"=====================================================================
29 Run the Aleph typesetter on
33 If the file argument has no extension, ".tex" will be appended to it.
34 Instead of a filename, a set of Aleph commands can be given, the first
35 of which must start with a backslash.
38 argument Aleph uses a different set of precompiled commands,
40 .IR format\fB.fmt\fP ;
41 it is usually better to use the
46 Aleph is a version of the \*(TX program modified for multilingual
47 typesetting. It uses Unicode, and has additional primitives for
48 (among other things) bidirectional typesetting.
50 Aleph's command line options are similar to those of \*(TX.
52 Aleph is no longer being actively developed; see LuaTeX for current
54 .\"=====================================================================
56 Run aleph --help to see the complete list of options; this is not
62 as the name of the format to be used, instead of the name by which
68 Exit with an error code when an error is encountered during processing.
71 Print help message and exit.
74 Be `initial' Aleph for dumping formats; this is implicitly true if the
78 .BI --interaction \ mode
79 Sets the interaction mode. The mode can be one of
85 The meaning of these modes is the same as that of the corresponding
89 Send DVI output to a socket as well as the usual output file. Whether
90 this option is available is the choice of the installer.
95 and starts the server at the other end as well. Whether this option
96 is available is the choice of the installer.
98 .BI --kpathsea-debug \ bitmask
99 Sets path searching debugging flags according to the bitmask. See the
113 .BI --no-maketex \ fmt
123 .BI --output-comment \ string
126 for the DVI file comment instead of the date.
128 .BI --output-directory \ directory
129 Write output files in
131 instead of the current directory. Look up input files in
133 first, the along the normal search path.
135 .B --parse-first-line
136 If the first line of the main input file begins with
138 parse it to look for a dump name.
140 .BI --progname \ name
141 Pretend to be program
143 This affects both the format used and the search paths.
146 Enable the filename recorder. This leaves a trace of the files opened
147 for input and output in a file with extension
149 (This option is always on.)
153 .BI \ewrite18{ command }
156 can be any Bourne shell command. By default, this construct is
157 enabled in a restricted mode, for security reasons.
160 Print version information and exit.
161 .\"=====================================================================
163 See the Kpathsearch library documentation (the `Path specifications'
164 node) for precise details of how the environment variables are used.
167 utility can be used to query the values of the variables.
169 One caveat: In most Aleph formats, you cannot use ~ in a filename you
170 give directly to Aleph, because ~ is an active character, and hence is
171 expanded, not taken as part of the filename. Other programs, such as
172 \*(MF, do not have this problem.
176 Normally, Aleph puts its output files in the current directory. If
177 any output file cannot be opened there, it tries to open it in the
178 directory specified in the environment variable TEXMFOUTPUT.
179 There is no default value for that variable. For example, if you say
181 and the current directory is not writable, if TEXMFOUTPUT has
184 Aleph attempts to create
188 if any output is produced.) TEXMFOUTPUT is also checked for input
189 files, as \*(TX often generates files that need to be subsequently
190 read; for input, no suffixes (such as ``.tex'') are added by default,
191 the input name is simply checked as given.
199 This should start with ``.'', so
200 that user files are found before system files. An empty path
201 component will be replaced with the paths defined in the
203 file. For example, set TEXINPUTS to ".:/home/user/tex:" to prepend the
204 current direcory and ``/home/user/tex'' to the standard search path.
207 Command template for switching to editor. The default, usually
209 is set when Aleph is compiled.
210 .\"=====================================================================
212 This manual page is not meant to be exhaustive. The complete
213 documentation for this version of Aleph can be found in the info
215 .IR "Web2C: A TeX implementation" .
216 See http://tug/org/web2c.
217 .\"=====================================================================
219 This version of Aleph implements a number of optional extensions.
220 In fact, many of these extensions conflict to a greater or lesser
221 extent with the definition of Aleph. When such extensions are
222 enabled, the banner printed when Aleph starts is changed to print
227 This version of Aleph fails to trap arithmetic overflow when
228 dimensions are added or subtracted. Cases where this occurs are rare,
229 but when it does the generated
231 file will be invalid.
232 .\"=====================================================================
236 .\"=====================================================================
238 The primary authors of Aleph are John Plaice and Yannis Haralambous.