Re: Many more problems with chm version of php manual

OK, so first of all I am happy to read, that someone deeply tested this CHM. Some errors are long lasting ones (still here from sample 3), and nobody noticed (or at least nobody reported) them. > JavaScript errors: > I wrote earlier about broken links and JavaScript errors. Later I > found that these links were actually not broken but there was > problem with JavaScript and thats why links were broken. Then > I removed file php_manual_notes.chm from the directory where > php_manual_en.chm was present and then opened php_manual_en.chm > and everything worked fine. Do you mean that there were *no* problems with links, JS and other kind of things. So you can read all pages without the notes file? That would be quite interesting, as the php_manual_en.chm files tries to find the notes files the same way if the notes.chm is there... > Search highlighting problem. > Second problem is when searching using search box many times matches > are shown but no keyword on the searched page is highlighted [...] Nobody seems to find OS and IE version information important. Search highlight *never* works on Win2k + IE5 as I have tested, but it seems to work all right on WinXP + IE6. It may be a bug in IE, adding more priority to the CSS then the highlight... > Copy and find in this page are must. > Because a custom menu is displayed when right clicking on a > page opened in the display pane we cannot copy source code or > other text as there is no copy item in the pop-up menu, without > using Ctrl-C. Find in this page is also missing. This is more > important in a large page like where all function links are displayed Ctrl-C and Ctrl-Ins are working for copy, Ctrl-F is working for Find. If you can provide me any JS functions that give you this functionality, I would be very happy to include them as possible custom context menu items. I know that there is a find() function in JS, but it needs to be given some data, and it does not pop up the find dialog box AFAIK. If you would like to see those menu items that we are unable to port to JS functions, you need to switch off the custom JS menu (this is one of the strongest reasons why it is optional). > No all function list on first page. > First link in TOC (first page) "PHP Manual" should not display > complete function list of all extensions only categories should > be displayed(as is done in no chm version). Complete function list > of all extensions can be provided on a separate page as has been > already done ( in Part IV. Function Reference page) but not on > the first page itself. This is actually a quite painful problem with the XSLT sheets, as you have the option to set the deepness of the menu, but if you set any deepness more then 0, all the points are listed. I don't know actually why, but it is a more general problem and affects all XSLT generated DocBook documents in the world AFAIK... The Function index also should not be on the same page as the appendices toc, I also know about this problem (although it was never reported). I thought that it would be better to release these samples, even as I cannot find any solution to these XSLT problems, because all the other features are cute [:)] and neraly everybody uses the tree TOC on the left, and the index provided by the CHM, not the one on the appendices page. Goba