linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: linux@trios.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel source spellchecker
Date: Sun, 02 Mar 2003 21:36:19 -0800	[thread overview]
Message-ID: <3E62E9D3.60103@kegel.com> (raw)
In-Reply-To: <1046661777.7527.518.camel@spc1.mesatop.com>

"Jared Daniel J. Smith" wrote:
> Even a single lost pun because of overenthusiastic spellchecking is
> not worth the cleanup. I would prefer to see typos than lose a single
> intentional 'misspelling'. It would be best if you posted all changes 
> somewhere so that they could be verified manually.
> 
> Consider the following:
> 
> alignment=alignement
> alignmement is French; is this intentional?

No.  All three instances were english typos.

> constants=konstants
> konstants is German; is this intentional?

No.  All three instances were english typos.

> consumer=comsumer
> comsumer is a neologism: http://www.firstmonday.dk/issues/issue5_5/henshall/

That may be, but in the neologism, it seems to be usually partially capitalized,
and the C source sure looks like just a typo:
/* producer/comsumer pointers for Tx/Rx ring */

> Converted=Coverted
> is it a pun on something 'hidden' or is it something transformed?

Allan said it was a copy/paste error and should be fixed.

> descriptor=decriptor,desciptor
> is it descriptor or decrypter?

You be the judge:
      /* Initiliaze Transmit/Receive decriptor and CR3/4 */

All instances I saw were just english typos.

> invocation=invokation
> invokation is German; is this intentional?

No idea, seems to be gone in the current kernel source?

> negative=negativ
> negativ is a legitimate non-English word; is this intentional?

Where I spot-checked it, it was always just an English typo.

> signaled=signalled
> signaling=Signalling
> signaling=signalling
> signalled is a legitimate alternate spelling of signaled.

Thanks, fixed!

> succeeded=succeded
> succeded could also be a typo for 'succeed'
> 
> through=throught,throuth
> throught could also be a typo for 'thought'

Yes.  These will have to be hand-reviewed.  I do recommend absolutely
every change be hand-reviewed just in case.

> writable=writeable
> writeable is a legitimate alternate spelling of writable

You're right, though I had to dig to find a dictionary that agreed with you.

I've updated http://www.kegel.com/kerspell to remove the "signall*" and "writeable"
corrections.  (My stoplist already listed them as acceptable, fwiw.)

Thanks!
- Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


  parent reply	other threads:[~2003-03-03  5:15 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27  6:59 [PATCH] kernel source spellchecker 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
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 [this message]
     [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=3E62E9D3.60103@kegel.com \
    --to=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@trios.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).