|To:||"Nicholas Miell" <nmiell@xxxxxxxxxxx>|
|Subject:||Re: RFC: Case-insensitive support for XFS|
|From:||"Barry Naujok" <bnaujok@xxxxxxx>|
|Date:||Mon, 08 Oct 2007 17:00:58 +1000|
|Cc:||"Christoph Hellwig" <hch@xxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, urban@xxxxxxxxxxxxxx|
|References:||<op.ty6361ut3jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <op.tzpbqspl3jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20071005154442.GA6432@xxxxxxxxxxxxx> <1191610338.2695.8.camel@entropy> <op.tzu4jagf3jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1191822288.2694.10.camel@entropy>|
|User-agent:||Opera Mail/9.10 (Win32)|
On Mon, 08 Oct 2007 15:44:48 +1000, Nicholas Miell <nmiell@xxxxxxxxxxx>
You also have to decide whether to screw over people who speak Turkic languages and expect an 'I' to 'ı' mapping or everybody else who expect an 'I' to 'i' mapping.
I suspect they would be used to the false case-insensitive match. I tested it on Windows XP with NTFS: İ (U+0130) did not match I or i or ı (U+0131). I also tested it with the Turkish language/keyboard set. Once it's set in a filesystem, the handling of it can't really be swapped back and forth either, otherwise, you may lose access to that file. There is no practical way that I can see of supporting this fully, even with using the NLS tables. The on-disk hashes have to remain consistent regardless of what language is specified. Barry.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||PARTIAL TAKE 971186 - fix 32-bit compat ioctls for GETXFLAGS, SETXFLAGS, GETVERSION, Lachlan McIlroy|
|Next by Date:||TAKE 971597 - fsck.xfs doesn't verify that the device exists, Barry Naujok|
|Previous by Thread:||Re: RFC: Case-insensitive support for XFS, Barry Naujok|
|Next by Thread:||Re: RFC: Case-insensitive support for XFS, Barry Naujok|
|Indexes:||[Date] [Thread] [Top] [All Lists]|