On Sun, 14 Jan 2007 00:00:42 +0100 (CET) Werner LEMBERG <[EMAIL PROTECTED]> wrote: >> and please review attached patch for documents. > >Committed (with slight modifications). Please check.
I've checked, your modification improves well, thank you. >> I was going to add new function FT_GetFileRef_From_Mac_ATSName(). >> If adding new function in release-candidate phase is acceptable, >> please let me know. I will do that within 24 hours. > >This is fine for me, if it helps to resolve compatibility issues with >older FreeType versions. No, FT_GetFileRef_From_Mac_ATSName() won't help the behaviour compatibility issues with older FreeType2 versions, at all. It is a public function for (near-)future Mac OS X missing the functions and data-types that have been announced as deprecated. On such system missing deprecated Carbon function & data-types, I cannot provide behaviour-compatible function (of FT_GetFile_xxx), only I can do is providing a function with similar behaviour (FT_GetFileRef_xxx) to help the migration. If adding new symbol in 2.3.0 -> 2.3.1 is better than that in 2.2.1 -> 2.3.0, I will postpone. # IMHO, FT_GetFileRef_xxx() will be deprecated in long-future. # The incompatible behaviour issues will continue until Carbon- # free Mac font support (that I'm working but long work). # The root of problem was introduced between 2.0.5 and 2.0.6. # http://cvs.savannah.gnu.org/viewcvs/freetype/freetype2/src/base/ftmac.c?r1=1.15&r2=1.16 Regards, mpsuzuki _______________________________________________ Freetype mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype
