[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Six problems
Re: Six problems
Fri, 10 Jun 2005 15:55:21 -0400 (EDT)
On Thu, 9 Jun 2005, Erik Sandberg wrote:
> > 1. In the first measure the dynamics "sfz" and "pp" for the first
> > two notes overlap.
> known bug
> > 2. The "sfz" and "pp" strings aren't aligned vertically. That is,
> > the baseline for the "sfz" is lower than the baseline for the
> > "pp". Is this a problem in the original font definition?
> it's standard behaviour; vertical position of text strings is taken relative
> the staff.
That doesn't explain it. If the text strings had their baselines at a
fixed position relative to the staff then the letters would align. Do you
mean instead that the bounding boxes are placed at a fixed distance from
> > 3. In the second measure the word "crescendo" overlaps with the
> > hairpin crescendo marking.
> known bug; text scripts generally collide with most other things.
Is there any way to make things expand so that there is room for the text?
The same approach might help answer question 1 as well.
> > 4. At the key change in the third measure a B-natural symbol is
> > printed followed immediately by a B-flat symbol. Printing
> > redundant symbols like that looks silly; there's no reason
> > to cancel the B-flat from the old key signature when the new
> > signature includes a B-flat.
> See the section about key signatures for a workaround.
I have read that section (section 5.3.2 in the Lilypond 2.4.6 manual).
It's very short and contains nothing about any workarounds. It implies
that KeyCancellation and KeySignature objects have something to do with
this, and the new-accidentals and old-accidentals properties seem to be
relevant. But I can't figure out how to get at these things. The
following \applyoutput routine:
#(define (show-stuff grob origin current)
doesn't even show anything for the key change! (Or for the notes, for
that matter.) What am I missing?