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 1svEFv-00DLtd-Ln for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Sep 2024 11:07:56 +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 1svEFt-00Gbti-RA for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Sep 2024 11:07:53 +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 1svEFt-00Gbta-Fv for pgsql-hackers@lists.postgresql.org; Mon, 30 Sep 2024 11:07:53 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1svEFp-001pLT-B6 for pgsql-hackers@postgresql.org; Mon, 30 Sep 2024 11:07:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=QI0hG+A9E0rIWsqTGa1iBspKKslI/siNwvArRGUOjMk=; b=BU26tmUEWJwYm4flrLhx6SNotH UjMesv7TQqGkh3P4zsVUdugon1X47SMOhsYFZpQADDaR47sb1IUa8MvbizZS0UnI8ylT73L9Orn+b /YtCVRt9tKrHm8Q4XSuaUNqttsWpdQno/HygSVpJQ+f5Qcj4tl6XmgK8AVXu+a4jUN4XAnDgYM+mc zdyRVGz67AGv0osFeXfNsXx7Nq5CjIQ5I89QhPyCbB9Fb24bjrUHUJif1ylQsosvGGYNi+gZURPiQ uESViFnGvpj6dsqEVdlaVQEFu/dOC366x8ZONEQwOHNTLW3ivTpFSkzVZM1Wo91e6L+EGQhcNPTft iveG8Ldw==; Received: from [2409:11:4120:300:6aea:b78c:73cc:e354] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (Exim 4.94.2) (envelope-from ) id 1svEFh-004t9y-N7; Mon, 30 Sep 2024 11:07:45 +0000 Date: Mon, 30 Sep 2024 20:07:31 +0900 (JST) Message-Id: <20240930.200731.666191321972616000.ishii@postgresql.org> To: nagata@sraoss.co.jp Cc: daniel@yesql.se, pgsql-hackers@postgresql.org Subject: Re: Doc: typo in config.sgml From: Tatsuo Ishii In-Reply-To: <20240930193402.e4630ff8288305b480705243@sraoss.co.jp> References: <20240930.180344.557179938418470100.ishii@postgresql.org> <20240930193402.e4630ff8288305b480705243@sraoss.co.jp> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:6aea:b78c:73cc:e354 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk >> I wonder if it would be worth to add a check for this like we have t= o tabs? +1. >> The attached adds a rule to "make -C doc/src/sgml check" for trappin= g nbsp >> (doing so made me realize we don't have an equivalent meson target).= > = > Your patch couldn't detect 0xA0 in config.sgml in my machine, but it = works > when I use `grep -P "[\xA0]"` instead of `grep -e "\xA0"`. > = > However, it also detects the following line in charset.sgml. > (https://www.postgresql.org/docs/current/collation.html) > = > For example, locale und-u-kb sorts '=E0e' before 'a=E9'. > = > This is not non-breaking space, so should not be detected as an error= .= That's because non-breaking space (nbsp) is not encoded as 0xa0 in UTF-8. nbsp in UTF-8 is "0xc2 0xa0" (2 bytes) (A 0xa0 is a nbsp's code point in Unicode. i.e. U+00A0). So grep -P "[\xC2\xA0]" should work to detect nbsp. Best reagards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp