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 1xR2fR-00000000cvB-04ex for pgsql-docs@arkaria.postgresql.org; Wed, 11 Nov 2026 07:22:49 +0000 Received: from localhost ([127.0.0.1]:35542 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xR2fP-00000009FX6-2sva for pgsql-docs@arkaria.postgresql.org; Wed, 11 Nov 2026 07:22:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:33824) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xR2fP-00000009FWt-1k5G for pgsql-docs@lists.postgresql.org; Wed, 11 Nov 2026 07:22:47 +0000 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1xR2fO-00000000KcQ-2Jm9 for pgsql-docs@lists.postgresql.org; Wed, 11 Nov 2026 07:22:46 +0000 Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-49d05d51553so19676555e9.2 for ; Tue, 10 Nov 2026 23:22:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1794381765; x=1794986565; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:content-type :references:in-reply-to:date:cc:to:from:subject:message-id:from:to :cc:subject:date:message-id:reply-to:content-type; bh=4Wfw8F0aIHf1T+gQOPZ0EDkMUaHA10z3vYwiyeTjUhI=; b=OUE48iVsNRf9Ow1aDONqi81Pf2VfUuf1SZ2qhGqMqy+hpoq03/snLA1P9UKB6rqdWQ 5Kpmj3VYVow4ygouELdXYTQZtwCSTjlA7AQdEFqvR0nuwk6x4Y82fC2SHRa5H9wHlNOu j/+bEBbHH5xyRTslSHukgNos4y0zVd0ycd5dGOmC/Pj29ktFiuW9IhGFKyhofIqwOXTe pmvU7ZqYkY+n+jsONqJzQt6colA3Viid5B3+mJGzMBUiDzNRRJX0OewuK86xBnxgPiwA mWyAmaZvzgaxYevSYTGUGxBRafdHudZi1sUq1Pum4mRTQXA+QK9aimEJbxBQlJ/ASfFI RqBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1794381765; x=1794986565; h=mime-version:user-agent:content-transfer-encoding:content-type :references:in-reply-to:date:cc:to:from:subject:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=4Wfw8F0aIHf1T+gQOPZ0EDkMUaHA10z3vYwiyeTjUhI=; b=WrKeZG6DL8uZb4xgDRtixGG8uqVEuHXcc3aN6Cgl7PcONOqQVQCUW592jugraKdSE/ Go2qkz0MBhppYW+zZ1MKKPIcmacUpA6lNLmvGjX5DILEbZOhQTUQB0B24Wvanf9AhtVS w3ZTNeCi6G1vnHL6SdB83Fg2ZqDJU0b3VNBXy2DxgjQEQjKHUoJDv27OBFZ0EDB51hi5 paojQOWRvk7DiaPN8YVw3Q/yAW0HWrJoPTF8diwRc2P6yTuznuJCHAG3Y7d+j0DAd5eu kyiJ1x9ljZQAJFBq/b/jxJjE7agyytIcVJ41xYkKrI435/3Jzco5gNKfrDVU1uUjw/ff IrGg== X-Forwarded-Encrypted: i=1; AL+hErHzxpssghnYFHgbv0ko4276/VjjGGaPxMTvfr6pw05eqokXzMouAKOW/eqStsNt1rb0v8a0o3xL0vws@lists.postgresql.org X-Gm-Message-State: APuU4Z/UYZHBj9x6iFuqAnAXjUSIwU0UmZ43o7smadp079dSYdjmPNPH LkxtawOWdK3+Wd8YVdjzMR6b/PjTY1XNXBVlZVeQLKP76VK1zwDJolHEHPyI0Wqtd6A= X-Gm-Gg: AYBFou2tK2wFNx5kfY0xUhl9irBZEvzvkXoz8i9Jj3FeL8xEAlAIoIebNZhMF1Q1Otp tp4oC/UUVhGo+NTOdjuI+3DSisMlPDjIgPzFzm3zXuzWuUZ/3/3ldUTlbL1oPIBZsJVNGwC2zLJ +zqmV9aoQY5MPCDSj+bDmizyUWOrIfy6WAAGBXa+WyCmShX2pfoK0a5Ms+Uxl3IkzQgl2G0bzXP rqhemstZWncC3M8hU6UCSmY+VD89ZsmwaKshEp4CZKurAEOybZH9gYk0VVuDi/JPOHb2IktATPZ AnqZ/kYv5BEHyDENDl+qkOJx/mrXMY+BShctXMQ/9HymAWBMWK6ZeO4XDfLcqGcTm5zT5D585zH YJUYZHWpNr5QT7bGkau9NbOfBRcXtkeaLH7+h1JQCR4/q5UaevkPuhG8sm8Aqj+PtWSlEwNxdet jRizSanSwOPuOGfxfeyDp00Oy07pMHlV71N6+JyDxg5AbIRZ6Nn/97rN7IzG85+8YtxPI4PpZOT YoC45ejJlzM9hjv00btZNJ8DmdUeCWacu4HIjiSME/2i/bYArwcxI3zKZ69gRXqvdhoHvaMqxt6 uRJLodrSizNpKG983Y59jPU6OaLBnTfb1qBS2ftXIoog8sMftCaa+YY= X-Received: by 2002:a05:600c:190a:b0:4a3:59ee:86b with SMTP id 5b1f17b1804b1-4ba0931ed3amr24713655e9.4.1794381764837; Tue, 10 Nov 2026 23:22:44 -0800 (PST) Received: from laurenz.albe-K4N0CV00F97414D ([41.66.98.224]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4ba01feee1asm158343595e9.12.2026.11.10.23.22.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 10 Nov 2026 23:22:44 -0800 (PST) Message-ID: <472e310fee1b497358a5c31ff25aebe11eb09d10.camel@cybertec.at> Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc.. From: Laurenz Albe To: Karen Jex , "David E. Wheeler" Cc: Karen Jex , Daniel Gustafsson , "pgsql-docs@lists.postgresql.org" Date: Wed, 11 Nov 2026 08:22:42 +0100 In-Reply-To: References: <0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.60.2 (3.60.2-3.fc44) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2026-11-10 at 17:30 +0100, Karen Jex wrote: > I originally thought we should standardise on "plaintext", but after > reviewing the ways in which the terms are used throughout the docs, I > propose the following approach: >=20 > 1. Use "plain text" to indicate unformatted text: e.g. "...a plain > text file with special syntax that translators edit." > (https://www.postgresql.org/docs/devel/nls-translator.html#NLS-TRANSLATOR= -CONCEPTS). >=20 > 2. Use "cleartext" to indicate unencrypted passwords/secrets: e.g. "It > is good practice not to send the original cleartext password..." > (https://www.postgresql.org/docs/devel/libpq-misc.html#LIBPQ-PQENCRYPTPAS= SWORDCONN). > This is consistent with the AuthenticationCleartextPassword server > message referenced on the same page. >=20 > This is consistent with the vocabulary that is used most often in the > documentation, and the terms are different enough to avoid > confusion/ambiguity. >=20 > I attach the proposed patch and, for completeness, a csv file that > lists the proposed changes. I would be very grateful for any feedback > before I submit it to -hackers. Submitting the patch to pgsql-docs is good enough; you don't need to re-send it to -hackers (but you can do that of course). You can have a commitfest entry point to a message in any PostgreSQL mailing list - just reference the message ID. I think your choice of "cleartext" and "plain text" is fine. I personally would feel better about "plain-text" whenever you use it as an adjective (like in "a plain-text file") and "plain text" for a noun (like "write a file as plain text"), but I am not a native speaker, and my feeling could be the German-speaker's preference for compound words. Also, the borders between noun and adjective in English are blurry ("a fun thing"). 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. You could add some of the considerations that led to your choice of words to the commit message, as well as "Author:", "Reviewed-By:" and "Discussion:" tags (see other commit messages). It would save the committer some keystrokes. Yours, Laurenz Albe