Re: Typo.

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Dmitry Igrishin <dmitigr(at)gmail(dot)com>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Typo.
Date: 2016-06-07 13:37:58
Message-ID: CACjxUsOk02Xu8cr7TRep-DfdkKgUhdUk5gYaUEf8qpdb=P4i9A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Tue, Jun 7, 2016 at 8:22 AM, Dmitry Igrishin <dmitigr(at)gmail(dot)com> wrote:
> 2016-06-07 15:44 GMT+03:00 Kevin Grittner <kgrittn(at)gmail(dot)com>:
>> On Tue, Jun 7, 2016 at 6:26 AM, Dmitry Igrishin <dmitigr(at)gmail(dot)com> wrote:
>>
>>> In "Internal position: this is defined the same as the P field, but it
>>> is used when the cursor position refers to an internally generated",
>>> "internally generated" should be replaced with "internally-generated".
>>
>> Not according to, for example, the Chicago Manual of Style:
>>
>> http://www.chicagomanualofstyle.org/16/images/ch07_tab01.pdf
>>
>> (See the "adverb ending in ly + participle or adjective" category.)
>>
>> I'm pretty sure that this has been discussed on this list before
>> and decided in favor of omitting the hyphenation in such cases.
> Hm, well, how about removing hypenation from
> "Internal query: the text of a failed internally-generated command",
> "procedural language functions and internally-generated queries",
> at https://www.postgresql.org/docs/9.6/static/protocol-error-fields.html
> and similar in other places?

I think we should be consistent, especially on adjacent lines. Oddly,
a single commit 12 years ago used both in close proximity.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

  • Re: Typo. at 2016-06-07 13:22:35 from Dmitry Igrishin

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2016-06-07 13:47:18 Re: Typo.
Previous Message Dmitry Igrishin 2016-06-07 13:22:35 Re: Typo.