<div dir="ltr">First, \input in LaTeX calls \@input which is stored plain \input. It allows macro expansion, so \ and ~ (because it is active) invoke expansion. Second, windows have short 8.3 names depending on your file system and the way how you call your programs, this is not a problem in pdftex but in Windows. It is safer to "cd" to the directory of your file and then call it without the path.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-06-10 9:20 GMT+02:00 Martin Heller <span dir="ltr"><<a href="mailto:mr_heller@yahoo.dk" target="_blank">mr_heller@yahoo.dk</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I am working on a windows system using TeXlive 2013<br>
<br>
pdflatex -version<br>
<br>
pdfTeX 3.1415926-2.5-1.40.14 (TeX Live 2013/W32TeX)<br>
kpathsea version 6.1.1<br>
Copyright 2013 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).<br>
There is NO warranty. Redistribution of this software is<br>
covered by the terms of both the pdfTeX copyright and<br>
the Lesser GNU General Public License.<br>
For more information about these matters, see the file<br>
named COPYING and the pdfTeX source.<br>
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).<br>
Compiled with libpng 1.5.16; using libpng 1.5.16<br>
Compiled with zlib 1.2.7; using zlib 1.2.7<br>
Compiled with xpdf version 3.03<br>
<br>
pdftex can be invoked in different ways. In particular, from `pdftex --help` I expected pdftex to first look if the provided non-option argument is a file and process the file if it exists. Subsequently, the alternative possibilities should be tried:<br>
<br>
Alternatively, if the first non-option argument begins with a backslash,<br>
interpret all non-option arguments as a line of pdfTeX input.<br>
<br>
Alternatively, if the first non-option argument begins with a &, the<br>
next word is taken as the FMT to read, overriding all else. Any<br>
remaining arguments are processed as above.<br>
<br>
Hovever, providing a valid full path to a tex file fails on Windows in many cases. Given that the file<br>
"c:\Documents and Settings\test.tex" exists, the following works as expected<br>
<br>
pdflatex "c:\Documents and Settings\test.tex"<br>
<br>
Using the 8.3 path name fails (pdftex tries to interpret the path as a line of pdfTeX input = alternative 1)<br>
<br>
pdflatex c:\Docume~1\test.tex<br>
<br>
! I can't find file `c:/Docume'.<br>
<to be read again><br>
\protect<br>
<*> c:/Docume~<br>
1/test.tex<br>
(Press Enter to retry, or Control-Z to exit)<br>
Please type another input file name:<br>
<br>
Escaping the tilde by \string and changing \ to / makes the 8.3 path work (but this should look for a file with the full path "c:\Docume\string~1\test.tex")<u></u>.<br>
<br>
pdflatex c:/Docume\string~1/test.tex<br>
<br>
Why is pdflatex interpreting the line in the first place? Non-option arguments should only be interpreted if they begin with a backslash?<br>
<br>
If I invoke pdflatex using<br>
<br>
pdflatex "\\?\c:\Documents and Settings\test.tex"<br>
<br>
it also fails because it interprets the argument as TeX input. However, the path is valid and should not be interpreted as a line of TeX input but rather be processed as a file?<br>
<br>
Is the above expected behavior? If yes, I think the wording in the help text is misleading or at least it confuses me.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Zdeněk Wagner<br><a href="http://hroch486.icpf.cas.cz/wagner/" target="_blank">http://hroch486.icpf.cas.cz/wagner/</a><br><a href="http://icebearsoft.euweb.cz" target="_blank">http://icebearsoft.euweb.cz</a>
</div>