linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Howells <dhowells@redhat.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Michael Halcrow <mhalcrow@google.com>,
	Jonathan Corbet <corbet@lwn.net>,
	torvalds@linux-foundation.org
Subject: Re: [PATCH] Documentation: Use "while" instead of "whilst"
Date: Tue, 20 Nov 2018 10:46:02 +0000	[thread overview]
Message-ID: <20181120104601.GB24824@arm.com> (raw)
In-Reply-To: <87in0sf35w.fsf@intel.com>

[+Linus]

On Tue, Nov 20, 2018 at 12:34:35PM +0200, Jani Nikula wrote:
> On Mon, 19 Nov 2018, Will Deacon <will.deacon@arm.com> wrote:
> > Whilst making an unrelated change to some Documentation, Linus sayeth:
> 
> Reference?

This was on the security list where we were dealing with something else, so
I'm afraid that it's not archived.

> >   | Afaik, even in Britain, "whilst" is unusual and considered more
> >   | formal, and "while" is the common word.
> >   |
> >   | [...]
> >   |
> >   | Can we just admit that we work with computers, and we don't need to
> >   | use þe eald Englisc spelling of words that most of the world never
> >   | uses?
> >
> > dictionary.com refers to the word as "Chiefly British", which is
> > probably an undesirable attribute for technical documentation.
> >
> > Replace all occurrences under Documentation/ with "while".
> 
> It's an innocent enough change I guess... but seriously? Do we now need
> a documentation style guide too...? Should we block an otherwise good
> patch with "whilst" in it from now on?

No, I don't think either of those two ideas are being proposed here.

"Whilst" feels natural to me, but apparently it comes across as strange
and antiquated to others. The dictionary confirms that it's not in
widespread use, so I don't see the problem with making the Documentation
clearer by using words that are more easily understood by the English-
speaking world (and I suspect it helps the poor souls that try to translate
this stuff as well).

> Personally, I'd accept that our documentation is a hodge podge of
> regional dialects, written by native and non-native speakers with
> incredibly diverse backgrounds and different levels of education and
> experience. If we can keep the documentation understandable and mostly
> typo free, I'd be happy. Even good grammar seems to be a stretch
> goal... ;)

This patch is definitely a drop in the ocean, but it also only took about
5 seconds to write using sed. If it stops a handful of people reading a
sentence twice, then it's a win imo.

Will

  reply	other threads:[~2018-11-20 10:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 11:02 [PATCH] Documentation: Use "while" instead of "whilst" Will Deacon
2018-11-20 10:34 ` Jani Nikula
2018-11-20 10:46   ` Will Deacon [this message]
2018-11-20 16:32 ` Jonathan Corbet

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=20181120104601.GB24824@arm.com \
    --to=will.deacon@arm.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=corbet@lwn.net \
    --cc=dhowells@redhat.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhalcrow@google.com \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).