Re: CHARSET considerations

Laurence Lundblade <lgl@nwnet.net> Mon, 17 May 1993 17:08 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01253; 17 May 93 13:08 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01247; 17 May 93 13:08 EDT
Received: from dimacs.rutgers.edu by CNRI.Reston.VA.US id aa09116; 17 May 93 13:08 EDT
Received: by dimacs.rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA20309; Mon, 17 May 93 12:16:43 EDT
Received: from norman.nwnet.net by dimacs.rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA20305; Mon, 17 May 93 12:16:42 EDT
Received: by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA25880; Mon, 17 May 93 09:16:14 -0700
Date: Mon, 17 May 1993 09:06:59 -0700 (PDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Laurence Lundblade <lgl@nwnet.net>
Subject: Re: CHARSET considerations
To: Mark Crispin <mrc@ikkoku-kan.panda.com>
Cc: ietf-charsets@innosoft.com, scs@adam.mit.edu, TROTH@ricevm1.rice.edu, pine-info@cac.washington.edu, ietf-822@dimacs.rutgers.edu, ietf-charsets@innosoft.com, dan@ees1a0.engr.ccny.cuny.edu, scs@adam.mit.edu
In-Reply-To: <MS-C.737437622.2035015474.mrc@Ikkoku-Kan.Panda.COM>
Message-Id: <Pine.3.07.9305170958.E23900-b100000@norman.nwnet.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I haven't followed this discussion, but Pine does do a few things with
character sets.  For example if you set Pine to use ISO-8859-1 and send an
all ASCII message it will tag it US-ASCII (instead of ISO-8859-1).  Also,
it's smart enough to display the lower 128 for all incoming messages in
the ISO-8859-X characters sets and greek the ones it can't if the
character set of the receiving Pine is US-ASCII or ISO-8859-X.  Thought
that was what required for minimal MIME compliance.

Hope I haven't upgraded the sin from omission to comision....

LL


On Fri, 14 May 1993, Mark Crispin wrote:
> 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
> now...
> 
> -- Mark --
>