Re: Link missing in the 14 release notes

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Link missing in the 14 release notes
Date: 2021-07-05 14:30:23
Message-ID: 20210705143023.GZ20766@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Greetings,

* Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> On Fri, Jul 2, 2021 at 05:15:23AM +0000, Daniel Westermann (DWE) wrote:
> > >On Thu, Jul  1, 2021 at 10:01:46PM -0400, Stephen Frost wrote:
> > >Only the first mention of "factorial()" uses a link;  the second item
> > >doesn't have any link.
> >
> > There are other places as well, like this on:
> > "The postgres_fdw supports these type of scans if async_capable is set."
> >
> > async_capable is not a link. Or this one:
> > "This speeds normalize() and IS NORMALIZED."
> >
> > I still think it should be more consistent and all should be links, even if they point to the same section.
>
> I am using standard typographic style, where the first mention of
> something is often italics, but later mentions might not be. I am not
> in favor of adding links to everthing that can have a link _unless_
> there is a unique URI for each item.

While I understand that's the approach you've been following, I don't
agree with it. Providing links gives users a way to find more
information and that applies to each equally. I don't believe users of
the website and release notes would be confused, upset, or otherwise
misunderstand when two items which are covered in the same place have a
repeated link for each of the items.

Thanks,

Stephen

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message rir 2021-07-06 19:25:31 Synopsis notation
Previous Message Tom Lane 2021-07-05 14:04:27 Re: Second-granular timezone offset format not documented