• 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: Ondra Cada <email@hidden>
  • Date: Tue, 11 Sep 2001 15:02:48 +0200

Andreas,

>>>>>> Andreas Monitzer (AM) wrote at Tue, 11 Sep 2001 14:16:45 +0200:
AM> >Well, yes and no. In majority of cases, definitely yes. Though, there
AM> >are not that spare cases when the type (whatever way expressed) _adds_
AM> >an important information.
AM> >
AM> >There is an application which uses a simple dictionaries, which are
AM> >stored as plain ASCII files. No content analysis can distinguish it from
AM> >a normal plaintext.
AM> >
AM> >Now, of course it is important that the fact that _is_ a text should be
AM> >known, and those files can be easily and without problems opened in any
AM> >text
AM> >editor (TextEdit, BBEdit, vi, emacs, you name it...).
AM> >
AM> >OTOH, the information that those are _primarily_ files of
AM> >SomeDictionaryApp
AM> >is quite important as well, and (as opposite to the default app binding)
AM> >it is independent of user.
AM>
AM> Maybe you didn't notice it, but you just advertised the concept of
AM> creators :-)

Not only I did not noticed it; i _do know_ that it's an utter nonsense.

I am sorry you still haven't understand the difference between types,
creators, and app/document bindings, but I just don't want to explain them
for the umpteenth time. I would recommend you to study the archives.

Hint1: there can be more apps which interpret the docs as dictionaries (say,
SomeDictionaryApp, SomeDictionaryAppCmpanion, and
SomeDictionaryAppCompetition), not just one.

Hint2: user might want to select some text editor as the default app binding
for these files, be they primarily dictionaries or not.

Result: we are speaking of _types_ here. They should be made more flexible
(by adding the contents analysis perhaps, by allowing typesets, by supporting
hierarchy...). MacOS creator code OTOH is a legacy PITA which should vanish
ASAP (to be replaced by some more flexible way of default app binding).
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc


References: 
 >Re: Mac OS X 10.1 File Name Extension Guidelines (From: Andreas Monitzer <email@hidden>)

  • Prev by Date: Re: Cocoa Open GL help
  • Next by Date: Re: Cocoa Open GL help
  • Previous by thread: Re: 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