On Wed, Mar 25, 2009 at 01:02:42AM +1300, Chris Bannister wrote: > On Mon, Mar 16, 2009 at 10:24:47AM -0400, Thomas H. George wrote: > > During bootup (Lenny) the console font changes to a thin, wiry font > > and then changes again to a font with much fatter characters. The final > > font is very readable but when I start mutt the symbols used to indicate > > threading of messages are weird. > > OK, install console-terminus then edit /etc/console-tools/config > > ------ /etc/console-tools/config ----------- > # Turn on numlock by default > #LEDS=+num > APP_CHARSET_MAP=utf8 > APP_CHARSET_MAP_vc1=utf8 > APP_CHARSET_MAP_vc2=utf8 > APP_CHARSET_MAP_vc3=utf8 > APP_CHARSET_MAP_vc4=utf8 > SCREEN_FONT=Uni3-TerminusBold16 > ------ /etc/console-tools/config ----------- > > The lines "# Turn on numlock by default" and "#LEDS=+num" should already > be there at the end of the file. > > Do the threading symbols now show correctly?
No, they have become more complex - i.e. the space between the start of a line and the threading symbol is now filled with capital n's with tilde over them. Previously there was just one N with tilde over it at the start of a line. Initially there was no change after editing /etc/console-tools/config as indicated above though echo $LANG responded en.US.UTF-8. I rebooted again seeing the switch to wiry fonts part way through the bootup. When the bootup was complete the console font looked like what I expect from en.US.UTF-8 but when I ran mutt the threading symbols were double line things and the space was filled with the N's with tilde over them. I ran consolechars -d and the threading switched to single line symbols and no N's with tilde. I'll check the archives as you suggested. > > I think that is all that is needed although you might want to check the > list archives as this problem has arisen in the past and there may be > something I've missed. > > According to /usr/share/doc/mutt/README.Debian: > > l10n support > ~~~~~~~~~~~~ > If you want to see non-ASCII characters on a Debian system, there's no > use fiddling with the variable "charset", as described in the manual > page muttrc(5). > Instead, you'll need to have the Debian package "locales" installed on > your system and set the LANG or LC_CTYPE environment variable. > e.g. US users will want to add "export LC_CTYPE=en_US" to their > ~/.bashrc. > If you have a /etc/locale.gen file read carefully the comment and do > what it says, or it will not work. > No, linux systems do not need --enable-locales-fix or > --without-wc-funcs, > so don't bother me saying these switches cure your problems. > > > BUT > > I haven't done that and it works fine -- see: > chr...@box:~$ echo $LC_CTYPE > > chr...@box:~$ echo $LANG > en_NZ.UTF-8 > > -- > Chris. > ====== > I contend that we are both atheists. I just believe in one fewer god > than you do. When you understand why you dismiss all the other > possible gods, you will understand why I dismiss yours. > -- Stephen F Roberts > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
