> 2. Apple's decision to deprecate resource forks happened when?
> Pre-2003? It's 2006 now and resource forks are still in wide use. One
> good example of indisposable resource fork use is Macintosh
> PostScript font files, of which I maintain a development repository
> of tens of thousands. If the resource fork is stripped from a Mac
> Postscript font, the file is useless.
OK, so now I'm curious. I know PostScript fonts are shipped with lots
of OSes, Windows and Unix included, and no resource forks are involved.
Are there concrete advantages, besides userbase momentum, to the Mac
variant format which requires a resource fork? Can a Mac PS font not
be round-trip converted to a .pfa or .pfb without loss of information?
If so, I'd suggest using .pfa in your repository, and convert to Mac PS
as needed, by some sort of build script.
It just seems odd to me that people would want to design fonts that
could _only_ be used on a Mac. You'd think they would prefer a format
that would allow them to sell their font to Windows users too.
Received on Wed Sep 20 03:24:40 2006