| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, pspung(at)northcarolina(dot)edu, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Typo |
| Date: | 2023-05-24 04:02:27 |
| Message-ID: | f2fcd2a8f75bde26ae20cf5777e716f3fc3b8046.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, 2023-05-24 at 07:32 +0900, Michael Paquier 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=Postgres95%20code%20was%20completely%20ANSI%20C.
> > A word or two should be added between 'completely' and 'ANSI C', such as
> > '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%.
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).
How about: "... was written completely in ANSI C ..."
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-05-24 04:25:27 | Re: Typo |
| Previous Message | David G. Johnston | 2023-05-23 23:44:26 | Re: Typo |