public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel utf-8 handling
Date: Sat, 2 Jun 2007 21:53:57 +0200	[thread overview]
Message-ID: <20070602195357.GA430@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.61.0706021246350.21057@yvahk01.tjqt.qr>

    Hi Jan :)

 * Jan Engelhardt <jengelh@linux01.gwdg.de> dixit:
> On Jun 2 2007 09:58, DervishD wrote:
> >
> > * H. Peter Anvin <hpa@zytor.com> dixit:
> >> Jan Engelhardt wrote:
> >> > (1) I can do <Compose><~><n> just fine on vt
> >> > (2) I can do <ö> just fine on vt too
> >> > (3) And copy+paste them both using GPM too, again w/o probs
> >> 
> >> Both of those are in the 0-255 range, though.  I thought the issue was
> >> with characters 256+, like ??.  At least on my FC6 system that doesn't
> >> work with gpm.
> 
> I've got a cp437 "DOS" font loaded[1], and giving a glance at
> /usr/share/kbd/unimaps/cp437.uni tells me right away:
> 
> 	0x01 U+263A
> 
> So I create U+263A in joe (ESC ' x 2 6 3 a), it displays fine (the
> smiley character), and I can copy/paste it using GPM without
> problems. Though, I have that patch[2] in my kernel. Can you check
> if it works if you apply it?

    I cannot reboot my machine right now, and I don't have GPM
installed, but if you give me a few days I think I'll be able to test.
I have to upgrade the kernel too (I'm using 2.6.19.5), so make it a week
O:)) I'll test ASAP.

    And thanks for the patch :))

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

  reply	other threads:[~2007-06-02 19:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 14:20 Kernel utf-8 handling DervishD
2007-06-01 14:30 ` CaT
2007-06-01 14:39   ` DervishD
2007-06-01 15:51 ` Éric Piel
2007-06-02  7:35   ` DervishD
2007-06-01 16:28 ` Alexander E. Patrakov
2007-06-01 16:41   ` Alexander E. Patrakov
2007-06-02  7:45     ` DervishD
2007-06-02 10:52       ` Jan Engelhardt
2007-06-02  7:43   ` DervishD
2007-06-01 19:21 ` Jan Engelhardt
2007-06-01 22:24   ` H. Peter Anvin
2007-06-02  7:58     ` DervishD
2007-06-02 10:51       ` Jan Engelhardt
2007-06-02 19:53         ` DervishD [this message]
2007-06-02  7:53   ` DervishD
2007-06-01 20:49 ` [PATCH] " Jan Engelhardt
2007-06-01 22:17 ` Ken Moffat
2007-06-02  7:51   ` DervishD

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=20070602195357.GA430@DervishD \
    --to=lkml@dervishd.net \
    --cc=hpa@zytor.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.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