In face, the examples _only_ deal with _comments_ in structured fields. Here, you are correct in that the handling is incorrect though:
MIME.decode_words_tokenized_labled_remapped("(=?ISO-8859-1?Q?a?=
b)"); (9) Result: ({ /* 1 element */ ({ /* 2 elements */ "comment", "ab" }) })
Here, the example says that the command should be decoded as "a b", so the result is wrong.
s/face/fact/ s/command/comment/
*sigh*
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2002-12-12 19:02: Subject: incorrect rfc2047 MIME decoding?
In face, the examples _only_ deal with _comments_ in structured fields. Here, you are correct in that the handling is incorrect though:
MIME.decode_words_tokenized_labled_remapped("(=?ISO-8859-1?Q?a?=
b)"); (9) Result: ({ /* 1 element */ ({ /* 2 elements */ "comment", "ab" }) })
Here, the example says that the command should be decoded as "a b", so the result is wrong.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
I have now committed an update to 7.5 which seems to generate the correct results for the comment examples. Feel free to try it out with other inputs.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2002-12-12 19:02: Subject: incorrect rfc2047 MIME decoding?
In face, the examples _only_ deal with _comments_ in structured fields. Here, you are correct in that the handling is incorrect though:
MIME.decode_words_tokenized_labled_remapped("(=?ISO-8859-1?Q?a?=
b)"); (9) Result: ({ /* 1 element */ ({ /* 2 elements */ "comment", "ab" }) })
Here, the example says that the command should be decoded as "a b", so the result is wrong.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
pike-devel@lists.lysator.liu.se
-
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum