Kyle, Also, I don't remember trying it through GUI. I am always working through ssh...so I guess the fonts that I have defined in n18i are for GUI based console session, and they don't exist in ssh session.
Best, Paul -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kyle Wheeler Sent: Monday, July 13, 2009 1:14 PM To: [email protected] Subject: Re: Several Mutt usage question -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Monday, July 13 at 12:41 PM, quoth Paul Grinberg: >Thank you, > >so far I removed charset definition, and it started to show this one. So > >Date: Sat, 11 Jul 2009 08:19:23 +0400 >From: п░п╩п╣п╨я│п╟пҐпЄя─ п⌠я─п╦пҐп╠п╣я─пЁ <[email protected]> >Subject: Re: Contacts > >піп╣п╩я┐я▌ Interesting! That shows up as jibberish to me, but we're obviously making some progress. >[pgrinb...@panther ~]$ locale -a | egrep "ru|he" >hebrew >he_IL >he_IL.iso88598 >he_IL.utf8 >ru_RU >ru_RU.iso88595 >ru_RU.koi8r >ru_RU.utf8 >russian >ru_UA >ru_UA.koi8u >ru_UA.utf8 Huh; so your system prefers the "utf8" style, but your LANG uses "UTF-8"? I wonder if the difference is mucking anything up... I'm guessing that your system supports en_US.utf8, right? Try setting LANG to that. >Passed on perl trick.... >[pgrinb...@panther ~]$ perl -e "" That's always a good sign. >Now I am thinking....maybe it lacks fonts? Actually, my next thought (assuming that changing LANG to en_US.utf8 doesn't fix things) is to question your terminal. What are you using? For example, if you use an xterm, for some reason the utf-8 mode is not enabled by default. But they usually provide a wrapper script called "uxterm" that will launch xterm with the proper flags to enable utf-8 mode. That makes it so that your terminal can recognize the characters it is being asked to display and can look for the correct glyph in the font that it's using. If your terminal is set up so that it can recognize the utf-8 characters that mutt is emitting, then after that we'll want to look at your fonts. Here's a way of testing whether your terminal and/or fonts can handle Russian characters: perl -e 'print "\xD0\x91\n"' That should print a single Russian character (I don't know what the name of it is, but it looks like a lowercase b with a flat line across the top). And here's a test for Hebrew: perl -e 'print "\xD7\xAA\n"' That should print out a Tav (I think that's what it's called). If those don't work, then your terminal and/or your font may not be working. If those DO work, but mutt doesn't, then there's probably something wrong with your terminal library (e.g. ncurses) and you'll probably want to ensure that mutt is using ncursesw instead of plain old ncurses (that's the ncurses variant that supports utf-8). ~Kyle - -- Difference of opinion leads to enquiry, and enquiry to truth; and that, I am sure, is the ultimate and sincere object of us both. We both value too much the freedom of opinion sanctioned by our Constitution, not to cherish its exercise even where in opposition to ourselves. -- Thomas Jefferson to P.H. Wendover, 1815 -----BEGIN PGP SIGNATURE----- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKW2tZAAoJECuveozR/AWenyoQAIi4BXzPS8aVFJXBAqIZNA6S Q3WDDHcerhK8Ls/XdUH7YNLq466GGFjCAReoo+Jq9N9B5X7NiqoSEt+Hx7QQSF8Q GyPGOMlNG7lrk2AtMlYct2/mev3F0Clskhe92Ab7G3zaky0PV2HpK2Byx7t9Ru8/ lphbceV6PTQ9R+fQ2p8FnIQwqZtnA+YJ5GZmbMCr2OjtdH+6cxgnWtvKRQRI1gIY hK03J6C9o/BtjTxTeXnSuKdv/jcLZi0xTY18TFY86qJ+zkHI/vzllS22osgWxUWI gJ2o6mdFOJptZtNRk5CxGve6dJG3x3DTKf7nlGwEd/ew4X04bN4RkJg9dCsntjJY fmjz6GfsjjW2hGSVZwKq9PEctc5hDnXiTnBgxGYDyDyTa0a1b6ZaJ2CX9aAGcxlf kn1ABpZvkhFtZ0gSKh/hCfCOiAS/cooKfbmA1TA/Vm+uVYsZvIOr5wmdkhe6D/DM mIe7cT/ih8IGq5EF3qmWRPm00kDnCGLro+hIZwwwzwJ1hDZ0fph4qu04eGP7eWao MTsC+gRxf+dkp6zRxAUSg3MItHBSETKG6xwfLUVhHFdCXHU4qpvViAHox1qRfwG+ /zLFcHxog/YBta7q5VOcslI8u/DaYmW5MIPHzd/pqsxV5PNr3KEqpPNJpnefG5Nk cnKxjf3bVPEfJv0CZCuw =2oMN -----END PGP SIGNATURE-----
