Re: Moving peardoc to XSLT

Hi Christian, Christian Weiske wrote: > 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. The first thing isn't really an issue currently, the second thing should be possible with Livedocs. > 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. That's because you're not following the standard scheme for the IDs. It should be e.g. "package.system.system-folders". (Otherwise the package name detection fails, and neither the two links will be added, nor the package name will be removed, nor will the "file a bug report" link on the bottom point to the package's bug report form.) > Another suggestion: > The "Download documentation" should be below and separated by a <hr/> > from package info and api doc links. Good point, I've changed it in CVS. > So if nobody else beside me thinks xslt would be nice, we should bury > this idea. For these rather little improvements it is IMHO not worth to spend time on XSL now. Let's wait for Livedocs getting ready. Regards, Mark P.S.: Can you please shorten your lines and set your clock to the right time? -- http://www.markwiesemann.eu