Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id DA41A1337B3E
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed,  3 Nov 2010 10:15:01 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 93629-04 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Wed,  3 Nov 2010 13:14:54 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from spinlock.commandprompt.com (host-215.commandprompt.net
	[207.173.203.215])
	by mail.postgresql.org (Postfix) with ESMTP id 9F95F1335B36
	for <pgsql-docs@postgresql.org>; Wed,  3 Nov 2010 10:14:54 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by spinlock.commandprompt.com (Postfix) with ESMTP id EA3CD348016;
	Wed,  3 Nov 2010 06:14:53 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at commandprompt.com
Received: from spinlock.commandprompt.com ([127.0.0.1])
	by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1])
	(amavisd-new, port 10024)
	with ESMTP id B5Q-H2w6YUgp; Wed,  3 Nov 2010 06:14:51 -0700 (PDT)
Received: from perhan.alvh.no-ip.org (unknown [190.95.28.71])
	by spinlock.commandprompt.com (Postfix) with ESMTPSA id 4B3EC348015;
	Wed,  3 Nov 2010 06:14:51 -0700 (PDT)
Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000)
	id 83A5A6E8DD; Wed,  3 Nov 2010 10:14:47 -0300 (CLST)
Content-Type: text/plain; charset=UTF-8
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Large SGML Cleanup
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Josh Kupershmidt <schmiddy@gmail.com>
In-reply-to: <AANLkTi=1Sm9N3Khiued9UiMfdd_TKLimMiO9mCfHtL39@mail.gmail.com>
References: <AANLkTi=1Sm9N3Khiued9UiMfdd_TKLimMiO9mCfHtL39@mail.gmail.com>
Date: Wed, 03 Nov 2010 10:14:47 -0300
Message-Id: <1288788816-sup-8169@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9
X-Spam-Level: 
X-Archive-Number: 201011/8
X-Sequence-Number: 6206

Excerpts from Josh Kupershmidt's message of mar nov 02 23:56:26 -0300 2010:
> [Resending without large attachment, looks like the previous attempt
> isn't going to make it]
> 
> Hi all,
> 
> I've gone through the SGML documentation, trying to push the output
> HTML towards HTML 4.01 compliance. By far the most common problem I
> found was incorrect nesting of <para> nodes, which results in invalid
> HTML.

I wonder if you're going to get stuck at some point due to invalid HTML
being output by the toolchain that cannot be fixed.  For example, there
are <A> elements inside other <A> elements in history.html.  How would
you fix that?  There's also a systematic problem in bookindex.html
which is a generated file.

I wonder if it would be better to see about switching the toolchain.  We
discussed jumping to XML; this was rejected in the past for no bigger
reason that not wanting to have to rename the files from .sgml to .xml.
Now that we're in Git, that's no longer a problem.  If we can switch to
a better toolchain for producing the HTML, maybe these problems would go
away.  (Of course, to be able to switch to XML we'd need to change a few
habits that no longer work such as using </> as closing tag).

Of course, switching to XML is going to meet a lot more resistance than
just committing these simple fixes to the SGML source.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support