Re: CHARSET considerations

Mark Crispin <> Sat, 15 May 1993 04:13 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa17845; 15 May 93 0:13 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa17839; 15 May 93 0:13 EDT
Received: from by CNRI.Reston.VA.US id aa02365; 15 May 93 0:13 EDT
Received: by (5.59/SMI4.0/RU1.5/3.08) id AA26857; Fri, 14 May 93 23:52:54 EDT
Received: from by (5.59/SMI4.0/RU1.5/3.08) id AA26853; Fri, 14 May 93 23:52:52 EDT
Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.27.MRC ) id AA16916; Fri, 14 May 93 20:51:19 -0700
Date: Fri, 14 May 1993 20:47:02 -0700 (PDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Crispin <>
Subject: Re: CHARSET considerations
In-Reply-To: <9305142129.AA22544@adam.MIT.EDU>
Message-Id: <MS-C.737437622.2035015474.mrc@Ikkoku-Kan.Panda.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Steve -

     Thanks for your comments.  You needn't convince me; I've been involved
with the MIME charset issue for a long time (you'll note that I am one of the
authors of the ISO-2022-JP spec).  In defense of the other Pine team members,
the sin is one of omission rather than of comission; they wanted to do
something about character sets and didn't want to wire in a table of legal
values (since it might change).

     I've suggested that as a first pass the charset should only be settable
in the system config file, and that the charset always be coerced to US-ASCII
unless the text contains 8-bit characters and/or has ``funny'' control
characters such as ESC or SI/SO.  More work would definitely be needed in this
area, but you'll appreciate that there are other, higher priorities just

-- Mark --