Subject: [sup-talk] utf patch needs work, i think

From: [email-masked] (Ben Walton)
Date: Thu, 28 May 2009 15:32:42 -0400

I just found something funny with the new utf patch.  The only thing I
noticed in the headers of relevance was:

To:    =?utf-16be?b?/v8AfgA6ACcAJwAgMEIwijBMMGgwRjBUMFYwRDB+MFcA?=
     =?utf-16be?b?MF8wAg==?= <j.chetwynd at btinternet.com>

The displayed mail can be seen here:
http://www.cquest.utoronto.ca/u/bwalton/utf-wtf.png

I'll save the message if it's of any use in debugging the problem (it
was a post to the git list).  There wasn't anything in the body itself
that looked odd to my quick visual inspection.

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090528/eec38321/attachment.bin>

---

From: [email-masked] (Ben Walton)
Date: Thu, 28 May 2009 19:32:56 -0400

>      =?utf-16be?b?MF8wAg==?= <j.chetwynd at btinternet.com>

...a followup on the list makes me wonder if this isn't actually a sup
thing, but a weird encoding 'joke' by the poster.  Even if the body
display wasn't a sup bug, the name is still munged up.

-Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090528/fc984a86/attachment.bin>

---

From: [email-masked] (William Morgan)
Date: Sat, 30 May 2009 17:59:51 -0700

> display wasn't a sup bug, the name is still munged up.

I have the same message. I'll play around with it... I suspect there's
something like a tab or a weird character coming out of the decoding
(which appears to be some non-utf16 text claiming a utf16 big-endian
encoding) that is screwing with Ncurses.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (William Morgan)
Date: Tue, 02 Jun 2009 07:54:23 -0700

Reformatted excerpts from William Morgan's message of 2009-05-30:
> I suspect there's something like a tab or a weird character coming out
> of the decoding (which appears to be some non-utf16 text claiming a
> utf16 big-endian encoding) that is screwing with Ncurses.

I've committed some changes that should remove invalid characters
for your encoding before display. I think this should help. Also
various display tweaks to account for multibyte characters. I still
see some inconsistencies but I think it's getting better.

That message renders "fine" for me now. (A bunch of nonsense Chinese
characters mixed with some boxes.) I'm using utf8 in a gnome-terminal.
-- 
William <wmorgan-sup at masanjin.net>