Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1jRgIn-0000G9-HT
	for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2020 18:10:21 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1jRgIm-0002mG-9h
	for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2020 18:10:20 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jRgIm-0002kN-1T
	for pgsql-hackers@lists.postgresql.org; Thu, 23 Apr 2020 18:10:20 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jRgIj-0005BJ-Ou
	for pgsql-hackers@lists.postgresql.org; Thu, 23 Apr 2020 18:10:19 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03NIA7GS019234;
	Thu, 23 Apr 2020 14:10:07 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: Bruce Momjian <bruce@momjian.us>,
        Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        Robert Haas <robertmhaas@gmail.com>,
        Steven Pousty <steve.pousty@gmail.com>,
        Pavel Stehule <pavel.stehule@gmail.com>,
        Isaac Morland <isaac.morland@gmail.com>,
        Pierre Giraud <pierre.giraud@dalibo.com>,
        PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Poll: are people okay with function/operator table redesign?
In-reply-to: <20200423174343.GA16996@alvherre.pgsql>
References: <20200423174343.GA16996@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@2ndquadrant.com>
	message dated "Thu, 23 Apr 2020 13:43:43 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <19232.1587665407.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Thu, 23 Apr 2020 14:10:07 -0400
Message-ID: <19233.1587665407@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> If we're doing nicer markup+CSS for this, then it might make sense to
> find a better solution for this kind of entry with multiple signatures
> (which was already an issue in the previous version):

Yeah, agreed.  I would like to be able to have multiple signature blocks
in one table cell, which the current hack can't handle.  There aren't
quite enough cases to make this mandatory, but it would be nicer.

It seems do-able if we explicitly mark signature blocks with their
own role, say

       <entry role="functableentry">
        <para role="funcsignature">
         text || anynonarray → text
        </para>
        <para role="funcsignature">
         anynonarray || text → text
        </para>
        <para>
          description ...

Then the CSS can key off of the role to decide what indentation to apply
to the para.  While I mostly see how that would work, I'm not very sure
about whether we can make it work in the PDF chain too.

Not sure whether it'd be worth inventing additional roles to apply to
description and example paras, or whether that's just inducing carpal
tunnel syndrome to no purpose.  We'd want to keep the role label on the
<entry>s anyway I think, and that context should be enough as long as
we don't need different formatting for descriptions and examples.
But maybe Peter's notion of "semantic markup" requires it anyway.

			regards, tom lane