On Thursday 5 November 2020 09:49:44 CET, Gero Treuner wrote:
* I interpret RFC2047 that separating encoded blocks by space (without newline) means two words, so space should be displayed to the user as-is (Mutt doesn't display the space, but this probably is a different story)
Mutt is right and you misunderstand. See RFC 2047 page 10, first sentence, and the surrounding text.
This rule seems strange at first, but makes sense when you remember that some languages use very long sequences of nonwhitespace, while RFC822 (like its successors) does not permit much more than seventy sequential nonwhitespace characters in a header field. Somehow, the encoded form of a string in such a language has to contain ignorable white space.
Arnt
