From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Add comma after e.g. and i.e.?
Date: Tue, 25 Aug 2020 15:10:44 -0400
Message-ID: <2760922.1598382644@sss.pgh.pa.us> (raw)
In-Reply-To: <20200825183619.GA22369@momjian.us>
References: <20200825183619.GA22369@momjian.us>
Bruce Momjian <bruce@momjian.us> 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.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us
Subject: Re: Add comma after e.g. and i.e.?
In-Reply-To: <2760922.1598382644@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox