Re: [9fans] UTF-8 handling in non-plan9 app: help finding bug

[David Presotto <presotto@closedmind.org>]

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

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.

[-- Attachment #2: Type: message/rfc822, Size: 2521 bytes --]

From: George Michaelson <ggm@apnic.net>
To: 9fans@cse.psu.edu
Subject: [9fans] UTF-8 handling in non-plan9 app: help finding bug
Date: Mon, 24 Mar 2003 11:48:06 +1000
Message-ID: <20030324114806.78f6cf04.ggm@apnic.net>


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', <user@dom.ain>

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 <real@dom.ain> is ok, but 
From: "other crap" <real@dom> 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?= <cmh@nic.or.kr>
	To:      "George Michaelson" <ggm@apnic.net>