From: Claus Färber (list-ietf-wg-apps-usefor@faerber.muc.de)
Date: Sun Aug 04 2002 - 09:32:00 CDT
Erland Sommarskog <sommar-usefor@algonet.se> schrieb/wrote:
> =?ISO-8859-1?Q?Claus_F=E4rber?= (list-ietf-wg-apps-usefor@faerber.muc.de) writes:
>> It is already solved for email with RFC 2047 for text fields, with RFC
>> 2231 for MIME parameters and with IDNs for the domain part of email
>> addresses. It's not an elegant solution, but it's fully backwards-
>> compatible
> Fully backwards-compatible? Only if your name reall is
> =?ISO-8859-1?Q?Claus_F=E4rber?=?
1. Has your MUA crashed?
2. Has your MTA (or any intermediate MTA) corrputed, bounced or dropped the message?
3. Has my mail be routed to the wrong recipient?
With raw UTF-8, 1 and 2 might have happened; if it was used for email
addresses (very similar to Newsgroup names, BTW), probably 3 might have
happened, too.
Backwards compatible does not mean that leagacy user agents are able to
display newsgroup names correctly (they can't with UTF-8 either).
Backwards compatible does mean that they can:
. access the newsgroup,
. create new postings, and
. create followups
without crashing or creating corrupted messages.
But I'm repeating myself here.
Claus
-- ------------------------ http://www.faerber.muc.de/ ------------------------ OpenPGP: DSS 1024/639680F0 E7A8 AADB 6C8A 2450 67EA AF68 48A5 0E63 6396 80F0