![]() | |||||||||||||
Messages in this thread |
On Sun, 30 Oct 2005, OGAWA Hirofumi wrote: > Ingo Oeser <ioe-lkml@rameria.de> writes: > >> 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? > > I don't know. Why do we need to care the collation sequences here? > > > Or is the file system always dependend on the locale of the Windows > > version, which created the file system? > > 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...) Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-10-29 18:51 [from the cache] ©2003-2008 | |||||||||||||