From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: tables on pgbench man page look garbled |
Date: | 2023-05-15 12:35:36 |
Message-ID: | FF518719-DC91-45ED-BF66-9F432F1D2624@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
> On 10 May 2023, at 22:08, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>> On 10 May 2023, at 17:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>>> I took a look at this using macOS as the initial testbed; the TLDR is that
>>> mandoc doesn't support macros in tables, and our single-column function
>>> signature tables rely on that. macOS switched to mandoc in v11 I think, but I
>>> don't have an older box handy to doublecheck.
>>
>> Hmm, any chance of addressing this by expanding out the relevant macros?
>
> Maybe, but I'm not too optimistic about that since I was unable to coerce
> mandoc into accepting any form of explicit linebreaks in T{T} text blocks.
Having spent some more time on this I've been unsuccessful in getting anything
to look better than the originally proposed diff upthread; which is far from
good but a) better than the current garbled output and b) fixes the warnings
from mandoc. Not sure how to make progress on this.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2023-05-16 11:49:23 | pg_basebackup application does not dump all database objects |
Previous Message | Daniel Gustafsson | 2023-05-10 20:08:34 | Re: tables on pgbench man page look garbled |