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 ) id 1jQ7TI-000503-8c for pgsql-hackers@arkaria.postgresql.org; Sun, 19 Apr 2020 10:46:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jQ7TG-0001V2-DG for pgsql-hackers@arkaria.postgresql.org; Sun, 19 Apr 2020 10:46:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jQ7TG-0001Uv-6R for pgsql-hackers@lists.postgresql.org; Sun, 19 Apr 2020 10:46:42 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jQ7TC-0000Jb-WB for pgsql-hackers@lists.postgresql.org; Sun, 19 Apr 2020 10:46:41 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 587056E1; Sun, 19 Apr 2020 06:46:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 19 Apr 2020 06:46:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=EH+JeDoWmbY446Pq0TeQJuH4IQ50T+nqzTUsDJiEV C0=; b=k+6PexfVpnuUgrSeMoYnS5wlnthHk1jtrSrdgZIJ501PaK1uNkU9nKxxk m9v7SxendIm+axxkLB5MD8mcVycVb1yvpn7IuJl2CY67iR2LBjxWoyJsQ+B4yRY3 XsOILBnlRem8a5XQplkB3yPkeBov+bqpz9cIy30O5v2v0BeHvW/dTE3Nx8i6tMJy +CuAsyEvqTX2jRFyRCISe5RNF5acf04BykRGSUxzayzDVzO6/Ne8LK1LImgTT0gK T/ahTwFSvnBcLCoG9Zlb+JIUjyToKkAB/C+nf2YnS+mELVRPe++0V6LQfrrelj/7 qY3NOdMlq8ZdAntMEYiLqmnci/1NQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgedugdefvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhfhokffffgggjggtgfesthejredttdefheenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqh hurggurhgrnhhtrdgtohhmqeenucffohhmrghinhepvdhnughquhgrughrrghnthdrtgho mhenucfkphepleefrddvgedvrddvudefrddvgedunecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhhtsedv nhguqhhurggurhgrnhhtrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p5df2d5f1.dip0.t-ipconnect.de [93.242.213.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 921603280059; Sun, 19 Apr 2020 06:46:33 -0400 (EDT) Subject: Re: Poll: are people okay with function/operator table redesign? To: Tom Lane , Alvaro Herrera References: <20200416230304.GA28390@alvherre.pgsql> <17560.1587083109@sss.pgh.pa.us> Cc: Robert Haas , Steven Pousty , Pavel Stehule , Isaac Morland , Pierre Giraud , PostgreSQL Developers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Sun, 19 Apr 2020 12:46:32 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <17560.1587083109@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 > 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