On Tue, Sep 19, 2006 at 11:18:31PM +0100, Philip TAYLOR wrote:
Reinhard Kotucha wrote:
>"John" == John R Culleton
writes: Very interesting, although I usually rename all those (IMO silly) Windows type filenames with spaces in them.
I do so as well. It's more a GUI than a Windows problem.
Now what about two spaces in a row? Just curious.
I tried and it seems that there is a severe bug in pdftex.
\input "foo bar"
loads the file "foo bar.tex" which is certainly not desired behavior.
Well, it may not be "desired", but it's certainly consistent with TeX's underlying scanner/parser, which will have already elided multiple spaces into a single space before \input gets a chance to see things. If you change TeX's behaviour here, you really are getting away from TeX as a consistent platform,
The syntax with quotes already excludes legal file names
on many file systems and operating systems, where quotes
are legal characters in file names. Therefore the quote extension
isn't a refinement of \input's syntax. It would be much better
to have separate primitives that uses <general text> for file
names as done in \pdfximage. Also it would be easy to test,
whether the new primitives are present. I don't know a
reliable way to test the supported syntax of \input.
Yours sincerely
Heiko