From: David Woodhouse <dwmw2@infradead.org>
To: Steven Cole <elenstev@mesatop.com>
Cc: Dan Kegel <dank@kegel.com>, Matthias Schniedermeyer <ms@citd.de>,
Joe Perches <joe@perches.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mike@aiinc.ca
Subject: Re: [PATCH] kernel source spellchecker
Date: 02 Mar 2003 11:21:58 +0000 [thread overview]
Message-ID: <1046604117.12947.16.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <1046578585.2544.451.camel@spc1.mesatop.com>
On Sun, 2003-03-02 at 04:16, Steven Cole wrote:
> Another correction to the corrections file:
>
> Licensed=Licenced
> ^^^^^^^^
> I think Licenced is OK in the UK.
> See http://www.gsu.edu/~wwwesl/egw/jones/differences.htm
'Licenced' is not OK in the UK; it should be corrected to 'Licensed'.
In the UK, 'licence' is a noun, 'license' is a verb -- just as with
practice/practise and advice/advise etc. in both variants of the
language.
I think we also want to add:
Decompressing=Uncompressing
You should also refrain from 'correcting' the already-correct British
spellings of 'modelled'.
It might also be worth adding a list of 'suspect' spellings -- which
require human intervention. Such items might include 'indices=indexes'
and 'erratum=errata' although you can't do it automatically because
sometimes the right-hand side is actually correct.
--
dwmw2
next prev parent reply other threads:[~2003-03-02 11:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 6:59 Dan Kegel
[not found] ` <1046330232.15763.97.camel@localhost.localdomain>
2003-03-01 5:38 ` Dan Kegel
2003-03-01 14:11 ` Matthias Schniedermeyer
2003-03-01 17:13 ` Matthias Schniedermeyer
2003-03-01 18:54 ` Dan Kegel
2003-03-01 19:18 ` Steven Cole
2003-03-01 21:20 ` Dan Kegel
2003-03-02 3:45 ` jw schultz
2003-03-02 2:08 ` Dan Kegel
2003-03-02 3:02 ` Dan Kegel
2003-03-02 3:54 ` Steven Cole
2003-03-02 8:04 ` Dan Kegel
2003-03-02 4:16 ` Steven Cole
2003-03-02 8:21 ` Dan Kegel
2003-03-02 8:40 ` jw schultz
2003-03-02 11:21 ` David Woodhouse [this message]
2003-03-02 13:49 ` Steven Cole
2003-03-02 14:55 ` David Woodhouse
2003-03-02 22:44 ` Alan Cox
2003-03-02 22:59 ` John Bradford
2003-03-03 2:29 ` Dan Kegel
[not found] ` <3E62C0FF.1090700@kegel.com>
[not found] ` <1046661777.7527.518.camel@spc1.mesatop.com>
2003-03-03 5:36 ` Dan Kegel
[not found] ` <3E62E4C0.9070103@kegel.com>
[not found] ` <1046668274.7527.533.camel@spc1.mesatop.com>
2003-03-03 5:48 ` Dan Kegel
2003-03-02 15:35 ` Dan Kegel
2003-03-02 8:09 ` Matthias Schniedermeyer
2003-03-02 8:13 ` Matthias Schniedermeyer
2003-03-02 3:29 ` Steven Cole
2003-03-01 19:30 ` Matthias Schniedermeyer
2003-03-01 20:33 ` Matthias Schniedermeyer
2003-03-01 21:25 ` Dan Kegel
2003-03-01 21:25 ` Matthias Schniedermeyer
2003-03-02 9:15 ` John Bradford
2003-03-02 9:31 ` Matthias Schniedermeyer
2003-03-02 3:16 ` Horst von Brand
2003-03-01 15:57 shaheed
2003-03-01 16:35 ` Jörn Engel
2003-03-01 18:01 ` shaheed
2003-03-01 18:31 ` Jörn Engel
2003-03-05 18:10 ` Pavel Machek
[not found] <20030301160017$56fc@gated-at.bofh.it>
2003-03-01 18:39 ` Pascal Schmidt
2003-03-02 18:56 Jared Daniel J. Smith
2003-03-02 17:22 ` Bernd Petrovitsch
2003-03-02 17:47 ` Werner Almesberger
2003-03-02 18:28 ` Bernd Petrovitsch
2003-03-02 18:46 ` Steven Cole
2003-03-02 22:32 ` Alan Cox
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=1046604117.12947.16.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=dank@kegel.com \
--cc=elenstev@mesatop.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@aiinc.ca \
--cc=ms@citd.de \
/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
all inboxes | Powered by JetHome®