• 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 (John Geleynse)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mac OS X 10.1 File Name Extension Guidelines (John Geleynse)


  • Subject: Re: Mac OS X 10.1 File Name Extension Guidelines (John Geleynse)
  • From: Jonathan Hendry <email@hidden>
  • Date: Sun, 9 Sep 2001 14:19:41 -0500

On Sunday, September 9, 2001, at 01:16 , Neal A. Crocker wrote:
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).

Presumably, the developers of BBEdit would make BBEdit behave in a useful
way, rather than the default. After all, this _is_ a typical use
of a text editor, especially among technical folks.


References: 
 >Re: Mac OS X 10.1 File Name Extension Guidelines (John Geleynse) (From: "Neal A. Crocker" <email@hidden>)

  • Prev by Date: Re: Formatters and TextViews
  • Next by Date: Validity of Localizable.strings file
  • Previous by thread: Re: Mac OS X 10.1 File Name Extension Guidelines (solution?)
  • Next by thread: Re: Mac OS X 10.1 File Name Extension Guidelines (John Geleynse)
  • Index(es):
    • Date
    • Thread