Re: "an SQL" vs. "a SQL" - Mailing list pgsql-hackers

From David Rowley
Subject Re: "an SQL" vs. "a SQL"
Date
Msg-id CAApHDvobGF8WfmPWd6UWS0zBS_a2v4qE2AyKWqtnpeUmCYr+HA@mail.gmail.com
Whole thread Raw
In response to Re: "an SQL" vs. "a SQL"  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: "an SQL" vs. "a SQL"  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
On Thu, 10 Jun 2021 at 20:58, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 10 Jun 2021, at 10:54, Dave Page <dpage@pgadmin.org> wrote:
>
> > .. I would perhaps suggest extending to any user-visible messages in the code.
>
> I agree, consistent language between docs and user-facing messages is
> important.

Yeah, agreed.

I came up with the attached patch.

The only additional abbreviation that I found to be incorrect that I'd
previously not mentioned was "SRF".  I changed that to use "an".

I only found 4 error messages that needed to be updated.  There's some
incorrect stuff remaining in a few README files which I couldn't
decide if I should update or not.

Most of the offenders away from the docs are the translator hint
comments and within the .po files themselves.

$ git grep -E "translator:.*(a|A)\sSQL" | wc -l
690

Only 816 instances of "a SQL" remain, so only 126 are not related to
translator hints or .po files.

Does anyone have any thoughts if the READMEs should be fixed up?

David

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CALL versus procedures with output-only arguments
Next
From: Roberto Mello
Date:
Subject: Re: "an SQL" vs. "a SQL"