On Mon, 09 Mar 92 13:17:13 PST,
jknowles(_at_)binky(_dot_)arc(_dot_)nasa(_dot_)gov wrote:
"Iso-2022-jp" was removed from MIME, and there were no public
protests, partly because there are so few Japanese on this list, but
also because the Japanese will continue to use their JUNET encoding
for some time, no matter _what_ MIME says.
No, Iso-2022-jp was removed for the same reason mnemonic was removed,
lack of a published specification acceptable to the IESG for citation
within the MIME document. It had nothing to do with the presence or
absence of Japanese on the list.
Please re-read what was said. The reasons given -- so few Japanese, and
because we will continue to use JUNET encoding no matter what MIME says -- are
for why there was no public protest for the removal of ISO-2022-JP.
The fact that both Iso-2022-jp and mnemonic had an established history of
use within some part of the Internet is why the working group tried to
include both. I doubt that many of us who supported this inclusion are
amused by all the invented reasons for their exclusion.
We aren't, but at least the IESG has been consistent.
I will consider it a show-stopper if mnemonic is reinserted without an IESG-
acceptable citation but ISO-2022-JP is not. I see no reason to coddle the
racist attitude that European languages are important but East Asian languages
are not.
Quite frankly, Japan is far more important than all of Scandanavia put
together. This is even more the case when you include the folks on the ISO-
2022-?? working group from the Republic of Korea and the Republic of China on
Taiwan who are working hard to come up with compatible extensions to ISO-2022-
JP to support Korean and Chinese as well.
Those of us working on ISO-2022 are trying to play ball with the IESG. If the
Europeans do not wish to play ball, then let them sulk in a corner and not
have anything that works for them. It's an annoyance to have to do things the
IESG's way, and it's worth doing only if everybody follows the rules too.