| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, tgl(at)sss(dot)pgh(dot)pa(dot)us, daniel(at)yesql(dot)se, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Doc: typo in config.sgml |
| Date: | 2024-10-15 21:08:15 |
| Message-ID: | a4deecf3-d912-438e-ba61-18bd629c42bb@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.10.24 22:37, Bruce Momjian wrote:
>> I don't understand the point of this. Maybe it's okay to try to detect
>> certain "hidden" whitespace characters, like in the case that started this
>> thread. But I don't see the value in prohibiting all non-ASCII characters,
>> as is being proposed here.
> 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.
But your patch prohibits even otherwise allowed Latin-1 characters.
I don't see why we need to enforce this at this level. Whatever
downstream toolchain has requirements about which characters are allowed
will complain if it encounters a character it doesn't like.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-10-15 21:25:50 | Re: Make foreach_ptr macro work in C++ extensions |
| Previous Message | Peter Eisentraut | 2024-10-15 20:48:08 | Re: Remove deprecated -H option from oid2name |