> 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. Bill _______________________________________________ Email-SIG mailing list [email protected] Your options: http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com
