From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 13:54:57 |
Message-ID: | Zw_Fsed0h2P9TtLS@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(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.
Yes, that does make sense, and if we fully supported Unicode, we could
ignore all of this.
--
Bruce Momjian <bruce(at)momjian(dot)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?"
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-10-16 13:55:14 | Re: Doc: typo in config.sgml |
Previous Message | Joe Conway | 2024-10-16 13:31:58 | Re: System views for versions reporting |