From: "Simon Horman [Horms]" <horms@debian.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: 333776@bugs.debian.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bug#333776: linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive
Date: Sat, 29 Oct 2005 12:45:17 +0900 [thread overview]
Message-ID: <20051029034516.GN4961@verge.net.au> (raw)
In-Reply-To: <87zmotvfwj.fsf@devron.myhome.or.jp>
On Sat, Oct 29, 2005 at 12:07:40AM +0900, OGAWA Hirofumi wrote:
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
>
> > Horms <horms@verge.net.au> writes:
> >
> >> static struct nls_table table = {
> >> .charset = "utf8",
> >> .uni2char = uni2char,
> >> .char2uni = char2uni,
> >> .charset2lower = identity, /* no conversion */
> >> .charset2upper = identity,
> >> .owner = THIS_MODULE,
> >> };
> >>
> >> I guess it is charset2lower or charset2upper that vfat is calling,
> >> which make no conversion, thus leading to the problem I outlined above.
> >>
> >> My question is: Is this behaviour correct, or is it a bug?
> >
> > This is known bug. For fixing this bug cleanly, we will need to much
> > change the both of nls and filesystems.
>
> And fatfs has "utf8" option, probably the behavior is preferable than
> "iocharset=utf8". However, unfortunately "utf8" has problem too.
Thanks
next prev parent reply other threads:[~2005-10-29 4:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051013165529.GA2472@tennyson.dodds.net>
[not found] ` <20051014023216.GJ8848@verge.net.au>
[not found] ` <20051015003549.GB11040@tennyson.dodds.net>
2005-10-28 8:22 ` Bug#333776: linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive Horms
2005-10-28 14:54 ` OGAWA Hirofumi
2005-10-28 15:07 ` OGAWA Hirofumi
2005-10-29 3:45 ` Simon Horman [Horms] [this message]
2005-10-29 14:45 ` Ingo Oeser
2005-10-29 16:28 ` OGAWA Hirofumi
2005-10-29 18:44 ` Anton Altaparmakov
2005-10-29 20:07 ` OGAWA Hirofumi
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=20051029034516.GN4961@verge.net.au \
--to=horms@debian.org \
--cc=333776@bugs.debian.org \
--cc=hirofumi@mail.parknet.co.jp \
--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.