Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
pdfinitex(1)
Edit
PageHistory
Diff
Info
LikePages
PDFTEX !!!PDFTEX NAME SYNOPSIS DESCRIPTION OPTIONS ENVIRONMENT FILES BUGS SEE ALSO AUTHORS ---- !!NAME pdftex, pdfinitex, pdfvirtex - PDF output from TeX !!SYNOPSIS __pdftex__ [[''options''] [[''commands''] !!DESCRIPTION This manual page is not meant to be exhaustive. The complete documentation for this version of TEX can be found in the info file or manual ''Web2C: A TeX implementation''. pdfTEX is a version of TEX that can create ''PDF'' files as well as ''DVI'' files. The typical use of pdfTEX is with a pregenerated formats for which PDF output has been enabled. The __pdftex__ command uses the equivalent of the plain TEX format, and the __pdflatex__ command uses the equivalent of the L A TEX format. The __pdfinitex__ and __pdfvirtex__ commands are pdfTEX's analogues to the __initex__ and __virtex__ commands. In this installation, they are symlinks to the __pdftex__ executable. pdfTEX's handling of its command-line arguments is similar to that of TEX. pdfTEX is beta software. !!OPTIONS This version of pdfTEX understands the following command line options. __--file-line-error-style__ Print error messages in the form ''file:line:error'' which is similar to the way many compilers format them. __--fmt__ ''format'' Use ''format'' as the name of the format to be used, instead of the name by which pdfTEX was called or a ''%'' line. __--help__ Print help message and exit. __--ini__ Be __pdfinitex__, for dumping formats; this is implicitly true if the program is called as __pdfinitex__. __--interaction__ ''mode'' Sets the interaction mode. The mode can be one of ''batchmode'', ''nonstopmode'', ''scrollmode'', and ''errorstopmode''. The meaning of these modes is the same as that of the corresponding commands. __--ipc__ Send DVI or PDF output to a socket as well as the usual output file. Whether this option is available is the choice of the installer. __--ipc-start__ As __--ipc__, and starts the server at the other end as well. Whether this option is available is the choice of the installer. __--kpathsea-debug__ ''bitmask'' Sets path searching debugging flags according to the bitmask. See the ''Kpathsea'' manual for details. __--maketex__ ''fmt'' Enable mktex''fmt'', where ''fmt'' must be one of ''tex'' or ''tfm''. __--no-maketex__ ''fmt'' Disable mktex''fmt'', where ''fmt'' must be one of ''tex'' or ''tfm''. __--output-comment__ ''string'' Use ''string'' for the DVI file comment instead of the date. __--progname__ ''name'' Pretend to be program ''name''. This affects both the format used and the search paths. __--recorder__ Enable the filename recorder. This leaves a trace of the files opened for input and output in a file with extension ''.fls''. __--shell-escape__ Enable the __write18{__''command''__}__ construct. The ''command'' can be any Bourne shell command. This construct is normally disallowed for security reasons. __--translate-file__ ''tcxname'' Use the ''tcxname'' translation table. __--version__ Print version information and exit. !!ENVIRONMENT See the Kpathsearch library documentation (the `Path specifications' node) for precise details of how the environment variables are used. The __kpsewhich__ utility can be used to query the values of the variables. One caveat: In most pdfTEX formats, you cannot use ~ in a filename you give directly to pdfTEX, because ~ is an active character, and hence is expanded, not taken as part of the filename. Other programs, such as M ETAFONT , do not have this problem. TEXMFOUTPUT Normally, pdfTEX puts its output files in the current directory. If any output file cannot be opened there, it tries to open it in the directory specified in the environment variable TEXMFOUTPUT. There is no default value for that variable. For example, if you say ''pdftex paper'' and the current directory is not writable, if TEXMFOUTPUT has the value ''/tmp'', pdfTEX attempts to create ''/tmp/paper.log'' (and ''/tmp/paper.pdf'', if any output is produced.) TEXINPUTS Search path for ''input'' and ''openin'' files. This should probably start with ``.'', so that user files are found before system files. An empty path component will be replaced with the paths defined in the ''texmf.cnf'' file. For example, set TEXINPUTS to '' TEXFONTS Search path for font metric (''.tfm'') files. TEXFORMATS Search path for format files. TEXPOOL search path for __pdfinitex__ internal strings. TEXEDIT Command template for switching to editor. The default, usually __vi__, is set when pdfTEX is compiled. !!FILES The location of the files mentioned below varies from system to system. Use the __kpsewhich__ utility to find their locations. ''pdftex.pool'' Encoded text of pdfTEX's messages. ''texfonts.map'' Filename mapping definitions. ''*.tfm'' Metric files for pdfTEX's fonts. ''*.fmt'' Predigested pdfTEX format (.fmt) files. !!BUGS This version of pdfTEX fails to trap arithmetic overflow when dimensions are added or subtracted. Cases where this occurs are rare, but when it does the generated ''DVI'' file will be invalid. Whether a generated ''PDF'' file would be usable is unknown. pdfTEX is beta software. Subscribe to the pdftex mailing list __pdftex@tug.org__ if you intend to use it. This is a majordomo list, to subscribe send a message containing ''subscribe pdftex'' to __majordomo@tug.org__. !!SEE ALSO tex(1), mf(1). !!AUTHORS The primary authors of pdfTEX are Han The Thanh, Petr Sojka, and Jiri Zlatuska. ----
One page links to
pdfinitex(1)
:
Man1p
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
