[Email-SIG] email.header.decode_header eats my spaces
janssen at parc.com
Tue Mar 27 19:20:31 CEST 2007
> I actually think we should be doing the opposite, namely preserving
> any FWS in the existing text and /not/ substituting continuation_ws
> for it when we re-break the headers. This is the only way to
> maintain idempotency short of saving the original header intact (but
> then memory usage doubles). continuation_ws should be used only when
> we're forced to break at a non-existing FWS location, e.g. if we've
> split a non-ascii header or at a non-whitespace header-specific
> syntactic break. In the case of RFC 2047 headers, the FWS gets
> consumed anyway so it isn't idempotentially (?!) significant.
Barry, this seems correct to me, too.
More information about the Email-SIG