Return-Path: X-Original-To: apmail-httpd-docs-archive@www.apache.org Delivered-To: apmail-httpd-docs-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1C2C59F43 for ; Sun, 22 Apr 2012 16:30:29 +0000 (UTC) Received: (qmail 15475 invoked by uid 500); 22 Apr 2012 16:30:29 -0000 Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 15115 invoked by uid 500); 22 Apr 2012 16:30:25 -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 List-Id: Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 15102 invoked by uid 99); 22 Apr 2012 16:30:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Apr 2012 16:30:25 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [91.198.169.23] (HELO csmtp3.one.com) (91.198.169.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Apr 2012 16:30:19 +0000 Received: from [192.168.1.34] (3304ds3-soeb.0.fullrate.dk [90.184.126.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by csmtp3.one.com (Postfix) with ESMTPSA id 17AC0240E820 for ; Sun, 22 Apr 2012 16:29:56 +0000 (UTC) Message-ID: <4F943203.30505@cord.dk> Date: Sun, 22 Apr 2012 18:29:55 +0200 From: Daniel Gruno User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: docs@httpd.apache.org Subject: Re: manual/developer/modguide.xml is not a valid XML document References: <4F93F887.2000201@medecine.uhp-nancy.fr> In-Reply-To: <4F93F887.2000201@medecine.uhp-nancy.fr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 22-04-2012 14:24, Lucien GENTIS wrote: > Hi all, > > Have you tried to enter "./build.sh validate-xml" for trunk or 2.4 branch ? > > I get hundreds of lines containing > "manual/developer/modguide.xml:1647:125: Attribute "style" must be > declared for element type ....." which hide other errors which may appear > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org > For additional commands, e-mail: docs-help@httpd.apache.org > Don't forget the equally famous one: The content of element type "p" must match "(em|strong|code|a|br|directive|module |program|img|cite|q|dfn|var|transnote|glossary|phonetic)" I've seen the errors, and I know of _a_ solution, which is to loosen up common.dtd in the build system to allow styles within a

 tag (and
subsequently allow for  inside a ), but the real rub here is
what Igor wrote in an email earlier this week; We don't have a
highlighting function for our documents, yet alone a way to distinguish
between configuration examples and source code, so we're forced to use
"invalid" XML segments in order to make the end result properly readable
for our readers.

So again, I implore anyone who has knowledge of, or knows someone who
knows someone who can help us in creating some form of highlighting
feature, please step forward and let us know. The alternate route would
be to just revert every example back to plain text, which would render
most of it quite unappetizing to most readers.

With regards,
Daniel.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org