lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: a new lilypond build failure


From: Thomas Bushnell BSG
Subject: Re: a new lilypond build failure
Date: Sun, 23 Oct 2005 15:14:12 -0700
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)

Han-Wen Nienhuys <address@hidden> writes:

> Thomas Bushnell BSG wrote:
>>>    ec-fonts-mftraced
>> Wait, you mean showed up and is now gone?  What's it for anymore?
>> Why
>> did we ever have it? :)
>
> It was for Lily 2.4, which supported Latin1 encoding and fonts, but not 
> unicode.

I see, so now that Unicode is supported, it's not relevant.  

Does that mean that nobody will ever want ec-fonts-mftraced anymore?
(If so, I can drop the Debian package itself too.)

> No, Lily used to be linked against libkpathsea to locate TeX fonts, so 
> it could determine dimensions of texts. This is no longer necessary with 
> Pango. LilyPond now outputs PS directly, which you can include into TeX 
> with \includegraphics{}. Supporting TeX (with all of its crappy support 
> tools) was one of the major headaches of deploying LilyPond, and I'm 
> very glad it's gone.
>
> If the manual suggests .tex is the default, then that would be a bug in 
> the manual then; can you pinpoint it more exactly?

Let me check to make sure I have the right version of the manual. :)
I'll get back to you on that.

Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]