pg.ddx.io pgsql-docs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
i.e. and e.g. used with incorrect meaning 2+ messages / 2 participants [nested] [flat]
* i.e. and e.g. used with incorrect meaning @ 2021-01-14 13:15 PG Doc comments form <noreply@postgresql.org> 2021-01-15 17:37 ` Re: i.e. and e.g. used with incorrect meaning Bruce Momjian <bruce@momjian.us> 0 siblings, 1 reply; 2+ messages in thread From: PG Doc comments form @ 2021-01-14 13:15 UTC (permalink / raw) To: pgsql-docs@lists.postgresql.org; +Cc: jon77h@gmail.com The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/ssh-tunnels.html Description: You're gonna hate this -- a grammar nit pick. But for the few of us who know what e.g. and i.e. mean, the wrong one is confusing. e.g. = exempli gratia = for example. i.e. = id est = that is. "that is" implies that there's no other option. "for example" implies that there are other options. So in the following text, they seem to be the wrong way round: "The name or IP address after this is the remote bind address you are connecting to, i.e., localhost, which is the default. The second number, 5432, is the remote end of the tunnel, e.g., the port number your database server is using." ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: i.e. and e.g. used with incorrect meaning 2021-01-14 13:15 i.e. and e.g. used with incorrect meaning PG Doc comments form <noreply@postgresql.org> @ 2021-01-15 17:37 ` Bruce Momjian <bruce@momjian.us> 0 siblings, 0 replies; 2+ messages in thread From: Bruce Momjian @ 2021-01-15 17:37 UTC (permalink / raw) To: jon77h@gmail.com; pgsql-docs@lists.postgresql.org On Thu, Jan 14, 2021 at 01:15:41PM +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/ssh-tunnels.html > Description: > > You're gonna hate this -- a grammar nit pick. > But for the few of us who know what e.g. and i.e. mean, the wrong one is > confusing. > > e.g. = exempli gratia = for example. > i.e. = id est = that is. > > "that is" implies that there's no other option. > "for example" implies that there are other options. I wrote this text in this commit: commit 472e518a44 Author: Bruce Momjian <bruce@momjian.us> Date: Fri Oct 2 21:39:33 2020 -0400 doc: clarify the use of ssh port forwarding Reported-by: karimelghazouly@gmail.com Discussion: https://postgr.es/m/159854511172.24991.4373145230066586863@wrigleys.postgresql.org Backpatch-through: 9.5 > So in the following text, they seem to be the wrong way round: > > "The name or IP address after this is the remote bind address you are > connecting to, i.e., localhost, which is the default. The second number, I think you are right that this should be e.g.. I used i.e. because I thought it was odd to have the "which is the default" text after the example text, since it might not make sense. I will change it to: "The name or IP address after this is the remote bind address you are connecting to, i.e., localhost (the default). > 5432, is the remote end of the tunnel, e.g., the port number your database > server is using." I think the above is correct, since "the port number your database server is using" is an example, not a rephrasing of the earlier part of the sentence. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2021-01-15 17:37 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-01-14 13:15 i.e. and e.g. used with incorrect meaning PG Doc comments form <noreply@postgresql.org> 2021-01-15 17:37 ` Bruce Momjian <bruce@momjian.us>
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