Re: multiple entries in send_charset
Hi Andrei,
On Wednesday, October 15, 2003 at 9:37:39 AM +0200, Andrei A. Voropaev wrote:
> I have to write emails in German. And I want to have "iso-8859-1" as
> charset for those emails. So I tried
> set send_charset="us-ascii:iso-8859-1:koi8-r"
> But it didn't work.
It works. Really. But in a so limited way it fails in practice.
> russian letters occupy the same position as most of special letters
> from western european alphabets
Exactly. And as you use a KOI8-R terminal, this can work only for
common chars. KOI8-R has 128 special chars, Latin-1 has 96, but only 6
are common:
U+00A0 ' ' no-break space
U+00A9 © copyright sign
U+00B0 ° degree sign
U+00B2 ² superscript two
U+00B7 · middle dot
U+00F7 ÷ division sign
If you write only US-Ascii and some of those 6, the mail will be
labelled L1. This might seem insuficient to write German, isn't it?
You have 2 solutions: Use 2 terminals, or use an UTF-8 one.
- 2 terms: Setup another terminal so that it has a L1 charset, and that
when you start it your LC_CTYPE is set to say "de_DE.iso-8859-1". Remove
explicit "set charset=..." from muttrc. Mutt started from this term will
be ready to play nice German. Mutt started from your today K8R term with
ru_RU.KOI8-R locale will continue to play Cyrillic.
- UTF-8 term: Setup everything in UTF-8. Terminal, charset, ru_RU.utf-8
locale, append ":utf-8" to $send_charset, etc... Mutt will show and let
you write simultaneously both charsets, and much more.
Both solutions have their own setup difficulties and drawbacks. Look
at archives here for tips to circumvent some of them. The JA-patch might
help. Mutt -v shows you +HAVE_LANGINFO_CODESET, right? What's the usage
status of ISO-8859-5 charset in Russia?
Bye! Alain.
--
Mutt muttrc tip to send mails in best adapted first necessary and sufficient
charset (version for East Europe Latin-2/CP-852/CP-1250 terminal users):
set
send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:iso-8859-2:windows-1250:utf-8"