On Tue, Oct 15, 2024 at 02:01:05PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.
Oh, good point. I did see the link 🔗 as a double-width character.
Let's keep §.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
