Re: [Ltru] Re: UTF-8

John Cowan <cowan@ccil.org> Sun, 17 September 2006 18:38 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GP1X9-00033G-Bi; Sun, 17 Sep 2006 14:38:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GP1X7-00033B-Fi for ltru@ietf.org; Sun, 17 Sep 2006 14:38:25 -0400
Received: from mercury.ccil.org ([192.190.237.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GP1X6-0001fR-93 for ltru@ietf.org; Sun, 17 Sep 2006 14:38:25 -0400
Received: from cowan by mercury.ccil.org with local (Exim 4.34) id 1GP1X3-00048K-MV; Sun, 17 Sep 2006 14:38:21 -0400
Date: Sun, 17 Sep 2006 14:38:21 -0400
To: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: [Ltru] Re: UTF-8
Message-ID: <20060917183821.GC26073@ccil.org>
References: <789E617C880666438EDEE30C2A3E8D10EEFC@mailsrvnt05.enet.sharplabs.com> <450B2B75.2F36@xyzzy.claranet.de> <6.0.0.20.2.20060916114849.081056e0@localhost> <450BD347.9EA@xyzzy.claranet.de> <6.0.0.20.2.20060917154808.08a12880@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.0.0.20.2.20060917154808.08a12880@localhost>
User-Agent: Mutt/1.3.28i
From: John Cowan <cowan@ccil.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ltru@ietf.org
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

Martin Duerst scripsit:

> Well, and then interpreted as Shift-JIS in the case of my
> mailer :-(. Our spec as well as the HTTP headers will say
> that it's UTF-8. That should be enough. People who are
> okay to see garbage will be as satisfied with Bokm&#xE5;
> as they are with Bokm?$B%F!&l, or any other weird rendering,
> but people who like to see the real thing will be best
> served by UTF-8.

Bokm&#xE5;l is at least reconstructible without knowing anything
except the SGML character reference conventions and the
codepoints of Unicode characters; Bokm?$B%F!&l (which is the
way it got to me, sans ESC characters) is nothing but rubbish.

This is an *excellent* example of why we need explicit escaping
(for which SGML is as good a convention as any) rather than
encoding, given the present state of email.

-- 
John Cowan  cowan@ccil.org  http://ccil.org/~cowan
In the sciences, we are now uniquely privileged to sit side by side
with the giants on whose shoulders we stand.
        --Gerald Holton

_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru