Re: CVS update: php3/doc

If I may interject---:) Jim Winstead writes: > Seems nobody wants to make this easy for us, including ourselves > (yeah, I forgot about the hardcoded crap in our Makefile). :) Perhaps this should be checked for (if possible) by configure? At least, sgmltools goes into /usr/local/ by default and the given RPMs like /usr/lib. I've just been editing Makefile and html.dsl by hand, but there must be a portable way. > And the mess with building up SGML_CATALOG_FILES is only necessary > if you don't just concatenate together a single catalog file in > the first place, which seems to me to be a much easier way to deal > with it. I'd agree with that. > The RPM stuff is actually somewhat close, and does a nice > job of dealing with constructing a single catalog file, but > it just doesn't work. > > Jim 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. 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. 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. Torben -- 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