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 chris@areti.co.uk
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.
I can't remember which distribution you use and this is sometimes handled by the setup tools. For debian, "dpkg-reconfigure locales" and then "locale-gen" often helps.
Hope that helps,
On Mon, Mar 13, 2006 at 09:36:44AM +0000, MJ Ray wrote:
Chris Green chris@areti.co.uk
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.
I can't remember which distribution you use and this is sometimes handled by the setup tools. For debian, "dpkg-reconfigure locales" and then "locale-gen" often helps.
I use slackware, I don't have locale-gen.
As far as I understand it if all of the right directories are present under /usr/lib/locale there's nothing to build/generate as such. I suspect that what I've lost is a link somewhere or I have a library which doesn't know where the locales are stored.
On Mon, Mar 13, 2006 at 09:57:05AM +0000, Chris Green wrote:
On Mon, Mar 13, 2006 at 09:36:44AM +0000, MJ Ray wrote:
Chris Green chris@areti.co.uk
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.
I can't remember which distribution you use and this is sometimes handled by the setup tools. For debian, "dpkg-reconfigure locales" and then "locale-gen" often helps.
I use slackware, I don't have locale-gen.
As far as I understand it if all of the right directories are present under /usr/lib/locale there's nothing to build/generate as such. I suspect that what I've lost is a link somewhere or I have a library which doesn't know where the locales are stored.
I've found the problem, I had just upgraded the glibc libraries using the package file glibc-solibs-2.3.6-i486-2.tar. I had assumed (wrongly) that this would work with my existing locale files. What I needed to do was to upgrade the locale information as well by installing glibc-i18n-2.3.6-noarch-2.tgz.
All is well now with no errors from tin.
-
Chris Green -
MJ Ray