Re: Doc: typo in config.sgml - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Doc: typo in config.sgml
Date
Msg-id a4deecf3-d912-438e-ba61-18bd629c42bb@eisentraut.org
Whole thread Raw
In response to Re: Doc: typo in config.sgml  (Bruce Momjian <bruce@momjian.us>)
List 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.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Remove deprecated -H option from oid2name
Next
From: Nathan Bossart
Date:
Subject: Re: Make foreach_ptr macro work in C++ extensions