Psi Aushilfe3 wrote:
I was trying to put an absolute http URL into an <fo:external-graphics>
src attribute and got an corrupted PDF which Acrobat refuses to open. If
I use an relative local file system path everything works just fine.
Narrow down the problem:
1. Does FOP signal any errors related to the external graphic?
2. Can you see the image if you point a browser on the machine
where FOP should run to the HTTP URL?
3. Can you download the image to a local file with wget (no
cookies, referers, common user agents...), and is this the
image you expect??
The most common causes for the sympoms you describe are spelling
errrors in the URL and server setups which require certain
context information from the browser.
Some more context would have helped too: FOP release number,
the URLs in question, the image format, whether you run FOP
from the CLI or embedded... Psychic powers are still in
limited supply.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
