RFC-2047 & encoded QP text

[Matthias Andree]

Boris 'pi' Piwinger <3.14 at logic.univie.ac.at> writes:

> Matthias Andree <matthias.andree at gmx.de> wrote:
>
>>>>> Regarding spaces, if necessary we could try something like "[^\t\r\n\?]"
>>>>> and see what happens.  Let's wait until there's a clear need.
>>>
>>> No, there MUST NOT be any non-ASCII-character.
>>
>>"Outlook bug compatibility" in presentation, without putting the system
>>integrity at stake, is more important than strict compliance.
>
> I don't see NON-ASCII in encoded words. And I don't see such
> a bug in Outlook or Outlook Express.

Whoops, your clue stick just hit me. OK, we should list the allowed
characters instead and see how that goes.

-- 
Matthias Andree