The examples you refer to are for structured fields, not text fields. Thus, it is MIME.decode_words_tokenized_remapped() you should compare them against.
Pike v7.4 release 4 running Hilfe v3.5 (Incremental Pike Frontend)
MIME.decode_words_tokenized_remapped("=?ISO-8859-1?Q?a?= b c =?ISO-8859-1?Q?d?=");
(1) Result: ({ /* 4 elements */ "a", "b", "c", "d" })
Here, you get four separate tokens, just like the spec says.
For text fields, the example section say that "the rules are slightly different", but give no relevant examples. Can you find a better reference that claims your variant is correct for text fields?
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2002-12-12 18:34: Subject: incorrect rfc2047 MIME decoding?
It looks like MIME.decode_words_text_remapped eats spaces in places it shouldn't:
MIME.decode_words_text_remapped("=?ISO-8859-1?Q?a?= b c =?ISO-8859-1?Q?d?=");
(17) Result: "ab cd"
The result should have been "a b c d". Whitespace is only supposed to be removed between adjacent encoded-words (section 6.2).
Maybe the samples from rfc2047 should be added to the MIME testsuite?
/ Brevbäraren