pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Daniel Gustafsson <daniel@yesql.se>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: David E. Wheeler <david@justatheory.com>
Cc: Karen Jex <karenjex@hotmail.com>
Cc: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc..
Date: Wed, 11 Nov 2026 12:43:13 +0100
Message-ID: <F2FB794A-6C35-421A-91AF-35D49D6CA2DC@yesql.se> (raw)
In-Reply-To: <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org>
References: <D7B95A7B-88B8-43E6-9DFB-2261B0849337@yesql.se>
	<DBAP195MB09396FA26617A837F43F7DF3CB762@DBAP195MB0939.EURP195.PROD.OUTLOOK.COM>
	<0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com>
	<72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org>

> On 11 Nov 2026, at 11:58, Peter Eisentraut <peter@eisentraut.org> 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







view thread (21+ messages)  latest in thread

Message-ID: <F2FB794A-6C35-421A-91AF-35D49D6CA2DC@yesql.se>
Permalink:  ../F2FB794A-6C35-421A-91AF-35D49D6CA2DC@yesql.se/
Also on:    postgresql.org/message-id/F2FB794A-6C35-421A-91AF-35D49D6CA2DC@yesql.se

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-docs@postgresql.org
  Cc: daniel@yesql.se, peter@eisentraut.org, david@justatheory.com, karenjex@hotmail.com
  Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc..
  In-Reply-To: <F2FB794A-6C35-421A-91AF-35D49D6CA2DC@yesql.se>
  References: <D7B95A7B-88B8-43E6-9DFB-2261B0849337@yesql.se> <DBAP195MB09396FA26617A837F43F7DF3CB762@DBAP195MB0939.EURP195.PROD.OUTLOOK.COM> <0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com> <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org> <F2FB794A-6C35-421A-91AF-35D49D6CA2DC@yesql.se>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox