Re: Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
- From: Ian Rawlings <news05@xxxxxxxxxxxxx>
- Date: Wed, 21 Dec 2005 10:01:57 +0000
On 2005-12-21, Nix <nix-razor-pit@xxxxxxxxxxxxx> wrote:
> You'd need to solve the locale-definition problem yourself, then, if
> you wanted locales to work at all.
Machine maintenance is a lot easier with distros which is the main
reason I stick with them, although I did use to build my linux boxes
with the bare minimum required which made maintenance easy but took a
while to add new packages, only to often find that they were pants
anyway and then have to remove all the crap they'd added. I used to
use the configure scripts on most of them to put everything pertinent
to an application into /usr/local/apps/<app name>-<app version> which
helped. I still do that for those non-system apps that don't have a
ready-made package.
> I'd guess your glibc post-install script failed to do that on
> your last glibc upgrade, for some reason.
Sommat like that, but whatever it was, I didn't spot it with my md5sum
checks, so it must have been something in directories other than the
en_GB directories/files in /usr/lib/locale, /usr/share/locale and
/usr/share/i18n. It was odd though that they all matched with the
working machine but the locale was still fubarred but then it should
be obvious by now that I don't know much about the locale system.
--
Blast off and strike the evil Bydo empire!
.
- Follow-Ups:
- References:
- Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
- From: Ian Rawlings
- Re: Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
- From: Ian Rawlings
- Re: Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
- From: Nix
- Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
- Prev by Date: Re: Emacs pound sign in non-windowed mode?
- Next by Date: Re: External RAID problems - suggestions please?
- Previous by thread: Re: Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
- Next by thread: Re: Locales: en_GB.iso8859-1 has LC_COLLATE=UTF-8
- Index(es):