Re: CVS update: php3/doc

From: Date: Mon, 10 May 1999 18:27:52 +0000
Subject: Re: CVS update: php3/doc
References: 1 2 3 4 5 6  Groups: php.dev 
Request: Send a blank email to php-dev+get-5484@lists.php.net to get a copy of this message
On May 09, Lars Torben Wilson wrote: > Actually, yesterday I uninstalled sgmltools just because I wasn't sure > whether these problems were caused by its unfinished status or what > (at least, the README says not to expect it to work). I went straight > to the RPM stuff, installed it, and blammo! Other than a couple of > quick edits in docbook.dcl to set OMITTAG YES and some length thing, I > ended up with a fully built doc tree. That's what I eventually found, too. Is this what other people have had to do? > BTW--good, basic information on DocBook seems hard to find. Good, > in-depth information abounds, of course ;), but does anybody know what > the Proper Way to deal with things like project-specific FEATURE > settings etc is? Asking people to edit system-wide setup files just to > compile PHP docs seems a bit extreme. Well, there's a book on DocBook coming out from O'Reilly in August, so maybe that will clear up some of the documentation problems. :) > Perhaps a quick *ahem* run through the PHP doc tree to normalize > everything would be in order, and setting the emacs local vars to not > omit tags etc may be a good idea. That does seem like it might be the way to go (and not too hard, since the only "problem" is unclosed SIMPARA tags). If we can at least work out of the box with one set of tools, we'll have something to point people at. Even more ideal would be being able to work with a reasonable Jade/DocBook/stylesheet installation, which means figuring out the path and FEATURE issues. Jim -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net

« previous php.dev (#5484) next »