multiple character sets in GeneralText

"Kevin E. Jordan" <> Tue, 07 June 1994 16:02 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa13881; 7 Jun 94 12:02 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13877; 7 Jun 94 12:02 EDT
Received: from by CNRI.Reston.VA.US id aa27467; 7 Jun 94 12:02 EDT
Received: from by with SMTP (PP) id <>; Tue, 7 Jun 1994 17:36:20 +0200
Received: from by; Tue, 7 Jun 94 10:39:34 -0600
Received: from localhost by; Tue, 7 Jun 94 10:36:10 -0500
Subject: multiple character sets in GeneralText
Date: Tue, 07 Jun 94 10:36:09 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Kevin E. Jordan" <>
Message-Id: <>

Has this question been asked before...  RFC1494 gives no guidance in the case
where an X.400 GeneralText body part contains multiple ISO-8859-x character
sets, e.g. ISO-8859-1 and ISO-8859-7.  This body part will contain multiple
integers in its character set SET, and it will also contain escape sequences
in its text that define designators, character set shifts, etc.  How should
this be mapped to MIME?  The following possibilities seem like options:

   1. Generate a text/plain part with multiple "charset=ISO-8859-x" parameters
      and leave the ISO-2022 escape sequences in.  Are multiple charset
      parameters legal in text/plain parts?

   2. Generate a default application/octet-stream part which preserves the
      whole X.400 body part intact.

Option 1 might at least provide something readable to the recipient, but it
depends upon the UA's ability to deal nicely with multiple charset parameters,
and it also assumes that the UA will interpet the ISO-2022 escape sequences.

Option 2 preserves the original information intact, but it probably won't
be readable unless the recipient's UA has a very clever interpreter for
application/octet-stream message parts.