To me, this is kind of tricky. Our environment contains a client/server architecture that involves using Unix servers to store DB information and executable scripts to transact against that information. However, the Vendor that created the system chose to use a Windows client front end for opperation. The Vendor chose to preserve case sensitiviy for search functionality, IE, if a script named
DO.THIS resides on the server, searching
do.this will yield 0 results.
I find this completely understanble coming from developer's perspective having some Linux/Unix experience. However, from a UX perspective, those that are expected to use this system typically have minimal computer experience with Windows as their only exposure. Needless to say, it's been a challenge trying to explain "why" they can find files using their Windows based search function using either casing but doens't translate very well using this one application. I have accepted the world I live in.
I happen to like the idea of doing the Windows/Unix infrastructure and considering doing something similar for a project we have coming up. I plan on preserving what our vendor has done for the sake of keeping things consistent here. But I if had chance to start from scratch, would the extra effort in translating casing result in a better UX experience, or is it the expected norm that *Nix system will always be case sensitive?