linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: "Jared Daniel J. Smith" <linux@trios.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] kernel source spellchecker
Date: 02 Mar 2003 11:46:33 -0700	[thread overview]
Message-ID: <1046630795.10138.495.camel@spc1.mesatop.com> (raw)
In-Reply-To: <20030302165127Z269240-29902+1551@vger.kernel.org>

On Sun, 2003-03-02 at 11:56, Jared Daniel J. Smith wrote:
> Regarding these two cautious comments:
> 
> ==========================================================================
> I wouldn't go that far. Better give a list of speling mistakes (file/line)
> and fix them by hand. It won't need to be done more than occasionally, so
> the overhead is not too bad. --Dr. Horst H. von Brand 
> 
> 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. --David Woodhouse
> ==========================================================================
> 
> I fully agree.
> 
> I have tried to automatically spell-check long, complex texts for years,
> with numerous algorithms; all of them fail for one reason or another,
> and I find that the only proper way to do it is the tedious work by hand.
> 
> 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.

More agreement. In this case it's better to commit a sin of omission
than one of commission.  In my recent cleanups, here are three cases
which were left alone:

./arch/sparc/kernel/head.S: * Sun people can't spell worth damn. "compatability" indeed.
./drivers/net/myri_sbus.h:      u32     shakedown;              /* DarkkkkStarrr Crashesss...   */
./drivers/scsi/FlashPoint.c:      return(0);  /*We WON! Yeeessss! */

> 
> Consider the following:
> 
[snip]
> 
> Converted=Coverted
> is it a pun on something 'hidden' or is it something transformed?
> 
./drivers/media/radio/radio-aimslab.c: * Coverted to new API by Alan Cox <Alan.Cox@linux.org>
./drivers/media/radio/radio-gemtek.c: *    Coverted to new API by Alan Cox <Alan.Cox@linux.org>
./drivers/media/radio/radio-rtrack2.c: * Coverted to new API by Alan Cox <Alan.Cox@linux.org>

Alan's humor can be subtle.  Better to ask him. AC added to cc list.
I just hope he doesn't start to pun "yn Cymraeg"

Steven



  parent reply	other threads:[~2003-03-02 18:37 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02 18:56 [PATCH] kernel source spellchecker 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 [this message]
2003-03-02 22:32   ` Alan Cox
2003-03-03  3:42     ` [PATCH] 2.5.63-current fix Coverted -> Converted , was (Re: [PATCH] kernel source spellchecker) Steven Cole
     [not found] <20030301160017$56fc@gated-at.bofh.it>
2003-03-01 18:39 ` [PATCH] kernel source spellchecker Pascal Schmidt
  -- strict thread matches above, loose matches on Subject: below --
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
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
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

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=1046630795.10138.495.camel@spc1.mesatop.com \
    --to=elenstev@mesatop.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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).