Issue 135 in project lilypond

[codesite-noreply]

Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135

Comment #2 by gpermus:
I haven't seen a response to Mats' email (on Jan 3, 2007) on the subject, so I'm
adding it here and marking the bug unresolved.


Mats wrote:
Can we turn this into a question: What's the best way to specify that a
TextScript attached to a spacer note does not occupy any horizontal space
(meaning that the bar lines are placed at the same place as if you didn't have
the text)?
The best I can come up with is
\override TextScript #'X-extent = #'(0 . 0)

However, this means that it isn't taken into account in the new fancy
collision avoidance.

A common situation where this is useful is when you have a tempo change
at a bar line and the instrumental part begins with a multi measure rest.
The following example illustrates four different solutions. The last one
is the only one that gives a really nice output, but I find it a bit embarrasing
for LilyPond that you can't get this layout without using such an ugly hack.

\version "2.10.0"
\relative c''' {
c1
% Nice handling of the text but wrong rest.
r1^\markup{"Andante molto"}
c1
% The text affects the bar lines
<< R1 s1^\markup{"Andante molto"} >>
c1
% Better, but the collision handling doesn't work
\once \override TextScript #'X-extent = #'(0 . 0)
<< R1 s1^\markup{"Andante molto"} >>
c1
% Desired layout, but ugly tweaks in the input:
<< R1 \once \override Rest #'transparent = ##t r1^\markup{"Andante 
molto"} >>
c1
}


Issue attribute updates:
        Status: Started

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings