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: Mon, 19 Feb 2007 18:03:04 +0100 [thread overview]
Message-ID: <45D9D848.4010608@drzeus.cx> (raw)
In-Reply-To: <87tzxim6ic.fsf@duaron.myhome.or.jp>
OGAWA Hirofumi wrote:
>> I'm experiencing a rather odd behaviour with the character set
>> conversion. If I mount a vfat fs with utf8 and then create a file
>> with invalid utf-8 sequences, the file will briefly exist with these
>> invalid sequences, then quickly convert to a stripped version.
>>
>
> Yes. utf8 support is broken, and it will fail to convert letter case
> on many case. And it's why that is not recommended.
>
>
Is there any ongoing work to fix this? UTF-8 is standard on more or less
every distribution these days.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-02-19 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 15:53 Pierre Ossman
2007-02-19 16:55 ` OGAWA Hirofumi
2007-02-19 17:03 ` Pierre Ossman [this message]
2007-02-19 17:32 ` OGAWA Hirofumi
2007-02-20 6:43 ` Pierre Ossman
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=45D9D848.4010608@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome