Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: [patch] (gnus)Splitting in IMAP
Date: Fri, 11 Jul 2003 19:54:03 +0200	[thread overview]
Message-ID: <iluy8z5dk5g.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4nel0xw0rm.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 11 Jul 2003 11:17:49 -0400")

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Fri, 11 Jul 2003, jas@extundo.com wrote:
>> Nah, my grammar is simply poor.  If I understood the English plural
>> forms, I would write a elisp grammar checker, but if I understood
>> the English plural forms, I wouldn't need a grammar checker. :-)
>> 
>> Hm.  Are there any free, general-purpose, grammar checkers?  I
>> recall looking for one a few years ago but ended up with nothing
>> really useful.  Having a flygrammar-mode in Emacs would be cool.
>
> I assume you mean *English* grammar checkers, right?  There are some
> commercial ones, but every single one I've tried, from the old
> Grammatik package to today's Word grammar checker, are not up to the
> task.  I'm not aware of any non-commercial ones (ELisp or otherwise),
> and Google searches came up empty.

Alas, that's my experience as well...

> It is possible to write specific checks, for instance one can check
> for passive voice or for incorrect pluralization, but language is so
> incredibly flexible that those checks will have limited usefulness.

If it would work like flyspell, and only highlight things it doesn't
like, it wouldn't be that obtrusive.  Some searching on the topic
yields:

http://owl.english.purdue.edu/
http://webster.commnet.edu/grammar/

Which contain many simple things to keep in mind, some of them could
probably be identified automatically.  I think I'll start on a
flygrammar that highlights a vs an mistakes, which seems simple enough
to start with, although perhaps not that useful.  Later it could be
extended to match other common things those web pages mention, and
even offer text discussing the mistake for the more complicated
issues.

I have a feeling this is getting a bit off topic though...




  reply	other threads:[~2003-07-11 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 10:03 Matthias Andree
2003-07-11 13:30 ` Simon Josefsson
2003-07-11 15:17   ` Ted Zlatanov
2003-07-11 17:54     ` Simon Josefsson [this message]
2003-07-11 19:02       ` Jesper Harder
2003-07-11 20:40       ` Ted Zlatanov
2003-07-12 10:37         ` Simon Josefsson

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=iluy8z5dk5g.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@gnus.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).