Return-Path: 
 <docs-return-10561-apmail-httpd-docs-archive=httpd.apache.org@httpd.apache.org>
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 A714C96FE
	for <apmail-httpd-docs-archive@www.apache.org>;
 Sun, 22 Apr 2012 23:42:11 +0000 (UTC)
Received: (qmail 49087 invoked by uid 500); 22 Apr 2012 23:42:11 -0000
Delivered-To: apmail-httpd-docs-archive@httpd.apache.org
Received: (qmail 49034 invoked by uid 500); 22 Apr 2012 23:42:11 -0000
Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:docs-help@httpd.apache.org>
list-unsubscribe: <mailto:docs-unsubscribe@httpd.apache.org>
List-Post: <mailto:docs@httpd.apache.org>
Reply-To: docs@httpd.apache.org
List-Id: <docs.httpd.apache.org>
Delivered-To: mailing list docs@httpd.apache.org
Received: (qmail 49025 invoked by uid 99); 22 Apr 2012 23:42:11 -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 23:42:11 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [217.160.171.50] (HELO jupiter.hal-nine-zero-zero-zero.net)
 (217.160.171.50)
    by apache.org (qpsmtpd/0.29) with SMTP; Sun, 22 Apr 2012 23:42:06 +0000
Received: (qmail 17919 invoked from network); 22 Apr 2012 23:41:42 -0000
Received: from unknown (HELO localhost) (217.160.171.50)
  by jupiter.hal-nine-zero-zero-zero.net with SMTP; 22 Apr 2012 23:41:42 -0000
From: =?iso-8859-1?q?Andr=E9_Malo?= <nd@perlig.de>
Organization: TIMTOWTDI
To: docs@httpd.apache.org
Subject: Re: manual/developer/modguide.xml is not a valid XML document
Date: Mon, 23 Apr 2012 01:42:27 +0200
User-Agent: KMail/1.9.10
References: <4F93F887.2000201@medecine.uhp-nancy.fr> <4F943203.30505@cord.dk>
In-Reply-To: <4F943203.30505@cord.dk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <201204230142.28759@news.perlig.de>
X-Virus-Checked: Checked by ClamAV on apache.org

* Daniel Gruno wrote:

> 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 <code> tag (and
> subsequently allow for <pre> inside a <p>),

<pre> is not allowed inside <p>, because both are blocks (in HTML then) and=
=20
nesting is forbidden there.

Also, style attributes are BAD. If you want to extend common.dtd, use=20
classes and extend the css files (or, better: add a new one).

> but the real rub here is=20
> 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.

=46ix the DTD and the XSLT. Breaking the build system is not a solution.

> 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.

I suggest pygments. If we get that to run with jython, we could use it to=20
auto-highlight code. But until then, it's plain text, yes; so please=20
revert.

nd
=2D-=20
"Das Verhalten von Gates hatte mir bewiesen, dass ich auf ihn und seine
beiden Gef=E4hrten nicht zu z=E4hlen brauchte" -- Karl May, "Winnetou III"

Im Westen was neues: <http://pub.perlig.de/books.html#apache2>

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