Thorsten Glaser <[email protected]> writes:
> This is true, but the encoder API must normally, if it requires the
> name of the header to *not* be part of the to-be-encoded string, have
> a provision for the caller to provide the length of it (PHP’s does,
> you can have the header name inline or separate passing its length).
Ah, yes, good point.
> AIUI, the encode('MIME-Q', …) API doesn’t, so it must cope with
> the leading header field (actually, it must *require* it).
Yeah, I think you've convinced me that the correct fix would be to
document that the encoding interface has to be given the entire RFC 5322
header field (and then fix it to do the right thing in that case), given
the line length limits.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
