From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Detailed release notes |
Date: | 2024-10-15 18:01:05 |
Message-ID: | 4086138.1729015265@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I thought we were restricted to Latin-1 characters, because those are
> the only characters that the PDF output supports.
> However, since we decided not to have the commit detail links in the PDF
> output, it is actually safe to use _any_ Unicode character as the commit
> detail link.
I don't think that gives us carte blanche to use anything whatsoever.
It has to be something that will be present in the fonts available on
Joe Average's web browser, and I think that means it had better be
something that has been around a long time. Sticking to LATIN-1 is
not such a bad idea from this perspective. (As an example, the
slightly old version of Emacs I'm using is failing to render
at all.)
Also, at least when looking at your message in Safari,
is just enormous in comparison to §. I think it would be quite
visually distracting, especially for release notes with several links.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-10-15 18:04:10 | Re: Detailed release notes |
Previous Message | Alexander Lakhin | 2024-10-15 18:00:00 | Re: [PoC] Federated Authn/z with OAUTHBEARER |