Tickets :: Comment on [#3101] Wrong mime-encoding of subject header

* Your Email Address
* Spam protection	Enter the letters below: ._..___.._.. .\ / \| _/ \| \| \| >< _\|_./__._\|_\|/\\|/ \
Comment	> When I write a new mail with umlaut characters in the subject, > sometimes spaces seem to be missing because the subjects seems to be > wrongly encoded. For example with: > > > > Subject: Infos über kIZ für die Nightline > > > > IMP encodes it as: > > > > Subject: Infos =?iso-8859-1?b?/GJlcg==?= kIZ =?iso-8859-1?b?Zvxy?= die > > Nightline > > > > Note that before "Nightline" there is a new-line and a tab. > > > > In RFC2047 it is written: > > > > > > When displaying a particular header field that contains multiple > > 'encoded-word's, any 'linear-white-space' that separates a pair of > > adjacent 'encoded-word's is ignored. (This is to allow the use of > > multiple 'encoded-word's to represent long strings of unencoded text, > > without having to separate 'encoded-word's where spaces occur in the > > unencoded text.) > > > > That is, I think that you need to put the newline between two encoded > words, so that the newline is ignored. Mutt does encode the same > subject like this: > > > > Subject: Infos =?iso-8859-1?Q?=FCber_kIZ_f=FC?= > > =?iso-8859-1?Q?r?= die Nightline > > > > Cheers > > David
Attachment
Watch this ticket