FOP only resolves URIs/URLs for resources it has to access (embedded
images, embedded ICC profiles, fonts). Things such as hyperlinks are not
processed because the rules here might be different. Who says that any
relative URL should be resolved at all? You'll have to resolve the URLs
yourself in XS
ferenced inside the stylesheet with:
("headers" being a directoy under the context root, "fonts" and "ttf" are
under WEB-INF)
Greetings and thanks again,
sonja
> -Original Message-
> From: Mike Trotman [mailto:[EMAIL PROTECTED]
> Sent: Freitag,
Message-
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]
> Sent: Freitag, 12. August 2005 22:20
> To: fop-users@xmlgraphics.apache.org
> Subject: Re: Relative URLs
>
> Sonja Löhr wrote:
> > I now try to replace an absolute URL on an external-graphic element
> > wit
005 22:20
> To: fop-users@xmlgraphics.apache.org
> Subject: Re: Relative URLs
>
> Sonja Löhr wrote:
> > I now try to replace an absolute URL on an external-graphic element
> > with a relative one.
>
> You'll probably need to set the baseDir in the FOP configurati
Sonja Löhr wrote:
I now try to replace an absolute URL on an external-graphic element with a
relative one.
You'll probably need to set the baseDir in the FOP configuration.
See
http://xml.apache.org/fop/embedding.html#config-internal
Try getRealPath("/") on the servlet context in order to get
Mike Trotman wrote:
You could try using the 'xml:base' attribute
FOP 0.20.5 doesn't process xml:base.
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I had some similar problems last year - but can't remember how I solved
them.
I have a nasty feeling that I ended up passing server names etc. as XSLT
parameters.
I also had problems between a version of XEP and FOP in their
interpretation of url() contents - which differed.
The resolution o
