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 344654 - xsltproc --output ${DIRECTORY} needs to end with a '/' to be recognized correctly
xsltproc --output ${DIRECTORY} needs to end with a '/' to be recognized corre...
Status: RESOLVED NOTABUG
Product: libxslt
Classification: Platform
Component: general
1.1.15
Other Linux
: Normal enhancement
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-12 12:52 UTC by Daniel Leidert
Modified: 2006-06-12 14:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
a patch to add a note about this to xsltproc(1) (1.54 KB, patch)
2006-06-12 14:00 UTC, Daniel Leidert
committed Details | Review

Description Daniel Leidert 2006-06-12 12:52:47 UTC
I observe an issue with the --outout|-o option of xsltproc. The following commands result in different results (say chunk.xsl is a file importing e.g. the chunk.xsl of docbook-xsl's HTML stylesheets):

(1) xsltproc -o testdir chunk.xsl test.xml
(2) xsltproc -o testdir/ chunk.xsl test.xml

In the first case, the created files are output to the current directory instead of testdir. In the second case, the files are output to testdir. Maybe this is just a limitation which can be removed/fixed and so also directories without an ending '/' path separator will be accepted.

If you need more information, please let me know.

PS: The issue appears (probably) up to version 1.1.17, but the bugzilla-interface atm only knows versions up to 1.1.15. System is an up-to-date Debian Sid.
Comment 1 Daniel Veillard 2006-06-12 13:23:36 UTC
That's normal. an xslt transform will by default generate an output file
(empty in your case, but still), and the extensions used to create new
documents use an URI as their target, the output being the computation of the
URI reference against the base of the current outupt document.

  The URI reference computation is described in RFC 2396 and laters
   URI_Ref('testdir', 'foo') -> foo
   URI_Ref('testdir/', 'foo') -> testdir/foo

so it's all normal, defined and should not be changed.

Daniel
Comment 2 Daniel Leidert 2006-06-12 14:00:48 UTC
Created attachment 67185 [details] [review]
a patch to add a note about this to xsltproc(1)

Thanks for the info. The following patch adds a note about this to the xsltproc manpage. Maybe you could be so nice to apply it.
Comment 3 Daniel Veillard 2006-06-12 14:33:00 UTC
Sure, commited, thanks

Daniel