After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 729571 - xsltproc - paths relative to xml or xslt locations
xsltproc - paths relative to xml or xslt locations
Status: RESOLVED NOTGNOME
Product: libxslt
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2014-05-05 13:24 UTC by Robert
Modified: 2014-10-04 09:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert 2014-05-05 13:24:52 UTC 
Hi

I use xsltproc along with DocBook to build html files from.

I used to use xsltproc version 1.1.26-8ubuntu1.3 on my Ubuntu 12. When I switched to Ubuntu 14.04, the xsltproc version changed to 1.1.28-2ubuntu1. With this version of xsltproc my bash scripts used to build documentation stopped working for some strange reason (it works just fine with the old xsltproc version). If you look at the script below, it looks like that for some reason the first invocation of xsltproc treats olinkdbLocation as relative to the xmlXsltLocation location, while the second treats is as relative to bookInputLocation.

bookInputID="topics_toc"
bookInputLocation="../../toc/books/toc/gateway"
bookOutputLocation="../../outputs/toc/gateway"
xsltLocation="../../XSLT/config/gateway.xsl"
olinkdbLocation="../../toc/config/olinkdb.xml"
xmlOutputLocation="../../outputs/toc/gateway/config"
xmlXsltLocation="../../XSLT/config/gateway-component.xsl"

xsltproc --xinclude --output $xmlOutputLocation/ --stringparam target.database.document $olinkdbLocation $xmlXsltLocation $bookInputLocation/$bookInputID.xml
xsltproc --xinclude --output $bookOutputLocation/ --stringparam target.database.document $olinkdbLocation $xsltLocation $bookInputLocation/$bookInputID.xml


Do you know what’s going on here?
I would really appreciate your help.

Best regards,
Robert
Comment 1 Nick Wellnhofer 2014-10-04 09:47:57 UTC 
I'm not aware of any changes to libxslt that might be the cause. I strongly suspect this is due to a change in the docbook-xsl stylesheets. If you can reproduce this issue with the *same* version of docbook-xsl and different versions of libxslt, please reopen.