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 1kB7oE-0007Q0-H1 for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2020 02:38:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kB7oB-0004c5-Kl for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2020 02:38:35 +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 1kB7oB-0004aq-El for pgsql-docs@lists.postgresql.org; Thu, 27 Aug 2020 02:38:35 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kB7o8-0000NB-AA for pgsql-docs@postgresql.org; Thu, 27 Aug 2020 02:38:34 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1kB7o6-0002k1-He; Wed, 26 Aug 2020 22:38:30 -0400 Date: Wed, 26 Aug 2020 22:38:30 -0400 From: Bruce Momjian To: Tom Lane Cc: PostgreSQL-documentation Subject: Re: Add comma after e.g. and i.e.? Message-ID: <20200827023830.GF13370@momjian.us> References: <20200825183619.GA22369@momjian.us> <2760922.1598382644@sss.pgh.pa.us> <20200825192732.GF26852@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200825192732.GF26852@momjian.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Aug 25, 2020 at 03:27:33PM -0400, Bruce Momjian wrote: > On Tue, Aug 25, 2020 at 03:10:44PM -0400, Tom Lane wrote: > > Bruce Momjian writes: > > > We are inconsistently about adding a comma after e.g. and i.e.: > > > > > This summarizes the recommended behavior: > > > https://jakubmarian.com/comma-after-i-e-and-e-g/ > > > In British English, “i.e.” and “e.g.” are not followed by a comma, so > > > the first example above would be: > > > They sell computer components, e.g. motherboards, graphic cards, CPUs. > > > Virtually all American style guides recommend to follow both “i.e.” and > > > “e.g.” with a comma (just like if “that is” and “for example” were used > > > instead), so the very same sentence in American English would become: > > > > > So, what do we want to do? Leave it unchanged, or pick one of these > > > styles? > > > > I think it's fairly pointless to try to enforce such a thing. > > Even if you made the docs 100% consistent on the issue today, > > they wouldn't stay that way for long, because nobody else is > > really going to care about it. > > > > (FWIW, I generally write a comma myself. But I'm not going > > to cry about text that hasn't got one.) > > I wasn't worried about enforcing going forward, but rather if we should > make what we have now consistent. I plan to move forward with this, and will backpatch it so later patches are easier to apply. I think we are fine with adding inconsistent usages over time --- this is probably only something we will address in mass every 10 years or so. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee