From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dmitry Igrishin <dmitigr(at)gmail(dot)com> |
Cc: | Kevin Grittner <kgrittn(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Typo. |
Date: | 2016-06-07 13:47:18 |
Message-ID: | 496.1465307238@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Dmitry Igrishin <dmitigr(at)gmail(dot)com> writes:
> 2016-06-07 15:44 GMT+03:00 Kevin Grittner <kgrittn(at)gmail(dot)com>:
>> 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?
They are both correct: it's just a matter of preference which one is used
in a particular place. Any particular instance might be that way because
whoever wrote it always writes that way, or maybe they actually thought
about it and decided a hyphen did or didn't read better there. (To my
taste, a hyphen is better if the phrase is being used as a compound
adjective, and otherwise probably not; but it's a minor thing.) It's just
make-work to try to make all the many hundreds of places where we have
such wording 100% consistent; and I seriously doubt that it would create
any improvement in readability.
If you're looking to improve the docs, there are many places where the
English is actually pretty bad ... but this isn't one.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Igrishin | 2016-06-07 14:20:33 | Re: Typo. |
Previous Message | Kevin Grittner | 2016-06-07 13:37:58 | Re: Typo. |