Re: Mac OS X 10.1 File Name Extension Guidelines (solution?)
Re: Mac OS X 10.1 File Name Extension Guidelines (solution?)
- Subject: Re: Mac OS X 10.1 File Name Extension Guidelines (solution?)
- From: "Neal A. Crocker" <email@hidden>
- Date: Sun, 9 Sep 2001 00:36:54 -0700
Suppose files of a certain type encode information in printable
characters but are not normally treated as text files. If some
savvy individual knows how the info is encoded in this type of file
and wants to use a text editor (not "word processor") such as
BBEdit to alter the contents of the file, they may find themselves
forbidden to save the file using its original extension (which, as
far as they are concerned, is still appropriate). If I read
correctly, they can set the desired file extension manually in
Finder, although they may have to deal with warnings about changing
the extension inappropriately. However, this would probably not be
sufficient to salve their frustration at not being able to save the
text they just edited with a file extension the they KNOW is
appropriate.
What if doing something like option-clicking the save button (or
some other consistent method in all save panels) just saved the file
as you typed it, correct extension or not. Those users with the
need (and who knew about this shortcut) wouldn't lose the ability to
save with any extension, and it shouldn't make life more difficult
for the novices at all.
Richard Schreyer
That would work. Alternatively, or perhaps in addtion, the dialog
box that tells the user "You can't save using that extension" should
have a "I know what I'm doing G*d d*mn it! Use the f***ing extension
I specified" button (pardon the attempt at humor). This button might
be more diplomatically labeled "Save as specified" or something.
Neal