bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 135 in project lilypond


From: Mats Bengtsson
Subject: Re: Issue 135 in project lilypond
Date: Mon, 22 Jan 2007 22:16:56 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20061113 Debian/1.7.8-1sarge8

Han-Wen Nienhuys wrote:

Joe Neeman escreveu:
On 1/22/07, address@hidden <address@hidden>
wrote:
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135

Comment #3 by hanwenn:
To make object partake in vertical skylining, it needs
outside-staff-priority.
This is not the problem: TextScripts have outside-staff-priority by
default. The problem is that the proposed workaround breaks
outside-staff positioning because the outside-staff positioning
algorithm thinks the TextScript has empty X-extent so it won't collide
with anything. In other words, there isn't a way to make a TextScript
over a spacer rest take up no space without causing other side-effects
(or at least, no one has thought of a way yet).

no, it actually is the problem. If you add the propery outside-staff-priority
to MultiMeasureRestText, R1^\markup{ bla } actually does the right thing.
Please read again the text I wrote, which is quoted in the
bug report. The typesetting problem I want to solve is to
have a text script (or whatever text ... grob) that is left aligned
with the beginning of the measure, when there is a multimeasure
rest. Since there is no really good way to obtain this with
LilyPond today, you should see the bug report as a feature
request.

  /Mats





reply via email to

[Prev in Thread] Current Thread [Next in Thread]