Hi Dominik, > > If you do not want to produce this documentation please use: > > > > ./configure --disable-htmldoc > > As the process take four times longer than building the > executables, may I suggest that > > a) the html pages are not built unless you specifically ask for > them,
Ok. I will change this soon. > b) the new man page stuff is disabled by default. Sorry, I don't understand what you mean. > > For developers, the XML source files supersede the old fvwm man page. > > Please make any documentation changes here & NOT in the fvwm/fvwm.1.in > > file. > > Well, I'd be willing to try that, but I am *not* going to search > through *400* files for the contents I want to edit (and all cross > references). There *must* be a way to have just one file per man > page. I'd like to be able to accomodate, but by having everything in one file we'd lose the ability to have separate HTML pages for each command. IMO, that's probably the most useful feature. See: http://members.optusnet.com.au/~scott.fvwm/allCommands.html It's natural to split up the documentation into smaller files. As an analogy, consider the FVWM source code - we don't have a single fvwm.c source file to make "searching" easier, but lots of separate source files with grouped functionality. I agree though, splitting up the documentation into multiple files has made "searching" a little harder. But, as Dan indicates, a few simple 'grep' commands should suffice. > What about the other markup mentioned at the top of the man page? Ok. I will expand the doc/README file further to include these. Scott. :)
