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