From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alexander E. Patrakov" Subject: Re: charset2upper broken Date: Wed, 24 May 2006 10:31:24 +0600 Message-ID: References: <44722ACE.3040500@austin.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: To: linux-kernel@vger.kernel.org In-Reply-To: <44722ACE.3040500@austin.rr.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Steve French wrote: > Charset2upper is broken, at least for utf8 (see line 41 of nls_utf8.c) > Seems straightforward to fix it for the key characters a-z (0x61-0x7a), > unless the uppercasing rules are stranger than I think - especially > since other places have it right e.g. nls_base.c seems to have it right > in its charset2upper. Don't use UTF-8. Neither the kernel nor userspace is fully ready. Also, it seems wrong to put such comples thing as a complete UNICODE upper/lower case mapping into the kernel, especially since this mapping is different for Turkish and non-Turkish cases (see http://www.i18nguy.com/unicode/turkish-i18n.html). So someone should convert all filesystems that use character conversion and case mapping to FUSE, so that they can use glibc to do all of this dirty/complex work. -- Alexander E. Patrakov