lilypond-auto
[Top][All Lists]
Advanced

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

[Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions


From: lilypond
Subject: [Lilypond-auto] Issue 3710 in lilypond: NR 4.4.1 collisions
Date: Sat, 07 Dec 2013 18:34:43 +0000

Status: Accepted
Owner: ----
Labels: Type-Documentation

New issue 3710 by address@hidden: NR 4.4.1 collisions
http://code.google.com/p/lilypond/issues/detail?id=3710

Report: http://lists.gnu.org/archive/html/bug-lilypond/2013-12/msg00042.html

Compare the two images here, under "In the following image, horizontal lines indicate the positions of these reference points":
http://lilypond.org/doc/v2.16/Documentation/notation/flexible-vertical-spacing-within-systems#within_002dsystem-spacing-properties

http://lilypond.org/doc/v2.17/Documentation/notation/flexible-vertical-spacing-within-systems#within_002dsystem-spacing-properties

in v2.17 there are collisions.

Comment by Phil:

I think this is because of some of Keith's changes to staff padding: in 2.17.27 - I think the old version only worked because markup was really too far from the stave. This is easily fixed in this example with this change:

labelContext =
#(define-music-function
(parser location context)
(string?)
#{ s1*0^\markup { \null \raise #2 \typewriter #context } #})


--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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