From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Missing links between system catalog documentation pages |
Date: | 2020-06-21 21:52:37 |
Message-ID: | alpine.DEB.2.22.394.2006212344520.859381@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Tom,
>>> I didn't think there was much point in linkifying both in that case,
>>> and other similar situations.
>
>> The point is that the user reads a sentence, attempts to jump but
>> sometimes can't, because the is not the first occurrence. I'd go for
>> all mentions of another relation should be link.
>
> That has not been our practice up to now, eg in comparable cases in
> discussions of GUC variables, only the first reference is xref-ified.
> I think it could be kind of annoying to make every reference a link,
> both for regular readers (the link decoration is too bold in most
> browsers)
Hmmm. That looks like an underlying CSS issue, not that links are
intrinsically bad.
I find it annoying that the same thing appears differently from one line
to the next. It seems I'm the only one who likes things to be uniform,
though.
> and for users of screen-reader software.
I do not know about those, and what constraints it puts on markup.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-06-21 22:52:04 | Re: Parallel Seq Scan vs kernel read ahead |
Previous Message | Andres Freund | 2020-06-21 20:55:17 | Re: [PATCH] Add support for choosing huge page size |