On Fri, 09 Dec 1994 18:27:14 +0900 you said:
So your interpretation of rfc822 seems to be something like this:
iso-2022-jp is not conformant to rfc822 because it's not strictly ASCII.
If it's right,
Q encoded iso-8859-1 is also not conformant because of the same reason.
Interpretation of rfc822 should not depend on the existence of charset label.
I think this kind of interpretation is not good for both
iso-2022-* and MIME charset labeling.
Except that, at some point in the (near ?) future, RFCxxxx describing MIME
will be declared an Internet standard. And this will have an effect.
Like what ? Back in the stone age, IP had no concept of a subnet mask.
Then RFC950 was declared a standard. IP software behavio(u)r had to be
modified (and made non-conformant to RFC791) to support subnets. Add to
this, if necessary, the appropriate wording about 'requirements' RFCs
coming out from time to time, and you'll begin to see the light.
Of course, it is the right of the japanese software industry to start
a policy of ignoring the Internet standard while developping software
to be used on the Internet. This will be a big relieve for software
houses all over the rest of the world, as the disparition of a potential
competitor always is...
/AF