linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Dan Kegel <dank@kegel.com>
Cc: Joe Perches <joe@perches.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel source spellchecker
Date: Sat, 1 Mar 2003 15:11:14 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0303011503590.29947-101000@korben.citd.de> (raw)
In-Reply-To: <3E60474C.1060304@kegel.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1928 bytes --]

On Fri, 28 Feb 2003, Dan Kegel wrote:

> Joe Perches wrote:
> > On Wed, 2003-02-26 at 22:59, Dan Kegel wrote:
> >
> >>Since the main remaining feature before release of the 2.6
> >>kernel is fixing all the remaining spelling errors,
> >>this patch seems appropriate.
> >
> >
> > Who let the comedian in? :o
>
> At first I was jokeing, but what the heck, I figured I'd run
> it.  Here are the mispelled words that occur in five
> or more files and that lookd like real misspellings to my eye.
> The list contains some words that are ok in British usage;
> I don't have a British spellchecker (that I know how to use).
>
> Perhaps some eagr Perl monger can (after removing the British-ok
> words!) contribute a spellcorrect-kernel program that takes
> in a liste of known misspellings + corrections, and applies
> them to the commments in all kernel source files...
> - Dan

I've no spelling knowledge, so the list of spellcorrections must be made
by someone else. But i can volunteer the perl-snippet to correct the
files. :-)

See attachment.

The programm uses this file-format:
correct=false1,false2,false3...

As there are many ways to false-write a word i think this is the best(tm)
solution to get readable file.
:-)

I've only done a "quick-debug", so there might still be errors in the
program. (Including spelling-bugs ;-) )

- snip -
Usage: spell_fix.pl <options>, where valid options are
    --help            # this message :-)
    --file <file>     # File(s) to be checked
    --dir <dir>       # Directory(s) to be checked (recursive!)
    --spell-file      # File with the correction-list
    --debug           # Debugging-Messages
- snip -




Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.


[-- Attachment #2: Type: APPLICATION/x-perl, Size: 3700 bytes --]

  reply	other threads:[~2003-03-01 14:01 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 [this message]
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
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=Pine.LNX.4.44.0303011503590.29947-101000@korben.citd.de \
    --to=ms@citd.de \
    --cc=dank@kegel.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.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).