Easily fixed when I know where to look. Thanks for tracking it down.
It's fixed in FOP Trunk now: http://svn.apache.org/viewcvs?rev=381978view=rev
On 01.03.2006 11:21:08 Florent Georges wrote:
Florent Georges wrote:
The reported unknown host is not the drive letter in the
URI, but the
Jeremias Maerki wrote:
Easily fixed when I know where to look. Thanks for tracking
it down. It's fixed in FOP Trunk now:
Perfect. Thanks for the quick reply.
http://svn.apache.org/viewcvs?rev=381978view=rev
Even simplified ;-)
Regards,
--drkm
Try if file:///C:/test/logo.svg works. That should remove any ambiguity
about what is the path and what is the hostname in the URL.
Manuel
On Wednesday 01 March 2006 00:49, Florent Georges wrote:
Jeremias Maerki wrote:
Hmm, as I said in my other response, I tested locally with
0.91beta and
Manuel Mall wrote:
I'll try tomorrow (as I can't reproduce the problem outside the
server). But as I said, the URI is generated by Saxon, by using the
XPath 2.0 fn:resolve-uri(). So I can't really change the format of the
URI.
If I remember well, I gave also:
Hi
I'm using the following to access an SVG file on a Windows
server:
fo:external-graphic src=url('file:/C:/...')/
See the value of the URI (i.e. 'file:/C:/...'). If I use a
relative URI, starting for example by '../', no problem.
But with the above URI the file is not found, and I get
Florent Georges wrote:
I'm using the following to access an SVG file on a Windows
server:
fo:external-graphic src=url('file:/C:/...')/
Sorry, I forgot to specify the version I use: FOP 0.91beta.
Regards,
--drkm
Both url(file:/C:/..) and url(file:///C:/..) work fine in FOP
0.91beta.
On 27.02.2006 17:08:23 Florent Georges wrote:
Hi
I'm using the following to access an SVG file on a Windows
server:
fo:external-graphic src=url('file:/C:/...')/
See the value of the URI (i.e.
Jeremias Maerki wrote:
Both url(file:/C:/..) and url(file:///C:/..) work fine in FOP
0.91beta.
Mmh, yes, I just checked this on a local directory. Maybe related to
the file permissions, I don't know. I'll investigate further.
Thanks, and sorry for the noise,
--drkm