"Russ" == Russ Allbery <rra(_at_)stanford(_dot_)edu> writes:
This is one of the reasons why my proposal (which was the basis
for what ended up in the draft, other than the fact that I did not
propose using UTF-8 for anything other than newsgroup names, or in
message/rfc822)
Russ> It lost quite a bit in the translation there; I would have
Russ> voted for that over the option chosen.
I know.
This, btw, for the ietf-822 crowd, was what I originally proposed to
Usefor a little over a year ago:
1. Strike all basic syntax and punt it back to the mail standards.
Remove any changes that would have the effect of allowing UTF-8 in
headers meaningful to mail. Instead, explicitly provide for the use
of UTF-8 in Newsgroups and Followup-To, and provide _exactly one_
mapping to a format compatible with mail, to allow gateways to handle
it, and to allow servers to reject Newsgroups lines which have been
munged for mail purposes. As regards UTF-8 in other fields, point out
that it should be a future direction, that there are currently issues
with interoperability with mail, but that both standards should be
aiming to migrate towards UTF-8 (or some such wording).
Russ> Clients are going to have to implement an encoding whatever way
Russ> you look at it; either they're going to have to implement
Russ> UTF-8, or they're going to have to implement something else.
Russ> I'm not sure that it's really that much easier to implement
Russ> UTF-8 than IDN.
It's clearly easier to implement UTF-8 than to implement UTF-8 _and_ IDN.
It's not an either-or situation.
--
Andrew.