tobold.org

correct • elegant • free

△ comp.mail.* △

◅ comp.mail.mime FAQ - call for new maintainer(s)

Rest off mail deleted after . ▻

MIME's default charset

In article <3apq1v$qpm@hasle.oslonett.no>, Gisle Hannemyr
<gisle@oslonett.no> wrote:
>I think there is a profound misunderstanding about between character
>_codes_ and characters _sets_ . RFC-822 specify character codes, and
>the character codes it specify are in the range [0,127] inclusive.
>There is no specification of character _set_ in RFC-822.

Wrong.  Where did you get this idea?

     3.1.  GENERAL DESCRIPTION

          A message consists of header fields and, optionally, a body.
     The  body  is simply a sequence of lines containing ASCII charac-
     ters.  It is separated from the headers by a null line  (i.e.,  a
     line with nothing preceding the CRLF).

Tim.
--
Tim Goodwin        | "The past contents of this file
Public IP Exchange | is now obsolete." -- u.nzl.1

Original headers:

From: tim@pipex.net (Tim Goodwin)
Newsgroups: comp.mail.mime
Subject: MIME's default charset (was Re: MacEudora and MIME charset)
Date: 21 Nov 1994 18:51:03 -0000
Organization: PIPEX, 216 Science Park, Cambridge, England
Message-ID: <3aqq6n$7r4@pipe.pipex.net>
References: <199411210506.AAA18768@wilma.cs.utk.edu>
  <3apq1v$qpm@hasle.oslonett.no>

△ comp.mail.* △

◅ comp.mail.mime FAQ - call for new maintainer(s)

Rest off mail deleted after . ▻