baseDir relative path

[TS...@gcr.com]

Hello everyone,

      I have a general question regarding relative paths, URI's in FOP.

>From reading various questions in reference to fo:external-graphic and
fo:background-image, the solutions apparently given remain to set the
baseDir either as part of the config file or by setting it programatically.
What I am wondering is why these functions do not take advantage of the
systemId property as part of the InputSource to resolve relative URI's?

This is apparently does not happen when using straight XSL type functions
for example Imports and document( ).

If I am of base,  please let me know.
Thanks.

Tom Seremet

Re: baseDir relative path

["J.Pietschmann" <j3...@yahoo.de>]

TSereme@gcr.com wrote:
>       I have a general question regarding relative paths, URI's in FOP.
>>>From reading various questions in reference to fo:external-graphic and
> fo:background-image, the solutions apparently given remain to set the
> baseDir either as part of the config file or by setting it programatically.
> What I am wondering is why these functions do not take advantage of the
> systemId property as part of the InputSource to resolve relative URI's?
> 
> This is apparently does not happen when using straight XSL type functions
> for example Imports and document( ).
> 
> If I am of base,  please let me know.

FOP was designed to be a stand-alone command line tool for processing
files. The heritage shows in the internal APIs: no InputSources.

J.Pietschmann