Received: by taz.hyperreal.com (8.7.6/V2.0) id QAA19303; Thu, 21 Nov 1996 16:15:45 -0800 (PST) Received: from nora.pcug.co.uk by taz.hyperreal.com (8.7.6/V2.0) with SMTP id QAA19297; Thu, 21 Nov 1996 16:15:41 -0800 (PST) Received: from imdb.demon.co.uk by nora.pcug.co.uk id aa06035; 22 Nov 96 0:15 GMT Message-Id: <199611212310.XAA03511> Subject: Re: docs progress To: new-httpd@hyperreal.com Date: Thu, 21 Nov 1996 23:10:18 +0000 (GMT) In-Reply-To: from "Brian Behlendorf" at Nov 21, 96 01:49:19 pm From: Rob Hartill Organization: Internet Movie Database X-pgp-public-key: http://us.imdb.com/pgp.html X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com Brian Behlendorf wrote: > >On Thu, 21 Nov 1996, Alexei Kosut wrote: >> So IMHO, as much of a pain it is to maintain, we should NOT use >> includes in the documentation. > >I disagree, but I'd settle for the following: if we could write a script which >expanded SSI's, just the vanilla #include file type, and run that at this is almost possible with lynx. You can set lynx to collect URLs from a given starting point and dump them to files (SSI expanded thanks to Apache). However, I say "almost" because I'm not aware of flags to keep lynx within a narrow enough region of the web to make this safe. I mention this in the hope that someone has worked out how to do it. An alternative is to ask lynx to -source each page individually. That will save the HTML (+ expanded SSI) to a file; but y'all knew that. rob