• 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: Graff <email@hidden>
  • Date: Sun, 07 Dec 2003 20:17:27 -0500

Ahh, nice. I somehow forgot about DeRez or I would have put it in as part of my hint. Definitely better than parsing out the raw resource fork manually.

- Ken

On Dec 7, 2003, at 6:36 PM, Christopher Nebel wrote:

On Dec 7, 2003, at 1:27 PM, Jonathan Levi MD wrote:

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.

Well, you do have to tell it to do so:

DeRez -only FOND myfile /System/Library/Frameworks/Carbon.framework/Headers/Carbon.r
_______________________________________________
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.

References: 
 >Re: Reading resource forks (From: Jonathan Levi MD <email@hidden>)
 >Re: Reading resource forks (From: Christopher Nebel <email@hidden>)

  • Prev by Date: Re: Drive-by sig files
  • Next by Date: RE: Reading resource forks
  • Previous by thread: Re: Reading resource forks
  • Next by thread: RE: Reading resource forks
  • Index(es):
    • Date
    • Thread