I have a setup with prince that uses wget to fetch all data, and prince runs over it with ease, except in one case. Suppose an img looks like this:
<img src="/graph/foo?data=%2Ftmp%2Fgraph%2Ffoobar">
%2F == '/', and wget seems to do the right thing by *not* decoding it, since '/' is illegal as part of a leaf file name. However, prince appears to not make the same assumption, and complains that the file ../graph/foo?data... does not exist. Since I can't see the source, I presume that it is decoding %2F, and expectedly failing (despite the error line displaying that it couldn't open '../graph/foo?data=%2Ftmp%2Ffoobar').
Without knowing more about how prince does its thing, I presume that this falls under the fix described here:
http://www.princexml.com/bb/viewtopic.php?t=166
Can prince be fixed to special case %2F, or is there perhaps another underlying problem here?
Thanks.
-ben
PS --
[mol] ~ $ prince --version
YesLogic Prince 5.1 rev 7
Copyright 2002-2006 YesLogic Pty. Ltd.
OEM License
<img src="/graph/foo?data=%2Ftmp%2Fgraph%2Ffoobar">
%2F == '/', and wget seems to do the right thing by *not* decoding it, since '/' is illegal as part of a leaf file name. However, prince appears to not make the same assumption, and complains that the file ../graph/foo?data... does not exist. Since I can't see the source, I presume that it is decoding %2F, and expectedly failing (despite the error line displaying that it couldn't open '../graph/foo?data=%2Ftmp%2Ffoobar').
Without knowing more about how prince does its thing, I presume that this falls under the fix described here:
http://www.princexml.com/bb/viewtopic.php?t=166
Can prince be fixed to special case %2F, or is there perhaps another underlying problem here?
Thanks.
-ben
PS --
[mol] ~ $ prince --version
YesLogic Prince 5.1 rev 7
Copyright 2002-2006 YesLogic Pty. Ltd.
OEM License
Edited by arbor