From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, daniel(at)yesql(dot)se, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Doc: typo in config.sgml |
Date: | 2024-10-15 21:51:46 |
Message-ID: | Zw7j8qpCzVKu60z_@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 15, 2024 at 05:27:49PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Well, we can only use Latin-1, so the idea is that we will be explicit
> > about specifying Latin-1 only as HTML entities, rather than letting
> > non-Latin-1 creep in as UTF8. We can exclude certain UTF8 or SGML files
> > if desired.
>
> That policy would cause substantial problems with contributor names
> in the release notes. I agree with Peter that we don't need this.
> Catching otherwise-invisible characters seems sufficient.
Uh, why can't we use HTML entities going forward? Is that harder? Can
we just exclude the release notes from this check?
--
Bruce Momjian <bruce(at)momjian(dot)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?"
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-10-15 21:59:05 | Re: Doc: typo in config.sgml |
Previous Message | Bruce Momjian | 2024-10-15 21:51:02 | Re: Doc: typo in config.sgml |