Re: rfc2047 decoding

["Bjørn Mork" <bjorn@mork.no>]

asjo@koldfront.dk (Adam Sjøgren) writes:

> What is the correct decoding of this header:
>
> Subject: =?UTF-8?Q?Hackerangreb=20mod=20it=2Dl?=
>  =?UTF-8?Q?everand=C3=B8r=20bag=20app=20ti?= =?UTF-8?Q?l=20DSB?='
>  =?UTF-8?Q?s=20gr=C3=A6nsekontrol?=
>
> Is it:
>
>  "Hackerangreb mod it-leverandør bag app til DSB' s grænsekontrol" - or:
>  "Hackerangreb mod it-leverandør bag app til DSB's grænsekontrol" ?
>
> Gnus decodes it to the first line. So I'm inclined to think that is
> correct.
>
> Perl's Encode::MIME::Header decodes it to the second line. But it also
> encoded the text in the first place, so I guess it {s,w}ould roundtrip.
>
> What gives?

The "=?UTF-8?Q?l=20DSB?='" part of the header is invalid:

    Ordinary ASCII text and 'encoded-word's may appear together in the
    same header field.  However, an 'encoded-word' that appears in a
    header field defined as '*text' MUST be separated from any adjacent
    'encoded-word' or 'text' by 'linear-white-space'.


So the formally correct decoding would be:

  "Hackerangreb mod it-leverandør bag app ti=?UTF-8?Q?l=20DSB?='s grænsekontrol"

But I believe both your examples are more reasonable attempts in the
spirit of rfc1123.


Bjørn