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.98.2) (envelope-from ) id 1xR6jk-00000000gfS-39YS for pgsql-docs@arkaria.postgresql.org; Wed, 11 Nov 2026 11:43:32 +0000 Received: from localhost ([127.0.0.1]:33444 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xR6jh-0000000AXm9-47ih for pgsql-docs@arkaria.postgresql.org; Wed, 11 Nov 2026 11:43:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:33740) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xR6jh-0000000AXm0-3C53 for pgsql-docs@lists.postgresql.org; Wed, 11 Nov 2026 11:43:30 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xR6jg-00000000MfD-1BWe for pgsql-docs@lists.postgresql.org; Wed, 11 Nov 2026 11:43:29 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id E82E77E8C1B for ; Wed, 11 Nov 2026 12:43:24 +0100 (CET) Received: from s980.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id D913E7E873A; Wed, 11 Nov 2026 12:43:24 +0100 (CET) Received: from localhost (unknown [172.22.191.5]) by s980.loopia.se (Postfix) with ESMTP id D71EA220166F; Wed, 11 Nov 2026 12:43:24 +0100 (CET) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s934.loopia.se ([172.22.191.6]) by localhost (s474.loopia.se [172.22.190.14]) (amavis, port 10024) with LMTP id a1x6sAj8B1Jc; Wed, 11 Nov 2026 12:43:24 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s934.loopia.se (Postfix) with ESMTPSA id 30042172771E; Wed, 11 Nov 2026 12:43:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1794397404; bh=aNLmNfcm7Wa9sAglh/5zwBh8ej3S6+pzsZNXOnmen38=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=DY5qi/qN4bpekDMMYBCsZu+wvAjaxJbE4GI2KuA19fmTGov2rSvm5VEvO+iVO8r81 Tk2CTomQ5Yza2KGuK68QpQIWIHvwll4Ldo8uJt+eSAM1jFY+Wxbou3Yf5L8F1f9BKQ duk0f+kkSLjjQ8VNJE+Go0h5Uq/XgNT78ow/VkRkC2Crx3kyAt7fU52P+cI/aVFBH3 kgkC8QBtNBFYaJu9ijZjUdz0yCeWCIAWTT1FOIgXZXRQ3AxtlAqfcM69LR1+n12yXk 2shRi5wzNoI152PfQrdj83V9KcZ4VLhXAB0/c1Iq02LkhXqid49BNxzxFmOZZPgF3H y0YXe2rWji8fg== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.12\)) Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc.. From: Daniel Gustafsson In-Reply-To: <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org> Date: Wed, 11 Nov 2026 12:43:13 +0100 Cc: "David E. Wheeler" , Karen Jex , "pgsql-docs@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com> <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org> To: Peter Eisentraut X-Mailer: Apple Mail (2.3776.700.51.11.12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 11 Nov 2026, at 11:58, Peter Eisentraut = wrote: Thanks for working on this Karen! > My understanding is/was that plaintext is data meant for encryption, = after which it becomes ciphertext. Cleartext is data not meant for = encryption. That's my understanding as well, but it's not standardized anywhere and scanning relevant RFC's didn't provide any real guidance. > If we tidy this up, consider adding glossary entries. +1 > There are three occurrences of "non-plain-text" that you changed to > "non-plain text". This feels wrong, since to me the hyphen ties = stronger > than the space. I would read that as meaning something like "compound = text". > I'd suggest that you rewrite those sentences to avoid the construct. non-plain-text was never good for non-native speakers, and this didn't = improve it. I agree with trying to rewrite the sentences to avoid this = construct. -- Daniel Gustafsson