Re: [ft] Carbon-free fonts support for Mac OS X 10.5 (Leopard) compatibility

[George Williams]

On Mon, 2007-12-10 at 07:17, address@hidden wrote:
> This issue may NOT be regression, it is NEW problem
> occurs since new fonts bundled to Mac OS X 10.3.
> 
> TimesLTMM and HelvLTMM have "POST" resource to store
> Adobe Type1 PS font in resource fork, but the resources
> are fragmented.
I don't think that is new... As I recall the pfb file is divided into
several segments (initial ASCII, middle binary, final ASCII) each of
which is chopped up into 0x800 byte chunks which are each stored in its
own POST resource.

I assumed this was because 128K macs didn't have much memory, and these
fragments had to be small enough to be dealt with easily. Now-a-days
it's a pain in the neck, of course.