| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-16 08:00:15 |
| Message-ID: | 10783d4f-2463-44c1-8140-e0d2f5d3f056@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.10.24 23:51, Bruce Momjian wrote:
> 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?
I think the question should be the other way around. The entities are a
historical workaround for when encoding support and rendering support
was poor. Now you can just type in the characters you want as is, which
seems nicer.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2024-10-16 08:01:37 | Re: Enable data checksums by default |
| Previous Message | Peter Eisentraut | 2024-10-16 07:58:23 | Re: Doc: typo in config.sgml |