Hi, Mats:
See http://lists.gnu.org/archive/html/bug-lilypond/2005-10/
msg00166.html
for a related discussion.
Thanks for the link
As it turns out, I've almost solved (i.e., found hacks for) all my
\mark-related problems on my own today -- decided it was too
important (to the readability of the parts I need to generate for
next week's rehearsal and performance), and so I dug in...
My current example file is attached below, for anyone who's
interested -- once the pressure's off, and I can research the *real*
effects of these hacks, I'll put together a full report.
Cheers,
Kieren.
%%% CODE SNIPPET BEGINS
\version "2.9.9"
\paper
{
ragged-right = ##t
indent = 0
}
invMMR = { \once \override MultiMeasureRest #'transparent = ##t R1 }
\relative c'
{
\override Score.TimeSignature #'stencil = ##f
\override Score.RehearsalMark #'self-alignment-X = #-1
c4 c \mark \markup "The default X-extent leads to split notes." c c
\break
c4 c
\once \override Score.RehearsalMark #'X-extent = #'(0 . 0)
\mark \markup "Setting X-extent = #'(0 . 0) avoids the split."
c c \break
\mark \markup "By default, \mark fills one MultiMeasureRest."
R1*4 \break
%\once \override Score.RehearsalMark #'minimum-X-extent = #'(0 . 25)
\mark \markup "Here, we hide a MMR to hack the width of a non-rest
measure."
<< { \invMMR } \\ { \oneVoice c4 c c c } >> \break
\once \override Score.RehearsalMark #'X-extent = #'(0 . 0)
\override MultiMeasureRest #'minimum-length = #21
\mark \markup "Choose the MMR min-length appropriately." R1*4
\break
\once \override Score.RehearsalMark #'X-extent = #'(0 . 0)
\override MultiMeasureRest #'minimum-length = #10
\mark \markup "Choose the MMR min-length appropriately." R1*4
\break
}%%% CODE SNIPPET ENDS
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
