Re: CHARSET considerations

Mark Crispin <> Mon, 17 May 1993 22:44 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa14695; 17 May 93 18:44 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa14689; 17 May 93 18:44 EDT
Received: from by CNRI.Reston.VA.US id aa20627; 17 May 93 18:44 EDT
Received: by (5.59/SMI4.0/RU1.5/3.08) id AA25602; Mon, 17 May 93 18:11:53 EDT
Received: from by (5.59/SMI4.0/RU1.5/3.08) id AA25598; Mon, 17 May 93 18:11:51 EDT
Received: from by (5.65/UW-NDC Revision: 2.28 ) id AA29327; Mon, 17 May 93 15:10:29 -0700
Date: Mon, 17 May 1993 15:05:50 -0700 (PDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Crispin <>
Subject: Re: CHARSET considerations
To: Laurence Lundblade <>
In-Reply-To: <>
Message-Id: <MS-C.737676350.662824084.mrc@Tomobiki-Cho.CAC.Washington.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi Laurence -

     Perhaps all that is needed is a list in the system .pinerc file of all
the valid charsets, and not let the user set her charset to one that is not in
the list.  So, perhaps Pine could have US-ASCII, ISO-2022-JP, and the various
ISO-8859-x sets wired in as an initial list, and the system file specify
additional valid sets?

     The concern is to avoid letting users do things like set it to things
such as ``Latin-1'' or ``ASCII'' or similar bogons...

     What do you think?

-- Mark --