linux-kernel - Re: Kernel utf-8 handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0706012117250.11140@yvahk01.tjqt.qr>
Date:	Fri, 1 Jun 2007 21:21:49 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	DervishD <lkml@...vishd.net>
cc:	Linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Kernel utf-8 handling


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

so not sure where your problem is. 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 :)



	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/