From: Bruce Momjian <bruce@momjian.us>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: peter@eisentraut.org
Cc: tgl@sss.pgh.pa.us
Cc: nagata@sraoss.co.jp
Cc: daniel@yesql.se
Cc: pgsql-hackers@postgresql.org
Subject: Re: Doc: typo in config.sgml
Date: Fri, 1 Nov 2024 21:28:06 -0400
Message-ID: <ZyWAJp3Ujb2LNFpk@momjian.us> (raw)
In-Reply-To: <20241102.072700.1635141881080027242.ishii@postgresql.org>
References: <10783d4f-2463-44c1-8140-e0d2f5d3f056@eisentraut.org>
<Zw_Fsed0h2P9TtLS@momjian.us>
<ZyUGLQ1jZ5MtRFnl@momjian.us>
<20241102.072700.1635141881080027242.ishii@postgresql.org>
On Sat, Nov 2, 2024 at 07:27:00AM +0900, Tatsuo Ishii wrote:
> > 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.
>
> I thought the conclusion of the discussion was allowing to use LATIN1
> (or UTF-8 encoded LATIN1) characters in SGML files without converting
> them to HTML entities. Your patch seems to do opposite.
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=641a5b7a1447954076728f259342c2f92...
Yes, we _allow_ LATIN1 characters in the SGML docs, but I replaced the
LATIN1 characters we had with HTML entities, so there are none
currently.
I think it is too easy for non-Latin1 UTF8 to creep into our SGML docs
so I added a cron job on my server to alert me when non-ASCII characters
appear.
--
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?"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, ishii@postgresql.org, peter@eisentraut.org, tgl@sss.pgh.pa.us, nagata@sraoss.co.jp, daniel@yesql.se
Subject: Re: Doc: typo in config.sgml
In-Reply-To: <ZyWAJp3Ujb2LNFpk@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox