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 1kAeET-0001sg-9k for pgsql-docs@arkaria.postgresql.org; Tue, 25 Aug 2020 19:03:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kAeES-0001YY-7v for pgsql-docs@arkaria.postgresql.org; Tue, 25 Aug 2020 19:03:44 +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 1kAeER-0001YQ-T4 for pgsql-docs@lists.postgresql.org; Tue, 25 Aug 2020 19:03:44 +0000 Received: from lb2-smtp-cloud9.xs4all.net ([194.109.24.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kAeEL-0006yn-Kt for pgsql-docs@postgresql.org; Tue, 25 Aug 2020 19:03:43 +0000 Received: from webmailclassic.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:214]) by smtp-cloud9.xs4all.net with ESMTPA id AeEIkcVTVuuXOAeEIk9uVT; Tue, 25 Aug 2020 21:03:35 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=s1; t=1598382215; bh=fkTcLHBtJmHff4uNxUxAsM0VPqVAb3lECypH1GZrvZo=; h=MIME-Version:Content-Type:Date:From:To:Subject:Message-ID:From: Subject; b=n7sDYauFbuDjFSimMYRbh/76lnKeT1DZW1F5ItrbOTHuWQjx333DneVlGDcxafnHu /11E/lTy/EiAq2MGRfk7pnV/jLY4CDhZtZ6bL0SOdJ08qpEa+8BYZU59ZrXpx4+hpc be8PTA3txNVxllwfkqQJuJgjd+lPn3CEU3LbQOmrrN3FbqCvfBrdIt8pvqbxBEth/E X+C+ufOe4YvA07TNBgX8AmDdqauq3gwAjLK6Bcdc+/iByRSE6uIe2I82H1UxEj4y8e YpdxSzWhbj5DTMejNjFUQx9huTCm/2g4Q/A1XeWBh7nrGv2tH1G/Z6/wkVgaHJHk2u 9deyWzBkyC7hQ== Received: from fc0c:c185:a5f8:6dfd:a400:6e47:313b:867f by webmailclassic.xs4all.nl with HTTP (HTTP/1.1 POST); Tue, 25 Aug 2020 21:03:34 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 25 Aug 2020 21:03:34 +0200 From: Erik Rijkers To: Bruce Momjian Cc: PostgreSQL-documentation Subject: Re: Add comma after e.g. and i.e.? In-Reply-To: <20200825183619.GA22369@momjian.us> References: <20200825183619.GA22369@momjian.us> Message-ID: X-Sender: er@xs4all.nl User-Agent: XS4ALL Webmail X-CMAE-Envelope: MS4wfAsGYspE/3PQ2/Z9L9i8orC/82DQF8sdhlzKz4KRlwuWcp+BcafS/DNVDmlQbqlyvUcPafrQ+2yW2RCVkYSaLD0CWX2I94oSyRaszn3aKFVQclZUI2nX 7Xv6eoi+rQUrZkkhioZNvUZ3Xu37b02zAHFTn/6/tuBZSbWd4U1CTgYnnJuxNVdWtVeSlbyARaGGTa6utSp1xISk5GwGjWhW1eDu7Fh8gB7cqsufilFLyGHQ 0+r+lHGAy9HvUnVY5fe1og== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-08-25 20:36, Bruce Momjian wrote: > We are inconsistently about adding a comma after e.g. and i.e.: [..] > 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? For what it's worth, I am in favor of that comma. Erik Rijkers