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 1t6uoQ-00GPY3-UG for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Nov 2024 16:47:50 +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 1t6uoO-00FRJC-Ov for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Nov 2024 16:47:49 +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 1t6uoO-00FRJ3-Eu for pgsql-hackers@lists.postgresql.org; Fri, 01 Nov 2024 16:47:48 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6uoM-004DDA-9o; Fri, 01 Nov 2024 16:47:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=3TYzUUcQXugZCdbcg5yQt0STsWi5o4O0e0LtyLbNjV8=; b=g6fog nyIfwgz5bo/OUQtU3XXmIo32iI9oXQg+hN22bEAqHUdXHfeNGg9bAwaRbj+Lzfr4Ic3hnayMGBWlT CmamPgdFfTkPVh5h0mE/Gs3DaDtSR3QWCjgYp5ZiEzT910TXIwrjT7uivY0Q7rDHriY3rfFvWUqza nFnFZPsfTWL5r1lcTH2Kj7KBbktQpxQ38yM1Y8hOkrFQxVhkl7RLYcGWlLcCeCsUhcqGHu3PAp1AB ApR+bQ8SrGWLEhPz3IGbeEh+y1Rznes7VTq0Upy2fUB/yGY9XKsnXgtT1mCrrpwUwdWBnY3gqPIJl 8462it4KmlzipP9KeEGw5v+tRONeQ==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1t6uoH-008Tgs-0h; Fri, 01 Nov 2024 12:47:41 -0400 Date: Fri, 1 Nov 2024 12:47:41 -0400 From: Bruce Momjian To: Peter Eisentraut Cc: Tom Lane , Yugo NAGATA , Tatsuo Ishii , daniel@yesql.se, pgsql-hackers@postgresql.org Subject: Re: Doc: typo in config.sgml Message-ID: References: <20241015101036.d8c29e4aada1c3e92ddcef9d@sraoss.co.jp> <4125339.1729027669@sss.pgh.pa.us> <10783d4f-2463-44c1-8140-e0d2f5d3f056@eisentraut.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 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. -- Bruce Momjian 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?"