From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LdMWl-000212-3u for garchives@archives.gentoo.org; Sat, 28 Feb 2009 10:34:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 41D4AE03E3; Sat, 28 Feb 2009 10:34:37 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by pigeon.gentoo.org (Postfix) with ESMTP id F35BFE03E3 for ; Sat, 28 Feb 2009 10:34:36 +0000 (UTC) Received: from bertrandrussell.teuto37.teuto.37.de (dslb-088-078-031-216.pools.arcor-ip.net [88.78.31.216]) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis) id 0ML21M-1LdMWh49My-00067l; Sat, 28 Feb 2009 11:34:36 +0100 From: "Florian v. Savigny" To: gentoo-user@lists.gentoo.org In-reply-to: <20090227210537.GA10044@marvin.heimnetz.local> (message from Sebastian =?iso-8859-1?Q?G=FCnther?= on Fri, 27 Feb 2009 22:05:37 +0100) Subject: Re: [gentoo-user] Kernel update messed up console encoding References: <0MKv1o-1Ld6WW1EfT-000DMF@mrelayeu.kundenserver.de> <20090227210537.GA10044@marvin.heimnetz.local> Message-Id: <0ML21M-1LdMWh49My-00067l@mrelayeu.kundenserver.de> Date: Sat, 28 Feb 2009 11:34:35 +0100 X-Provags-ID: V01U2FsdGVkX19j5oqhIWwM9jdXfcAlpI7POPR/bNILgZ71Unc UjFx9/foSKthDvXWdJK74Cf+XqaNkSHe7j24znY2z0E3mHomIK WGXymc0lFxpVQ34TsGh5w== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Archives-Salt: 0fbd87a7-47ba-450a-846f-37c513cc879a X-Archives-Hash: 2493de393694c2744f4b14a48f504fbe Dear Sebastian, thank you for your thoughts. I am afraid switching to UTF-8 for everything, although I see that this is the sound thing to do eventually, is not currently an option for me - there are far too many things which depend on that. (Also, it would tend to obscure or complicate the problem rather than fix it, since Emacs obviously gets confused by the console behaviour). > there still is /etc/conf.d/consolefont that could mess up things The only variable that's set there is CONSOLEFONT="cp1250". I would not understand how the font could have an influence on the characters *produced* by the console, and it seems also difficult to explain why the shell and Emacs, which of course use the same console font, behave differently. (Under the shell, it looks fine while you type it, i.e. you cannot tell that your u umlaut actually consists of two bytes. But Emacs displays the lower-case umlauts followed by a space (i.e. two characters, but not those that most of us are probably quite familiar with, i.e. which you see when UTF-8 is displayed as if it were ASCII), while for upper-case umlauts and the eszett complains that e.g. "\204 is undefined".) It definitely looks to me as if the core of the problem is what the console produces, not what it shows, i.e. what a keypress produces. The variable CONSOLETRANSLATION is commented out, meaning I am using the "default one", whichever that is. As to the locale, where can I look that up ... ? I seem to remember I purposely use no locale (or "C", I think), but I don't remember where I set that. CONFIG_NLS_DEFAULT is indeed different for the two kernels, but not in a way that seems to explain anything, as those two encodings differ only on a few positions (not umlauts or eszett): linux-2.6.17-gentoo-r7: "iso8859-15" linux-2.6.27-gentoo-r8: "iso8859-1" Also, I think what I said last time holds: that only applies to filenames in the filesystem, doesn't it? I'll follow your suggestion and re-post the problem on gentoo-user-de, although I think running into that sort of problem might happen to anybody who uses a European language other than English (one of those covered by iso-8859-1, more precisely), so comments here are still welcome! But who still sometimes uses the console, except me? I think I'll also write a small script that compares the settings in the two kernel .configs systematically. Could also be of use for later kernel updates ... Thanks very much! Florian