||*()*|| Hi, Gabor. >> Are there any plans to provide a means for people downloading the XML >> sources via CVS to be able to build a COMPLETE PHP Manual? >> >> By complete, I mean, PHP, PEAR, ZendAPI, etc, the whole lot. All >> documentation associated with PHP. >> >> I understand that most users would only want the PHP part, though, I >> think the PEAR documentation should be included also. >> >> Currently, I can ... >> >> ./configure --with-chm=yes --with-source=./../php-src >> --with-pecl-source=./../pecl --with-pear-source=./../pear>> ../conf.log >> >> The PEAR source doesn't seem to produce any output. >> >> The PECL documentation produces a single section with 4 subsections >> (HTML parser extension, EXIF tag access library, MDB data file access >> library and UUID extension). The level of documentation here is brief.
GH> CHM building uses interesting tricks, but it is still a good question, GH> whether we can make it possible to build a complete PEAR+PHP manual. Could GH> someone from the peardoc front comment on this? PEAR manual already renders in CHM and it takes about 2.4Mb additional load. ZendAPI is not included in xCHM, but present in standart CHM version. I guess it is possible to link these CHM's together, but I doubt somebody will benefit from this if Index and Search capabilities merge. PEAR index can greatly confuse users who learn PHP. Search results make it even worse producing informational garbage gathered from all three files rather than displaying only relevant info. I don't know a way to limit search scope and it seems to me, that having three separate manuals is the best solution. t --
