public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dmitry Igrishin <[email protected]>
To: Tom Lane <[email protected]>
Cc: Kevin Grittner <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Typo.
Date: Tue, 7 Jun 2016 17:20:33 +0300
Message-ID: <CAAfz9KP12cpVUnRXojQE31cr9SbyDKva++WWspcr-MHS2s5vBg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAfz9KPouU8BosWL4C=fWcnkzMo8YGos+=x50PLMuYstjk9=HQ@mail.gmail.com>
<CACjxUsMnkE444oA+0a1WgcN-E5qQ5BcJkBrjj2P1-A=RR1z-Ww@mail.gmail.com>
<CAAfz9KOSLojrymEmWVY8BtiBnmXgZ-X1K6+x72jXK-6=oO-GRg@mail.gmail.com>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
2016-06-07 16:47 GMT+03:00 Tom Lane <[email protected]>:
> Dmitry Igrishin <[email protected]> writes:
>> 2016-06-07 15:44 GMT+03:00 Kevin Grittner <[email protected]>:
>>> 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.
Hm, maybe. Shrug.
> (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.)
Yes, I agree here.
> 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.
Well, I usually report here when I read the documentation to do my
work and see some annoying inconsistency. And often I stop myself, but
in certain cases I can't refrain not to report. Sorry if I too bother
for things that don't worth it.
--
// Dmitry.
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
view thread (12+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Typo.
In-Reply-To: <CAAfz9KP12cpVUnRXojQE31cr9SbyDKva++WWspcr-MHS2s5vBg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox