Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q1gEE-0005X5-92 for pgsql-docs@arkaria.postgresql.org; Wed, 24 May 2023 04:36:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q1gED-0004J7-0o for pgsql-docs@arkaria.postgresql.org; Wed, 24 May 2023 04:36:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q1gEC-0004Iy-PA for pgsql-docs@lists.postgresql.org; Wed, 24 May 2023 04:36:00 +0000 Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q1gE9-001njZ-KS for pgsql-docs@lists.postgresql.org; Wed, 24 May 2023 04:36:00 +0000 Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-510ede0f20aso1007553a12.3 for ; Tue, 23 May 2023 21:35:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684902956; x=1687494956; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GZmtfqS3uheaNDvB0t7bmz96znJDoyZS//qXetmlQ4Y=; b=Y3KqwSyqkKcSKl9yIfPCNmYQb1Vgh0k6Lzq2XqLd0OAeXZoe4aiTXAnwK7FNJGp9sj 9vo1b0v6IdFQ8dWXY35x+JOGN6JCfXhsXmR0GJ0mZmVnSLOs67rYdqd0Tm6znPBZqMPk J3W/ZRm6nMO+EffekASgL1lnchLkAtsbf/DAzVeicarRVJYU2TDmpTKY7x+7OVLQGz7e 9+1dFGO3WKkiVh7MEB0E5Kw1qcTl19ycp0CMUqFqm48fRRNH4CUVxgtrRF84tL4avsIE gRtbW+THj7xHweniA15B0bpQJ1cYt3e10xpYdCd2FS1A9EKo78ahS8oElZfWQYuG8aOO mODw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684902956; x=1687494956; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GZmtfqS3uheaNDvB0t7bmz96znJDoyZS//qXetmlQ4Y=; b=OA7tcaIi8cxZqO+brkKYEclVPE5bJYw4dABH4X8fSV1ZObD+eSwBBq2Qz1LsjBAE4T Ih3Cti/LGxDMnunSzv9XijzuUisppWcZ3GTfXU/C+gXaIXhRR7Mp3frRr3vs2diz5iJF QV66dGFFWR92Os+KP5lkB29Oy541me2cuaCrGqhcLIz96US0z8wHi4HwomeD3tjbIJSj BW9HQX025Gm4cGANTuC6bIW8WfJa0sjI0FXJ2P9plKZAk5cmiPeKjVtDnmSrc2cBd14b 0TF+D+5GVs+m//Vc6uM5CrcNB3hg8RmM36vE7h9mDlXF/fvJgr2l7UK986wsBRD7LHdY k/7A== X-Gm-Message-State: AC+VfDzmzddQ12phVIChlkJ1ZOsMicnu1frH1IHLoogdhaTPs8lyNMHr fjWuiJmkf/dgZ0EucixZn7vr0I/a4WgMxk+goQM= X-Google-Smtp-Source: ACHHUZ6uPc7E3wmpFv8s3RrBMAZiWaH9hXkCND7AkvvioQ8+zeYppdYs55MXzOXzDIzqn0C3XE8dHlCqzsuqKBP9erM= X-Received: by 2002:aa7:d948:0:b0:50c:52d:7197 with SMTP id l8-20020aa7d948000000b0050c052d7197mr931728eds.2.1684902956368; Tue, 23 May 2023 21:35:56 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a98:d958:0:b0:1cd:4a4f:77c1 with HTTP; Tue, 23 May 2023 21:35:55 -0700 (PDT) In-Reply-To: <1048164.1684902327@sss.pgh.pa.us> References: <168487514505.719.16546639844327379750@wrigleys.postgresql.org> <1048164.1684902327@sss.pgh.pa.us> From: "David G. Johnston" Date: Tue, 23 May 2023 21:35:55 -0700 Message-ID: Subject: Re: Typo To: Tom Lane Cc: Laurenz Albe , Michael Paquier , "pspung@northcarolina.edu" , "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000032078705fc690a4d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000032078705fc690a4d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, May 23, 2023, Tom Lane wrote: > Laurenz Albe writes: > > On Wed, 2023-05-24 at 07:32 +0900, Michael Paquier wrote: > >> This is the current sentence, and it sounds kind of OK to me, FWIW: > >> "Postgres95 code was completely ANSI C and trimmed in size by 25%. > > > That uses "ANSI C" as an adjective, which I think is sloppy wording > > (even though English is somewhat relaxed about the distinction between > > classes of words). > > Yeah, it's not great English, but it's not awful English either; > just a rather telegraphic (abbreviated) style. > > Here's the thing: at this point, this documentation is itself a > historical artifact. git excavation dates the current wording to > 8baa8fcf4 of 1999-06-21, and that was just a small adjustment of > c8cfb0cea of 1998-03-01, and it seems likely that that was pulled > verbatim from some older source. > > So I'm disinclined to change it on grounds of "I think the grammar > is a bit shaky". It is what it is. > > > Agreed. Besides, after a couple of more passes it grew on me, once I filled in the missing =E2=80=9Ccompared to what=E2=80=9D sufficiently. David J. --00000000000032078705fc690a4d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, May 23, 2023, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Laurenz= Albe <laurenz.albe@cybertec= .at> writes:
> On Wed, 2023-05-24 at 07:32 +0900, Michael Paquier wrote:
>> This is the current sentence, and it sounds kind of OK to me, FWIW= :
>> "Postgres95 code was completely ANSI C and trimmed in size by= 25%.

> That uses "ANSI C" as an adjective, which I think is sloppy = wording
> (even though English is somewhat relaxed about the distinction between=
> classes of words).

Yeah, it's not great English, but it's not awful English either; just a rather telegraphic (abbreviated) style.

Here's the thing: at this point, this documentation is itself a
historical artifact.=C2=A0 git excavation dates the current wording to
8baa8fcf4 of 1999-06-21, and that was just a small adjustment of
c8cfb0cea of 1998-03-01, and it seems likely that that was pulled
verbatim from some older source.

So I'm disinclined to change it on grounds of "I think the grammar=
is a bit shaky".=C2=A0 It is what it is.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0=C2=A0

Agreed.=C2=A0 Besides, after a couple of m= ore passes it grew on me, once I filled in the missing =E2=80=9Ccompared to= what=E2=80=9D sufficiently.

David J.
--00000000000032078705fc690a4d--