Re: LilyPond 1.5.67 -- almost 1.6!

2002-07-14 Thread Rune Zedeler
Han-Wen wrote: > both fixed in CVS. Thanks for the report. Ok. The 2nd example still looks ugly, though. In this ex, 1st beam differs from 3rd and 4th even though they should be identical (consists same notes). \score { \context PianoStaff \notes \transpose c'' < \context Staff = up

Re: LilyPond 1.5.67 -- almost 1.6!

2002-07-14 Thread Han-Wen
[EMAIL PROTECTED] writes: > Han-Wen wrote: > > > Handling of knee beaming was added to CVS today. > > eh... > Lets take two quick examples... (to be compiled seperately) :-) > The first one gets different beams on the same construct. > The second one fails with > warning: Programming error: boun

Re: LilyPond 1.5.67 -- almost 1.6!

2002-07-14 Thread Rune Zedeler
Han-Wen wrote: > Handling of knee beaming was added to CVS today. eh... Lets take two quick examples... (to be compiled seperately) :-) The first one gets different beams on the same construct. The second one fails with warning: Programming error: bounds of this piece aren't breakable. and an un

Re: part combiner questions

2002-07-14 Thread Jan Nieuwenhuizen
Carter Brey <[EMAIL PROTECTED]> writes: [cc: devel list] > Yes, it would be great if texts could avoid any staff grobs by > default. I experimented with two kinds of padding, as you can see. Han-Wen and I discussed this a bit; what would needed to be done is to make a staff-text-engraver, that m