From: Daniel Gustafsson <daniel@yesql.se>
To: Karen Jex <karenhjex@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: David E. Wheeler <david@justatheory.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: Thu, 12 Nov 2026 10:11:42 +0100
Message-ID: <ADDB5690-C818-4F8C-B904-8550108250BA@yesql.se> (raw)
In-Reply-To: <CAOpR_fZKXs+r6N-Ny0h=t+hqO-ObJ7DMd8P8GpcxEk6XUu+t-Q@mail.gmail.com>
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>
<CAOpR_fZKXs+r6N-Ny0h=t+hqO-ObJ7DMd8P8GpcxEk6XUu+t-Q@mail.gmail.com>
> On 11 Nov 2026, at 16:16, Karen Jex <karenhjex@gmail.com> wrote:
> I can attempt to split out cleartext and plaintext entries if there's
> appetite for that, but I suspect that may actually confuse things
> rather than clarifying them.
Agreed; we should write the docs for postgres users, knowledge of terminology
in cryptography should not be a prerequisite.
> Instead, I propose the following glossary
> entries to define the way in which we're using the terms:
>
> plain text
> Unformatted, human-readable text that consists of a sequence of
> printable characters in a character encoding such as UTF-8.
>
> cleartext
> Unencrypted data; data that exists in an unprotected, readable format
> during storage or transmission. Sometimes used as a synonym for
> plaintext; the input to an encryption algorithm.
Sounds good. I was trying to make the cleartext entry specify that it is
generally data which is intended as input to processing, but I wasn't
particularly successful in creating anything which reads better than what you
have above.
--
Daniel Gustafsson
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, karenhjex@gmail.com, peter@eisentraut.org, david@justatheory.com
Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc..
In-Reply-To: <ADDB5690-C818-4F8C-B904-8550108250BA@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> <CAOpR_fZKXs+r6N-Ny0h=t+hqO-ObJ7DMd8P8GpcxEk6XUu+t-Q@mail.gmail.com> <ADDB5690-C818-4F8C-B904-8550108250BA@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