Re: Issue 1208 in lilypond: Some combination of 'staff-affinity for two Lyrics may cause unwanted vertical space

[lilypond]

Updates:
        Labels: -Type-Defect -Priority-Critical Type-Enhancement Priority-High

Comment #5 on issue 1208 by Carl.D.Sorensen: Some combination  
of 'staff-affinity for two Lyrics may cause unwanted vertical space
http://code.google.com/p/lilypond/issues/detail?id=1208

I think you misunderstand the meaning of CENTER when it is applied to  
lyrics.

CENTER does *not* mean "center the lyrics between the staffs".

CENTER means "look up to the next line -- if it's a staff, use  
inter-staff-spacing, if it's
a non-staff (e.g. lyrics) use inter-loose-line-spacing.  Then look down to  
the next line -- if it's
a staff, use inter-staff-spacing, if it's a non-staff use  
inter-loose-line-spacing".

So if you have two lyrics with CENTER affinity, they should *not* be  
aligned, in general.  They should be separated by  
inter-loose-line-spacing.  If you want them to be aligned, then set the  
minimum-spacing entry of inter-loose-line-spacing to be 0.

Did you try running the code I included last time?  Here's the output of  
the code, which uses CENTER-CENTER.

At any rate, this is *not* a regression.  It is not a change that broke  
intended behavior.  So the priority should not be critical.  I also don't  
think it's a defect.  I think the code works just as advertised and  
intended.

If there is only one lyric line, and the staff spacing has not been  
adjusted, the lyrics should be in the same location regardless of  
staff-affinity.  That's what the current code does, and why the UP-CENTER  
example works the way it does.  For each measure, there is only one lyrics  
active.

I think that this may be more of a usage issue than a bug.  Perhaps if you  
posted an example of what you want to accomplish and having a hard time  
with, we could provide some help.

I'd still prefer the Invalid tag, but I'm willing to have some non-critical  
issue on this.


Attachments:
        lyric-center.png  12.3 KB