[Prev][Next][Index][Thread]
Re: Resource -> Data fork help
>>>>> "Scott" == Scott Shuchart <shuchart@fas.harvard.edu> writes:
In article <4i8din$7k4@decaxp.harvard.edu> shuchart@fas.harvard.edu (Scott Shuchart) writes:
Scott> Wow. I've finally found a Mac --> PC cross-platform
Scott> problem Executor can't seem to help me with, so here's an
Scott> appeal for a (preferrably freeware) solution to a small
Scott> problem.
Scott> THE PROBLEM: I need to convert a Mac TrueType font to a
Scott> Windows TrueType font. I have a DOS program which does
Scott> this. Mac TT fonts are stored in resource forks. If I
Scott> take the Mac font and copy it to a FAT volume in Executor,
Scott> I get a 0-byte data fork-file (fontname, we'll call it),
Scott> and a good-sized %fontname file (~400k, say). The problem
Scott> is that the DOS program can't find the font info. in this
Scott> file (usually it can detect what kind of info. is in a
Scott> file), I think because the %fontname file has, in addition
Scott> to the resources, the finder information. I need a way of
Scott> getting JUST the resource fork, nothing else, into a DOS
Scott> file.
When you save a file to a non-HFS filesystem, Executor uses
AppleDouble, which stores the data fork in one file and all the rest
of the file information (including a table of contents) in a separate
file. We have deliberately set things up so that the resource fork
will always begin at byte offset 512 in the %file.
Scott> Ideas? Thanks. Please e-mail suggestions, files to look
Scott> for on Info-MAC, etc.
As long as the AppleDouble files you're dealing with were created by
Executor, you only need to remove the first 512 bytes to get the
resource fork. If you want a general solution that will work with
non-Executor created AppleDouble files, then you'll need to parse the
table of contents yourself, something I can help you with, but I'd
guess you don't need to do that.
Scott> Scott Shuchart shuchart@fas.harvard.edu
--Cliff
ctm@ardi.com
References: