Re: "an SQL" vs. "a SQL"

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: "an SQL" vs. "a SQL"
Дата
Msg-id CAApHDvobGF8WfmPWd6UWS0zBS_a2v4qE2AyKWqtnpeUmCYr+HA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: "an SQL" vs. "a SQL"  (Daniel Gustafsson <daniel@yesql.se>)
Ответы Re: "an SQL" vs. "a SQL"  (David Rowley <dgrowleyml@gmail.com>)
Список 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

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: CALL versus procedures with output-only arguments
Следующее
От: Roberto Mello
Дата:
Сообщение: Re: "an SQL" vs. "a SQL"