From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Steven Pousty <steve.pousty@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Isaac Morland <isaac.morland@gmail.com>
Cc: Pierre Giraud <pierre.giraud@dalibo.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Poll: are people okay with function/operator table redesign?
Date: Sun, 19 Apr 2020 12:46:32 +0200
Message-ID: <f17a1d71-e8bf-3571-bcda-081289eccb31@2ndquadrant.com> (raw)
In-Reply-To: <17560.1587083109@sss.pgh.pa.us>
References: <20200416230304.GA28390@alvherre.pgsql>
<17560.1587083109@sss.pgh.pa.us>
On 2020-04-17 02:25, Tom Lane wrote:
> I eventually figured out that the approved way to do per-table-entry
> customization is to attach "role" properties to the DocBook elements,
> and then key off the role names in applying formatting changes in
> the customization layer. So attached is a v3 that handles the desired
> formatting changes by applying a hanging indent to table <entry>
> contents if the entry is marked with role="functableentry". It may
> well be possible to do this in a cleaner fashion, but this seems
> good enough for discussion.
This scares me in terms of maintainability of both the toolchain and the
markup. Table formatting is already incredibly fragile, and here we
just keep poking it until it looks a certain way instead of thinking
about semantic markup.
A good old definition list of the kind
synopsis
explanation
example or two
would be much easier to maintain on all fronts. And we could for
example link directly to a function, which is currently not really possible.
If we want to draw a box around this and change the spacing, we can do
that with CSS.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, robertmhaas@gmail.com, steve.pousty@gmail.com, pavel.stehule@gmail.com, isaac.morland@gmail.com, pierre.giraud@dalibo.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Poll: are people okay with function/operator table redesign?
In-Reply-To: <f17a1d71-e8bf-3571-bcda-081289eccb31@2ndquadrant.com>
* 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