How to make mutt understand KOI-8
Ignoramus9483
characters. Whatever I have in my current settings, does not work
right, so, if anyone knows how ot fix mutt to display KOI8, let me
know.
i
Rocco Rutte
You need to properly setup your locale first, Google should help.
Rocco
RS Wood
I agree with Rocco. But an interesting question is, "at the console, or
in a graphical session?" The reason I ask is that I've had characters
give me trouble even with the locale set right on a machine where the
console used a font that didn't have those characters available. Just a
thought. I think the first place to Google is within Googlegroups, as
this sort of question has been handled in this newsgroup for as long as
I've been reading it.
Ignoramus14704
I am going to try some things.
Somewhat complicating the issue is that I often use mutt through SSH,
but I will first try to use mutt on a local machine without ssh.
i
Ignoramus14704
I have made some progress.
If I set:
LC_CTYPE="ru_RU.UTF-8"
then my mutt and "less" work perfectly with Russian characters,
meaning display them, and it lets me enter Cyrillic characters in
Subject: and other prompts.
So I think that as far as mutt is concerned, I have resolved the
issue.
However, my another issue, not really mutt related, is that my
favorite editor is xemacs and it does not work with russian characters
in console mode. (xemacs -nw).
Gotta go to xemacs newsgroup, I suppose.
I noticed that "emacs -nw" supports russian with the same settings, so
maybe I will just switch to it.
i
Rocco Rutte
> I agree with Rocco. But an interesting question is, "at the console, or
> in a graphical session?" The reason I ask is that I've had characters
> give me trouble even with the locale set right on a machine where the
> console used a font that didn't have those characters availabl
Yeah, but with a correct locale setup and correctly labeled mail, the
console will do something sane (i.e. display some box or whatever), not
random garbage.
Rocco
Peter Vereshagin
I asked here about utf-8 locale issue and was replied a while ago.
So you can have my suggestion on KOI8-R best with Russian usenet/email for mutt.
At least I was explained here about why can't I set mutt to display 8-bit characters as koi8 by default with UTF-8 locale that I use to prefer now.
This is a must de facto at least for usenet with mutt because ms-outlook is ~90% of newsreaders and it has default setting of 8-bit headers, Subject: at least. And, koi8 is historically a standard ( more about this at http://koi8.pp.ru ) for news and mail, so without base64 or quoted printable encoding the headers will not be diusplayed correctly in your mutt with utf-8 locale.
As for me the only reason I need for koi8 locale is mutt. Well, and unicode-uncapable freebsd syscons(4) console, too. ;-)
2009/07/30 11:30:51 -0500 Ignoramus14704 <ignoram...@NOSPAM.14704.invalid> => comp.mail.mutt:
I> LC_CTYPE="ru_RU.UTF-8"
I> then my mutt and "less" work perfectly with Russian characters,
I> meaning display them, and it lets me enter Cyrillic characters in
I> Subject: and other prompts.
73! Peter
--
http://vereshagin.org
Ignoramus28480
> Concrete jungle, oh Ignoramus14704, you've got to do your best...
>
> I asked here about utf-8 locale issue and was replied a while ago.
> So you can have my suggestion on KOI8-R best with Russian
> usenet/email for mutt. At least I was explained here about why
> can't I set mutt to display 8-bit characters as koi8 by default with
> UTF-8 locale that I use to prefer now.
> This is a must de facto at least for usenet with mutt because
> ms-outlook is ~90% of newsreaders and it has default setting of
> 8-bit headers, Subject: at least. And, koi8 is historically a
> standard ( more about this at http://koi8.pp.ru ) for news and mail,
> so without base64 or quoted printable encoding the headers will not
> be diusplayed correctly in your mutt with utf-8 locale. As for me
> the only reason I need for koi8 locale is mutt. Well, and
> unicode-uncapable freebsd syscons(4) console, too. ;-)
So, what locale environment variables you set to what?
And what mutt settings?
I thought that I was all set with UTF-8, and could send beautiful
Russian emails to myself.
But it turns out that they do not work with gmail.
игорь
Peter Vereshagin
2009/08/03 13:39:20 -0500 Ignoramus28480 <ignoram...@NOSPAM.28480.invalid> => comp.mail.mutt:
I> So, what locale environment variables you set to what?
I> And what mutt settings?
my #muttrc cyrillic setup is:
===
set allow_8bit
set charset=koi8-r
set send_charset=koi8-r
===
environment variable is:
LANG=ru_RU.KOI8-R
koi8 locale can be named differently in Ukraine/etc. and different OS, too, at least on Gentoo I could see ru_RU.koi8-r locale and not sure if it can be aliased with uppercase. Also, not sure about Cygwin, by far it has the only russian locale, the 'ru' and it seems to be the windows-1251. so we still have a place to challenge into. ;-)
I> I thought that I was all set with UTF-8, and could send beautiful
I> Russian emails to myself.
I>
I> But it turns out that they do not work with gmail.
Sure, You should also check for Russian Usenet hierarchies' rules, like those of fido7.*, concerning composed messages' encoding. etc.
Also, the Outlook Express as a standard MUA de facto is a nice example of where you should view the messages snipped from mutt as a test of readability for anyone else. Same about webmails, e. g. gmail: you can rfc2047- or mime- encode the headers or body of outgoing mutt messages to try with them, but not sure about Usenet: by far the slrn can list the messages index with headers in koi8-r while executing under utf-8 locale, but no mutt can do this.
I> О©╫О©╫О©╫О©╫О©╫
Rocco Rutte
> my #muttrc cyrillic setup is:
> ===
> set allow_8bit
> set charset=koi8-r
> set send_charset=koi8-r
> ===
Please do _not_ do that, at least not before reading and understanding:
http://dev.mutt.org/doc/manual.html#charset-handling
(this applies to any mutt version)
Rocco
Peter Vereshagin
Did you mean this?
===
Warning: (...) may make it behave badly with non-ascii input: it will fail at seemingly random places. (...) sent messages may carry wrong character set information the receiver has too deal with. The need to set $charset directly in most cases points at terminal and environment variable setup problems, not Mutt problems.
===
ok, the first problem: I never use the non-ascii input to drive Mutt. I probably could try Cyrillic hotkeys with localized LC_MESSAGES, but I don't localize this part of the system..
The second: care about the receiver side. For my recipients, I should always use the koi8-r no matter if my current locale utf-8 or koi8-r. And, I use to note on the Usenet group if I cannot see 8-bit headers in mutt when in utf-8 locale. Because it is a standard de facto to post 8-bit koi8 headers there.
So mutt probably need no more disclaimers, if that part of the documentation is the one.
2009/08/21 18:48:45 +0000 Rocco Rutte <pd...@gmx.net> => comp.mail.mutt:
RR> * Peter Vereshagin <pe...@vereshagin.org>:
RR>
RR> > my #muttrc cyrillic setup is:
RR> > ===
RR> > set allow_8bit
RR> > set charset=koi8-r
RR> > set send_charset=koi8-r
RR> > ===
RR>
RR> Please do _not_ do that, at least not before reading and understanding:
RR>
RR> http://dev.mutt.org/doc/manual.html#charset-handling
RR>
RR> (this applies to any mutt version)
RR>
RR> Rocco
73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627)
--
http://vereshagin.org