Re: [DOCS] backpatching documentation after conversion to XML

Поиск
Список
Период
Сортировка
Искать
От
Jürgen Purtz
Тема
Re: [DOCS] backpatching documentation after conversion to XML
Дата
Msg-id
16ce423b-d451-587b-93f8-86a687666f8f@purtz.de
Ответ на
Список
Дерево обсуждения
[DOCS] backpatching documentation after conversion to XML Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [DOCS] backpatching documentation after conversion to XML Jürgen Purtz <juergen@purtz.de>
Re: [DOCS] backpatching documentation after conversion to XML Alexander Lakhin <exclusion@gmail.com>
Re: [DOCS] backpatching documentation after conversion to XML Tom Lane <tgl@sss.pgh.pa.us>
Re: [DOCS] backpatching documentation after conversion to XML Alexander Lakhin <exclusion@gmail.com>
Re: [DOCS] backpatching documentation after conversion to XML Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: [DOCS] backpatching documentation after conversion to XML Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
On 21.10.2017 18:57, Peter Eisentraut wrote:
> One workaround (other than being careful) would be to write
>
>      
>
> 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
В списке pgsql-docs по дате отправления
От: Peter Eisentraut
Дата:
От: Alexander Lakhin
Дата:
FAQ