sorry, this one scrolled off the top, and I didn't read it before
sending my other reply.
On approximately 11/6/2008 9:02 AM, came the following characters from
the keyboard of Barry Warsaw:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 6:39 PM, Glenn Linderman
On approximately 11/6/2008 3:59 AM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
> There is no reference to the word emacs or types in any of the messages
> you've posted in this thread, maybe you are referring to ano
On approximately 11/5/2008 11:47 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
> But the API could speak Unicode, and do the appropriate translations.
> Or in some cases, inappropriate translations.
You've written that ki
On approximately 11/5/2008 6:09 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
> On approximately 11/5/2008 2:59 PM, came the following characters from
> the keyboard of Andrew McNamara:
> >> I would find
> >>
On approximately 11/5/2008 4:24 PM, came the following characters from
the keyboard of Andrew McNamara:
But I'm not at all clear on what you mean by a round-trip through the
email module. Let me see... if you are creating an email, you (1)
should encode it properly (2) a round-trip is mostly me
On approximately 11/5/2008 2:59 PM, came the following characters from
the keyboard of Andrew McNamara:
I would find
message[b'Subject'] = b'Hello'
to be totally gross.
While RFC Email is all ASCII, except if 8bit transfer is legal, there
are internal encoding provided that permit the
On approximately 11/5/2008 12:38 PM, came the following characters from
the keyboard of Barry Warsaw:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 30, 2008, at 6:17 PM, Andrew McNamara wrote:
That's a tricker case, but I think it should use bytes internally. One of
the early goals of e
