Re: How to prevent recoding of attachments?
Hi Kyle,
Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx> wrote:
> On Thursday, October 9 at 02:27 PM, quoth Jörg Sommer:
>> when sending LaTeX files or translations of program strings mutt
>> recodes them and breaks them. How can I prevent mutt sends the
>> attachment with a different encoding as the local? In the LaTeX file
>> I define the encoding of the file as option of the package inputenc.
>> If I say utf8 there, mutt can't tell the recipient of the mail the
>> file is encoded in latin1 or something else.
>
> The fundamental problem is that text attachments get labeled with a
> character set, and mutt has to make sure that this label is correct.
> Your solution for po files solves this problem by tricking mutt into
> believing that it's not actually a text file.
>
> Mutt *can* attempt to guess what character set text file attachments
> are in, using the $attach_charset setting. Here's the snippet from the
> manual:
>
> attach_charset
> Type: string
> Default: ""
>
> This variable is a colon-separated list of character encoding
> schemes for text file attachments. If unset, the value of
> $charset will be used instead. For example, the following
> configuration would work for Japanese text handling:
>
> set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
I've set this variable to us-ascii:utf-8, but Mutt still uses iso-8859-1.
I thought I can force mutt to encode every non‐ascii attachment in utf-8,
but it's not so. Did I something wrong? What can I do else?
Bye, Jörg.
--
Der Wille und nicht die Gabe macht den Geber.