Subject: separate charsets for header encoding and 'Content-Type'

From: Jungshik Shin <[email-masked]>
Date: Mon, 10 Jun 1996 15:12:12 -0400

It may sound silly, but I'd like to suggest
that Pine  allow users to optionally use  two separate
character set names for header encoding (=?charset?B?....?= or
=?charset?Q?....?=) and 'charset=' parameter 
of 'Content-Type:' header. With this **optional**
(thus not affecting those who don't need it)
feature, one would be able to send out 
Korean messages strictly conforming to RFC 1557,
which requires that KSC 5601(8bit, EUC-KR) 
in the body of the message is encoded in ISO-2022-KR
(thus in 'Content-Type:' header,paramter 'charset=' 
is to be 'ISO-2022-KR') while EUC-KR characters 
in header are to be B or Q encoded with charset name 
'EUC-KR'. (B encoding is preferred). The same may be
the case for Chinese messages in ISO-2022-CN, for which
RFC is being written(or may have been already written). 

  Enclosed is what Korean message following RFC 1557 looks like
where ^[ stands for ESC(ASCII 27, \033), ^N for SO(ASCII 14),
and ^O for SI(ASCII 15) and 'Korean' means any EUC-KR(8bit)
characters with MSB stripped off to make them 7bit. 
Details are not relevant to this suggestion since code conversion 
can be done by 'sending-filter' in Pine 3.92 or later. 

---------
Subject: =?EUC-KR?B?......?=
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-KR
Content-Transfer-Encoding: 7bit
Other-headers.....

Message body....US-ASCII.....

^[$C)
^NKorean^OUS-ASCII ^NKorean^O US-ASCII ^N
US-ASCII^NKorean^O
-------------

  I would be very grateful for careful consideration of this 
proposal by the Pine team. 

   Jungshik Shin