On Fri, 1 Jan 2010 01:56:15 -0500, P S wrote:
>On Fri, Jan 1, 2010 at 12:33 AM, Paul Gilmartin wrote:
>
>> Which is why I suggested keeping all alphabetic characters in a single
>> case, followed by a bitmap identifying the case of the characters.
>> Case-insensitive lookup would ignore the bitmap; case sensitive would
>> consider it.
>
>OK, but that's implementation. From a usage standpoint, I'm still unclear
>what you'd want changed in how Windows works. Or did I miss it?
>
I said earlier in the thread:
On Thu, 31 Dec 2009 15:23:18 -0600, Paul Gilmartin wrote:
>
>I wasn't proposing a different specification; ...
I said earlier in the thread:
On Thu, 31 Dec 2009 15:23:18 -0600, Paul Gilmartin wrote:
>
>I wasn't proposing a different specification; ...
>
I care little what NTFS does (I avoid Windows as much as possible).
However, when I mount a Samba share from a UNIX host and some
directory there contains "foobar", "FooBar", "foo,bar", etc.,
Explorer should display those names as faithfully as possible as
they would appear on the host platform, and clicking on each should
open the respective different file. Similarly, in CMD.EXE, the
commands (guessing):
type "foobar"
type "FooBar"
type "foo,bar"
should type the content of the respective file.
The implementation principle is simple: the API/GUI/CLI should
perform no transformation of the filename string, but pass it
unmodified to the filesystem (in this case, Samba client) which
should validate and resolve it.
Same should apply in z/OS.
.. gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
