If it fixes it at all, it would do so upon a recompile of Lilypond
*after* installing the new mftrace. But it looks like that is what
you've done, and still have problems. <sigh> You saved me the trouble
of trying to build 2.5.14 when I get home. The last problem-free
version for me was 2.5.10.
--d
David Bobroff wrote:
Well, on your advice earlier I upgraded to mftrace 1.1.5 when you told
me I needed potrace or autotrace. So, no, I don't think mftrace 1.1.5
fixes this.
On Mon, 2005-03-07 at 17:10 -0800, Daniel Johnson wrote:
I've heard that mftrace-1.1.5 may fix this. Is this correct?
David Bobroff wrote:
I've got version 2.5.14 up and running (with the exception of the emacs
mode issue I posted to the user list) and I found something odd. In
this example:
\version "2.5.14"
\score{
\relative c{
\time 3/4
\set Score.skipBars = ##t
R2.*2
}
}
I'm getting an inappropriate font for the time signature as well as over
the multimeasure rest. I'm getting a rather large sans serif font
rather than the \number font I would normally expect.
-David
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
