From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
Subject: | Add comma after e.g. and i.e.? |
Date: | 2020-08-25 18:36:19 |
Message-ID: | 20200825183619.GA22369@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
We are inconsistently about adding a comma after e.g. and i.e.:
$ cd doc/src/sgml/
$ cat *.sgml */*.sgml | egrep -c '(e\.g\.|i\.e\.),'
255
$ cat *.sgml */*.sgml | egrep -c '(e\.g\.|i\.e\.)[^,:]'
87
I removed the colon because using a trailing colon is always valid in
context.
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?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-08-25 18:38:11 | Re: Procedures |
Previous Message | Bruce Momjian | 2020-08-25 14:06:25 | Re: Document "59.2. Built-in Operator Classes" have a clerical error? |