Re: Racy NLS behaviour in FAT (and possible other fs)

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Racy NLS behaviour in FAT (and possible other fs)
  - From: OGAWA Hirofumi <[email protected]>

References:
- Racy NLS behaviour in FAT (and possible other fs)
  - From: Pierre Ossman <[email protected]>
- Re: Racy NLS behaviour in FAT (and possible other fs)
  - From: OGAWA Hirofumi <[email protected]>

Prev by Date: Bugreport: SATA Problem: port is slow to respond
Next by Date: Re: [PATCH] Block layer: separate out queue-oriented ioctls
Previous by thread: Re: Racy NLS behaviour in FAT (and possible other fs)
Next by thread: Re: Racy NLS behaviour in FAT (and possible other fs)
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]