Re: Detailed release notes - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Detailed release notes
Date
Msg-id CAGECzQQUmN2HSGSrbs6Z51aoie0S9342DbaDN3Z=QQU_9SGQFQ@mail.gmail.com
Whole thread Raw
In response to Re: Detailed release notes  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Detailed release notes
List pgsql-hackers
On Wed, 18 Sept 2024 at 11:26, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> On 2024-Sep-17, Bruce Momjian wrote:
>
> > I think trying to add text to each item is both redundant and confusing,
> > because I am guessing that many people will not even know what a commit
> > is, and will be confused by clicking on the link.
>
> Uh, I 100% disagree that Postgres users reading the release notes would
> not know what a commit is.

+1, IMO it seems completely reasonable to assume that anyone
interested enough in postgres to read the release notes also knows
what a commit is.

> IMO we should be looking at a more surgical approach to implement this,
> perhaps using a custom SGML tag and some custom XSLT code to process
> such tags that adds links the way we want, rather than generic <ulink>
> tags.  Or maybe <ulink> is OK if we add some class to it that XSLT knows
> to process differently than generic ulinks, like func_table_entry and
> catalog_table_entry.

Is it easy to just remove/hide the links completely from the PDF? I
doubt many people read the release notes by going to Appendix E in the
PDF anyway.

It seems a shame to remove those links from the HTML view where they
look acceptable and which most people will use, just because they look
bad in the pdf. And honestly, they don't even look that terrible in
the PDF imo.



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: Detailed release notes
Next
From: Alvaro Herrera
Date:
Subject: Re: Detailed release notes