Re: Moving peardoc to XSLT

Mark, > In the referenced post from me [1] there is a "no" missing and a "a" too > much; my sentence should begin with "Switching to XSLT would bring us no > benefit in this regard [...]". Then I misunderstood you. > Can you please elaborate what XSL would make possible for us that is > currently not possible? We could put the stuff we're doing with php right now (linking package page and this toc generation) into manual generation itself, but performance isn't the issue now. We also could automatically link <classname>, <function> and <method> tags to their appropriate API documentation pages. Btw, I didn't see that it already works because http://pear.php.net/manual/en/package.system.folders.php and http://pear.php.net/manual/en/package.system.windrives.windrives.system-windrives.php don't link the package page, and the classname is still there in the method list. Another suggestion: The "Download documentation" should be below and separated by a <hr/> from package info and api doc links. So if nobody else beside me thinks xslt would be nice, we should bury this idea. -- Christian