On Tue, Aug 21, 2007 at 11:01:29AM +1000, Scott Smedley wrote: > > > > Log message: > > > > * Check for sed, perl and tbl, needed to build docs. > > > > > > Why do we need perl to build the documentation? > > > > Because of the script doc/util/genAllCommands.pl. > > Pretend it's not there. Delete it from CVS if it really bothers you > (I can keep my own version). I only wrote it to assist me in editing > the allCommands.html file on the infrequent occassion when a new command > is added to FVWM. > > > At the moment I'm quite unhappy with it: > > Sure. Like I said previously, if you want to automate this further > go right ahead. You'll probably agree,
That's not so simple. For the docuementation you use some extra information that can not be derived from the sources: * Whether a command is obsolete or deprecated * To which logical group the command belongs * Where to begin a new column on the page with all the commands (is that the meaning of the "--"-lines?) Did I miss anything else? The first two can be solved by extending the tagging in functable.c (I'll do that later). But do you have an idea how to format the big command list automatically, without any manual editing? > perl may not be the best tool for it though. Oh, I am sure perl is perfectly suitable for the task, but many proprietary UNIX-machines don't have perl. > Then, generation of the documentation shouldn't have to depend on perl. Ciao Dominik ^_^ ^_^ -- Dominik Vogt, dominik.vogt (at) gmx.de
signature.asc
Description: Digital signature
