On Tue, Apr 07, 2009 at 08:42:10PM +1200, Chris Bannister wrote: > On Mon, Apr 06, 2009 at 08:57:26AM -0400, Thomas H. George wrote: > > On Mon, Apr 06, 2009 at 10:42:24PM +1200, Chris Bannister wrote: > > > [Sorry for the late post.] > > > What is the output of: > > > grep -v ^# /etc/console-tools/config > > > > > > BLANK_TIME=30 > > > > > > BLANK_DPMS=off > > > > POWERDOWN_TIME=30 > > > > > > 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-TerninusBold16 > > OK, same here > > > > > > > > > and: > > > locale > > > > > > LANG=en_US.UTF-8 > > LC_CTYPE="en_US.UTF-8" > > LC_NUMERIC="en_US.UTF-8" > > LC_TIME="en_US.UTF-8" > > LC_COLLATE="en_US.UTF-8" > > LC_MONETARY="en_US.UTF-8" > > LC_MESSAGES="en_US.UTF-8" > > LC_PAPER="en_US.UTF-8" > > LC_NAME="en_US.UTF-8" > > LC_ADDRESS="en_US.UTF-8" > > LC_TELEPHONE="en_US.UTF-8" > > LC_MEASUREMENT="en_US.UTF-8" > > LC_IDENTIFICATION="en_US.UTF-8" > > LC_ALL= > > OK, same here > > > > > > > Also if you start mutt like > > > chr...@box:~$ LANG=C mutt > > > > > > You should see the symbols ok? > > > > Nope, still the same old funny symbols. > > That is weird! > > OK, maybe something in your .muttrc is having an effect. > > Start mutt like so: > chr...@box:~$ LANG=C mutt > Once started, type ! > then when you see "Shell command:" type: > echo $LANG > it should display: > C
Ah-ha! The response to echo $LANG is en_US.UTF-8 both before and after I run consolechars -d. But the problem is not just a mutt problem. For example, the response to sensors is acpitz-virtual-0 Adapter: Virtual device temp1: +40.0°C (crit = +75.0°C) k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +23.0°C Core0 Temp: +29.0°C Core1 Temp: +27.0°C Core1 Temp: +18.0°C and I recall that the other day reading a man page I found a very weird character being used for bullets. I'd show you what my mutt output is like but I haven't figured out how to capture it. At any rate I appreciate all your suggestions Chris. Since the problem is not very serious and easily corrected by the consolechars -d command I'll just live with it for now. It is a curiosity and if I ever find out the cause I'll be sure to let you know. Best regards, Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org