From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Various documentation typo/grammar fixes |
Date: | 2014-08-30 17:43:26 |
Message-ID: | 6438.1409420606@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> Patch 1 pushed, with each fix back-patched as far as the error
> exists in supported releases. I held off on patch 2 -- partly
> because I spotted at least one case where things weren't quite
> right, partly because there's so much I haven't had time to go over
> it in sufficient detail, and partly because commas are omitted so
> consistently where most style guides want them that I thought
> someone might want to argue that this was an intentional style
> choice and should be preserved.
I would argue against applying patch 2 at all. I think it's what
John McIntyre (http://www.baltimoresun.com/news/language-blog/)
would call peeverism. If there are any places where the extra
commas/periods actually add anything to clarity, then sure, change
those places --- but doing it only because some style guide tells
you to is not the way to approach the issue. We're writing English
not C code here, and so there is no single standard of correctness.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G Johnston | 2014-08-30 21:44:03 | Re: [PATCH] Various documentation typo/grammar fixes |
Previous Message | Kevin Grittner | 2014-08-30 16:33:03 | Re: [PATCH] Various documentation typo/grammar fixes |