locale problem - what has changed to cause this?

Chris Green <[email protected]> Mon, 13 Mar 2006 09:13:35 +0000
Newsgroups gmane.network.tin.user
Message-ID <[email protected]>
Until a couple of days ago I had my locales working OK, I just had all
the LC_xxx environment variables set to their default value of "C"
except for LC_TYPE set to "en_GB".  This allowed accented characters
to work correctly in mutt and tin.

However something I have done over the weekend has broken this, now
whenever I start tin for example I get the message:-

    Can't set the specified locale!

If I set LC_CTYPE back to the default "C" then the message goes away
so, for some reason, setlocale() cant find then "en_GB" locale.  I've
tried some other locales and I get the same message so I seem to have
lost all of them.

I haven't *really* lost all of them, the locale database is still in
place at /usr/lib/locale.

The most likely candidate for breaking this as far as I can see is
that I upgraded the glibc library to get the latest Bluefish to work.
What I don't know is how to get my locale database working again.

-- 
Chris Green ([email protected])

    "Never ascribe to malice that which can be explained by incompetence."