Re: Scripts lose their extensions in OSX 10.3.3
Re: Scripts lose their extensions in OSX 10.3.3
- Subject: Re: Scripts lose their extensions in OSX 10.3.3
- From: Walter Ian Kaye <email@hidden>
- Date: Fri, 14 May 2004 14:07:00 -0700
At 02:14p -0400 05/14/2004, Steven Valenti didst inscribe upon an
electronic papyrus:
We use a Win2000 server for storage. I recently been upgrading macs
from 10.2.8 to 10.3.3. I notice that all my script library icons are
showing up as Unix Executable Files in this new operating system and I
can't load any of them without the message that says it doesn't belong
to applescript or open them in an editor unless I type .scpt after it.
Does anyone know why the extensions are not recognized by 10.3.3?
I can't speak to the difference between Jaguar and Panther, but I can
tell you that data fork-based scripts (which Script Editor 2.0
generates) require .scpt extension. If you do not want that
limitation, then resave them from either Script Editor 1.9 or Script
Debugger.
-W
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.