Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
On Windows, file comparisons are case insensitive operations. However, a truly case insensitive system would be sensitive to locale settings, and would have to deal with three cases, rather than two (at least, according to Unicode). For various reasons, I’d like to replicate the way Windows does this outside of Windows, if possible.
Does Windows use this kind of locale support, or does it follow a more predictable pattern (e.g. somewhat like C#’s OrdinalIgnoreCase settings)?
As far as I know NTFS supports two modes:
POSIX namespace:
Any UTF-16 code unit (case sensitive) except U+0000 (NUL) and / (slash).
Win32 namespace:
Any UTF-16 code unit (case insensitive) except U+0000 (NUL) / (slash) \ (backslash) and some other characters like
:*"etc.In Win32 mode any program using the Win32-API converts any character of a filename to uppercase (if possible) and uses that name internally.