Re: chord name collide with staff

2013-02-16 Thread Colin Hall
m...@mikesolomon.org writes: On 4 févr. 2013, at 08:00, m...@mikesolomon.org wrote: On 4 févr. 2013, at 01:00, MING TSANG tsan...@rogers.com wrote: Hi fellow lily users: I have a chord name and a melody staff. The chord name collide with the melody staff on 2nd 3rd systems

Re: chord name collide with staff

2013-02-06 Thread m...@mikesolomon.org
On 6 févr. 2013, at 00:17, David Kastrup d...@gnu.org wrote: m...@mikesolomon.org m...@mikesolomon.org writes: Find #3 was wrong. There should have been no suicides in this precise case. LilyPond just does not know how to do spacing on empty skylines. This makes sense, as it is difficult

Re: chord name collide with staff

2013-02-06 Thread David Kastrup
m...@mikesolomon.org m...@mikesolomon.org writes: On 6 févr. 2013, at 00:17, David Kastrup d...@gnu.org wrote: m...@mikesolomon.org m...@mikesolomon.org writes: Find #3 was wrong. There should have been no suicides in this precise case. LilyPond just does not know how to do spacing on

Re: chord name collide with staff

2013-02-05 Thread m...@mikesolomon.org
On 4 févr. 2013, at 08:00, m...@mikesolomon.org wrote: On 4 févr. 2013, at 01:00, MING TSANG tsan...@rogers.com wrote: Hi fellow lily users: I have a chord name and a melody staff. The chord name collide with the melody staff on 2nd 3rd systems in v2.17.11, but in v2.16.2 they are ok

Re: chord name collide with staff

2013-02-05 Thread David Kastrup
m...@mikesolomon.org m...@mikesolomon.org writes: On 4 févr. 2013, at 08:00, m...@mikesolomon.org wrote: On 4 févr. 2013, at 01:00, MING TSANG tsan...@rogers.com wrote: Hi fellow lily users: I have a chord name and a melody staff. The chord name collide with the melody staff on 2nd

Re: chord name collide with staff

2013-02-05 Thread David Kastrup
m...@mikesolomon.org m...@mikesolomon.org writes: Doing some preliminary tests in page layout problem to see why the spacing is so cramped - this is gonna be a tough one to solve... I think you are on the wrong track here. If this was merely a problem of cramped spacing, all systems should be

Re: chord name collide with staff

2013-02-05 Thread m...@mikesolomon.org
On 5 févr. 2013, at 21:32, m...@mikesolomon.org m...@mikesolomon.org wrote: So, find #1... If you replace all of the empty strings in the fourth lyric group by: \repeat unfold 33 \skip 1 or \repeat unfold 33 The problem goes away. So the skyline code doesn't like something about the

Re: chord name collide with staff

2013-02-05 Thread m...@mikesolomon.org
On 5 févr. 2013, at 10:16, David Kastrup d...@gnu.org wrote: m...@mikesolomon.org m...@mikesolomon.org writes: Doing some preliminary tests in page layout problem to see why the spacing is so cramped - this is gonna be a tough one to solve... I think you are on the wrong track here. If

Re: chord name collide with staff

2013-02-05 Thread m...@mikesolomon.org
On 5 févr. 2013, at 21:55, m...@mikesolomon.org wrote: On 5 févr. 2013, at 21:32, m...@mikesolomon.org m...@mikesolomon.org wrote: So, find #1... If you replace all of the empty strings in the fourth lyric group by: \repeat unfold 33 \skip 1 or \repeat unfold 33 The problem goes

Re: chord name collide with staff

2013-02-05 Thread m...@mikesolomon.org
On 5 févr. 2013, at 22:15, m...@mikesolomon.org wrote: On 5 févr. 2013, at 21:55, m...@mikesolomon.org wrote: On 5 févr. 2013, at 21:32, m...@mikesolomon.org m...@mikesolomon.org wrote: So, find #1... If you replace all of the empty strings in the fourth lyric group by: \repeat

Re: chord name collide with staff

2013-02-05 Thread David Kastrup
m...@mikesolomon.org m...@mikesolomon.org writes: Find #3 was wrong. There should have been no suicides in this precise case. LilyPond just does not know how to do spacing on empty skylines. This makes sense, as it is difficult to estimate the distance between something and nothing. So,