From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3032e34b48396811828667e33f9592bf@plan9.bell-labs.com> From: David Presotto To: 9fans@cse.psu.edu Subject: Re: [9fans] UTF-8 handling in non-plan9 app: help finding bug In-Reply-To: <20030324114806.78f6cf04.ggm@apnic.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-tbpkcvyxfxurxxngslxpmijjew" Date: Sun, 23 Mar 2003 22:01:26 -0500 Topicbox-Message-UUID: 8385b4be-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-tbpkcvyxfxurxxngslxpmijjew Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit The base64 string decodes to 9 UTF bytes whose hex values are: ec b2 9c eb ac b4 ed 98 b8 Not a comma in there. This UTF string converts to 3 Unicode characters: cc9c bb34 d638 This is in the right range for Korean and there isn't a comma in there at all. All the =?charset?encoding?stuff?= is supposed to be treated as a single symbol so you needn't worry about commas in there anyways. My best guess is that your gui saw some characters that it couldn't figure out how to display and stuck in its own goofie looking From: line. --upas-tbpkcvyxfxurxxngslxpmijjew Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Sun Mar 23 20:49:32 EST 2003 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Sun Mar 23 20:49:29 EST 2003 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.6.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id B6EE5199E4; Sun, 23 Mar 2003 20:49:09 -0500 (EST) Delivered-To: 9fans@cse.psu.edu Received: from garlic.apnic.net (garlic.apnic.net [202.12.29.224]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id CCD96199BB for <9fans@cse.psu.edu>; Sun, 23 Mar 2003 20:48:31 -0500 (EST) Received: (from ggm@localhost) by garlic.apnic.net (8.11.6/8.11.6) id h2O1m7n00737; Mon, 24 Mar 2003 11:48:07 +1000 (EST) From: George Michaelson To: 9fans@cse.psu.edu Message-Id: <20030324114806.78f6cf04.ggm@apnic.net> In-Reply-To: References: <29e8ba954a1cd5ac7b8a9f509008e9da@centurytel.net> Organization: APNIC Pty Ltd X-Mailer: Sylpheed version 0.8.10claws101 (GTK+ 1.2.10; i386--netbsdelf) X-Fruit-Of-The-Month-Club: persimmon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [9fans] UTF-8 handling in non-plan9 app: help finding bug Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Mon, 24 Mar 2003 11:48:06 +1000 Not a plan9 bug, but I'd appreciate debug help. I am UTF-8 illiterate. This From: address appears to render in my gui as From: 'binary meant to be korean', Is this because the UTF-8 decoder has mapped a 16 byte char into ASCII which ends with a comma, and the gui hasn't made this SMTP legal? Some people think From: any crap you like is ok, but From: "other crap" is clearly nicer, since you can probably quote the trailling , equally, the "," may not be there. it might be the UTF-8 decoder or something else is broken. so can one of you RUNIC wizards tell me if this is valid hypotheses? Is this actually a bug their side, sending invalid RFC822/SMTP header? -george From: =?UTF-8?B?7LKc66y07Zi4?= To: "George Michaelson" --upas-tbpkcvyxfxurxxngslxpmijjew--