public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Florian v. Savigny" <lorian@fsavigny.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel update messed up console encoding
Date: Sat, 28 Feb 2009 11:34:35 +0100	[thread overview]
Message-ID: <0ML21M-1LdMWh49My-00067l@mrelayeu.kundenserver.de> (raw)
In-Reply-To: <20090227210537.GA10044@marvin.heimnetz.local> (message from Sebastian Günther on Fri, 27 Feb 2009 22:05:37 +0100)



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




  reply	other threads:[~2009-02-28 10:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 17:29 [gentoo-user] Kernel update messed up console encoding Florian v. Savigny
2009-02-27 21:05 ` Sebastian Günther
2009-02-28 10:34   ` Florian v. Savigny [this message]
2009-02-28 11:34     ` Eray Aslan
2009-02-28 14:26     ` Sebastian Günther
2009-02-28 17:38       ` Florian v. Savigny
2009-02-28 18:48         ` Sebastian Günther
2009-03-01  9:36           ` Florian v. Savigny
2009-03-01 10:30             ` [gentoo-user] " Nikos Chantziaras
2009-03-01 12:25               ` Florian v. Savigny
2009-03-01 12:48                 ` Nikos Chantziaras
2009-03-02  1:01                   ` Florian v. Savigny
2009-03-02 11:29                     ` Nikos Chantziaras
2009-03-02 12:51                       ` Florian v. Savigny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ML21M-1LdMWh49My-00067l@mrelayeu.kundenserver.de \
    --to=lorian@fsavigny.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox