Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Sun, 24 Nov 2002 21:21:13 -0800
From: Justin Erenkrantz <jerenkrantz@apache.org>
Reply-To: Justin Erenkrantz <jerenkrantz@apache.org>
To: dev@httpd.apache.org
Subject: Re: cvs commit: httpd-site/docs/dev anoncvs.txt devnotes.html
 how-to-release.html
Message-ID: <1080996003.1038172873@localhost>
In-Reply-To: <5.1.0.14.2.20021124214720.025dd008@pop3.rowe-clan.net>
References: <20021123192842.37298.qmail@icarus.apache.org>
 <20021123192842.37298.qmail@icarus.apache.org>
 <5.1.0.14.2.20021124214720.025dd008@pop3.rowe-clan.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--On Sunday, November 24, 2002 9:51 PM -0600 "William A. Rowe, Jr." 
<wrowe@apache.org> wrote:

> Can I just state that this surprise really sucks?  Why couldn't we
> follow the same protocols as in httpd-2.0/docs/manual/ where xml
> coexists peacefully alongside html output???

We don't want to serve the original XML files.  httpd-2.0's docs have 
valid XSLTs which mean that they can be rendered with modern web 
browsers.  httpd-site's content doesn't have a XSLT.  Therefore, if 
we exposed the raw XML files to a web browser, they wouldn't make any 
sense to anyone.

The eventual goal is not to have a docs directory in CVS at all, but 
we can't do that given our current infrastructure.  Therefore, all of 
the content must be generated statically and checked into the 
repository.  Hence, docs/ is only valid for transformations.  -- 
justin