Re: problem with Mime headers

[Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, May  5 at 01:32 PM, quoth Christoph Kukulies:
> During searching for a way to pretty print my Emails from mutt I found, 
> that all messages (or at least the message under concern)
> are stored from ISO-8859-1 to quoted-printable.

I don't understand... you mean they're *converted* into 
quoted-printable from ISO-8859-1?

> I tried various converters, especially "recode" and recode is 
> complaing about some ungueltige Eingabe in data. (when I type =FC 
> into stdin, recode behaves brave and issues an u-umlaut), so it's 
> not the needs getting used to command line syntax of "recode".

I'm pretty sure recode is not what you want.

My *guess* is that you have unset $print_decode, so mutt is passing 
raw message data to your $print_command. If you set $print_decode, 
mutt should convert all output into $charset as it gets passed to 
$print_command.

> My questions are:
>
> \1 What mechanism causes mutt to produce a quoted printable encoded copy 
> of the message, when I save the file?

None.

Let me clarify: when you save a copy of a message somewhere, mutt 
leaves it AS IS (unless you use something like <decode-save>). So if 
the message was encoded with quoted-printable to begin with, it will 
stay that way.

> \2 When I view the message in mutt, umlauts are shown as two byte 
> characters, e.g. an u-umlaut is represented as \374.
>    Would be nice, mutt would do that right away with the correct 
> character set. Only when invoking the editor (vi) to
>   write a reply, the characters are shown correctly.

Technically, that's not a question. ;)

But if mutt is displaying umlauts as byte-codes (e.g. \374) instead of 
as an umlaut or even as a masked unprintable character (displayed as a 
question mark), then your charset environment is incorrectly 
configured.

Let me guess, you set $charset manually, don't you. (Hint: that's 
almost always the wrong thing to do, for lots of reasons.)

Step 1: stop setting $charset
Step 2: set up your LANG environment variable correctly
Possible Step 3: correctly configure your terminal

~Kyle
- -- 
I think we ought always to entertain our opinions with some measure of 
doubt. I shouldn't wish people dogmatically to believe any philosophy, 
not even mine.
                                                    -- Bertrand Russell
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iEYEARECAAYFAkoAVQwACgkQBkIOoMqOI14LxACgw/qx8gVs3NDg8276Y2EUXom6
Mz0AmQEVnCdDTDoefCbXHNWUPbzcHLvn
=dg0V
-----END PGP SIGNATURE-----