Thanks for your reply. > > Last but not least: one feature I find misisng from the xxe > stock configuration: a menu item to use the xhtml transforms, > to generated xhtml docs instead of the html version. > > The stock DocBook configuration does not pretend to be > production-ready > for all users. It is intended to be customized if needed to. It is not > difficult to add such menu item yourself. >
In fact I have read the docs, and already modified the docbook menu, adding an entry to produce xhtml docs. I just tought that having by default both set of entries available for conversion to either html or xhtml would be nice (or provide an option to let the user decide which to produce, html or xhtml...). I also have created a customization file to pass parameters to docb.toHTML.transformParameters, but somehow all customizations I attempt result in no visible output... One option I think would be nice to have is to leave open the dialog with all xslt formatting messages even after the transform completes, so that the user can check what is going on under the hood, if he wants to. Finally, a couple more questions: - is support for docbook 5 planned? is the standard too unstable at the moment? - docbook xslt provide support for source code highlighting via usage of xslthl. Is this a planned extension of xxe? Or is it feasible to add it via customization to teh std transformation tasks? Keep up the good work bye Gaetano Giunta PS: imho the current xslt have a couple of bugs, such as duplicating the first parameter inside a funcprototype or eating up empty lines at the beginning of code inside a programlisting. I tried asking about that on the docbook-apps mailing lists but got no response. Any idea on how to best act to see it fixed?
