• 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: Reading resource forks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reading resource forks


  • Subject: Re: Reading resource forks
  • From: Jonathan Levi MD <email@hidden>
  • Date: Sun, 7 Dec 2003 16:27:31 -0500

At 9:38 PM -0800 12/5/03, Graff <email@hidden> wrote:
Well, technically under HFS+ you can access a resource fork for a file with the name "filename" by using:
filename/..namedfork/rsrc
the data fork would be at:
filename/..namedfork/data

Very nice. I was able to use this to copy a resource fork (not a single resource) to data using "do shell script" and cat.

On Sat, 06 Dec 2003 16:48:59 -0500, Graff <email@hidden> wrote:
And, yeah, it's just the raw data. I figured he might have a way of
parsing it out. I know it can be done, but I don't know the format
exactly and couldn't be bothered to figure it out! :-)

I seem to remember that the original writer was interested in FOND resources. One way to extract an individual resource would be to use the DeRez application (either in MPW -- you can put any MPW commands into an AppleScript -- or in /Developer/Tools.) I was hoping to format the data using the MPW version of derez in conjunction with the Fonts.r Rez Includes file, but for some reason derez wouldn't utilize this file: it kept spitting out the (minimally) formatted hex version of my FOND resources. You might have to use Fonts.r to analyze your FOND by hand (ugh!) Maybe Chris has an idea why derez wouldn't apply Fonts.r.

Jonathan
_______________________________________________
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.

  • Follow-Ups:
    • Re: Reading resource forks
      • From: Christopher Nebel <email@hidden>
  • Prev by Date: Re: Urgent Quark scripting problem
  • Next by Date: Re: Drive-by sig files
  • Previous by thread: RE: Reading resource forks
  • Next by thread: Re: Reading resource forks
  • Index(es):
    • Date
    • Thread