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

From Peter Eisentraut
Subject Re: Doc: typo in config.sgml
Date
Msg-id 10783d4f-2463-44c1-8140-e0d2f5d3f056@eisentraut.org
Whole thread Raw
In response to Re: Doc: typo in config.sgml  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Doc: typo in config.sgml
List 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@momjian.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.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Doc: typo in config.sgml
Next
From: Daniel Gustafsson
Date:
Subject: Re: Enable data checksums by default