Re: Mac OS X 10.1 File Name Extension Guidelines
Re: Mac OS X 10.1 File Name Extension Guidelines
- Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
- From: j o a r <email@hidden>
- Date: Tue, 11 Sep 2001 00:14:41 -0700
On Monday, September 10, 2001, at 02:21 , Ondra Cada wrote:
A particular example might be .tar.gz. It is more than just .gz; it
brings
not just the information "this can be decoded by gzip" as any other .gz
file,
but *also* it informs "it can be decoded by gnutar -z".
Why not be even more explicit while we're at it:
MyDocument.html.txt.tar.gz
Woho, types through file name extensions! The type is longer then the
file name! Don't forget to tell your mom that she can use long file
names, up to 255 characters, _provided_ that she uses the right file
type. Otherwise she'll need to remember to truncate the file name by the
length of the file name extension - got that mom?
On the other hand, if we* _accept_ that it's OK to use file system meta
data, we could easily add any number of extra tags - besides or instead
of T/C - for hierarchial types or whatever we think is reasonable. Why
not have a "backed up" flag as well? Or perhaps shoot for a general
purpose extensible xml field for whatever we might think of later?
*) hopefully "we" could be some standards organization with members from
the rest of the industry.
Another example is the subtyping of backup files (like .rtf and .rtf~,
or
.nib and .nib~, or, actually, .whatever and .whatever~).
What's wrong with:
MyDocument
MyDocument backup file
The backup file isn't really of a different _type_, now is it?
BTW. What do you say we take this thread to macosx-talk instead Ondra?
Parts of it is there already.
Regards,
j o a r