Date: Tue, 15 Oct 2024 16:37:05 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Yugo NAGATA <nagata@sraoss.co.jp>, Tatsuo Ishii <ishii@postgresql.org>,
	tgl@sss.pgh.pa.us, daniel@yesql.se, pgsql-hackers@postgresql.org
Subject: Re: Doc: typo in config.sgml
Message-ID: <Zw7ScRYKZVj3pBva@momjian.us>
References: <2565921.1728531809@sss.pgh.pa.us>
 <20241010.160041.949661508167788393.ishii@postgresql.org>
 <20241011114122.c90f8a871462da36f2e2afeb@sraoss.co.jp>
 <20241011.121650.2077607600187658573.ishii@postgresql.org>
 <20241011123653.09a67d3ad7b60a59e4558403@sraoss.co.jp>
 <Zw1rf7vm3FqpItw4@momjian.us>
 <Zw1_j_jofafQbNKl@momjian.us>
 <20241015101036.d8c29e4aada1c3e92ddcef9d@sraoss.co.jp>
 <Zw6eQxtpXIccYpOQ@momjian.us>
 <f1bc1bcd-a71c-411a-9bfd-8cd6ec2ae007@eisentraut.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f1bc1bcd-a71c-411a-9bfd-8cd6ec2ae007@eisentraut.org>
Archived-At: 
 <https://www.postgresql.org/message-id/Zw7ScRYKZVj3pBva%40momjian.us>
Precedence: bulk

On Tue, Oct 15, 2024 at 10:34:16PM +0200, Peter Eisentraut wrote:
> On 15.10.24 18:54, Bruce Momjian wrote:
> > > I agree with encoding non-Latin1 characters and disallowing non-ASCII
> > > characters totally.
> > > 
> > > I found your patch includes fixes in *.svg files, so how about checking
> > > also them by check-non-ascii? Also, I think it is better to use perl instead
> > > of grep because non-GNU grep doesn't support hex escape sequences. I've attached
> > > a updated patch for Makefile. The changes in release.sgml above is not applied
> > > yet, though.
> > Yes, good idea on using Perl and checking svg files --- I have used your
> > Makefile rule.
> > 
> > Attached is an updated patch.  I realized that the new rules apply to
> > all SGML files, not just the release notes, so I have created
> > README.non-ASCII and moved the description there.
> 
> I don't understand the point of this.  Maybe it's okay to try to detect
> certain "hidden" whitespace characters, like in the case that started this
> thread.  But I don't see the value in prohibiting all non-ASCII characters,
> as is being proposed here.

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.

-- 
  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?"