Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 07FF51337BD2;
	Mon,  4 Apr 2011 13:37:46 -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 67504-04; Mon,  4 Apr 2011 16:37:28 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
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 4E57B1337B68;
	Mon,  4 Apr 2011 13:37: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 p34GbPAM001504;
	Mon, 4 Apr 2011 12:37:25 -0400 (EDT)
To: Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
cc: Robert Haas <robertmhaas@gmail.com>, pgsql-docs@postgresql.org,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Uppercase SGML entity declarations 
In-reply-to: <4D99F09D.3000606@2ndQuadrant.it> 
References: <4D998B49.8050000@2ndQuadrant.it>
	<BANLkTikwxtb9MU-Bn7XqCJSCEdEuJPL+Lg@mail.gmail.com>
	<4D99F09D.3000606@2ndQuadrant.it>
Comments: In-reply-to Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
	message dated "Mon, 04 Apr 2011 18:23:57 +0200"
Date: Mon, 04 Apr 2011 12:37:24 -0400
Message-ID: <1503.1301935044@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: 201104/19
X-Sequence-Number: 6590

Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it> writes:
> My intention was to start and change some simple documentation files in 
> order to make our conversion process from SGML to XML smoother, while 
> keeping the SGML compatibility of the original documentation intact. 

AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie, <foo>whatever</>).  Which is something that
we are not likely to give up.  So I'm not sure of the point of changing
something as trivial as entity declaration casing.  You're going to end
up having to fork the documentation anyway, or at least feed it through
an SGML to XML converter.  So why not fix the entity casing then?

			regards, tom lane