From: Randy Dunlap <rdunlap@infradead.org>
To: Allen Hubbe <Allen.Hubbe@emc.com>,
"'Austin S. Hemmelgarn'" <ahferroin7@gmail.com>,
"'Ken Moffat'" <zarniwhoop@ntlworld.com>,
"'Justin Keller'" <justincompsci@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] documentation: ntb.txt correct grammar "however"
Date: Mon, 6 Jun 2016 12:09:10 -0700 [thread overview]
Message-ID: <5755CA56.7010202@infradead.org> (raw)
In-Reply-To: <011801d1c026$96f98440$c4ec8cc0$@emc.com>
On 06/06/16 12:06, Allen Hubbe wrote:
> From: Austin S. Hemmelgarn
>> On 2016-06-04 21:36, Ken Moffat wrote:
>>> On Sat, Jun 04, 2016 at 03:34:01PM -0400, Justin Keller wrote:
>>>> Correct the grammar around the word however.
>
>>>> -besides Netdev, however no other applications have yet been written.
>>>> +besides Netdev; however, no other applications have yet been written.
>>>
>>> As a user of British English, the original looks fine. Your change,
>>> however, looks odd - a semi-colon seems out of place. If you
>>> replaced it by a full-stop it would look acceptable to me - but not
>>> in any sense better than what is there at the moment.
>> FWIW, the existing usage in the file is common enough in at least
>> British, American, and Australian English to be borderline idiomatic
>> syntax, but is technically not correct based on traditional punctuation
>> rules in any of them.
>>
>> Personally, I'd leave it as is, especially considering that usage is
>> also used by most translation services, and that proper usage of
>> semicolons isn't taught much anymore even in collegiate English courses,
>> so many younger individuals who speak English natively will think it
>> looks odd.
>
> As the however-challenged author, I have no preference one way or any other about the phrasing of this line.
>
> To address others' concerns, perhaps I might suggest a change that resolves the correctness issue without appearing odd: change however to but.
>
I think that the patch is good, but the latter suggestion is sufficient and good enough also.
--
~Randy
prev parent reply other threads:[~2016-06-06 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 19:34 [PATCH] documentation: ntb.txt correct grammar "however" Justin Keller
2016-06-05 1:36 ` Ken Moffat
2016-06-06 18:56 ` Austin S. Hemmelgarn
2016-06-06 19:06 ` Allen Hubbe
2016-06-06 19:09 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5755CA56.7010202@infradead.org \
--to=rdunlap@infradead.org \
--cc=Allen.Hubbe@emc.com \
--cc=ahferroin7@gmail.com \
--cc=justincompsci@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox