<div dir="ltr"><div class="gmail_extra">does not exist for me. pdftex -help gives:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">Usage: pdftex [OPTION]... [TEXNAME[.tex]] [COMMANDS]</div>
<div class="gmail_extra"> or: pdftex [OPTION]... \FIRST-LINE</div><div class="gmail_extra"> or: pdftex [OPTION]... &FMT ARGS</div><div class="gmail_extra"> Run pdfTeX on TEXNAME, usually creating TEXNAME.pdf.</div>
<div class="gmail_extra"> Any remaining COMMANDS are processed as pdfTeX input, after TEXNAME is read.</div><div class="gmail_extra"> If the first line of TEXNAME is %&FMT, and FMT is an existing .fmt file,</div><div class="gmail_extra">
use it. Else use `NAME.fmt', where NAME is the program invocation name,</div><div class="gmail_extra"> most commonly `pdftex'.</div><div class="gmail_extra"><br></div><div class="gmail_extra"> Alternatively, if the first non-option argument begins with a backslash,</div>
<div class="gmail_extra"> interpret all non-option arguments as a line of pdfTeX input.</div><div class="gmail_extra"><br></div><div class="gmail_extra"> Alternatively, if the first non-option argument begins with a &, the</div>
<div class="gmail_extra"> next word is taken as the FMT to read, overriding all else. Any</div><div class="gmail_extra"> remaining arguments are processed as above.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
If no arguments or options are specified, prompt for input.</div><div class="gmail_extra"><br></div><div class="gmail_extra">-draftmode switch on draft mode (generates no output PDF)</div><div class="gmail_extra">
-enc enable encTeX extensions such as \mubyte</div><div class="gmail_extra">-etex enable e-TeX extensions</div><div class="gmail_extra">[-no]-file-line-error disable/enable file:line:error style messages</div>
<div class="gmail_extra">-fmt=FMTNAME use FMTNAME instead of program name or a %& line</div><div class="gmail_extra">-halt-on-error stop processing at the first error</div><div class="gmail_extra">
-ini be pdfinitex, for dumping formats; this is implicitly</div><div class="gmail_extra"> true if the program name is `pdfinitex'</div><div class="gmail_extra">-interaction=STRING set interaction mode (STRING=batchmode/nonstopmode/</div>
<div class="gmail_extra"> scrollmode/errorstopmode)</div><div class="gmail_extra">-ipc send DVI output to a socket as well as the usual</div><div class="gmail_extra"> output file</div>
<div class="gmail_extra">-ipc-start as -ipc, and also start the server at the other end</div><div class="gmail_extra">-jobname=STRING set the job name to STRING</div><div class="gmail_extra">-kpathsea-debug=NUMBER set path searching debugging flags according to</div>
<div class="gmail_extra"> the bits of NUMBER</div><div class="gmail_extra">[-no]-mktex=FMT disable/enable mktexFMT generation (FMT=tex/tfm/pk)</div><div class="gmail_extra">-mltex enable MLTeX extensions such as \charsubdef</div>
<div class="gmail_extra">-output-comment=STRING use STRING for DVI file comment instead of date</div><div class="gmail_extra"> (no effect for PDF)</div><div class="gmail_extra">-output-directory=DIR use existing DIR as the directory to write files in</div>
<div class="gmail_extra">-output-format=FORMAT use FORMAT for job output; FORMAT is `dvi' or `pdf'</div><div class="gmail_extra">[-no]-parse-first-line disable/enable parsing of first line of input file</div><div class="gmail_extra">
-progname=STRING set program (and fmt) name to STRING</div><div class="gmail_extra">-recorder enable filename recorder</div><div class="gmail_extra">[-no]-shell-escape disable/enable \write18{SHELL COMMAND}</div>
<div class="gmail_extra">-shell-restricted enable restricted \write18</div><div class="gmail_extra">-src-specials insert source specials into the DVI file</div><div class="gmail_extra">-src-specials=WHERE insert source specials in certain places of</div>
<div class="gmail_extra"> the DVI file. WHERE is a comma-separated value</div><div class="gmail_extra"> list: cr display hbox math par parend vbox</div><div class="gmail_extra">
-synctex=NUMBER generate SyncTeX data for previewers if nonzero</div><div class="gmail_extra">-translate-file=TCXNAME use the TCX file TCXNAME</div><div class="gmail_extra">-8bit make all characters printable by default</div>
<div class="gmail_extra">-help display this help and exit</div><div class="gmail_extra">-version output version information and exit</div><div class="gmail_extra"><br></div><div class="gmail_extra">
Email bug reports to <a href="mailto:pdftex@tug.org">pdftex@tug.org</a>.</div><br><div class="gmail_quote">On Wed, Apr 25, 2012 at 8:43 PM, Martin Heller <span dir="ltr"><<a href="mailto:mr_heller@yahoo.dk" target="_blank">mr_heller@yahoo.dk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Vafa Khalighi wrote, on <a href="tel:25-04-2012%2010" value="+12504201210" target="_blank">25-04-2012 10</a>:04:<div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
places output files (including pdf/dvi) in the test directory. How can<br>
one places pdf in the current directory but all other output files in<br>
the test directory?<br>
</blockquote>
<br></div>
from pdflatex -help:<br>
<br>
-aux-directory=DIR<br>
<br>
Use DIR as the directory to write auxiliary files to.<br>
<br>
______________________________<u></u>_________________<br>
TeX FAQ: <a href="http://www.tex.ac.uk/faq" target="_blank">http://www.tex.ac.uk/faq</a><br>
Mailing list archives: <a href="http://tug.org/pipermail/texhax/" target="_blank">http://tug.org/pipermail/<u></u>texhax/</a><br>
More links: <a href="http://tug.org/begin.html" target="_blank">http://tug.org/begin.html</a><br>
<br>
Automated subscription management: <a href="http://tug.org/mailman/listinfo/texhax" target="_blank">http://tug.org/mailman/<u></u>listinfo/texhax</a><br>
Human mailing list managers: <a href="mailto:postmaster@tug.org" target="_blank">postmaster@tug.org</a><br>
</blockquote></div><br></div></div>