Message-ID: <354C8C24.AFF4BF3F@Golux.Com>
Date: Sun, 03 May 1998 11:24:20 -0400
From: Rodent of Unusual Size <Ken.Coar@Golux.Com>
Organization: The Apache Group
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: cvs commit: apache-devsite/apidoc README dict-ap_cpystrn.html
	 dict-ap_destroy_pool.html dict-ap_make_sub_pool.html
References: <19980503012411.6152.qmail@hyperreal.org>
	 <354C747C.4F4C5DEA@algroup.co.uk> <354C78FF.5B11CB63@Golux.Com>
 <354C7D97.924C82A6@algroup.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Ben Laurie wrote:
> 
> Oh, I see. Why don't the doc files get it done automatically, then?

I didn't do that in the current version for a few reasons:

 . The doc file is included verbatim; someone wrote it to look
   the way it does.
 . Marking up the doc file contents would almost certainly push
   lots of lines past column 80.
 . Some sections would probably end up so liberally sprinkled
   with links as to be annoying.
 . Each link adds 16 bytes to the file.
 . Dealing with word forms gets difficult - should "pool" be a
   link but "pools" not?
 . What if a doc file talks about the server's "pool of children"?
   Or "the module source files"?  Parsing by intent is a little
   problematical..

However, most of these would only apply to common multi-value words
like "pool" or "module" and so it might not be a big deal.  I'm
not opposed to giving it a try.. but I don't think it would be an
improvement.

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>