From: "Florian v. Savigny" <lorian@fsavigny.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel update messed up console encoding
Date: Sun, 01 Mar 2009 10:36:19 +0100 [thread overview]
Message-ID: <0ML21M-1Ldi5r2mAw-00066S@mrelayeu.kundenserver.de> (raw)
In-Reply-To: <20090228184805.GA7841@marvin.heimnetz.local> (message from Sebastian Günther on Sat, 28 Feb 2009 19:48:05 +0100)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
Hi Sebastian,
> That is a problem of the consolefont, since the console can't display it
> with cp1250...
Maybe - if this font has codepage 1250, as one would assume, it should
normally display a capital A with a short accent (I think that's a
slavonic letter) in position hex c3. True, that is different from the
capital A tilde it should have in iso-8859-1. But this is hardly the
heart of the matter- the c3 shouldn't be there in the first place.
> echo "äöüÄÖÜß" > console.test
> then write the same in emacs and save as emacs.test.
>
> And then compare the output of
>
> file console.test
> and
> file emace.test
>
> If there are differences, somewhere here lies the Problem
But I have already described the result of the first procedure in my
first posting (UTF-8 when echoed under the new kernel, iso-8859-1 when
echoed under the old kernel) and the result of the second one - IN
DETAIL - in my last posting (too long to repeat; see there), which I
assume you have read. Have I missed something?
> locale
> should shown it to you
Thanks. $LANG and $LC_ALL are not set (i.e. locale simply shows
"LANG=" and "LC_ALL=" with no values). All other LC_... variables are
set to "POSIX".
> > Does nobody know where the kernel controls what the keys of the
> > console keyboard send when pressed?
> >
> > (BTW, KEYMAP="de-latin1-nodeadkeys", in /etc/conf.d/keymaps.)
>
> Exactly there.
Could you explain that, please (do you perhaps mean "this is where the
kernel's behaviour IS CONTROLLED")? As I have repeatedly said, all
variable settings are of course the same under both kernels, so both
definitely behave differently with the same settings.
Regards,
Florian
PS: Just one thing: do you think you could cite only those portions of
postings that you are replying to? Having to wade through tons of
cited material to find any replies is quite hard on the eyes,
especially when understanding one another seems to be difficult.
next prev parent reply other threads:[~2009-03-01 9:36 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
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 [this message]
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-1Ldi5r2mAw-00066S@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