From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | peter(at)eisentraut(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, nagata(at)sraoss(dot)co(dot)jp, daniel(at)yesql(dot)se, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Doc: typo in config.sgml |
Date: | 2024-11-02 01:28:06 |
Message-ID: | ZyWAJp3Ujb2LNFpk@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(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.
> >
> > 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=641a5b7a1447954076728f259342c2f9201bb0b5
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(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 | Tatsuo Ishii | 2024-11-02 03:02:12 | Re: Doc: typo in config.sgml |
Previous Message | Michel Pelletier | 2024-11-02 00:53:14 | Re: Using Expanded Objects other than Arrays from plpgsql |