> to be honest, the only thing that needs to happen is a conversion to xslt > and not jade. Any other things are incidental.
Hartmut tested the XSL sheets to generate PDF with FOP and maybe some other tool too. What was the problem is that FOP does not support some formattings generated by the DocBook XSL sheets, and some pages looked crappy. The other problem I have faced with the XSLT sheets in HTML generation is that the TOC cannot be limited into something that can be handled by a person. If you look at the TOC of the new CHM edition, you can see that it simply contains all the subparts and subchapters, down to the function's documentation pages. It is more then 300K in size, the full TOC of the manual in a single HTML file. Imagine to come up with such a TOC at http://php.net/manual/en ... I have contacted the DocBook mailing list sometime ago, and they said that there is no solution to our roblem in the stylesheets (to limit a TOC to 2 level deepness for example), so we need to have our own TOC generator code as a customization of the DocBook one. There are parameters in the style sheets which seem to be appropriate for us, but as it turned out after conversations with the authors, they mean something different... Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
