From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: no more SGML empty tags
In-reply-to: <6d137bd0-eef6-1d91-d9b8-1a5e9195a899@2ndquadrant.com>
References: <6d137bd0-eef6-1d91-d9b8-1a5e9195a899@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Tue, 17 Oct 2017 16:21:15 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1735.1508425918.1@sss.pgh.pa.us>
Date: Thu, 19 Oct 2017 11:11:58 -0400
Message-ID: <1736.1508425918@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> In XML, empty tags such as </> are no longer allowed.  In preparation
> for converting the documentation to DocBook XML, I have committed a
> patch that expands all such empty tags.  There is also now a warning
> from onsgmls when empty tags are used.  (There is no -werror option,
> unfortunately.)

I just want to point out that this patch has more or less entirely
destroyed any hope of cleanly back-patching documentation changes.

Should we consider applying the same transformation to the back
branches?

			regards, tom lane


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs