[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Don't change RFC822 for the worse!
On Dec 10, 1:02am, Masataka Ohta wrote:
} Subject: Re: Don't change RFC822 for the worse!
} Passing the mail message or any other text on the Internet to UNIX pipe,
} to another Internet commands etc. are the thing we are doing everyday.
} I don't mind if some of you don't need it, as long as you don't
} say we should suffer a lot of inconvenience.
Yet you would ask that many others suffer inconvenience on your behalf.
Assuming ISO 2022 is as much an inconvenience for some as you would say
that not assuming it is for you.
} I have said several times that I don't mind you use MIME.
And I do not mind if you use ISO-2022-INT. But given that I have strong
reason to use one, and you have strong reason to use the other, wouldn't
we be able to communicate better if both of us used both?
} > Why
} > must I continue only to guess, when it would be so simple to be told?
} You don't have to. You can just assume ISO-2022-INT-*, not US-ASCII.
For now and for the foreseeable future, assuming iso-2022-int-* is still
a guess, and one more likely to be wrong than many other guesses that I
} > You say, "The reality is that it is readable by all the people who can
} > read it." Each time I see a message from you, I wonder with sorrow why
} > you seek to exclude so many from that group.
} From which group?
The group of those who can conveniently read email written in Japanese.
} Are you saying I should teach Japanese to all
} the people in the world?
I'm saying that refusal to employ the appropriate methods to make it easy
to differentiate messages containing iso-2022-int-* from those that do not
contain it is needlessly excluding a large number of persons who already
Bart Schaefer Vice President, Technology, Z-Code Software
firstname.lastname@example.org Division of Network Computing Devices, Inc.
civilization (siv"i-le-za'shen), n., see ISO 2022