ii) by using MIME to label your use of ISO-2022, you give the recipient
a way to know (at least, and maybe see) what you intended.
By using ISO 2022 to label, the recipient has a way to know (at least,
and maybe see) what we intended.
True. Excellent.
Oh, you are so clever. Many non-experts are still can't understand this
basic point.
Now what we need to do is use MIME to label the use
of ISO 2022,
Why? When we can interoperate and actually are interoperating completely
well without MIME, why you think we need it?
There are no point MIME say something about the outside-of-MIME
world.
What we need to do is, when MIME is used, the charset should
be specified. Then, the default may be US-ASCII.
But leave NET-ASCII as is.
so that the recipient of a message can have a chance to
know (a) that ISO 2022 shifts are going to be used in the message text,
and maybe even (b) which flavors of ISO 2022 charset shifts are going to
be used.
How can a MIME conformant reader can have a chance to know about
unknown MIME charset label of 2022 based encoding (a) that ISO
2022 shifts are going to be used in the message text and maybe even (b)
which flavors of ISO 2022 character set shifts are going to be
used?
It can't.
MIME might have addressed the issue of multiple mono-, bi- or tri-
lingual messages.
MIME does not address the issue of a single truly-multi-lingual message.
So, don't try to pretend that MIME has solved the I18N issue and
let ISO-2022-INT-* address the untouched issue.
Without a label, who outside Japan will be expecting full ISO 2022 in a
piece of mail?
Who, within or outside of japan, is expecting full 2022?
Masataka Ohta