From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3E8080BC.3030704@strakt.com> From: Boyd Roberts User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] UTF-8 handling in non-plan9 app: help finding bug References: <29e8ba954a1cd5ac7b8a9f509008e9da@centurytel.net> <20030324114806.78f6cf04.ggm@apnic.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 25 Mar 2003 17:15:56 +0100 Topicbox-Message-UUID: 83d425a4-eacb-11e9-9e20-41e7f4b1d025 George Michaelson wrote: > From: =?UTF-8?B?7LKc66y07Zi4?= > That's a totally bogus interpretation 'cos that's a: route-addr with a non-null phrase My guess is that it smashed it into two addresses, seperated by a comma, 'cos the MIME encoded atom was a case it couldn't cope with. It would have been better to encode it as the hex chars in a comment or a quoted atom, as it would appear it can't cope with real utf-8: "cc9c bb34 d638" (cc9c bb34 d638) Or even: (Unrepresentable UNICODE hex values follow) "cc9c bb34 d638"