Penguin
Recent Changes
Blame: pdfeinitex(1)
EditPageHistoryDiffInfoLikePages
Annotated edit history of pdfeinitex(1) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 PDFTEX
2 !!!PDFTEX
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 ENVIRONMENT
8 FILES
9 BUGS
10 SEE ALSO
11 AUTHORS
12 ----
13 !!NAME
14
15
16 pdfetex, pdfeinitex, pdfevirtex - PDF output from e-TeX
17 !!SYNOPSIS
18
19
20 __pdfetex__ [[''options'']
21 [[''commands'']
22 !!DESCRIPTION
23
24
25 This manual page is not meant to be exhaustive. The complete
26 documentation for this version of TEX can be found in the
27 info file or manual ''Web2C: A TeX
28 implementation''.
29
30
31 pdfeTEX is a version of e-TEX that can create ''PDF''
32 files as well as ''DVI'' files.
33
34
35 The typical use of pdfeTEX is with a pregenerated formats
36 for which PDF output has been enabled. The __pdfetex__
37 command uses the equivalent of the plain e-TEX format, and
38 the __pdfelatex__ command uses the equivalent of the e-L
39 A TEX format.
40
41
42 The __pdfeinitex__ and __pdfevirtex__ commands are
43 pdfeTEX's analogues to the __einitex__ and __evirtex__
44 commands. In this installation, they are symlinks to the
45 __pdfetex__ executable.
46
47
48 pdfeTEX's handling of its command-line arguments is similar
49 to that of e-TEX.
50
51
52 pdfeTEX is beta software.
53 !!OPTIONS
54
55
56 This version of pdfeTEX understands the following command
57 line options.
58
59
60 __--efmt__ ''format''
61
62
63 Use ''format'' as the name of the format to be used,
64 instead of the name by which pdfeTEX was called or a
65 ''%'' line.
66
67
68 __--file-line-error-style__
69
70
71 Print error messages in the form ''file:line:error''
72 which is similar to the way many compilers format
73 them.
74
75
76 __--help__
77
78
79 Print help message and exit.
80
81
82 __--ini__
83
84
85 Be __pdfeinitex__, for dumping formats; this is
86 implicitly true if the program is called as
87 __pdfeinitex__.
88
89
90 __--interaction__ ''mode''
91
92
93 Sets the interaction mode. The mode can be one of
94 ''batchmode'', ''nonstopmode'', ''scrollmode'', and
95 ''errorstopmode''. The meaning of these modes is the same
96 as that of the corresponding commands.
97
98
99 __--ipc__
100
101
102 Send DVI or PDF output to a socket as well as the usual
103 output file. Whether this option is available is the choice
104 of the installer.
105
106
107 __--ipc-start__
108
109
110 As __--ipc__, and starts the server at the other end as
111 well. Whether this option is available is the choice of the
112 installer.
113
114
115 __--kpathsea-debug__ ''bitmask''
116
117
118 Sets path searching debugging flags according to the
119 bitmask. See the ''Kpathsea'' manual for
120 details.
121
122
123 __--maketex__ ''fmt''
124
125
126 Enable mktex''fmt'', where ''fmt'' must be one of
127 ''tex'' or ''tfm''.
128
129
130 __--no-maketex__ ''fmt''
131
132
133 Disable mktex''fmt'', where ''fmt'' must be one of
134 ''tex'' or ''tfm''.
135
136
137 __--output-comment__ ''string''
138
139
140 Use ''string'' for the DVI file comment instead of the
141 date.
142
143
144 __--progname__ ''name''
145
146
147 Pretend to be program ''name''. This affects both the
148 format used and the search paths.
149
150
151 __--shell-escape__
152
153
154 Enable the __write18{__''command''__}__ construct.
155 The ''command'' can be any Bourne shell command. This
156 construct is normally disallowed for security
157 reasons.
158
159
160 __--translate-file__ ''tcxname''
161
162
163 Use the ''tcxname'' translation table.
164
165
166 __--version__
167
168
169 Print version information and exit.
170 !!ENVIRONMENT
171
172
173 See the Kpathsearch library documentation (the `Path
174 specifications' node) for precise details of how the
175 environment variables are used. The __kpsewhich__ utility
176 can be used to query the values of the
177 variables.
178
179
180 One caveat: In most pdfeTEX formats, you cannot use ~ in a
181 filename you give directly to pdfeTEX, because ~ is an
182 active character, and hence is expanded, not taken as part
183 of the filename. Other programs, such as M
184 ETAFONT , do not have this
185 problem.
186
187
188 TEXMFOUTPUT
189
190
191 Normally, pdfeTEX puts its output files in the current
192 directory. If any output file cannot be opened there, it
193 tries to open it in the directory specified in the
194 environment variable TEXMFOUTPUT. There is no default value
195 for that variable. For example, if you say ''pdfetex
196 paper'' and the current directory is not writable, if
197 TEXMFOUTPUT has the value ''/tmp'', pdfeTEX attempts to
198 create ''/tmp/paper.log'' (and ''/tmp/paper.pdf'', if
199 any output is produced.)
200
201
202 TEXINPUTS
203
204
205 Search path for ''input'' and ''openin'' files. This
206 should probably start with ``.'', so that user files are
207 found before system files. An empty path component will be
208 replaced with the paths defined in the ''texmf.cnf''
209 file. For example, set TEXINPUTS to
210 ''
211
212
213 TEXFONTS
214
215
216 Search path for font metric (''.tfm'')
217 files.
218
219
220 TEXFORMATS
221
222
223 Search path for format files.
224
225
226 TEXPOOL
227
228
229 search path for __pdfeinitex__ internal
230 strings.
231
232
233 TEXEDIT
234
235
236 Command template for switching to editor. The default,
237 usually __vi__, is set when pdfeTEX is
238 compiled.
239 !!FILES
240
241
242 The location of the files mentioned below varies from system
243 to system. Use the __kpsewhich__ utility to find their
244 locations.
245
246
247 ''pdfetex.pool''
248
249
250 Encoded text of pdfeTEX's messages.
251
252
253 ''texfonts.map''
254
255
256 Filename mapping definitions.
257
258
259 ''*.tfm''
260
261
262 Metric files for pdfeTEX's fonts.
263
264
265 ''*.fmt''
266
267
268 Predigested pdfeTEX format (.efmt) files.
269 !!BUGS
270
271
272 This version of pdfeTEX fails to trap arithmetic overflow
273 when dimensions are added or subtracted. Cases where this
274 occurs are rare, but when it does the generated ''DVI''
275 file will be invalid. Whether a generated ''PDF'' file
276 would be usable is unknown.
277
278
279 pdfeTEX is beta software. Subscribe to the pdftex mailing
280 list __pdftex@tug.org__ if you intend to use it. This is
281 a majordomo list, to subscribe send a message containing
282 ''subscribe pdftex'' to
283 __majordomo@tug.org__.
284 !!SEE ALSO
285
286
287 tex(1), mf(1), etex(1).
288 !!AUTHORS
289
290
291 The primary authors of pdfTEX are Han The Thanh, Petr Sojka,
292 and Jiri Zlatuska.
293 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.