pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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
Date: Thu, 19 Oct 2017 11:11:58 -0400
Message-ID: <1736.1508425918@sss.pgh.pa.us> (raw)
In-Reply-To: <6d137bd0-eef6-1d91-d9b8-1a5e9195a899@2ndquadrant.com>
References: <6d137bd0-eef6-1d91-d9b8-1a5e9195a899@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>

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



view thread (6+ messages)  latest in thread

Message-ID: <1736.1508425918@sss.pgh.pa.us>
Permalink:  ../1736.1508425918@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1736.1508425918@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com
  Subject: Re: no more SGML empty tags
  In-Reply-To: <1736.1508425918@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox