[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: case-insensitive file extensions

From: Richard Frith-Macdonald
Subject: Fwd: case-insensitive file extensions
Date: Sun, 13 Apr 2003 15:02:34 +0100

Begin forwarded message:

From: address@hidden
Date: Sun Apr 13, 2003  1:17:11  pm Europe/London
To: Richard Frith-Macdonald <address@hidden>
Subject: Re: case-insensitive file extensions

OK, thanks for explaining that. it all makes lots of sense then, and the gnustep port should be altered. One more comment. If extensions are case insesitive, and the workspace app will say I can open a ZIP file, then when I get an NSOpenPanel and ask it to only list .zip files, shouldn't it list .zip and .ZIP. For the sake of consistency?
Richard Frith-Macdonald writes:
On Sunday, April 13, 2003, at 05:35  am, address@hidden wrote:
Thanks for the reply. It seems like a reasonable solution. But you miay be interested to know that some variety of openstep out there, may have done it differently. I came up with the question while working on the GNUstep port of OpenUp. OpenUp treats all of the extensions it deals with as case sensative. As a result, double clicking on that .ZIP file, that looks just like it should work, doesn't get you anywhere. I don't know if this was a bug OpenUp had on other systems, or if other systems dealt with file extensions differently.
That's a behavior change ... MacOS-X uses case-insensitive extensions and GNUstep currently does the same ... it uses the MacOS-X style NSTypes info in Info.plist. OPENSTEP uses NSExtensions (which listed case sensitive extensions). Actually, I prefer the case sensitive behavior ... but you can see why people want case-insensitivity on MacOS and Windoze, where people expect that behavior. I'm not sure *what* GNUstep should do about Info.plist support. We followed a lot of MacOS-X changes, but now Apple has changed all the keys in the plist again. Probably we should stick to our own versions.

What do people think we should do about this?

Personally I dislike the case insensitive behaviors ... but Rob is obviously correct to point out the inconsistency between the current case-insensitive behavior in mapping filename extensions to the applications used to open them, and the case sensitive behavior of things like NSOpenPanel.

I'd quite like to go back to the NeXTstep behavior of having case sensitivity throughout.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]