Description: ------------ Probably another long-term issue. Adjust pearweb doc stylesheets to link from package documentation to package information.

I think this is possible if somebody would change the DSSSL stylesheets. Since I don't understand them (/me is just xslt), I ask the ones who wrote them to look at this issue.

I have no clue about DSSSL and in fact I did not write it. I just adopted it from phpdoc.

While working on #10867, I noticed that the code for this request already exists, but doesn't work because of a small typo, IMHO not really optimal code and because of broken layout after fixing the typo. After some fixes a manual page on my local pearweb installation looks like this: http://www.markwiesemann.eu/tmp/pear-manual.png Comments about how the "Package info" link could be placed are welcome. (Note: No change in the stylesheets is needed with my solution.)

I would place a separator between Download Docs and Package info and made the font size for info the same. It is also looks like left menu is overloaded. I bet half of the links will be never or very rarely used from manual pages. Instead there could be shortcuts for package statistics and package download, "report bug for this package" (for reporting mistakes in documentation), view bugs etc. These are more actual when reading package documentation than "News" or "The PEAR Group".

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. --- - moved to pearweb - closed (Note to Anatoly: I didn't get the email about your answer on May 2th from the bug tracker. Since my last comment on this bug the layout of my changes has changed. If you have further ideas, that's maybe something for a new request.)

I do not see any changes yet, but sole presence of the link to package somewhere on documentation pages will be enough for me (and for this bugreport too).