[Email-SIG] fixing the current email module
Glenn Linderman
v+python at g.nevcal.com
Fri Oct 9 08:31:32 CEST 2009
On approximately 10/8/2009 8:47 PM, came the following characters from
the keyboard of Tokio Kikuchi:
>>> Actually, as long as the prepended text is ASCII, all that work can be
>>> done on the encoded value. When it is not ASCII, it may still be
>>> separated and recognizable. Still that logic is more complex than
>>> decoding, handling as Unicode, and encoding.... when it works. Just
>>> pointing out that there is more than one way to do things...
>>>
>
> Oh, really?
>
> Base64 is 3 to 4 octets encoding and there is no way to prepend padding.
>
In header values, encoding is done using encoded-words. A header value
consists of a sequence of ASCII words, and encoded-words. While an
encoded word, that uses base64 encoding cannot easily be adjusted to
prepend data into that encoded-word, additional ASCII or encoded-words
can be prepended in front of the other ASCII or encoded words within the
header-value.
So, yes, really!
--
Glenn -- http://nevcal.com/
===========================
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
More information about the Email-SIG
mailing list