Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no
Subject: Re: Suggestions
Date: 02 May 1996 17:29:10 +0200	[thread overview]
Message-ID: <vafwx2vozzt.fsf@ls6.informatik.uni-dortmund.de> (raw)
In-Reply-To: "Ketil.Z"'s message of 02 May 1996 16:31:07 +0200

>>>>> On 02 May 1996 16:31:07 +0200, "Ketil.Z" <ketil@ii.uib.no> said:

  Ketil> Anyway, what I'd really like for [SR]Gnus, is to recognize,
  Ketil> and do various things with different regions of a message.
  Ketil> In particular, I'd like source code to be treated differently
  Ketil> from text - perhaps according to defaults in text-mode versus
  Ketil> cc-mode (other modes might apply)?

  Ketil> Other things, like tables and such would be nice to
  Ketil> recognize, too.  I guess the most important problem is
  Ketil> knowing when to auto fill, and when not to.

I think this problem is AI complete if you want to do it properly.  I
propose the following view on this:

The author of a mail message wrote it in a monospaced (as opposed to
proportional) font.  The author of a message tries to make it
readable.  Therefore the rendition of a message that the author sees
can be expected to be rather readable.  Thus you shouldn't
second-guess that and just use a monospaced font for everything.

I'd imagine recognizing C might be rather easy: if the lines ends in
";" it's C, if the prev and/or the next line is C and the line
contains "else", it's C, too.

But how would you tell the difference between English and Cobol in
"add a to b giving c"?

Just my $0.02,
kai
-- 
Gleep!


  reply	other threads:[~1996-05-02 15:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-02 14:31 Suggestions Ketil.Z
1996-05-02 15:29 ` Kai Grossjohann [this message]
1996-05-02 18:07   ` Suggestions Steven L Baur
1996-05-02 23:46     ` Suggestions Per Abrahamsen
1996-05-03  7:38   ` Suggestions Ketil Z Malde
1996-05-03 19:35     ` Suggestions Steven L Baur
1996-05-04  2:02       ` Suggestions Per Abrahamsen
1996-05-04  6:11         ` Suggestions Steven L Baur
1996-05-04  9:33           ` Suggestions Per Abrahamsen
1996-05-05 14:20           ` Suggestions 守岡 知彦 / MORIOKA Tomohiko
1996-05-05 11:37       ` Suggestions Ketil.Z
1996-05-05 13:28         ` Suggestions Per Abrahamsen
1996-05-05 21:49           ` Suggestions Lars Magne Ingebrigtsen
1996-05-05 22:34             ` Suggestions Per Abrahamsen
1996-05-05 23:41               ` Suggestions Steven L Baur
1996-05-05 23:52               ` Suggestions Lars Magne Ingebrigtsen
1996-05-06  5:10                 ` Suggestions Jacob Morzinski
1996-05-07 14:15                   ` Suggestions Lars Magne Ingebrigtsen
1996-05-07 18:55                 ` Suggestions Paul Franklin

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=vafwx2vozzt.fsf@ls6.informatik.uni-dortmund.de \
    --to=grossjoh@charly.informatik.uni-dortmund.de \
    --cc=ding@ifi.uio.no \
    /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).