Re: Don't change RFC822 for the worse!

[toriver@xxxxxxxxxxx (Tor Iver Wilhelmsen)]

mohta@necom830.cc.titech.ac.jp (Masataka Ohta) writes:
>
>Who are the many people? As you can see, no Japanese implementor-user
>say such a thing. I have never told by anyone that my Japanese
>message is unreadable because it is not labelled.
>
>That's the reality. There is working code. There is strict consensus
>on the use of RFC 822 for Japanese.

Which is all well and fine, and it's also why the RFCs say: As long as
you have a consensus in a mail domain (say, Japan), you can do whatever
you want within that area. Send 16-bit mail, use authorization mechanisms
to your hearts content etc. But as soon as you start interacting with
mail domains _outside_ the area of consensus, you need to follow the
standards. And that currently means MIME or X.400. If you send me
ISO-2022-* mail I cannot read it, since I don't have access to any
machines (that I know of) that can display said character set. If,
however, you send me ISO-8859-1 mail, I can display that easily.

>
>The reality is that it is readable by all the people who can read it.

That's a tautology. If you reread that sentence, it amounts to 1 = 1. And
that is uninteresting.

- Tor Iver