Description: ------------ The automatically added linebreaks in the navigation bar on the right side of the manual pages seems to "fail" on lines that contain "&". For example, in the docs for the Spreadsheet_Excel_Writer package, "Workbook::&setTempDi r" is shown (note: "&" is used in the XML file): http://pear.php.net/manual/en/package.fileformats.spreadsheet-excel-writer.intro.php I haven't checked whether this should be fixed in pearweb or in in peardoc.

I guess we could always decode, then wordwrap and then encode again, that might solve it.

While looking again into the S_E_W docs, I just noticed that also "Worksheet::setMarginRigh t ", "Worksheet::setHPagebreak s", and "Worksheet::setVPagebreak s" are shown in the menu bar (in IE 7 and FF 2). Maybe the length values should be revised?

I have this weird feeling that we'll never manage to fix it to suite every single doc thing :-/ I can check it out but as I said, I think something else will go haywire instead.

Helgi, how about simply using HTML linebreaks (<br> or <br />) instead of "\n"? A single letter in the new line would still look kind of weird but IMHO be more reasonable than a space in the same line.

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. Looks like phd fixed it ? At least I don't see the problem anymore

> Looks like phd fixed it ? At least I don't see the problem anymore No, it's not fixed. One example: http://pear.php.net/manual/en/package.structures.structures-datagrid.structures-datagrid-datasource.php ("Structures_DataGrid_Colu mn" in the same row in FF 3 and IE 7 on WinXP) I still propose to use <br />.

Then write the patch and commit, you do have cvs access you know :)

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. Went ahead and added br where \n was - still think phd should be solving most of this