Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bAHrz-0002UO-AA for pgsql-docs@arkaria.postgresql.org; Tue, 07 Jun 2016 14:20:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bAHry-0003E0-Oq for pgsql-docs@arkaria.postgresql.org; Tue, 07 Jun 2016 14:20:38 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bAHry-0003CA-5J for pgsql-docs@postgresql.org; Tue, 07 Jun 2016 14:20:38 +0000 Received: from mail-it0-x234.google.com ([2607:f8b0:4001:c0b::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bAHrv-0005VE-J2 for pgsql-docs@postgresql.org; Tue, 07 Jun 2016 14:20:37 +0000 Received: by mail-it0-x234.google.com with SMTP id h62so27117243itb.1 for ; Tue, 07 Jun 2016 07:20:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+icN4qL00GGNYPbZaCP5lAkJ+q88rpH/9N4eVDfE4tU=; b=w7NGdbR5GfLpL3e567My6Gr6+px5ZAVtzdpkJ0F+/ryslPBtV9Yl4I5JI3anS8k5KA aLYwdZD1KVTn12oVcDFpkSUen+g+s8VB/wSR3s/ttql7JFZofkK6IfG45mRr+y7VeWLT 8GCyvG4+ZRo2zb0oD4fZ4zEPOmIfHIC8ubE8y7y5qt8FcY6qVWRkaMneumPlD5zZkmTo 9ApT+fPu63ZOGS5b3I1jkAlFQNVypY7UUrMKsHT7RqB7D6s/bE6ytVkGG7Ep3OQpxdGs 3G5Es1tCeva1Tx2ZSEbZzY4L6EyDLO3w5MiDwIVWoKp02kniUn8wZtl4PDLsMRBpJRiZ 2yTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+icN4qL00GGNYPbZaCP5lAkJ+q88rpH/9N4eVDfE4tU=; b=m36bqNNd72hefG8IU7TPSbFpWmvrVrKwFngqQNGFlM4gWVn7WZ8p806DbVM1Sb1auY uUWchuWQfLU9YSJh/eqqAWZPTcVFLIlqAUgwLNd1TPRLeNwV+nFz/VEQy/M/BxRqe/5d LPlI+ncSuMEljD651Za0WAIA9vhxIdpr3o8r8M3xE6OmZ8WNQsVBcZozxNeJtpwfl2Ig 18NQGBvyfljlfAlN5u+z3ErlTqQ+/oVSPMvtz5/K8oqYLxRfRp/i5uN2hMwphu0xH5oH FSXX+cmGM9Hg5tOS+uszG+J25wI6fC18Bcvt/DwVy6iTbuy0uo6++LRegJ7vynCXzaSm u2Tw== X-Gm-Message-State: ALyK8tIbX3yYyIDXu6XSW0efEpz+8F9q3VtUfkS53B1tlGFZYG1hqUx8KTn57oJUdSaN3iv7ciBiAGaGCw4bwA== X-Received: by 10.36.54.200 with SMTP id l191mr4094559itl.79.1465309233926; Tue, 07 Jun 2016 07:20:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.130.131 with HTTP; Tue, 7 Jun 2016 07:20:33 -0700 (PDT) In-Reply-To: <496.1465307238@sss.pgh.pa.us> References: <496.1465307238@sss.pgh.pa.us> From: Dmitry Igrishin Date: Tue, 7 Jun 2016 17:20:33 +0300 Message-ID: Subject: Re: Typo. To: Tom Lane Cc: Kevin Grittner , pgsql-docs Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 2016-06-07 16:47 GMT+03:00 Tom Lane : > Dmitry Igrishin writes: >> 2016-06-07 15:44 GMT+03:00 Kevin Grittner : >>> 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 (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs