• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Mac OS X 10.1 File Name Extension Guidelines
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mac OS X 10.1 File Name Extension Guidelines


  • Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
  • From: Richard Schreyer <email@hidden>
  • Date: Fri, 7 Sep 2001 13:03:59 -0700

Well, I guess I'll be the first to comment on this.

Overall, these rules make sense. Especially the part about ensuring that an extension would never be hidden if that would make the file appear to be a different type. It looks like it will work, on one condition:

That file extensions exist for compatibility with other platforms only, and that Mac OS X does not use the filename extension in determining what kind of file it is. Of course, right now it appears that this is sadly not the case.

Even just setting type/creators on a per-user basis would be good enough. Obviously, the HFS space reserved for types/creators couldn't be used for per-user settings, but I really don't care where it is actually put, as long as it is put somewhere.

Are type/creators set per-user in 10.1, or if not, do we have any hope of a filetyping system that does not require the existence of filename extensions in the future?

Personally, I would love to see the hierarchical system that some have talked about here: image/jpeg/com.apple.Preview, text/html/com.barebones.BBEdit

In the meantime, I guess I had better start looking at what changes to my code this will require.

Richard Schreyer


  • Follow-Ups:
    • Re: Mac OS X 10.1 File Name Extension Guidelines
      • From: rsharp <email@hidden>
References: 
 >Mac OS X 10.1 File Name Extension Guidelines (From: John Geleynse <email@hidden>)

  • Prev by Date: Initialization of doubles
  • Next by Date: Re: Memory fragmentation
  • Previous by thread: Mac OS X 10.1 File Name Extension Guidelines
  • Next by thread: Re: Mac OS X 10.1 File Name Extension Guidelines
  • Index(es):
    • Date
    • Thread