Re: Textual tempo markers in adjacent bars are stacked

[Xavier Scheuer]

Hi,

2010/1/7 Reinhold Kainhofer <address@hidden>:

> PS: I'm forwarding this to bug-lilypond, so that it gets at least recorded for
> the future.

There are already (at least) 2 open issues about this:

684: Enhancement: MetronomeMark should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
712: alignment of multiple \tempo marks over `church rests'
http://code.google.com/p/lilypond/issues/detail?id=712

Several people have already complained about this (including me, actually I
"groused" about it, which wasn't the best way to move forward  :p ).
The thread about this can be found in the archives of this mailing-list
(gnu.org archives seems unavailable now but subject was "Tempo mark alignment"
and date was 23/05/2009).
Nabble archive:
http://old.nabble.com/Tempo-mark-alignment-ts23679524.html#a23773635

As a workaroud I use this user-defined "TempoMark" command for textual
tempo marks:

tempoMark = #(define-music-function (parser location markp) (string?)
#{
  \once \override Score.RehearsalMark #'self-alignment-X = #LEFT
  \once \override Score.RehearsalMark #'break-align-symbols =
#'(time-signature key-signature)
  \once \override Staff.TimeSignature #'break-align-anchor-alignment = #LEFT
  \once \override Score.RehearsalMark #'font-size = #1
  \mark \markup { \bold $markp }
#})

There was a debate about issues priority classification, someone (Werner?)
spoke about an "annoying" tag, which seems now to be "Priority-High".
I hope these issues are "eligible" to this higher priority.

Cheers,
Xavier

PS: +1  Me too!  ;-D

-- 
Xavier Scheuer <address@hidden>