lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 6 Jun 2016 12:09:10 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Allen Hubbe <Allen.Hubbe@....com>,
	"'Austin S. Hemmelgarn'" <ahferroin7@...il.com>,
	'Ken Moffat' <zarniwhoop@...world.com>,
	'Justin Keller' <justincompsci@...il.com>
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] documentation: ntb.txt correct grammar "however"

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ