From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] utf patch needs work, i think
Date: Thu, 28 May 2009 19:32:56 -0400 [thread overview]
Message-ID: <1243553511-sup-472@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1243539136-sup-9008@ntdws12.chass.utoronto.ca>
Excerpts from Ben Walton's message of Thu May 28 15:32:42 -0400 2009:
>
> 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>
...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
--
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/fc984a86/attachment.bin>
next prev parent reply other threads:[~2009-05-28 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 19:32 Ben Walton
2009-05-28 23:32 ` Ben Walton [this message]
2009-05-31 0:59 ` William Morgan
2009-06-02 14:54 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1243553511-sup-472@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox