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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0608072003460.3365@yvahk01.tjqt.qr>
Date:	Mon, 7 Aug 2006 20:06:25 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
cc:	"Alexander E. Patrakov" <patrakov@....usu.ru>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] UTF-8 input: composing non-latin1 characters, and
 copy-paste

>
>> argument. This means that only characters present in Latin-1 (i.e., with 
>> codes <256) can be produced by composing while the keyboard is in 
>> Unicode mode. This is certainly unacceptable for Eastern Europe (i.e., 
>> former ISO-8859-2 users) who need to get ^+ Z = Ž.
>
>Its not useful for most of Western europe either nowdays.

As far as I can follow...

I don't think so. I have set my keyboard to US, but I regularly require 
<Compose><"><a> and such to generate Umlauts and Eszet. Now, ä is present 
in ISO-8859-1/15, but what if it were not?


Jan Engelhardt
-- 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ