Re: cvs: /phpdoc howto.sgml.in manual.sgml.in /phpdochowto.sgml manual.sgml /phpdoc configure.in

Lars Torben Wilson wrote: > > Stig Bakken writes: > > On Thu, 21 Oct 1999, Torben Wilson wrote: > > | Use configure to check for the system's DocBook DTD. This should allow > > | folks with a stock DocBook 3.1 to compile the manual without having to > > | edit phpdoc files (to set the doctype) and DocBook files (to allow > > | tag minimilization). > > > > The Right Way (tm) to fix this is to have configure generate its own > > catalog file with the necessary entries, and refer to it with the -c > > option to nsgmls/jade. > > > > - Stig > > OK, cool. Is there anyplace you know of where I can find a suitable > algorithm for locating these entries on any given system? The one I'm > using at present simply searches through $SGML_CATALOG_FILES until it > finds the first public identifier for docbook.dtd; I've been > suspecting that this solution was sub-optimal. :) > > Should it just look though a list of directories, like the docbook.dsl > check? As far as I can tell, directories in various SGML setups are > not particularly standardized. SGMLtools seems to have a pretty good > thing going on with its catalog.d, but I don't think everyone has > that. We could try two approaches: 1. Locating the DTD files for DSSSL stylesheets and DocBook by checking a list of directories. 2. Locating catalog files the same way, and concatenating them. The problem with this approach is that we would have to expand relative paths inside the found catalog files. Testing whether an option works should probably be done by trying to validate a test document. If it really is so that turns out that people have different SGML declarations in their DocBook installations, we should provide our own docbook.dcl with OMMITTAG enabled and a long enough NAMELEN. - Stig