On 26 Jul 2002 20:41, jennyw wrote:
> of mutt. Also, how did you figure out the real name of the charsets?
> There's no way I would have guessed that US-ASCII was really CP1251.
Oh sorry, forgot about this part. us-ascii has nothing to do with
cp1251. But because in cp1251 the latin letters ar
On 26 Jul 2002 20:41, jennyw wrote:
> I also have /usr/share/i18n/charmaps/CP1251.gz. However, when I use your
> hooks, I still get the =?us-ascii ... I'm using Debian 3.0, by the way.
The snip from my .muttrc was thought as an example only, because cp1251
refers to cyrillic encoding and my lo
On 26 Jul 2002 21:22, Velko Hristov wrote:
> But, sorry, I don't know what you have to do in order to get it work.
> Probably you should check if this encoding is installed on your system
> and if so - try setting charset=us-ascii in your .muttrc. Only guessing,
> any
so-8859-1:utf-8"
which should be overwritten by the hook. Obviously mutt 1.4 knows that
iso-8859-1 is the wrong guess and doesn't want to apply it.
Actually I still *can* set the wrong encoding by hand, but cannot let
mutt do it for me automatically.
Greetings - Velko
-- informal
Hello,
in my .muttrc file I have the lines:
set charset=windows-1251
set send_charset="us-ascii:windows-1251:iso-8859-1:utf-8"
and the hook:
send-hook kristina 'set send_charset="iso-8859-1"'
which I need for sending windows-1251 encoded mails, pretending
they are iso-8859-1 encoded (work-arou