Enrique Rodriguez wrote:
> I have a directory tree with various folders with diferent depth. On
...
> <fop format="application/pdf" outdir="${dir.salida.pdf}"
> messagelevel="debug">
> <fileset dir="${dir.salida.fo}">
> <include name="**/*.fo"/>
...
> So waht i need is to change the base dir directory for each . fo file of
> the fileset.
OK, I understand.
> What i did is to extend the Fop Task to replace this behaviour. I take
> the Fop 0.20.5 version becouse i have problem with the latest
> nigthly bluid.
>
> This is the little change i make, near line 250
>
> fileSetFOFileBaseURL =f.getParentFile().toURL().toExternalForm();
> Configuration.put("baseDir",fileSetFOFileBaseURL);
>
> I get as basedir the parenFile of the "f", the .fo file of the fileset.
>
> Maybe it will be a good idea to add this configuration to the
> "Key-Value Configuration Options". I think this have sense becouse if
> the .fo file is the source of the translation its folder should be the
> basedir of the translation.
I'm more inclined to think it should be an attribute on the FOP task in Ant,
since I can't think of any other place where it isn't convenient to just use
the baseDir configuration option. If you agree, would you mind adding this
as an enhancement request in Bugzilla?
http://xml.apache.org/fop/bugs.html#issues_new
Be sure to include your proposed patch.
Or, better yet, maybe you would like to go ahead and propose a PATCH to
implement the Ant attribute. I guess it would just be a boolean, perhaps
something like basedirfromfo, where true would implement your change, and
false would use the basedir for the fileset. Or, there may be some other
similar issues that need to be rolled into this idea.
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
