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 1t14UW-00Eadn-92 for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Oct 2024 13:55:08 +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 1t14UU-003fBf-DW for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Oct 2024 13:55:06 +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 1t14UU-003fBW-1L for pgsql-hackers@lists.postgresql.org; Wed, 16 Oct 2024 13:55:06 +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 1t14UR-001MfH-PL; Wed, 16 Oct 2024 13:55:05 +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=KbL7CgU0rp+YTr0r+/I0jlMsJhzSwHW3acJ9n8QH7Uw=; b=TXX2L B1XHE6o6OAb5wYesM42MC/3VClgD66vz2XPMG/piSPVCw0x4/Y7zPJk1dANAbFoKYU9rzGXwr7bA5 gJg4M43xwO5UgyyXiIAXuyC62EYdt4GzTrBxeu6Varu/1h3rGJTA3d5zuGa9e5uTR62bshgeEzVpr of8/JIqBxsZBnF50/bviBFK2iXq2+Mzhl7w/aw3fsTm02WO/mnXkvqiGUvw3wh5UyfLTsuTq3umU6 U95VH+6ILgIOxlmOFYr/4pFsC+7mZPrqPs6AlGOGeTCK0krERnK5XB2ed9Owh9SCPLjmGRKMoyJeQ XGbNMQGwoXHigRaWrWDSHZfnMEHDw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1t14UL-0087Xd-2r; Wed, 16 Oct 2024 09:54:57 -0400 Date: Wed, 16 Oct 2024 09:54:57 -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: <20241011123653.09a67d3ad7b60a59e4558403@sraoss.co.jp> <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: <10783d4f-2463-44c1-8140-e0d2f5d3f056@eisentraut.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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. -- 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?"