Hi, On Friday 28 October 2005 16:54, OGAWA Hirofumi wrote: > Horms <[email protected]> writes: > > 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. Using per locale collation sequences? :-) Do you know, how Windows handles the problem of differing collation sequences on the file system? Or is the file system always dependend on the locale of the Windows version, which created the file system? I'm so happy, that Unix is not case insensitive :-) Regards Ingo Oeser
Attachment:
pgpSeNw6RCyK2.pgp
Description: PGP signature
- Follow-Ups:
- References:
- Prev by Date: Re: [PATCH] toshiba_ohci1394_dmi_table should be __devinitdata, not __devinit
- Next by Date: Re: Intel D945GNT crashes with AGP enabled
- Previous by thread: Re: Bug#333776: linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive
- Next by thread: Re: Bug#333776: linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive
- Index(es):
 |