| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Karen Jex <karenjex(at)hotmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc.. |
| Date: | 2026-11-11 11:43:13 |
| Message-ID: | F2FB794A-6C35-421A-91AF-35D49D6CA2DC@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
> On 11 Nov 2026, at 11:58, Peter Eisentraut <peter(at)eisentraut(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-11-11 12:29:07 | Introductory docs-hacking task: Example markup |
| Previous Message | Peter Eisentraut | 2026-11-11 10:58:48 | Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc.. |