![](https://secure.gravatar.com/avatar/adfff96f4299fb3ee3b199b06eea68da.jpg?s=120&d=mm&r=g)
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: Heiko Oberdiek (oberdiek)
Date: 2005-07-04 16:07
Message:
Logged In: YES
user_id=1276
Hello,
I must disagree, "the same behaviour on all platforms"
can not mean to add the limitations of all platforms.
Now you want the limitation of windows that quotes
cannot be used apply on the other systems?
There are operating systems that deal with 8+3 file
names only. Do you want to forbid long file names,
for example?
Thus we are loosing both quotes and spaces. Spaces still
cannot be used in general. Other TeX engines
does not know about quoting. There is no secure way
to know, whether quoting is working. Thus code that
is intended for different systems must avoid spaces.
And the current quoting scheme does not solve the
problem at all, it moves the problem from spaces to
quotes, spaces can still not be used and quotes are
now made unavailable. Also the quoting scheme does
not allow quoting of the quotes themselves.
A solution would allow *all* characters.
The solution should be able to deal with utf-8 or
even ucs-2/4 encoded file names.
That is already given by the syntax of \pdfximage.
Thus new primitives \pdfinput, \pdfopenin, \pdfopenout
with <general text> would allow any file name and a
macro code can test, whether this feature is available
by testing the command names.
Yours sincerely
Heiko