[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: MDN usage question.
Why do not we put the supported Character set
in the capabilities of receiver and transmitter.
At 01:03 01/03/14 -0500, Robert A. Rosenberg wrote:
At 16:18 -0800 on 03/12/2001, McIntyre, Lloyd wrote about RE: MDN usage
> Example: if an offramp gateway receives a "text/plain;
message but the fax offramp is only capable of US-ASCII, you
would want the
message rejected? What if the message contained all ASCII
is, no characters that weren't in both US-ASCII and ISO-8859-1?
Again I would recommend processing and rendering with the resident charset,
however, a notice should be returned to the sender notifying that
information may have been lost due to the mismatch. This is what is realized
with the proposal, in this case the disposition modifier could be something
disposition=processed/error:image rendered with different character set"
ONLY if there is one or more High-ASCII Characters in the message. So long
as the ACTUAL Character set is US-ASCII (ie: Only x00-x7F codepoints occur
in the message) just claiming to be ISO-8859-1 (or even UTF-8 <g>) is NOT
IMO a reason to send this erroneous error message.
MIE Development Div. 2