All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gu, Yang <yang.gu@intel.com>
To: ofono@ofono.org
Subject: RE: [PATCH] Fix common misspellings
Date: Wed, 15 Sep 2010 13:26:44 +0800	[thread overview]
Message-ID: <CE761E84DADF2947A4AF22FB8D97A4732A79D8BA@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <AANLkTinSaL8amVpp1KOUkmWuL1xZj6YqLrWsHJZAtY_E@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

Hi


>
>Yes, I use a script I made based on the format of misspelling
>corrections available at wikipedia. I've uploaded the 3 files I used
>to http://people.profusion.mobi/~lucas/playground/
>
>First, and most important: fix-typos.sh. It reads from stdin the words
>to fix in the following format:
>
>word->correction
>
>If there is more than 1 possible fix, use a "," in the end of the
>correction. In that case it will output to stderr the suggestions
>instead of automatically fixing.
>
>The second file, typos.txt, is the dictionary, based on that of
>wikipedia. I prepared it paying attention to some problematic words
>and suggestions from other projects (mainly EFL and Linux kernel)
>
>The third file is a script to get the changed words in the format I
>used in commit message. It needs to be in a git repository in order to
>work.
>
>
>I usually run like this:
>
>~/bin/fix-typos.sh 2>&1 > /tmp/log.txt < ~/tmp/typos.txt | tee /tmp/log2.txt
>
>In /tmp/log.txt will be the progress of the substitutions. It will
>print it word it's searching for.
>In /tmp/log2.txt will be the fixes made and suggestions about other
>words that can be manually fixed later.
>
>
>I hope this helps.

Thanks for sharing the useful scripts!

Regards,
-Yang

      reply	other threads:[~2010-09-15  5:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  1:32 [PATCH] Fix common misspellings Lucas De Marchi
2010-09-14  1:35 ` Marcel Holtmann
2010-09-14  2:32   ` Lucas De Marchi
2010-09-14  2:37     ` Denis Kenzior
2010-09-14  3:06       ` [PATCH 1/6] Fix common misspellings in documentation Lucas De Marchi
2010-09-14  3:06       ` [PATCH 2/6] Fix common misspellings in drivers Lucas De Marchi
2010-09-14  5:08         ` Marcel Holtmann
2010-09-14  6:51           ` Aki Niemi
2010-09-14  7:02             ` Marcel Holtmann
2010-09-14  3:06       ` [PATCH 3/6] Fix common misspellings in gatchat Lucas De Marchi
2010-09-14  3:06       ` [PATCH 4/6] Fix common misspelling in gisi Lucas De Marchi
2010-09-14  3:06       ` [PATCH 5/6] Fix common misspellings in TODO file Lucas De Marchi
2010-09-14  3:06       ` [PATCH 6/6] Fix common misspelling in source files Lucas De Marchi
2010-09-14  3:21 ` [PATCH] Fix common misspellings Gu, Yang
2010-09-14 22:36   ` Lucas De Marchi
2010-09-15  5:26     ` Gu, Yang [this message]

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=CE761E84DADF2947A4AF22FB8D97A4732A79D8BA@shsmsx501.ccr.corp.intel.com \
    --to=yang.gu@intel.com \
    --cc=ofono@ofono.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.