Steve Langasek writes: > On Mon, Apr 06, 2009 at 05:33:35PM +0000, Thorsten Glaser wrote:
>> If you need a specific locale (as seems from "mksh", not >> sure if it is a bug in that program), you need to set it. >> >> You can only set a locale on a glibc-based system if it's >> installed beforehand, which root needs to do. This is of course a horrid bug. I'm fighting it right now. I install a zam.mo file, nothing else, and I damn well expect that file to get used for messages! Obviously, it's UTF-8. Obviously, I expect towupper() to follow Unicode defaults. > You can build-depend on the locales package and generate the locales > you want locally, using LOCPATH to reference them. There's no need > for Debian to guarantee the presence of a particular locale ahead of > time - particularly one that isn't actually useful to end users, > as C.UTF-8 would be. Unless plain "C" goes UTF-8, that's exactly the locale I need. The stupid broken en_US.UTF-8 fucks up the sort order. Granted, fixing en_US.UTF-8 would be sweet, but it may be far too late. We really need a do-nothing locale that follows the Unicode spec using the UTF-8 encoding. We could also use a do-nothing locale that follows the Unicode spec using the Latin-1 encoding. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
