From: Pierre Ossman <drzeus-list@drzeus.cx>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Racy NLS behaviour in FAT (and possible other fs)
Date: Tue, 20 Feb 2007 07:43:04 +0100 [thread overview]
Message-ID: <45DA9878.2040108@drzeus.cx> (raw)
In-Reply-To: <87ps86m4to.fsf@duaron.myhome.or.jp>
OGAWA Hirofumi wrote:
> Yes. But sorry, I don't have any plan and time to fix it now.
>
I know the feeling. :)
I just wanted to know where things stand as I have little insight into
vfat development.
> If you are using "iocharset=utf8" now, "codepage=cp???,iocharset=xxx,utf8"
> might help a bit.
>
These tests was with the "utf8" option.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
prev parent reply other threads:[~2007-02-20 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 15:53 Racy NLS behaviour in FAT (and possible other fs) Pierre Ossman
2007-02-19 16:55 ` OGAWA Hirofumi
2007-02-19 17:03 ` Pierre Ossman
2007-02-19 17:32 ` OGAWA Hirofumi
2007-02-20 6:43 ` Pierre Ossman [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=45DA9878.2040108@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--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.