Re: various problems using lilypond 1.3.111

[Michael Vanier]

> Cc: address@hidden
> Content-Type: text/plain; charset=us-ascii
> Date: Mon, 27 Nov 2000 12:12:09 +0100
> From: Mats Bengtsson <address@hidden>
> 
> > > > 2) I've been unable to figure out a way to specify a bass clef for any 
> > > > .ly
> > > >    files.  The old system doesn't work, and I can't get any of the test
> > > >    files to give me a bass clef either (e.g. inputs/test/clefs.ly).  
> > > > Side
> > > >    note: the test files don't have a single standard for this either, 
> > > > with
> > > >    some using
> > > > 
> > > >        \clef "bass";
> > > > 
> > > >    and others
> > > > 
> > > >        \clef bass;
> > > > 
> > > >    What is the correct way to do this?  The documentation barely 
> > > > mentions
> > > >    this. 
> > > > 
> > > >    BTW many of the test files generate fatal errors when run through
> > > >    ly2dvi.  I can supply a list if you're interested.
> > > 
> > > Please read the FAQ on messed up symbols at
> > > http://appel.lilypond.org/wiki/index.php?PostProcessing
> > 
> > I did, and I re-installed the fonts, but I still can't get a bass clef.
> > The notes that should be in the bass clef are shifted down so they appear
> > in a line with a treble clef and a lot of ledger lines at the bottom.
> 
> You are right, this is a bug in 1.3.111, as is apparant from the 
> examples on the Lilypond WWW page. (If you don't want to wait for 
> 1.3.112, I can tell you that 1.3.110 was fairly stable.)
> 
>     /Mats
> 
> 
> 

At the rate new releases come out, I think I can wait :-)

Thanks,

Mike