Re: Bug#333776: linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive

[OGAWA Hirofumi]

Anton Altaparmakov <aia21@xxxxxxxxx> writes:

>> Probably, yes. I think we need to know on-disk filename's code set.
>
> If FAT stores the filenames in 8 bits (non-UTF) then yes, it will be in 
> the current locale/code page of the Windows system writing them (e.g. that 
> happens with the names of EAs in NTFS).
>
> If the names are stored in 16-bit Unicode like on NTFS then obviously they 
> are completely locale/code page independent.  (Makes my life in NTFS a 
> _lot_ easier.  Especially since the NTFS volume contains an upcase table 
> for the full 16-bit Unicode which we load and use to do upcasing for the 
> case insensitive comparisons...)

Yes, I got to know it from fs/ntfs/*. :)  Unfortunately, FAT stores
8/16bits codeset filename always. (Unicode (UCS2?) is stored in only
case of longname.)

Thanks.
-- 
OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/