Description of problem: The --output option of db2html is supposed to produce output in the specified directory. It actually has the following behavior: - display an erroneous message "output is <dir>", where <dir> is the base directory of the source document - generate the html output file in the specified directory - create a stylesheet-images directory as a subdirectory of <dir> Version-Release number of selected component (if applicable): 0.6.14 How reproducible: Always Steps to Reproduce: 1. have a HOME/C/nact.xml 2. cd HOME 3. db2html --output html --nochunks C/nact.xml Actual results: - displays "output is C/nact" - creates html/nact.html - creates C/nact/stylesheet-images/ subdirectory Expected results: - displays "output is html/nact.html" - creates html/nact.html - creates html/stylesheet-images/ subdirectory Additional info:
Thanks for report, db2html is very stupid wrapper shell script and it doesn't know anything about the options you provided to jw which actually does the work(and has this --output option). However, I agree that the db2html could(and should) be improved a bit to better understand output-related jw options to produce correct results in the situations like you described...
Should be fixed in docbook-utils-0.6.14-29.fc17 ...
docbook-utils-0.6.14-29.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/docbook-utils-0.6.14-29.fc16
I'll have only one word: great! Thanks. Regards, Pierre
Package docbook-utils-0.6.14-29.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing docbook-utils-0.6.14-29.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16470/docbook-utils-0.6.14-29.fc16 then log in and leave karma (feedback).
docbook-utils-0.6.14-29.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.