Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 43645 invoked by uid 500); 19 Feb 2002 18:46:22 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 43409 invoked from network); 19 Feb 2002 18:46:20 -0000 From: "Joshua Slive" To: Cc: Subject: xml module docs Date: Tue, 19 Feb 2002 13:46:00 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N If you monitor the CVS list, you have by now noticed that we are converting the apache module docs (ie, the reference manual part of the docs) to xml. I just committed for the first time the xslt transformation into cvs. I did this to assure that we don't need to maintain two sets of module docs in 2.0. Now, to edit module docs, first check if there is both an .xml and .html file. If there is only .html, then just edit the html as usual. If there is an .xml file, then don't edit the .html file, because it is generated from the .xml. Instructions on how to deal with the .xml are here: http://httpd.apache.org/docs-project/docsformat.html Note that, although the final .xml file will need to be transformed to .html, you don't need a full transformation setup to edit the docs and check your works. Recent versions of MSIE, Mozilla, and Netscape will render the xml directly with the xsl stylesheet if you request the .xml in your browser. Joshua.