Penguin
Recent Changes
Blame: pdfvirtex(1)
EditPageHistoryDiffInfoLikePages
Annotated edit history of pdfvirtex(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 pdftex, pdfinitex, pdfvirtex - PDF output from TeX
17 !!SYNOPSIS
18
19
20 __pdftex__ [[''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 pdfTEX is a version of TEX that can create ''PDF'' files
32 as well as ''DVI'' files.
33
34
35 The typical use of pdfTEX is with a pregenerated formats for
36 which PDF output has been enabled. The __pdftex__ command
37 uses the equivalent of the plain TEX format, and the
38 __pdflatex__ command uses the equivalent of the L
39 A TEX format.
40
41
42 The __pdfinitex__ and __pdfvirtex__ commands are
43 pdfTEX's analogues to the __initex__ and __virtex__
44 commands. In this installation, they are symlinks to the
45 __pdftex__ executable.
46
47
48 pdfTEX's handling of its command-line arguments is similar
49 to that of TEX.
50
51
52 pdfTEX is beta software.
53 !!OPTIONS
54
55
56 This version of pdfTEX understands the following command
57 line options.
58
59
60 __--file-line-error-style__
61
62
63 Print error messages in the form ''file:line:error''
64 which is similar to the way many compilers format
65 them.
66
67
68 __--fmt__ ''format''
69
70
71 Use ''format'' as the name of the format to be used,
72 instead of the name by which pdfTEX was called or a
73 ''%'' line.
74
75
76 __--help__
77
78
79 Print help message and exit.
80
81
82 __--ini__
83
84
85 Be __pdfinitex__, for dumping formats; this is implicitly
86 true if the program is called as
87 __pdfinitex__.
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 __--recorder__
152
153
154 Enable the filename recorder. This leaves a trace of the
155 files opened for input and output in a file with extension
156 ''.fls''.
157
158
159 __--shell-escape__
160
161
162 Enable the __write18{__''command''__}__ construct.
163 The ''command'' can be any Bourne shell command. This
164 construct is normally disallowed for security
165 reasons.
166
167
168 __--translate-file__ ''tcxname''
169
170
171 Use the ''tcxname'' translation table.
172
173
174 __--version__
175
176
177 Print version information and exit.
178 !!ENVIRONMENT
179
180
181 See the Kpathsearch library documentation (the `Path
182 specifications' node) for precise details of how the
183 environment variables are used. The __kpsewhich__ utility
184 can be used to query the values of the
185 variables.
186
187
188 One caveat: In most pdfTEX formats, you cannot use ~ in a
189 filename you give directly to pdfTEX, because ~ is an active
190 character, and hence is expanded, not taken as part of the
191 filename. Other programs, such as M ETAFONT ,
192 do not have this problem.
193
194
195 TEXMFOUTPUT
196
197
198 Normally, pdfTEX puts its output files in the current
199 directory. If any output file cannot be opened there, it
200 tries to open it in the directory specified in the
201 environment variable TEXMFOUTPUT. There is no default value
202 for that variable. For example, if you say ''pdftex
203 paper'' and the current directory is not writable, if
204 TEXMFOUTPUT has the value ''/tmp'', pdfTEX attempts to
205 create ''/tmp/paper.log'' (and ''/tmp/paper.pdf'', if
206 any output is produced.)
207
208
209 TEXINPUTS
210
211
212 Search path for ''input'' and ''openin'' files. This
213 should probably start with ``.'', so that user files are
214 found before system files. An empty path component will be
215 replaced with the paths defined in the ''texmf.cnf''
216 file. For example, set TEXINPUTS to
217 ''
218
219
220 TEXFONTS
221
222
223 Search path for font metric (''.tfm'')
224 files.
225
226
227 TEXFORMATS
228
229
230 Search path for format files.
231
232
233 TEXPOOL
234
235
236 search path for __pdfinitex__ internal
237 strings.
238
239
240 TEXEDIT
241
242
243 Command template for switching to editor. The default,
244 usually __vi__, is set when pdfTEX is
245 compiled.
246 !!FILES
247
248
249 The location of the files mentioned below varies from system
250 to system. Use the __kpsewhich__ utility to find their
251 locations.
252
253
254 ''pdftex.pool''
255
256
257 Encoded text of pdfTEX's messages.
258
259
260 ''texfonts.map''
261
262
263 Filename mapping definitions.
264
265
266 ''*.tfm''
267
268
269 Metric files for pdfTEX's fonts.
270
271
272 ''*.fmt''
273
274
275 Predigested pdfTEX format (.fmt) files.
276 !!BUGS
277
278
279 This version of pdfTEX fails to trap arithmetic overflow
280 when dimensions are added or subtracted. Cases where this
281 occurs are rare, but when it does the generated ''DVI''
282 file will be invalid. Whether a generated ''PDF'' file
283 would be usable is unknown.
284
285
286 pdfTEX is beta software. Subscribe to the pdftex mailing
287 list __pdftex@tug.org__ if you intend to use it. This is
288 a majordomo list, to subscribe send a message containing
289 ''subscribe pdftex'' to
290 __majordomo@tug.org__.
291 !!SEE ALSO
292
293
294 tex(1), mf(1).
295 !!AUTHORS
296
297
298 The primary authors of pdfTEX are Han The Thanh, Petr Sojka,
299 and Jiri Zlatuska.
300 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.