From: DervishD <lkml@dervishd.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel utf-8 handling
Date: Sat, 2 Jun 2007 09:53:57 +0200 [thread overview]
Message-ID: <20070602075357.GB20406@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.61.0706012117250.11140@yvahk01.tjqt.qr>
Hi Jan :)
* Jan Engelhardt <jengelh@linux01.gwdg.de> dixit:
> On Jun 1 2007 16:20, DervishD wrote:
> >
> > This said, I know that the console will give me no problems
> >regarding character representantion (heck, I'm pretty sure that I will
> >be able to use even the same font I'm using right now in the console if
> >I get the proper unicode map), but probably will give me problems when
> >*entering* characters. I've read that the kernel handles accented chars,
> >and things like 'ñ' (ntilde) because it assumes that any composed
> >character (composed using dead keys, for example) is in the latin1
> >range. While this is not a perfect behaviour, it will work for me.
>
> (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
Cool! :)))
> so not sure where your problem is.
Right now my only problem was lack of reliable information, but that
has been fully solved by all people who answered, so my next step is to
upgrade kbd and start making tests :))
> I do however have a patch that you could try should a problem arise. I
> should repost and ask around again and beat until it's in :)
Any patch regarding a better support of utf-8 is very welcome, and I
can help you beat anybody if that will make the patch in XD
Thanks a lot for the patch (I'll try it if I face problems) and for
your answer.
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!
next prev parent reply other threads:[~2007-06-02 7: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
2007-06-02 7:53 ` DervishD [this message]
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=20070602075357.GB20406@DervishD \
--to=lkml@dervishd.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.