Re: lynx-dev handling broken content-type specification in meta

[David Woolley]

> LS0tIExZQ2hhclV0aWxzLmMtd2FzCVdlZCBNYXkgIDggMjE6MDA6MTkgMjAw
> Mg0KKysrIExZQ2hhclV0aWxzLmMJV2VkIE1heSAgOCAyMTowNjoyMyAyMDAy

Pine strikes again with inappropriate content-transfer-encoding!
(Patches are better in the main body - people reading this with 
non-metamail based email programs probably had to explicitly open
the attachment, as I'd have to do to comment on the plain text.)

I would describe this as a workaround, not a fix.  It's also
the wrong workaround.  Almost certainly what the other browsers
are doing is saying that the document must be some form of HTML,
for them to have recognized META, so just completely ignore the
media type and look for the charset parameter.

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden