Re: [Devel] Re: Another approach to mac fonts...

[Dan Williams]

Ok, correct you are.  My first read of your comment was more general, 
hence my response.  However, I believe my comment here still stands:  
why should we not make this code available to other platforms?  I think 
it would be a huge benefit.  Furthermore, why shouldn't we simply 
compile ftmac.c for _all_ platforms, include your code here for walking 
the "resource" fork for non-mac platforms, otherwise compile with the 
code that's already in ftmac.c?

Dan

On Monday, May 19, 2003, at 09:19  AM, George Williams wrote:

> > Actually, the code is needed :)  This should allow other platforms 
> > to, as you say, open up Mac .dfont files.  I'm not so sure it should 
> > be special cased for Mac only; it probably should be made available 
> > to all platforms, such that if you pass in a font file with a .dfont 
> > extension, now Freetype can read it.  So you could conceivable copy a 
> > Mac .dfont file to a PC or other Unix box and use it with Freetype.  
> > Hence its utility.
> No, you misunderstand.
>
> The code protected by #ifdef FT_MACINTOSH within the #ifndef 
> FT_MACINTOSH has the sole function of opening the resource fork of a 
> file on Mac OS/X. The code which handles dfont files works on the data 
> fork and is not controled by the #ifdef FT_MACINTOSH, it will already 
> have been executed.
>
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel