[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Charset in newgroup sample


Hi,


     Content-Type: multipart/mixed; boundary="nxtprt"; charset=us-ascii


As near as I can tell from RFC 2046, charset is not a valid parameter for
multipart/* content types.  It's only supposed to go on the final
constituent parts.  Among other things, this avoids...


I also see that RFC 2046 only accepts US-ASCII for the preamble of
a MIME message (I thought a charset for multipart/mixed would be useful
for it, but it is in fact useless):

   preamble := discard-text
   discard-text := *(*text CRLF) *text
   text = <any CHAR, including bare CR & bare LF, but NOT including CRLF>
   CHAR = <any ASCII character> ; (  0-177,  0.-127.)


It is therefore impossible to write "This is a MIME control message."
in Chinese.

   Control: newgroup example.admin.info moderated
   MIME-Version: 1.0
   Content-Type: multipart/mixed; boundary="nxtprt"
   Content-Transfer-Encoding: 8bit

   This is a MIME control message.
   --nxtprt



The parts are defined as:

   body-part := MIME-part-headers [CRLF *OCTET]
   OCTET := <any 0-255 octet value>

That's fine.

--
Julien ÉLIE

« -- Il l'aura voulu.
-- Tu crois vraiment ? » (Astérix)