From: Jürgen Purtz <juergen@purtz.de>
To: pgsql-docs@postgresql.org
Subject: Re: backpatching documentation after conversion to XML
Date: Sun, 22 Oct 2017 09:30:32 +0200
Message-ID: <16ce423b-d451-587b-93f8-86a687666f8f@purtz.de> (raw)
In-Reply-To: <609dc528-6eab-522d-5b7d-842bd83159e5@2ndquadrant.com>
References: <609dc528-6eab-522d-5b7d-842bd83159e5@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
On 21.10.2017 18:57, Peter Eisentraut wrote:
> One workaround (other than being careful) would be to write
>
> <xref linkend="foo"></xref>
>
> and maintain that style until the last SGML-based version goes EOL.
>
> Another workaround would be to backpatch a check that greps for
> something like '[^<]/>' in *.sgml and errors on that.
Just to classify the impact: afaik we use the 'empty tag' technique for
the three docbook tags 'xref' (>3000 times), 'co' (7 times), and
'footnoteref' (4 times).
Jürgen Purtz
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
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: juergen@purtz.de
Subject: Re: backpatching documentation after conversion to XML
In-Reply-To: <16ce423b-d451-587b-93f8-86a687666f8f@purtz.de>
* 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