Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0pZQ-00DPPZ-Ur for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Oct 2024 21:59:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t0pZP-00C6Nt-27 for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Oct 2024 21:59:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0pZO-00C6Nk-Oh for pgsql-hackers@lists.postgresql.org; Tue, 15 Oct 2024 21:59:11 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0pZM-001Fat-U2; Tue, 15 Oct 2024 21:59:10 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 49FLx57n4129122; Tue, 15 Oct 2024 17:59:05 -0400 From: Tom Lane To: Bruce Momjian cc: Peter Eisentraut , Yugo NAGATA , Tatsuo Ishii , daniel@yesql.se, pgsql-hackers@postgresql.org Subject: Re: Doc: typo in config.sgml In-reply-to: References: <20241011114122.c90f8a871462da36f2e2afeb@sraoss.co.jp> <20241011.121650.2077607600187658573.ishii@postgresql.org> <20241011123653.09a67d3ad7b60a59e4558403@sraoss.co.jp> <20241015101036.d8c29e4aada1c3e92ddcef9d@sraoss.co.jp> <4125339.1729027669@sss.pgh.pa.us> Comments: In-reply-to Bruce Momjian message dated "Tue, 15 Oct 2024 17:51:46 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4129120.1729029545.1@sss.pgh.pa.us> Date: Tue, 15 Oct 2024 17:59:05 -0400 Message-ID: <4129121.1729029545@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bruce Momjian writes: > On Tue, Oct 15, 2024 at 05:27:49PM -0400, Tom Lane wrote: >> 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? Yes: it requires looking up the entities. The mail you are probably consulting to make a release note or commit message is most likely just going to contain the person's name as normally spelled. Plus (as you pointed out earlier today) there aren't HTML entities for all characters. > Can we just exclude the release notes from this check? What is the point of a check we can only enforce against part of the documentation? regards, tom lane