Re: mail back to UTF-8 before save to HD

[Emanuel Berg <embe8573@student.uu.se>]

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

Teemu Likonen <tlikonen@iki.fi> writes:

> But if you always want UTF-8 charset and 8bit
> content transfer encoding

Are there any drawbacks to that?

> (setq mm-body-charset-encoding-alist '((utf-8 . 8bit))
> mm-coding-system-priorities '(utf-8))
>
> (add-to-list 'mm-content-transfer-encoding-defaults
> '("text/.*" 8bit))

I already did try all combinations with
`mm-content-transfer-encoding-defaulst' to no avail.

Setting `mm-coding-system-priorities' doesn't seem to
influence either, at least not with

    (setq mm-body-charset-encoding-alist '((utf-8 . 8bit)))

- however that (almost) did it.

file -i says:

    message/rfc822; charset=utf-8

and the headers are now:

    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: 8bit

Only the Subject is now =?utf-8?B?w6XDpMO2IMOFw4TDlg==?
for "åäö ÅÄÖ" - and there is no
"mm-SUBJECT-charset-encoding-alist"...

And, with `gnus-summary-show-article' and one C-u, it
looks like this:

    ¥¤¶ …„–

-- 
underground experts united
http://user.it.uu.se/~embe8573