On Wed, Nov 08, 2006 at 06:54:32PM -0800, Graham Percival wrote: > Cameron Horsburgh wrote: > >On Wed, Oct 25, 2006 at 11:03:42PM -0700, Graham Percival wrote: > >>Hi Cameron and Marcus, > >> > >>Both of you reported this bug. Could you check if it has anything to do > >>with #'break-align-symbol ? I'm thinking of something like the > >>examples in the doc section on Text marks. > > > >I've had a bit if a fiddle with different settings for > >#'break-align-symbol. The correct (IMO) result comes when I set it to > >#'clef, which surprises me a little, because it centres over the bar > >line (cf. the example in the section on text marks). > > > >It still isn't perfect -- the mark over the double bar line is aligned > >to the first of the two bar lines, which means it's slightly off to the > >left. Currently it seems to align over the right line, so in this case > >the fix is no worse than the current situation. > > > I'm not really certain where that leaves this bug report. Are you > proposing that > \override Score.RehearsalMark #'break-align-symbol = #'clef > should be the default? Do you have any complaints with #'clef, other > than bug #97 ? >
I have fewer complaints with #'clef than anything other option. I tried Mats' example in 2.9.27 and marks seemed to be little offset to the left, but it's a minor nitpick and it certainly fixes the problem of collisions with key and time signatures. I was worried about what would happen if there was a rehearsal mark at the beginning of the piece, but that doesn't seem to move at all. So to answer your question in a roundabout way, if #'clef doesn't become default I will be adding it to all of my scores from now on! -- ============================================= Cameron Horsburgh ============================================= _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
