> > - Much more powefull design (as we are hosting this > > help file for an "enterprise quality product" - PHP, > > and so the big mans there like good looking things, > > and me too :) I am not a designer, so it would be > > better, if some designer can come up with better > > graphics, than I have done, but it is certainly better > > in the file mentioned above, than now. > > The graphics and layout seems to be quite good. I myself can
This sentence was not finished. I am not really satisfied with the graphics, I'll try to find some people with better graphics skills. > boxing warnins and notes would be great. > about see also: for now this is done actually with (you know better > than I): > <para> > See also: <function>mysql_query</function>. > </para> > Whats the problem to do this in this way? (ok, I am not so experienced > in xml and building issues), but this see also does actually work for > the chm`s. This is not a convention, it is just often used this way. A <seealso> kind of tag would be great. Unfortunately there is a seealso tag in DocBook, but it is not intended to be used this way... It seems to me, that it just complicates things... > Generally, I would like to see a section in the manual/chms of > unsupported functions for windows and vice versa a section of > functions only working on *nix or windows. > Actually there is only a note within the function description(see for > example the Filesystem functions). An overview would be great. > Also more windows specific notes: > what extensions are included in the win-distribution? > what extensions are included but need installation of additional > programms/libraries? These questions need to be addressed in the manual, and not part of the CHM development. These informations should be there in all formats and languages. If somebody has the time to contribute and collect such indexes, it would be great :)) There is also a need for a full alphabetical list of functions for some time, but noone had the time to make a program to generate it... Goba
