[xml/sgml-pkgs] Bug#568894: xmlto: Issues

[Ondrej Vasik]

Hello Daniel,
thanks for forwarding these issues to me...

On Sun, 2011-11-27 at 17:22 +0100, Daniel Leidert wrote:
> tags 568894 + upstream confirmed
> forwarded 568894 ovasik at redhat.com
> thanks
> 
> Hello Ondrej,
> 
> I would like to discuss two bugs/issues in xmlto with you.
> 
> (1) xmlto sets both fop.extensions and fop1.extensions. This is not how
> things should work. You either have to set fop.extensions (for fop
> 0.20.5 or earlier) *or* fop1.extensions (for fop >= 0.90), not both
> together. I'm sure, this might cause build issues. What about handling
> this during configure time: check fop's version output and just set one
> parameter in xmlto?

Yes, I'm aware of that issue and I do plan to fix it in next xmlto
version...
Handling it in configure time with fop1.extensions as default type (when
no fop is found) seems to be the best way for me.

> (2) Te current way of creating temporary stylesheets in /tmp creates a
> problem, which is described e.g. here: http://bugs.debian.org/568894.
> The problem is, that the .fo file is in a different directory than the
> source and thus the second step, running fop, won't find the image. A
> possible fix might be to set img.src.path to be the path of the working
> directory. E.g.
> 
> XSLTPARAMS="$XSLTPARAMS --stringparam img.src.path `pwd`/"
> 
> But this might create problems for images declared with an absolute
> path! IMO the only way of fixing this is to create the .fo file inside
> the source directory. Maybe as .xmlto.fo.XXXXXX or similar? What do you
> think?

Thanks for reporting that, you are right that handling that via setting
img.src.path is not the best option. Temporary file created by mktemp in
the source directory should work in that case. As these two fixes seems
to be important enough (broken fop support and support for external data
files), I'll try to prepare new xmlto version (just these two fixes)
next week.

Greetings,
         Ondrej Vasik