Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)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

In response to

• Re: [HACKERS] Uppercase SGML entity declarations at 2011-04-04 16:23:57 from Gabriele Bartolini

Responses

• Re: [HACKERS] Uppercase SGML entity declarations at 2011-04-04 17:18:21 from Gabriele Bartolini
• Re: [HACKERS] Uppercase SGML entity declarations at 2011-04-04 17:26:45 from Susanne Ebrecht

pgsql-docs by date

Next:	From: Gabriele Bartolini	Date: 2011-04-04 17:18:21
	Subject: Re: [HACKERS] Uppercase SGML entity declarations
Previous:	From: Gabriele Bartolini	Date: 2011-04-04 16:23:57
	Subject: Re: [HACKERS] Uppercase SGML entity declarations

pgsql-hackers by date

Next:	From: Alexander Korotkov	Date: 2011-04-04 16:38:24
	Subject: Re: Proposal: q-gram GIN and GiST indexes
Previous:	From: Jan-Erik Lärka	Date: 2011-04-04 16:34:21
	Subject: Non Win/*nix UTF-8 codepage not known to PostgreSQL developers?!