MIME-Version: 1.0
References: <168487514505.719.16546639844327379750@wrigleys.postgresql.org>
 <ZG0+9kCWYg9tzL6m@paquier.xyz>
In-Reply-To: <ZG0+9kCWYg9tzL6m@paquier.xyz>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Tue, 23 May 2023 16:44:26 -0700
Message-ID: 
 <CAKFQuwZbQLq-bmoaQo_NB9TpouABPm9R0s=H9se+ckex5Y-r-w@mail.gmail.com>
Subject: Re: Typo
To: Michael Paquier <michael@paquier.xyz>
Cc: pspung@northcarolina.edu, pgsql-docs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000bbf86f05fc64f853"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwZbQLq-bmoaQo_NB9TpouABPm9R0s%3DH9se%2Bckex5Y-r-w%40mail.gmail.com>
Precedence: bulk

--000000000000bbf86f05fc64f853
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, May 23, 2023 at 3:32=E2=80=AFPM Michael Paquier <michael@paquier.xy=
z> wrote:

> On Tue, May 23, 2023 at 08:52:25PM +0000, PG Doc comments form wrote:
> > There appears to be a typo, here:
> >
> https://www.postgresql.org/docs/current/history.html#:~:text=3DPostgres95=
%20code%20was%20completely%20ANSI%20C
> .
> > A word or two should be added between 'completely' and 'ANSI C', such a=
s
> > 're-written in', or 're-coded using', or some such.
>
> 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%.
>
>
I agree with the OP, that is missing something.  Maybe:

Between the 4.2 release and the release of Postgres95 the code was made to
completely adhere to ANSI C and the size was reduced by 25%.

David J.

--000000000000bbf86f05fc64f853
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Tue, May 23, 2023 at 3:32=E2=80=AFPM Michael Paquier &l=
t;<a href=3D"mailto:michael@paquier.xyz">michael@paquier.xyz</a>&gt; wrote:=
</span><br></div></div><div class=3D"gmail_quote"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">On Tue, May 23, 2023 at 08:52:25PM +0000, PG Doc c=
omments form wrote:<br>
&gt; There appears to be a typo, here:<br>
&gt; <a href=3D"https://www.postgresql.org/docs/current/history.html#:~:tex=
t=3DPostgres95%20code%20was%20completely%20ANSI%20C" rel=3D"noreferrer" tar=
get=3D"_blank">https://www.postgresql.org/docs/current/history.html#:~:text=
=3DPostgres95%20code%20was%20completely%20ANSI%20C</a>.<br>
&gt; A word or two should be added between &#39;completely&#39; and &#39;AN=
SI C&#39;, such as<br>
&gt; &#39;re-written in&#39;, or &#39;re-coded using&#39;, or some such.<br=
>
<br>
This is the current sentence, and it sounds kind of OK to me, FWIW:<br>
&quot;Postgres95 code was completely ANSI C and trimmed in size by 25%.<br>=
<br></blockquote><div><br></div><div class=3D"gmail_default" style=3D"font-=
family:arial,helvetica,sans-serif">I agree with the OP, that is missing som=
ething.=C2=A0 Maybe:</div><div class=3D"gmail_default" style=3D"font-family=
:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif">Between the 4.2 release and the=
 release of Postgres95 the code was made to completely adhere to ANSI C and=
 the size was reduced by 25%.</div><div class=3D"gmail_default" style=3D"fo=
nt-family:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default=
" style=3D"font-family:arial,helvetica,sans-serif">David J.</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif"><br></div></div></div>

--000000000000bbf86f05fc64f853--