Re: backpatching documentation after conversion to XML

From: Jürgen Purtz <juergen(at)purtz(dot)de>
To: pgsql-docs(at)postgresql(dot)org
Subject: Re: backpatching documentation after conversion to XML
Date: 2017-10-22 07:30:32
Message-ID: 16ce423b-d451-587b-93f8-86a687666f8f@purtz.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Alexander Lakhin 2017-10-22 15:33:26 Re: backpatching documentation after conversion to XML
Previous Message Peter Eisentraut 2017-10-21 16:58:04 Re: no more SGML empty tags