Return-Path: Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 12320 invoked by uid 500); 8 May 2002 18:56:50 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: docs@httpd.apache.org Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 12309 invoked from network); 8 May 2002 18:56:49 -0000 X-Authentication-Warning: cancer.clove.org: jerenk set sender to jerenkrantz@apache.org using -f Date: Wed, 8 May 2002 11:56:54 -0700 From: Justin Erenkrantz To: docs@httpd.apache.org Subject: Re: xml build system Message-ID: <20020508115654.L24386@apache.org> References: <3CD89A10.6080101@slive.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rbowen@rcbowen.com on Wed, May 08, 2002 at 07:28:37AM -0400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, May 08, 2002 at 07:28:37AM -0400, Rich Bowen wrote: > Agreed, but if most of the developers were to use an XML browser, the > conversion could be done, say, once a week, by someone with the > know-how, rather than having to have all of the individuals involved > know how to do it. The rationale for standardizing on a specific XML toolset is so that the conversions in the repository don't consistently flip-flop. Right now, if everyone were to use their own transformation tools and versions, the diffs in the repository would be horrendous. I would back the rationale for updating the HTML at the same time as the XML so that our website could be properly updated when the docs change. -- justin --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org