[ pdftex-Bugs-377 ] unqoute image filenames not only on windows
Bugs item #377, was opened at 2005-07-02 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106 Category: Image inclusion Group: None Status: Open Resolution: None Priority: 5 Submitted By: Georg Baum (baum) Assigned to: Martin Schröder (oneiros) Summary: unqoute image filenames not only on windows Initial Comment: The file pdftex-1.30.0-rc1/src/texk/web2c/pdftexdir/writeimg.c contains in the function readfile() a code block to unqoute file names which is inside #ifdef WIN32 ... #endif. This code should be enabled on all platforms (or at least on linux), since quoted filenames (which are necessary if the name contains spaces) do not only work well on linux. Thanks, Georg ----------------------------------------------------------------------
Comment By: Georg Baum (baum) Date: 2005-07-04 13:46
Message:
Logged In: YES
user_id=2590
I agree that the quote stripping is a hack and should
eventually be replaced by something better.
I do think however that the behaviour on all platforms
should be the same if it is at all possible. Right now,
filenames with quotes work on linux and not on windows, and
quoted filenames with spaces work on windows but not on linux.
Thanks for the hint to pdfximage, I did not know about that
(coming from standard LaTeX and always using \includegraphics}
Georg
----------------------------------------------------------------------
Comment By: Heiko Oberdiek (oberdiek)
Date: 2005-07-04 13:13
Message:
Logged In: YES
user_id=1276
Hello,
it is a very bad idea, quotes are perfectly legal
in linux and other operating systems. Also image
inclusion is done by \pdfximage that uses
<general text>, by <general text>, text surrounded
by curly braces (catcode 1 and 2) *all* possible
file names can be given including quotes and spaces.
We need rather new primitives for
\input, \openin, and \openout to provide the file
names as <general text>. The all file names can
be given without the need of quoting at all.
See also the discussion about \pdfinput in
the ntg-pdftex mailing list.
Yours sincerely
Heiko
participants (1)
-
noreply@sarovar.org