Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id D26BC1337B2F
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed,  3 Nov 2010 00:15:39 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 06948-08 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed,  3 Nov 2010 03:15:28 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 30C09133798F
	for <pgsql-docs@postgresql.org>; Wed,  3 Nov 2010 00:15:28 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oA33FQt7023258;
	Tue, 2 Nov 2010 23:15:27 -0400 (EDT)
To: Josh Kupershmidt <schmiddy@gmail.com>
cc: pgsql-docs@postgresql.org
Subject: Re: Large SGML Cleanup 
In-reply-to: <AANLkTi=1Sm9N3Khiued9UiMfdd_TKLimMiO9mCfHtL39@mail.gmail.com> 
References: <AANLkTi=1Sm9N3Khiued9UiMfdd_TKLimMiO9mCfHtL39@mail.gmail.com>
Comments: In-reply-to Josh Kupershmidt <schmiddy@gmail.com>
	message dated "Tue, 02 Nov 2010 22:56:26 -0400"
Date: Tue, 02 Nov 2010 23:15:26 -0400
Message-ID: <23257.1288754126@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201011/4
X-Sequence-Number: 6202

Josh Kupershmidt <schmiddy@gmail.com> writes:
> This HTML fails validation, as one isn't supposed to be stuffing
> tables inside <p> nodes. The attached patch fixes all the instances of
> this I could find, by closing out <para> nodes before beginning lists
> and tables.

I think this isn't even worth thinking about applying, unless you can
provide a way to get future cases of that to fail during "make html".
The chances that it'll stay fixed without such a check are not
distinguishable from zero.

An alternative that might be more workable is to fix the toolchain
so that it generates valid HTML from what is evidently perfectly
acceptable SGML.

			regards, tom lane