From: Neil <neil@fairwindsoft.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Punctuation error
Date: Wed, 19 Sep 2018 10:23:41 -0500
References: <153731137094.14990.16664858806045765740@wrigleys.postgresql.org>
 <14262.1537368205@sss.pgh.pa.us>
To: pgsql-docs@lists.postgresql.org
In-Reply-To: <14262.1537368205@sss.pgh.pa.us>
Message-Id: <29493585-B7F7-4B2A-9ACA-80705EA39160@fairwindsoft.com>
Precedence: bulk


> On Sep 19, 2018, at 9:43 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> =3D?utf-8?q?PG_Doc_comments_form?=3D <noreply@postgresql.org> writes:
>> This sentence should not use a semicolon: "Both the ADD TABLE and =
DROP TABLE
>> operations are transactional; so the table will start or stop =
replicating at
>> the correct snapshot once the transaction has committed."
>=20
> That looks perfectly fine to me.  Moreover, there are a *lot* of =
places
> in the PG docs that we'd have to change if we got persnickety about =
this
> sort of thing.
>=20
>> You can either
>> change it to a comma, or else leave out the "so" that follows the =
semicolon.
>> The text that follows a semicolon must be a complete sentence that =
stands on
>> its own.
>=20
> I am unfamiliar with this grammar "rule", and vigorously dispute that
> anyone follows it in the real world.
>=20
> 			regards, tom lane
>=20

Seems Tom is correct for at least the last 100 years or so.  =46rom =
Strunk & White, Elements of Style 1918, Rule 5 (available on-line). Not =
saying this is the definitive PG writing guide, but most of us in the US =
used it for college writing.

=E2=80=9CNote that if the second clause is preceded by an adverb, such =
as accordingly, besides, so, then, therefore, or thus, and not by a =
conjunction, the semicolon is still required.=E2=80=9D

=E2=80=9CI had never been in the place before; so I had difficulty in =
finding my way about.=E2=80=9D

Neil=