Re: i.e. and e.g.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: john(dot)naylor(at)enterprisedb(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: i.e. and e.g.
Date: 2022-07-14 06:38:37
Message-ID: 20220714.153837.2007183381600922203.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 14 Jul 2022 09:40:25 +0700, John Naylor <john(dot)naylor(at)enterprisedb(dot)com> wrote in
> On Wed, Jul 13, 2022 at 4:13 PM Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
> wrote:
> >
> > At Wed, 13 Jul 2022 18:09:43 +0900 (JST), Kyotaro Horiguchi <
> horikyota(dot)ntt(at)gmail(dot)com> wrote in
> > > So, "e.g." (for example) in the message sounds like "that is", which I
> > > think is "i.e.". It should be fixed if this is correct. I'm not sure
> > > whether to keep using Latin-origin acronyms like this, but in the
> > > attached I used "i.e.".
>
> I did my own quick scan and found one use of i.e. that doesn't really fit,
> in a sentence that has other grammatical issues:
>
> - Due to the differences how ECPG works compared to Informix's
> ESQL/C (i.e., which steps
> + Due to differences in how ECPG works compared to Informix's ESQL/C
> (namely, which steps
> are purely grammar transformations and which steps rely on the

Oh!

> I've pushed that in addition to your changes, thanks!

Thanks!

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2022-07-14 06:51:24 Re: [PROPOSAL] Detecting plan changes with plan_id in pg_stat_activity
Previous Message John Naylor 2022-07-14 06:24:41 Re: First draft of the PG 15 release notes