Message-ID: <4D99F09D.3000606@2ndQuadrant.it>
Date: Mon, 04 Apr 2011 18:23:57 +0200
From: Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; it;
	rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Robert Haas <robertmhaas@gmail.com>
CC: pgsql-docs@postgresql.org,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Uppercase SGML entity declarations
References: <4D998B49.8050000@2ndQuadrant.it>
	<BANLkTikwxtb9MU-Bn7XqCJSCEdEuJPL+Lg@mail.gmail.com>
In-Reply-To: <BANLkTikwxtb9MU-Bn7XqCJSCEdEuJPL+Lg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Robert (and Tom),

Il 04/04/11 16:57, Robert Haas ha scritto:
> Forgive me for asking what may seem like a stupid question, but what's
> not XML compliant about them now, and why do we care?  The text is
> only ever going to parse as SGML (not XML) so I guess I don't see why
> it matters.  I don't really object to the proposed patch but I guess
> I'm not sure what it accomplishes.

My apologies, I should have explained it better and at once.

Here is the context. I am coordinating the Italian translation of the 
documentation and we are about to create a branch for 9.1. The 
publishing mechanism is based on DocBook XML (as well as the French 
one), as we are facing extreme difficulties publishing using SGML tools.

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. 
Also I was trying to make the ENTITY declarations consistent throughout 
the documents.

I hope I gave you a more clear explanation.

Cheers,
Gabriele

-- 
  Gabriele Bartolini - 2ndQuadrant Italia
  PostgreSQL Training, Services and Support
  gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it