RE: [Freetype] Question on MacOS X

[Leonard Rosenthol]

At 03:21 PM 11/30/2001 -0800, Wenlin Institute wrote:
> At 7:09 PM -0500 11/28/01, Leonard Rosenthol wrote:
> >         Yes.  It supports all of the formats supported by Mac OS X - or 
> > at least it is supposed to ;).
>
> It doesn't seem to work with .dfont files.

        Yeah, it looks like all my changes are still on my local disk 
:(.  I PROMISE to check them in this weekend!!


> On the bright side, FT 2.0.5 does work with Mac "suitcase" fonts under OS 
> 9 and OS X.

        It should ;).


> For OS X, to use Unix-style pathnames, it's necessary to change 
> file_spec_from_path() in ftmac.c to something like this:

        A reasonable recommendation, but as noted in the temporarily 
defunct TN 2034, paths are faster - I'll stay with paths except where 
necessary to call specific API routines.


> There are some unused variables in ftmac.c (reported by GCC)
> A compiler warning is given for size_p being possibly uninitialized in 
> read_lwfn(). It's not obvious (to me) whether it would always be 
> initialized before use even if a file were corrupted. It would be safest 
> to initialize size_p = NULL, and check if (size_p != NULL) before writing 
> to it.

        I'll check these...


> "#define macintosh" causes a conflict with the precompiled header for 
> CoreServices.framework. This can be solved by defining a unique name such 
> as FT_MACINTOSH, to replace "macintosh" in ftmac.c and ftobjs.c.

        Yup, I'll change that - thanks!!


Leonard