[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] IDNs in email message bodies
- To: "idn working group" <idn@ops.ietf.org>
- Subject: Re: [idn] IDNs in email message bodies
- From: "William Tan" <william.tan@i-dns.net>
- Date: Mon, 26 Mar 2001 12:34:35 +0800
- Delivery-date: Sun, 25 Mar 2001 20:39:25 -0800
- Envelope-to: idn-data@psg.com
- Organization: i-DNS.net Internation Inc.
> > However, I agree that ACE should be 'converted' for display, and
> > strictly for display only. This is analogous from mail clients
> > detecting mail / url addresses and hyperlinking it.
>
> I disagree. I don't think it is analogous. Hyperlinking the text may
> add underlines or color, but it does not change the text itself.
>
> The recipient, looking at the message body, should ideally see the
> same thing the sender saw when composing the message body. If the
> message body contains Chinese characters XXX.cn, then that's what
> should be displayed. But if the message body contains ASCII characters
> bq--xxx.cn, then that's what should be displayed, because that's what
> the sender saw and intended for the recipient to see.
I agree that everything in the message body (after the headers) should not
be touched.
I envisage the following sending process:
1. User compose a message to an IDN email address.
2. MUA converts the IDN email address to ACE
3. MUA uses the ACE for RFC821 MAIL and RCPT commands
4. MUA uses the ACE in RFC822 From: and To: headers (as recommended in
idn-mua I-D)
5. MUA leaves the message body untouched.
wil.