Oops! Another Revised Patch for MacOS font problems

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Oops! Another Revised Patch for MacOS font problems

Matthias Neeracher
Just my luck! My previous path used an API that changed in 2.5.28 so  
lilypond would segfault. This one should finally work.

Here is a revised patch, based on the discussion we've had the last  
couple of days. Basically, it does the same thing as the fontforge  
based patch, but now is based on fondu.

Although fondu is platform independent, my patch is preprocessor  
bracketed to only compile on MacOS X, because some of the  
functionality used in this version, notably glob(), may not be  
available on other platforms.

Matthias


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel

another-fondu.patch (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Oops! Another Revised Patch for MacOS font problems

Han-Wen Nienhuys
Matthias Neeracher wrote:

> Just my luck! My previous path used an API that changed in 2.5.28 so  
> lilypond would segfault. This one should finally work.
>
> Here is a revised patch, based on the discussion we've had the last  
> couple of days. Basically, it does the same thing as the fontforge  
> based patch, but now is based on fondu.
>
> Although fondu is platform independent, my patch is preprocessor  
> bracketed to only compile on MacOS X, because some of the  functionality
> used in this version, notably glob(), may not be  available on other
> platforms.
>

Hi,

This type of code (interfacing with the system, not performance
critical) should be done in Scheme entirely. Can you do that?


--
  Han-Wen Nienhuys - [hidden email] - http://www.xs4all.nl/~hanwen


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel