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

From Bruce Momjian
Subject Re: Doc: typo in config.sgml
Date
Msg-id ZyUGLQ1jZ5MtRFnl@momjian.us
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 Wed, Oct 16, 2024 at 09:54:57AM -0400, Bruce Momjian wrote:
> On Wed, Oct 16, 2024 at 10:00:15AM +0200, Peter Eisentraut wrote:
> > 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.
> 
> Yes, that does make sense, and if we fully supported Unicode, we could
> ignore all of this.

Patch applied to master --- no new UTF8 restrictions.

-- 
  Bruce Momjian  <bruce@momjian.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?"



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Count and log pages set all-frozen by vacuum
Next
From: "Andrey M. Borodin"
Date:
Subject: Re: UUID v7