At 2:23 AM 11/18/94, Kazuhiko Yamamoto
=?ISO-2022-JP?B?GyRCOzNLXE9CSScbKEI=?= <kazu wrote:
- I don't think 'charset' subtype is necessary if we use ISO 2022.
This is not a matter subject to opinion. In other words, the charset
parameter very much IS required for any text which is not simple ASCII.
You are simply wrong. However strongly you might require, charset
parameter does NOT EXIST in non-MIME mails.
For such mails, ISO-2022-INT can be default encoding without any
difficulty.
Moreover, on the strongly connectionless Internet world (outside of
MIME) or on filetype-less UNIX world, there are no charset exist.
For such environment, ISO-2022-INT can be the only encoding for
the Internatonalized global communication.
I don't mind those who needs multiple localizations (Swedesh need only
one and not) keep using charset mechanism.
But, at the same time, there are no reason for MIME worshippers to
stop the development of the Internatonalized global communication.
MIME and the Internatonalized global communication are completely
unrelated (except for the current MIME requirement on non-MIME mails).
Understand?
In effect, you are saying that any subgroup on the Internet may decide to
declare their own default character set and then it would not need to have
Mime objects specify that type explicitly. While there is nothing to
prevent any subgroup from doing what it wishes, of course, the behavior
will be completely non-standard.
Not at all, it is the subgroup of all the people on the Internet who is
interested in the Internatonalization.
Those who are not (apparently exist) may use a localization with or
without MIME or localizations with MIME but have no reason to stop
us develop the Internationalized Internet.
Masataka Ohta