From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: charset2upper broken
Date: Wed, 24 May 2006 10:31:24 +0600 [thread overview]
Message-ID: <e50nie$3ud$1@sea.gmane.org> (raw)
In-Reply-To: <44722ACE.3040500@austin.rr.com>
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.
<troll>
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.
</troll>
--
Alexander E. Patrakov
prev parent reply other threads:[~2006-05-24 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 21:19 charset2upper broken Steve French
2006-05-24 4:31 ` Alexander E. Patrakov [this message]
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='e50nie$3ud$1@sea.gmane.org' \
--to=patrakov@ums.usu.ru \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).