From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-docs@lists.postgresql.org, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Another modest proposal for docs formatting: catalog descriptions
Date: Sat, 9 May 2020 08:54:10 +0200 (CEST)
Message-ID: <alpine.DEB.2.22.394.2005090847090.914063@pseudo> (raw)
In-Reply-To: <23610.1588978416@sss.pgh.pa.us>
References: <20200506213810.GA29168@alvherre.pgsql>
<14800.1588805800@sss.pgh.pa.us>
<23610.1588978416@sss.pgh.pa.us>
Hello Tom,
> Here's a more fully fleshed out draft for this, with stylesheet
> markup to get extra space around the column type names.
I find this added spacing awkward, espacially as attribute names are
always one word anyway. I prefer the non spaced approach.
If spacing is discussed, should the layout rather try to align type
information, eg:
attribute type
description
---
foo bla
this does this and that ...
and here is an example about it
---
foo-foo-foo bla-bla
whatever bla bla blah bla foo foo foo ...
and stuff
I'm not sure how achievable it is from a xml & processing point of view,
and how desirable it is, I'm just throwing it for consideration.
--
Fabien.
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-docs@postgresql.org
Cc: coelho@cri.ensmp.fr, tgl@sss.pgh.pa.us, jkatz@postgresql.org, alvherre@2ndquadrant.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Another modest proposal for docs formatting: catalog descriptions
In-Reply-To: <alpine.DEB.2.22.394.2005090847090.914063@pseudo>
* 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