From: Tor L. <tm...@ik...> - 2010-09-13 06:30:56
|
> is it too difficult to implement such a feature? Perhaps not, but nobody has felt it important enough to bother? Making utilities like ls display non-ASCII file names correctly would be slightly useful, but it is in no way essential, IMHO. (And I say that as somebody whose native language is not English, and who always uses the local keyboard layout, not en-US one, even if that means accessing keys like \ { [ ] } is behind AltGr.) You should consider what is the intended purpose of MSYS: running configure and other software build scripts, Makefiles etc. And also provide a familiar Unix-style interactive *software development environment*. Mainly, perhaps, for software being ported from Unix, and especially for developing and porting Open Source software to Windows. Do you know many software packages (Open Source or proprietary) that would use non-ASCII source file name? If you are on Windows and handle lots of files with non-ASCII names, you most likely are handling end-user documents, not developing software. Then MSYS is perhaps not the right tool for you. Have you tried Microsoft's SUA (a.k.a. Interix), does it handle non-ASCII file names better? Or Cygwin, I know they did some significant changes for UTF8ification of Cygwin in version 1.7. --tml |